Help with this HRESULT Error, please?

Yesterday I was working on my home box on an image into which I had
files all the Swazoo and Spray (SOAP) stuff. I had written a simple
program that would fetch the WSDL for a web service from a url and allow
you to send messages to that web service. I moved that image and the
supporting cast to my laptop to bring that program to work. Now, when I
try to execute the WSDL fetch, I get the walkback shown below. I tried
filing the Swazoo/Spray install script into a virgin image, thinking
perhaps the setup did something specific to the machine, but the same
problem occurs. It would appear that I don't have some library
installed, but I don't know which one. Both boxen are Win2k Pro, Dolphin
4.01.3.

Any ideas?

Thanks,
Joey

9:13:18 AM, Friday, July 27, 2001: 'HRESULT Error: Class not registered
(FACILITY_ITF)'
OLELibrary(ExternalLibrary)>>invalidCall
OLELibrary>>coGetClassObject:dwClsContext:pServerInfo:riid:ppv:
IXMLDOMDocument class(COMInterface class)>>
onCLSID:outerIUnknown:hostName:licenseKey:
IXMLDOMDocument class(COMInterface class)>>onCLSID:outerIUnknown:
IXMLDOMDocument class(COMInterface class)>>onCLSID:
IXMLDOMDocument class(COMInterface class)>>new
IXMLDOMDocument class>>newEmpty
IXMLDOMDocument class>>loadSBytes:
IWinHttpRequest class>>getIXMLDocument:
WSDLDefinitions>>rootUrl:transport:
WSDLDefinitions class>>onUrl:transport:
WSDLDefinitions class>>onUrl:
SOAPTestShell>>getURL
Symbol>>forwardTo:
[] in Command>>value
BlockClosure>>ifCurtailed:
BlockClosure>>ensure:
Command>>value
SOAPTestShell(Shell)>>performCommand:
CommandQuery>>perform
DelegatingCommandPolicy(CommandPolicy)>>route:
[] in PushButton(View)>>onCommand:
BlockClosure>>ifCurtailed:
BlockClosure>>ensure:
Cursor>>showWhile:
PushButton(View)>>onCommand:
PushButton>>onActionPerformed
PushButton(View)>>performAction
PushButton>>command:id:
ShellView(View)>>wmCommand:wParam:lParam:
ShellView(View)>>dispatchMessage:wParam:lParam:
[] in InputState>>wndProc:message:wParam:lParam:cookie:
BlockClosure>>ifCurtailed:
ProcessorScheduler>>callback:evaluate:
InputState>>wndProc:message:wParam:lParam:cookie:
PushButton(ControlView)>>defaultWindowProcessing:wParam:lParam:
PushButton(View)>>defaultWindowProcessing:
PushButton(View)>>onLeftButtonReleased:
PushButton(View)>>wmLButtonUp:wParam:lParam:
PushButton(View)>>dispatchMessage:wParam:lParam:
[] in InputState>>wndProc:message:wParam:lParam:cookie:
BlockClosure>>ifCurtailed:
ProcessorScheduler>>callback:evaluate:
InputState>>wndProc:message:wParam:lParam:cookie:
ShellView(View)>>isDialogMessage:
ShellView>>preTranslateMouseInput:
ShellView(View)>>preTranslateMessage:
InputState>>preTranslateMessage:
InputState>>pumpMessage:
InputState>>loopWhile:


--
-- Sun Certified Java2 Programmer
-- My Pocket Smalltalk Stuff: www.joeygibson.com/st
--
-- "We thought about killin' him, but we kinda
--  hated to go that far...." - Briscoe Darling



-----= Posted via Newsfeeds.Com, Uncensored Usenet News =-----
http://www.newsfeeds.com - The #1 Newsgroup Service in the World!
-----==  Over 80,000 Newsgroups - 16 Different Servers! =-----

In article <[hidden email]>,
[hidden email] says...
        For anyone interested, Steve Waring pointed me to a MSKB article
http://support.microsoft.com/support/kb/articles/q278/6/36.asp that
detailed what can happen if you install MSXML3... DLL Hell!
Unregistering the MSXML3 and re-registering thej MXSML2 worked just
fine.

Joey
--
-- Sun Certified Java2 Programmer
-- My Pocket Smalltalk Stuff: www.joeygibson.com/st
--
-- "We thought about killin' him, but we kinda
--  hated to go that far...." - Briscoe Darling



-----= Posted via Newsfeeds.Com, Uncensored Usenet News =-----
http://www.newsfeeds.com - The #1 Newsgroup Service in the World!
-----==  Over 80,000 Newsgroups - 16 Different Servers! =-----

> For anyone interested, Steve Waring pointed me to a MSKB article
> http://support.microsoft.com/support/kb/articles/q278/6/36.asp that
> detailed what can happen if you install MSXML3... DLL Hell!
> Unregistering the MSXML3 and re-registering thej MXSML2 worked just
> fine.

Hi Joey,
As the article points out installing MSXML3 is not the problem, installing
it in "replace" mode is. As I understand it, this was supposed to be used
for developers to test existing applications and MSXML3, but I have read
reports of it being used in installation routines. Not a good thing.

I have the final release of MSXML3 installed in the side by side mode. As an
experiment, I switched the
IXMLDOMDocument>>clsid method to answer the "new" MSXML2.DOMDocument CLSID,
and it worked without problem. Possibly you had one of the older MSXML3 beta
releases installed in replace mode.

Steve