VB6 & Windows 7 Soap Issues??

[dandeveloper]

I've been trying to get my VB6 app to work on Windows 7 desktop and have got it working all bar getting it work when it's called a web service via soap as per the code below:

Dim SoapObjectclient As New SoapClient
'Call the web service passing the built up xml string
Call SoapObjectclient.mssoapinit(WSDL)

It comes up with the error:

ActiveX Component can't create object HResult:1AD.

Any ideas?

[dilettante]

Only one release of Windows ever shipped with the SoapClient library and that was Windows XP.

To use this in actual applications you should be deploying it anyway. Link Removed, it only offered an update patch and not the entire Toolkit.

However this is all deprecated technology, and unlike VB6 programs themselves these SOAP tools were never supported after Windows XP. While programs using them and properly deployed may well run on Vista and later, all bets are off so some things may not work as expected.

There was never any replacement issued. Your alternatives include .Net Interop or 3rd party tools.

[TysonLPrice]

We run SOAP from VB 6.0 on Windows 7 calling a web service and it seems OK. I really don't know all that much about it. I can provide you specifics about how it is called if that would help. Are you sure you have it included as a reference? We have:

Microsoft SOAP Type library v3.0.

[dandeveloper]

We run SOAP from VB 6.0 on Windows 7 calling a web service and it seems OK. I really don't know all that much about it. I can provide you specifics about how it is called if that would help. Are you sure you have it included as a reference? We have:

Microsoft SOAP Type library v3.0.

We just have Microsoft Soap Type Libary (mssoap1.dll). Do you think we need to get the 3.0 toolkit installed? If so do you know where i can get it from as Microsoft doesn't seem to have it anymore?

If you provide the specifics about how it is called that would be great.

Thanks

[jggtz]

To download the toolkit see post #2

[TysonLPrice]

We just have Microsoft Soap Type Libary (mssoap1.dll). Do you think we need to get the 3.0 toolkit installed? If so do you know where i can get it from as Microsoft doesn't seem to have it anymore?

If you provide the specifics about how it is called that would be great.

Thanks

I know we had to install the product and it is a lot more than the dll. The person that knows the most about it is not available right now. I'll try and get back with you. I can tell by IDE that in the variable you have as WSDL we have the web page:

http://dotnetweb/Rateinvitationxi/RatePacket.asmx?wsdl

All they pieces that get connected via that process I don't deal with much.

[dilettante]

The link I had provided in post #2 above did not provide the Toolkit, only a patch for it.


As far as I can tell Microsoft no longer hosts the SOAP Toolkit 3.0 SDK or Redist packages for downloading. This another of those "you snooze, you lose" as support for products like VB6 and Windows XP fades away.

Note that the Redist EULA states:

You may copy and redistribute only the Microsoft Installer Component of the SOFTWARE PRODUCT, which are the files identified as winhttp51.msm, isapi3_files.msm, and soap3_core.msm (the “Redistributable Components”), ...

I.e., extracting the DLLs involved and distributing them "naked" outside the MSMs does not seem to have been permitted.


The Redist.doc from the package says:

The following Microsoft Installer 2.0 merge modules are included in the redistributable package:

• Soap3_core.msm
• Isapi3_files.msm
• Winhttp.msm

Soap3_core.msm and winhttp.msm are required for all soap installations and isapi3_files.msm is dependent on soap3_core.msm.

This also requires MSXML 4.0 SP1 or later as well.

Redist.doc goes on to say:

How to redistribute SOAP Toolkit 3.0 components

With addition of the winhttp.msm, merging the SOAP Toolkit 3.0 redistributable modules became more complicated then it used to be for the previous 2.0 SP2 version.

The winhttp.msm contains installers for the system http library Winhttp 5.1 (winhttp.dll).

The reason for complexity is that winhttp.msm contains platform specific installers of the for each W2K, NT4 and XP. Once installed, winhttp.dll file becomes System File Protected. Microsoft does not provide any means to uninstall winhttp.dll.

... along with more details on how you must create your application's Installer MSI package.

There is no provision for installing via legacy scripted installers such as the PDW.


The EULA also doesn't permit anyone else to just "give you a copy."