This works, but when I make both processes run on the same machine (in
different
IIS Applications) I get this error when I run the mssoapinit method on the
MSSoap
object on the client:
Error code: -2147352567
Error Description: WSDLReader:Loading of the WSDL file failed
HRESULT=0x80070057 - WSDLReader:XML Parser failed at linenumber 0,
lineposition 0, reason is: No data is available for the requested resource.
HRESULT=0x1
I have checked the WSDL on the server process and it is correct and shows
properly
in IE 5.5 and MS XML Notepad.
What is going wrong?
Regards,
Laurence Everitt
I could not replicate the error going from my own machine to my own
machine or my own machine to the server. When I included the "fix" as
suggested, the issue was solved, so the problem seems to be with the
High level API and MSXML3 on the Server.
I have verified that the two MSXML3 DLL's on my machine and the
Server machine are the same version. The only difference between the
installations of SOAP are:
I took the copy for my machine from the MSDN site last Friday and
I took the copy for the server from the MSDN site on Monday.
Ideas?
"Laurence Everitt" <Laur...@zy.com> wrote in message
news:tk6ad0t...@xo.supernews.co.uk...
I do not know why the code worked on my test and not the server
machine, but I used this code to get the SOAP to work:
set oObject = Server.CreateObject("MSSOAP.SoapClient")
oObject.ClientProperty("ServerHTTPRequest") = True
oObject.mssoapinit("http://server/Thing/Thing.wsdl")
I had omitted to insert the ServerHTTPRequest property line after creating
the
MSSOAP.SoapClient object. I will be creating all my SOAP objects in this
way from here on.
Regards,
Laurence
"Laurence Everitt" <Laur...@zy.com> wrote in message
news:tk6fq02...@xo.supernews.co.uk...