My ASP code is:
set soapclient = server.createobject("MSSOAP.SoapClient")
soapclient.ClientProperty("ServerHTTPRequest")
soapclient.mssoapinit
("http://systemone/sa/soap/saworkflow.wsdl","saWorkflow","WorkFlowSoapPort")
bRetVal = soapclient.UserLogon(sXML)
I have run the profxycfg -d and it says:
Flags PROXY_TYPE_DIRECT
Proxy Server = not set
Bypass List = not set
Thanks,
Steve
-----Original Message-----
Are you setting the serverxmlhttp properties and did you run the proxycfg
utility ?
Regards
Frank Mantek
Microsoft
"Stephen Miller" <stephen...@sjmsoftware.com> wrote in message
news:269301c0ae08$c6b22930$19ef2ecf@tkmsftngxa01...
I have the following code in ASP, attempting to invoke a method on a remote
machine. Both machines are W2000 Pro and have SOAPISAP.dll configured in
IIS5.0
with the wsdl extension.
Error Type:
Client (0x80020009)
WSDLReader:Analyzing the WSDL file failed
HRESULT = 0x80004005
Any ideas? Cheers
Steve
.
Regards
Frank Mantek
Microsoft
"Stephen Miller" <stephen...@sjmsoftware.com> wrote in message
news:262501c0aed9$29908fd0$a5e62ecf@tkmsftngxa07...
You need to set the ClientProperty "ServerHTTPRequest" to True. For example
in VBScript:
soapclient.ClientProperty("ServerHTTPRequest") = True
Unless, this is a typo in the code snippet you posted, you currently are
not setting this property to True. Thus "server safe" ServerXMLHTTP will
not be used to load the file. Make sure this property is set to True.
I hope this helps,
Steve Lindeman
Microsoft Developer Support
"Stephen Miller" <stephen...@sjmsoftware.com> wrote in message
news:262501c0aed9$29908fd0$a5e62ecf@tkmsftngxa07...
Sorry, there was a typo in my code snippet. I have set the ServerHTTPRequest
property to True but still no joy. Do you know of any other reason why the
WSDLReader would fail with 'Analyzing the WSDL file failed HRESULT = 0x80004005'?
I just can't see why this can be failing.
Many thanks,
Steve
-----Original Message-----
Hi Steve,
I hope this helps,
My ASP code is:
Thanks,
Steve
Regards
Any ideas? Cheers
Steve
..
.
Set SoapClient = CreateObject("MSSOAP.SoapClient")
SoapClient.ClientProperty("ServerHTTPRequest") = True
Call SoapClient.mssoapinit("http://garden/aWebService/aWebService.wsdl",
"aWebService", "aServiceSoapPort")
MsgBox (SoapClient.CallMethod())
However if I change the script slightlty to call an asp page:
Set SoapClient = CreateObject("MSSOAP.SoapClient")
SoapClient.ClientProperty("ServerHTTPRequest") = True
Call SoapClient.mssoapinit("http://garden/aWebService/aWebService.asp",
"aWebService", "aServiceSoapPort")
MsgBox (SoapClient.CallMethod())
I get a failure:
WSDLReader:Analyzing the WSDL file failed.HRESULT=0x80004005
I have run proxycfg -d.
Any ideas what to try? I am using an asp file straight out of the WSDL
Wizard. Client and server are on the same machine.
Thanks!
Regards - Jim
Looking over your wsdl file, I do not see anything that appears to be wrong.
Also, I was able to load the wsdl file from an ASP page successfully.
Frank asked this question, do you see any other information in the client
fault properties? (Ex: SoapClient.faultstring, SoapClient.detail,
SoapClient.fault etc..)
Does the problem seem to be specific to running the soap client from an ASP
page. If you move the client code out of ASP does the same error occur? I
assume the mssoapinit call is failing, but could you confirm.
Also, you also might try using the MSSaopT trace utility to make sure the
wsdl file is being sent across the wire properly.
thanks,
Steve Lindeman
Microsoft Developer Support
"Stephen Miller" <stephen...@sjmsoftware.com> wrote in message
news:2cb001c0b057$e38c7410$b1e62ecf@tkmsftngxa04...
Set SoapClient = CreateObject("MSSOAP.SoapClient")
SoapClient.ClientProperty("ServerHTTPRequest") = True
Call SoapClient.mssoapinit("http://garden/aWebService/aWebService.wsdl",
"aWebService", "aServiceSoapPort",
"http://garden/aWebService/aWebService.wsml")
MsgBox (SoapClient.CallMethod())
-Andy Hopper
"James N. McClatchey" <j...@saf.com> wrote in message
news:OFuW7vKsAHA.1960@tkmsftngp04...
"Andrew Hopper" <Andy....@junko.mindspring.com> wrote in message
news:#stGhRgsAHA.684@tkmsftngp03...