Thanks for the reply and link Rick.

I'm thinking of switching over to using HTTP Post instead. Any suggestions?

Mike

>The SOAP Toolkits WSDL import utility will fail on some complex Web Services. If the service is Java based and uses complex types and arrays especially it's likely that the SOAP Toolkit import will fail.
>
>This is one of the big problems with teh ST - it doesn't give useful error information on the actual problem. It could be anything. However, if you can ensure that the WSDL is actually accessible the above is the likely culprit.
>
>Alterntives are to skip the SOAP Toolkit and use possibly a .NET Web Service client and talk to it via COM Interop.
>
>http://www.west-wind.com/presentations/foxdotnetwebservices/
>
>+++ Rick ---
>
>>Hi,
>>
>>I'm having a problem trying to call a web service.
>>
>>1) When the web service's URL is set to use http there is no problem accessing the methods and things work fine.
>>
>>2) When the web service is changed to use https, VFP cannot communicate with it. In particular, if I use the XML Web Services utility in the Task Pane Manager, it throws the following error:
>>
>>

>>Error generating IntelliSense scripts. Check for a valid WSDL URL location or invalid WSDL content. The WSDL file may have also been in use -- try regenerating the XML Web Service files again.
>>
>>
>>
>>WSDLReader : WSDLReader:XML Parser failed at linenumber 0, lineposition 0, reason is: The download of the specified resource has failed.
>>
>> HRESULT=0x1: Incorrect function.
>>
>> - WSDLReader:Loading of the WSDL file failed HRESULT=0x80070057: The parameter is
>>
>>

>>
>>Any ideas what may be causing this behavior?
>>
>>Regards,
>>
>>Mike