Hi Joel,

thanks for your reply. I tried the wwSOAP library as you suggested. Unfortunately it suffers from the very same problem. Once the SocketWrench is initialized the wwSOAP fails with Error 2027 when trying to call HttpSendRequest from WININET.DLL

I guess that the SocketWrench does not dispose handles properly and they get somehow reused.

>Hi Andreas,
>
>Give wwSOAP a try: http://www.west-wind.com/wwsoap.asp. I prefer it over the SOAP Toolkit.
>
>If you want support with that, buy West Wind Client Tools: http://www.west-wind.com/wwClientTools.asp
>
>I don't know what you are doing with SocketWrench, but maybe West Wind tools will handle it as well.
>
>>Hi everybody,
>>
>>I have a rather strange problem using the SocketWrench ActiveX control from Catalyst. Recently we extended our application to consume a WebService using Microsoft SOAP Toolit 3.0. Everything works fine, until the users interact with a part of our application, that uses the Catalyst SocketWrench control.
>>
>>After this happens, the SOAP Toolkit cannot produce a connection anymore, until the application is restarted. The code acts like the SOAP Toolkit is not installed on the machine. Now I suppose that both the SocketWrench and SOAP Toolkit use some library and the SocketWrench does not unload it properly. The funny thing is, that SocketWrench works repeatedly without any problems even after SOAP. SOAP works just fine repeatedly until the first time the SocketWrench control is loaded.
>>
>>We use ver. 3.6 of the SocketTools Visual Edition by Catalyst. The control is initialized through adding it to a form like that:
>>
>>THISFORM.AddObject("socket", "Olecontrol", "Catalyst.SocketCtrl.1")
>>
>>Beyond this point, the Microsoft SOAP ToolKit 3.0 cannot produce a connection even to load the WSDL information. Has anyone experienced this before. Any help will be greatly appreciated, as I am looking two days in a row now without any idea of what can be causing the problem. I event tried rude commands like CLEAR ALL and CLEAR MEMORY but this does not help. The only thing that helps is restarting the development environment or the application (user case).