SOAP Toolkit 3.0 - help with strange problem : XML SOAP

I'm using SOAP Toolit 3.0 on W2K Pro, and I have an odd problem. I set
up the sample from the help file - DocSample1, and when I run the
client, I get the following:

Error source: WSDLReader
faultcode=Server
faultstring=Error source: WSDLReader
faultactor=http://tempuri.org/DocSample1/action/Sample1.EchoString
detail=<detail><mserror:errorInfo
xmlns:mserror="http://schemas.microsoft.com/soap-toolkit/faultdetail/error/"><mserror:returnCode>
HRESULT=0x80040154</mserror:returnCode><mserror:callStack><mserror:cal lElement><mserror:description>WSDLReader:Loading
of the WSDL file failed HRESULT=0x80040154: Class not registered
- Server:An unanticipated error occurred during the processing of this
request. HRESULT=0x80040154: Class not registered
</mserror:description></mserror:callElement></mserror:callStack></mserror:errorInfo></detail>

I also have another test case which produces the same error (but wrapped
in SOAP). Both of these test cases work fine on another W2K machine
(client and server running on the other machine). I've tried
re-installing IIS and the SOAP Toolkit, but to no avail. SOAPIS30.dll is
registered to handle .wsdl files, and if I allow directory browsing in
the server virtual directory, I can browse to, and retrieve, the .wsdl
file, so I don't think there are any problems with permissions. The WSDL
content must be correct because it works on another machine. So I'm at a
bit of a loss - the "Class not registered" message seems a bit
unhelpful. Can anyone throw any light on this?

(I need to have this work because I'm writing code to interface with
some 3rd party Web Services which use SOAP, and I need to write an
emulation for test purposes...)

Hello
My guess is that the COM object that you are using for the web service is
not registered correctly on the box with IIS. The Soap Toolkit ISAPI
listener will try and create the COM component that you are using for the
web service and if it fails it will give an error like this.


Thanks
Brian [MSFT]
Microsoft Developer Support
This posting is provided "AS IS" with no warranties, and confers no rights.
--------------------
| Date: Wed, 08 Dec 2004 19:54:16 +0000
| From: OxSc <a@b.c>
| User-Agent: Mozilla Thunderbird 0.9 (Windows/20041103)
| X-Accept-Language: en-us, en
| MIME-Version: 1.0
| Newsgroups: microsoft.public.xml.soapsdk
| Subject: SOAP Toolkit 3.0 - help with strange problem
| Content-Type: text/plain; charset=ISO-8859-1; format=flowed
| Content-Transfer-Encoding: 7bit
| Lines: 30
| Message-ID: <41b75be9$0$1075$db0fefd9@news.zen.co.uk>
| Organization: Zen Internet
| NNTP-Posting-Host: 82.69.19.208
| X-Trace: 1102535657 cockburn.zen.co.uk 1075 82.69.19.208:4992
| X-Complaints-To: abuse@zen.co.uk
| Path:
cpmsftngxa10.phx.gbl!TK2MSFTFEED01.phx.gbl!TK2MSFT NGP08.phx.gbl!newsfeed00.s
ul.t-online.de!t-online.de!news.zanker.org!feeder.enertel.nl!nntpfe ed-01.ops
.asmr-01.energis-idc.net!216.196.110.149.MISMATCH!border2.nntp.ams. giganews.
com!border1.nntp.ams.giganews.com!nntp.giganews.co m!caladan!news.anlx.net!de
dekind.zen.co.uk!zen.net.uk!fuller.zen.co.uk!cockb urn.zen.co.uk.POSTED!not-f
or-mail
| Xref: cpmsftngxa10.phx.gbl microsoft.public.xml.soapsdk:12331
| X-Tomcat-NG: microsoft.public.xml.soapsdk
|
| I'm using SOAP Toolit 3.0 on W2K Pro, and I have an odd problem. I set
| up the sample from the help file - DocSample1, and when I run the
| client, I get the following:
|
| Error source: WSDLReader
| faultcode=Server
| faultstring=Error source: WSDLReader
| faultactor=http://tempuri.org/DocSample1/action/Sample1.EchoString
| detail=<detail><mserror:errorInfo
|
xmlns:mserror="http://schemas.microsoft.com/soap-toolkit/faultdetail/error/"
><mserror:returnCode>
|
HRESULT=0x80040154</mserror:returnCode><mserror:callStack><mserror:cal lEleme
nt><mserror:description>WSDLReader:Loading
| of the WSDL file failed HRESULT=0x80040154: Class not registered
| - Server:An unanticipated error occurred during the processing of this
| request. HRESULT=0x80040154: Class not registered
|
</mserror:description></mserror:callElement></mserror:callStack></mserror:er
rorInfo></detail>
|
| I also have another test case which produces the same error (but wrapped
| in SOAP). Both of these test cases work fine on another W2K machine
| (client and server running on the other machine). I've tried
| re-installing IIS and the SOAP Toolkit, but to no avail. SOAPIS30.dll is
| registered to handle .wsdl files, and if I allow directory browsing in
| the server virtual directory, I can browse to, and retrieve, the .wsdl
| file, so I don't think there are any problems with permissions. The WSDL
| content must be correct because it works on another machine. So I'm at a
| bit of a loss - the "Class not registered" message seems a bit
| unhelpful. Can anyone throw any light on this?
|
| (I need to have this work because I'm writing code to interface with
| some 3rd party Web Services which use SOAP, and I need to write an
| emulation for test purposes...)
|

