Good info...

In response to his question though I doubt this is what the problem is. WinINet will work ok on most servers if there's no load or light load. Corruption occurs only under load...

I haven't used ServerHTTP actually - I assume proxy config is required only if a proxy connection needs to be set right? If you're sitting on a Web server especially a public one this may not be a huge issue because most likley no proxy config will be necessary.

+++ Rick ---

>>There doesn't seem to be any permission issues because I can call this WebService from a prg or from the command window - no problem (no login is required) It is only when I call this WS from within my WS.
>>
>>Thanks in advance.
>
>The MSSOAP client by default uses WinInet for remote connectivity, and WinInet is not safe for running under a service (ASP) because it gets it's proxy settings from the HKCU hive of the registry. If you want to use the SoapClient object from a server process, you need to make sure that you set it up to use the ServerHTTPRequest object that's safe for using under a service. You do this after instantiating the SOAP Client like:
>
>oClient.ClientProperty("ServerHTTPRequest") = .T.
>
>But before you can use the ServerHTTPRequest object at all, you have to make some registry entries that it can use to discover proxy info for the current machine. Download the WinHTTP Proxy config utility from http://msdn.Microsoft.com/downloads/default.asp?URL=/code/sample.asp?url=/msdn-files/027/001/468/msdncompositedoc.xml.