This isn't easy to fix because it appears the error occurs as part of the response from the server which is failing and returning an invalid SOAP response. Most likely the server crashes and returns a 500 error or something to this effect. What you need to do is set up special error handling ont he server to make sure that you wrap all errors explicitly and try to feed those back to the client. You can do this with try/catch blocks and the ERROR command in VFP (if that's what you're using on the server).

In addition I would use the SOAP methods directly instead of the Intellisense/FFC wrapper to get better control over the code and wrap the code in the appropriate try catch handlers.

My free wwSOAP tool includes a proxy class generator that allows you wrapper a Web Service's method on the client side with a class that does all the error trapping for you at least.

http://www.west-wind.com/wwsoap.asp


+++ Rick ---


>I am linking through to a web service and the routines work fine 99% of the time but occassionally crash out with :
>
>OLE error code 0x800a1518: Unknown COM status code.
>
>I am using VFP7 and have registered the web service in Fox and used intellisense to generate the neccessary code ie
>
>loPOSService = loWS.SetupClient("MyURL?wsdl", "POSService", "POSServicePort")
>
>The program then checks that this has worked okay and doesn't go any further if it hasn't
>IF VARTYPE(loPOSService) <> "O"
> RETURN .f.
>ENDIF
>
>The next line of code is to create another object that contains the response from one of the methods of the service
>
>loResponse = loPOSService.invokePOSService(lcMethod, "7_0_5", lcSendString)
>
>This is the line that gives the occassional error.
>
>I've checked with the web service we are using to find out if there's a problem at their end but they couldn't see any reason why the problem is occassionally happening.
>
>Is there anything else I can do to stop it happening or to stop the program crashing out.
>
>Thanks
>
>Sue