The SOAP Toolkit should still work as long as you're sure the AppPool is set to 32 bit. It's required since the Soap Toolkit and the VFP DLL it calls are 32 bit.

Are you getting any specific errors? If you can access the local console you can possibly see more error information when hitting the site locally as IIS provides more error info there, but then the MS SOAP Service is terrible at displaying error info in the first place but that's a place to start.

+++ Rick ---

>Did you already found a solution?
>
>We have a customer where our VFP webservice was working perfectly. Then they decided to install Exchange 2007 SP3 recently (on an SBS 2008 server) and now the webservce doesn't work anymore.
>
>The application pool was set to 64 bits and we got exactly the same error. After setting it back to 32 bits this error disappeared but the application pool stops working as soon as the webservice is called.
>
>We also noticed Microsoft has removed the SoapSDK from its download website recently. Is this just a co-incendence or are they terminating SOAP actively?