Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.

Forcing Soap Toolkit 3.0 to use WinInet...

Skip to first unread message

Richard Sbarro

Aug 1, 2002, 1:07:42 PM8/1/02
Sorry for the double post...

I've been dealing with this issue for the past week and have yet to
find a viable solution to this problem. I was hoping that the release
of the SOAP Toolkit 3.0 would help me out (with the WinInet SOAP
Connector Type Library) but unfortunately it hasn't (so far)...

Here's what I'm trying to do. I'm trying to write an ActiveX control
that will call a set of webservices. Since the control is supposed to
run in IE, I want to use WinINET so I don't have to deal with any
proxy settings / configuration scripts / etc. By default the SOAP
Toolkit of course uses WinHTTP on NT/2000/XP (at least it did in 2.0
SP2), so I tried the following code...

sWSDL = "http://server/whatever.wsdl"
mvar_SoapClient.ClientProperty("ServerHTTPRequest") = False
mvar_SoapClient.ClientProperty("ConnectorProgID") =
mvar_SoapClient.MSSoapInit sWSDL

This code works, but as soon as I try to call a web service method
from a machine behind a proxy I get an error to the effect of...

Connector:Connection time out. HRESULT=0x800A1527 - Client:An
unanticipated error occurred during the processing of this request.
HRESULT=0x800A1527 - Client:Sending the Soap message failed or no
recognizable response was received HRESULT=0x800A1527 -
Client:Unspecified client error. HRESULT=0x800A1527

This makes me think that the SoapClient is STILL not using WinINET and
is still relying on WinHTTP. Further evidence of this is shown by the
fact that the code works when it is run on a machine thats on the same
local network as the server and no proxy is needed. Is there any
solution to my problem outside of abandoning the SOAP Toolkit entirely
and rewriting everything using XMLHTTP...?

Rich Sbarro

Kirill Gavrylyuk

Aug 11, 2002, 10:26:36 PM8/11/02
To force using wininet connector just rename/delete whsc30.dll .

But all you need to do in order to use IE proxy settings, is set
SoapClient.ConnectorProperty("ProxyServer") = "<CURRENT_USER>"
before the Soap call. This way you don't have to care about existance of
winhttp settings on your machine.


"Richard Sbarro" <> wrote in message

0 new messages