Mike,

I started out with MS Soap 3 and had similar problems, all related to the proxy server / hardware firewall - my guess is you are running throgh a proxy server as well.

So I switched to PocketSoap, an open source (free) Soap Client which takes a bit more programming, but eventually worked.

For MS SOAP you have to set the loVersion.ConnectorProperty("ProxyServer") = "YourProxyServer:YourPort", the port most likely being 8080.

You also must set the ConnectorProperty("EndPointURL") = "http://62.242.131.12/axis/services/Version?wsdl", the http string obviously not pointing to the example, but to your wsdl.

Feel free to contact me for a sample Pocket soap app - and try to get around the proxy server alltogether, if you can.

As for the stuff Martín Salías points out, I don't know if PocketSoa has support for .Net stuf, but check it out at PocketSoap.com, and get all the nice tracing tools while you're at it.

HTH

>Hi Peter,
>
>I'm using SOAP 3. Yes it does indeed expose several methods in the dropdown list but when I try to test one by supplying the parameter, I get the errors.
>
>Try this. Register the ProFox web service as found here, http://www.leafe.com/ProFoxWS.wsdl
>
>Now try to use the GetMsg() method passing an integer. It does not work for me and I get an error message complaining that the parameter is incorrect. I've tried the examples provided at the following link:
>
>

>http://fox.wikis.com/wc.dll?Wiki~ProFoxWebServices~VFP
>

>
>and they don't work either. I'm not using a proxy and am on WindowsXP SP2
>
>Regards,
>
>Mike