Announcement

Collapse
No announcement yet.

soap call failing since upgrade

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • soap call failing since upgrade

    One of my clients has a Dotnet based application, that makes SOAP calls to an external site to retrieve an XML data file.
    This file is then stored on a network drive (U: in case it matters)

    There are no other elements of the application installed on the server.
    We recently did a swing migration from sbs03 to sbs08, and since the migration the application hasn't worked.

    We're not having any trouble using the application from an external source.
    There are no permissions problems on the network share.

    I've checked for firewalls on both client and server, and fully disabled them as well as Sophos, but the problem continues.


    The error message is:
    Code:
    "Initialisation error - WSDLREAder: Loading of the WSDL file failed, hresult=0x80070057 - wsdlReader:XML Parser failed at linenumber 0, line position 0, reason is system error-2146697191 hresult=0x1"
    From the computer with the application in question, we can browse to the url of the xml page to download it with no issues - so there's no security on this.


    I can't think where else to look - any suggestions ?
    Please do show your appreciation to those who assist you by leaving Rep Point https://www.petri.com/forums/core/im.../icon_beer.gif

  • #2
    Re: soap call failing since upgrade

    Hi,

    Does it make any difference if the file is stored on a local drive instead of u:
    gerth

    MCITP sa, ea & va, [email protected]

    Comment


    • #3
      Re: soap call failing since upgrade

      don't know, think we'd need to reconfiguer the whole thing for that, and the application vendor (naturally) thinks the application is fine
      It's hard to get any information out of him how it works. "It just makes a soap call"
      Please do show your appreciation to those who assist you by leaving Rep Point https://www.petri.com/forums/core/im.../icon_beer.gif

      Comment


      • #4
        Re: soap call failing since upgrade

        If you cannot test it, is the u: share connected with elevated privileges, normal, or both.
        gerth

        MCITP sa, ea & va, [email protected]

        Comment


        • #5
          Re: soap call failing since upgrade

          uhm, jus normal privileges i hink - under the user context
          Please do show your appreciation to those who assist you by leaving Rep Point https://www.petri.com/forums/core/im.../icon_beer.gif

          Comment


          • #6
            Re: soap call failing since upgrade

            IE runs onder the user context but the application might be running on a different user mode....
            I would verify that..

            Also when I google on this: reason is system error-2146697191 I found a lot which refer to IE 7..?
            Marcel
            Technical Consultant
            Netherlands
            http://www.phetios.com
            http://blog.nessus.nl

            MCITP(EA, SA), MCSA/E 2003:Security, CCNA, SNAF, DCUCI, CCSA/E/E+ (R60), VCP4/5, NCDA, NCIE - SAN, NCIE - BR, EMCPE
            "No matter how secure, there is always the human factor."

            "Enjoy life today, tomorrow may never come."
            "If you're going through hell, keep going. ~Winston Churchill"

            Comment


            • #7
              Re: soap call failing since upgrade

              I ended up escalating the case.. i'll try and remember to find out what the hell happened
              Please do show your appreciation to those who assist you by leaving Rep Point https://www.petri.com/forums/core/im.../icon_beer.gif

              Comment


              • #8
                Re: soap call failing since upgrade

                Originally posted by tehcamel View Post
                i'll try and remember to find out what the hell happened
                Check your Rep Points. Reason why it happens is there. Click image for larger version

Name:	acclaim.gif
Views:	8
Size:	1.4 KB
ID:	464703
                1 1 was a racehorse.
                2 2 was 1 2.
                1 1 1 1 race 1 day,
                2 2 1 1 2

                Comment

                Working...
                X