Did you look at the VFP Help topic: "Walkthrough: Creating a Visual FoxPro Application Setup Program Using InstallShield"?

The topic includes this section:

Web Services and SOAP
If your application uses Web services or SOAP, you must include the following merge modules: 

SOAP SDK Files (Soap_Core.msm)
Visual Basic Virtual Machine (MSVBVM60.msm)
Microsoft Component Category Manager Library (Comcat.msm)
Microsoft OLE 2.40 (OLEAUT32.msm)

>We're a bit confused right now on the minimum components needed on a remote server to deploy a web service there.
>
>We currently have a web service that runs without problem on a remote IIS server - as long as the VFP IDE is installed on the box. Because we will not be able to install a whole IDE onto a customer's server, we removed the IDE and then installed the SOAP toolkit (MSXML included) as well as the Runtime components. The SOAPIS30 is handling the WSDLs in IIS. The runtime components go out standardly with our applications. We also installed the VB Virtual Machine, which we found as a suggestion for another link.
>
>Pinging the webservice after removing the IDE (and adding the other components, plus reboot) gets a "WSDLOperation:Instantiating the dispatch object for method Ping failed" message.
>
>Does anyone happen to know what the minimum components are to run a web service, without installing the IDE? Again - I think everything is registered and the client is fine because this function works without problem when the IDE is on the server. (If we reinstall the IDE the service comes back without problem.)
>
>just in case it helps, technical information:
>a VFP client (three lines) simply instantiates a C# .dll "broker" class (the broker handles the authentication and communicates with the VFP service located on the IIS box). I needed to write the broker in C# because I was having a lot of issues with the SOAP toolkit using credentials or client certificates. Then the VFP client uses the broker to call the Service methods - for example:
>
>

>oBroker = createobject('Services.Broker')
>wait window oBroker.Initialize(wsdl,clientcert) && "initialized"
>wait window oBroker.Ping() && which calls the service's Ping().
>

>
>Thanks a lot, in advance, if someone knows what the problem might be.
>Ryan