none
.NET Web Service ( ASMX Web Service) RRS feed

  • Question

  •  here is the Scenario

    This an .ASMX Web Service not WCF

    A .NET web Service (.ASMX)  is is installed under Web Server A
    Visual Foxpro Application is installed under 2 different Citrix Servers.

    VFP Application  is calling the  .ASMX Web Service (hosted under Web Server A).

    the .NET Web service is Authenticating a certain user to create  PDF file and save the PDF  under a directory under Citrix.

    the whole process is working OK  under one Citrix Server but not on another Citrix Server

    the Citrix Server where the error is showing  has this configuration:
       Window Server 2008 R2-64 Bit

    here is the error:

    ERROR: 1429 - OLE IDISPATCH Exception code 0 from WSDLReader:

    SDLReader: XML Parser failed at linenumber 0, lineposition 0, Reason is:

    Access denied.

    since it is working under one Citrxi Server, not sure if  the issues IIS Web Server!
    We are trying to find out what  setting(s) or Configurations  on new Citrix server is causing the error above  to show !!

    - jhhaidar@sbcglobal.net


     

    Tuesday, September 10, 2013 2:55 PM

Answers

  • <copied>

    what is the link for  Legacy .ASMX  Web Service Forum?

    <end>

    It seems that the WCF and ASMX has been combined on MSDN from what I can see. Maybe they should be separate forms.

    <copied>

    ERROR: 1429 - OLE IDISPATCH Exception code 0 from WSDLReader:

    SDLReader: XML Parser failed at linenumber 0, lineposition 0, Reason is:

    Access denied.

    <end>

    The above message for whatever user account the Web service is running under it is being denied access, because the account doesn't have rights/permissions to access the resource.

    NT AUTHORITY\NETWORK SERVICE is the ASP.NET Worker Process account. All ASP.NET applications are run by the ASP.NET Worker Process using that account, unless it is told otherwise by using account impersonation for an account that has the permissions.

    So NT AUTHORITY\NETWORK SERVICE is given the permissions (not recommended), or one uses an account and impersonates using the account that has been given the necessary rights.

    You may have to go to the Web service itself on IIS to set impersonation or look at the Application Pool and see what account it is using on IIS. 

      

    Tuesday, September 10, 2013 5:27 PM
  • Hi,

    >>what is the link for Legacy .ASMX Web Service Forum?

    This is the forums for the ASMX Web Service Forums.

    #ASMX  Web Service Forums:
    http://forums.asp.net/28.aspx/1?WCF+ASMX+and+other+Web+Services .

    >>ERROR: 1429 - OLE IDISPATCH Exception code 0 from WSDLReader: SDLReader: XML Parser failed at linenumber 0, lineposition 0, Reason is:Access denied.

    As the @darnold924 said, it seems that it is the something with the permissions.

    So please try to check the identity of the application pool. The default (network service) will not have access to control services.  To test this you can change the user to local system which has full control over the host system, however in a live environment you should create a user that has only the permissions you need.

    Best Regards,
    Amy Peng


    <THE CONTENT IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND, WHETHER EXPRESS OR IMPLIED>
    Thanks
    MSDN Community Support

    Please remember to "Mark as Answer" the responses that resolved your issue. It is a common way to recognize those who have helped you, and makes it easier for other visitors to find the resolution later.

    Wednesday, September 11, 2013 5:35 AM
    Moderator

All replies

  • <copied>

    This an .ASMX Web Service not WCF

    <end>

    When did the MSDN WCF forum become a Legacy ASP.NET Web service forum?

    Tuesday, September 10, 2013 3:04 PM
  • what is the link for  Legacy .ASMX  Web Service Forum?

    Tuesday, September 10, 2013 4:39 PM
  • <copied>

    what is the link for  Legacy .ASMX  Web Service Forum?

    <end>

    It seems that the WCF and ASMX has been combined on MSDN from what I can see. Maybe they should be separate forms.

    <copied>

    ERROR: 1429 - OLE IDISPATCH Exception code 0 from WSDLReader:

    SDLReader: XML Parser failed at linenumber 0, lineposition 0, Reason is:

    Access denied.

    <end>

    The above message for whatever user account the Web service is running under it is being denied access, because the account doesn't have rights/permissions to access the resource.

    NT AUTHORITY\NETWORK SERVICE is the ASP.NET Worker Process account. All ASP.NET applications are run by the ASP.NET Worker Process using that account, unless it is told otherwise by using account impersonation for an account that has the permissions.

    So NT AUTHORITY\NETWORK SERVICE is given the permissions (not recommended), or one uses an account and impersonates using the account that has been given the necessary rights.

    You may have to go to the Web service itself on IIS to set impersonation or look at the Application Pool and see what account it is using on IIS. 

      

    Tuesday, September 10, 2013 5:27 PM
  • Hi,

    >>what is the link for Legacy .ASMX Web Service Forum?

    This is the forums for the ASMX Web Service Forums.

    #ASMX  Web Service Forums:
    http://forums.asp.net/28.aspx/1?WCF+ASMX+and+other+Web+Services .

    >>ERROR: 1429 - OLE IDISPATCH Exception code 0 from WSDLReader: SDLReader: XML Parser failed at linenumber 0, lineposition 0, Reason is:Access denied.

    As the @darnold924 said, it seems that it is the something with the permissions.

    So please try to check the identity of the application pool. The default (network service) will not have access to control services.  To test this you can change the user to local system which has full control over the host system, however in a live environment you should create a user that has only the permissions you need.

    Best Regards,
    Amy Peng


    <THE CONTENT IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND, WHETHER EXPRESS OR IMPLIED>
    Thanks
    MSDN Community Support

    Please remember to "Mark as Answer" the responses that resolved your issue. It is a common way to recognize those who have helped you, and makes it easier for other visitors to find the resolution later.

    Wednesday, September 11, 2013 5:35 AM
    Moderator