Error: Loading WSDL file failed

[Matt Gould]

Howdy.

I'm getting this error on only one machine out of about 10 that have been
tested. I'm using SOAP Toolkit version 2 and am attempting to call
MySoapClient.mssoapinit from within a VBA class in Excel. The weird thing
is that on virtually all machines this code works, but on one machine we get
the following error:

Runtime error '-2147221164 (80040154):
WSDLReader:Loading of the WSDL file failed HRESULT=0x80040154

I've tried putting "MySoapClient.ClientProperty("ServerHTTPRequest") = True"
on the line before the mssoapinit call, but that doesn't fix the problem.

I'd appreciate any help anyone can give.

Matt Gould

[Roger Wolter[MS]]

This "class not registered" error usually means one of the progid's listed
in the WSML file isn't registered correctly on the machine.

--
This posting is provided "AS IS" with no warranties, and confers no rights.

"Matt Gould" <mgo...@calpine.com> wrote in message
news:OJWk#9$BCHA.1880@tkmsftngp04...

[Matt Gould]

Roger:

Thank you that gives me some much needed information that should help me
start troubleshooting this.

Some of this code was just handed to me, so forgive me if I seem a little
uninformed about how it works. I assume the WSML file exists on the client
box, correct? Time to market was crucial on this, so in our rush to put
together a deployment package we wrapped the SOAP redistributable msm files
in a more or less silent install built in .NET and *then* packaged the whole
thing up in a Wise installer (built with version 8.1). Very clunky, I know,
but it got everything installed successfully on *most* machines.

Any idea why the SOAP msm files might not get everything working on a
particular machine?

I'll try running the stand-alone SOAP Toolkit installer on the box where
we're having problems. If that works, maybe we can just wrap it up in the
Wise installer and run it silently (somehow).

Thanks again,

Matt

"Roger Wolter[MS]" <rwolte...@microsoft.com> wrote in message
news:uLssRBACCHA.2072@tkmsftngp02...

[Roger Wolter[MS]]

If it was one of the Soap Toolkit files that wasn't registered you would get
an error when you create the client. Getting the error on mssoapinit
usually means that a progid listed in the WSML file isn't registered - this
would normally be a custom type mapper. If you're not using a custom type
mapper, you don't need a WSML file on the client and the fix might be as
simple as taking the WSML file out of the mssoapinit call.

--
This posting is provided "AS IS" with no warranties, and confers no rights.

"Matt Gould" <mgo...@calpine.com> wrote in message

news:esuw#KACCHA.2596@tkmsftngp05...

[Matt Gould]

Roger:

I ran the full, standalone SOAP Toolkit install on the box and now the
problem has disappeared.

My mssoapinit call is just "MySoapClient.mssoapinit sPath" where "sPath" is
the path to the web service (i.e.,
http://myserver/mywebservice/mywebservice.asmx?wsdl. Like I mentioned
earlier, I didn't build this code so based on what you've told me I'm next
going to do some reading to figure out what a WSML file is and whether we
are using a custom type mapper. Unfortunately, the guy who knows more about
this stuff is out today.

Thanks again for your help,

Matt

"Roger Wolter[MS]" <rwolte...@microsoft.com> wrote in message

news:Ogy7RYACCHA.1696@tkmsftngp05...