Brian Combs wrote:
> Hello
> My guess is that the COM object that you are using for the web service is
> not registered correctly on the box with IIS. The Soap Toolkit ISAPI
> listener will try and create the COM component that you are using for the
> web service and if it fails it will give an error like this.
>
>
> Thanks
> Brian [MSFT]
> Microsoft Developer Support
> This posting is provided "AS IS" with no warranties, and confers no rights.

The object used for the web service is an Activex .dll, built using
Visual Basic. It appears from a quick inspection of the registry that it
is registered (I didn't register it - I assume VB does this as part of
the build process.) I have another machine where it all works fine -
again, VB built the Activex .dll, I didn't manually register anything.
Is there an easy way to test whether or not registration has been
successful?

TIA

Hello
VB does a lot of strange things when it builds a DLL. It will register the
DLL, but if you have built the DLL before and then make changes to the
interface and rebuild it will give you new guids for the DLL. You may then
have more the one entry in your registry for this DLL. However only one
will be correct. You should clean your registry of all entries to this DLL.
Rebuild and then run WSDL generator on the new DLL and then test.

Please see the following topic on MSDN

http://msdn.microsoft.com/library/de...us/vbcon98/htm
l/vbconversioncompatibility.asp

Thanks
Brian [MSFT]
Microsoft Developer Support
This posting is provided "AS IS" with no warranties, and confers no rights.
--------------------
| Date: Tue, 14 Dec 2004 16:05:27 +0000
| From: OxSc <a@b.c>
| User-Agent: Mozilla Thunderbird 0.9 (Windows/20041103)
| X-Accept-Language: en-us, en
| MIME-Version: 1.0
| Newsgroups: microsoft.public.xml.soapsdk
| Subject: Re: SOAP Toolkit 3.0 - help with strange problem
| References: <41b75be9$0$1075$db0fefd9@news.zen.co.uk>
<80$XMZU4EHA.3200@cpmsftngxa10.phx.gbl>
| In-Reply-To: <80$XMZU4EHA.3200@cpmsftngxa10.phx.gbl>
| Content-Type: text/plain; charset=ISO-8859-1; format=flowed
| Content-Transfer-Encoding: 7bit
| Lines: 22
| Message-ID: <41bf0f48$0$1061$db0fefd9@news.zen.co.uk>
| Organization: Zen Internet
| NNTP-Posting-Host: 82.69.19.208
| X-Trace: 1103040328 cockburn.zen.co.uk 1061 82.69.19.208:3069
| X-Complaints-To: abuse@zen.co.uk
| Path:
cpmsftngxa10.phx.gbl!TK2MSFTFEED02.phx.gbl!tornado .fastwebnet.it!tiscali!new
sfeed1.ip.tiscali.net!border2.nntp.ams.giganews.co m!border1.nntp.ams.giganew
s.com!nntp.giganews.com!dedekind.zen.co.uk!zen.net .uk!fuller.zen.co.uk!cockb
urn.zen.co.uk.POSTED!not-for-mail
| Xref: cpmsftngxa10.phx.gbl microsoft.public.xml.soapsdk:12340
| X-Tomcat-NG: microsoft.public.xml.soapsdk
|
| Brian Combs wrote:
| > Hello
| > My guess is that the COM object that you are using for the web service
is
| > not registered correctly on the box with IIS. The Soap Toolkit ISAPI
| > listener will try and create the COM component that you are using for
the
| > web service and if it fails it will give an error like this.
| >
| >
| > Thanks
| > Brian [MSFT]
| > Microsoft Developer Support
| > This posting is provided "AS IS" with no warranties, and confers no
rights.
|
| The object used for the web service is an Activex .dll, built using
| Visual Basic. It appears from a quick inspection of the registry that it
| is registered (I didn't register it - I assume VB does this as part of
| the build process.) I have another machine where it all works fine -
| again, VB built the Activex .dll, I didn't manually register anything.
| Is there an easy way to test whether or not registration has been
| successful?
|
| TIA
|