Using MSSoap with VB6 and HTTPS

[mtber]

I am trying to get my VB6 application to interact with a webservice using MSSOAP. My problem occures when i have to change the URL of the webservice to HTTPS. It works fine when i use HTTP but once the application goes to the Production server it will need to be HTTPS. Below is the structure of my code and i notice that the problem occures when i go to pass my parameters to the webservice i get an error, I have also placed the text from the error below my code. Can anyone Help? Thanks.

Dim pstrWebservice As New SoapClient30
Dim pstrResponse As String

Set pstrWebservice = CreateObject("MSSOAP.SoapClient30")

pstrWebservice.MSSoapInit "https://Server-Name/Root-Folder/file.cfc?wsdl"

pstrResponse = (pstrWebservice.webservice(Param1, Param2, Param3, Param4)
[/CODE]

[CODE]
Run-time error '-2147467259(80004005):

Attachment:Maximum retry on the connection exceeded. HRESULT=0x80004005: Unspecified error
-Client:An unanticipated error occured during the processing of this request. HRESULT=0x80004005: Unspecified error
-Client:Sending the Soap message failed or no recognizable response was received HRESULT=0x80004005: Unspecified error
-Client:Unspecified client error. HRESULT=0x80004005: Unspecified
[/CODE]

[garethevans1986]

This may sound daft and doesn't answer your question but why the need to use VB6?

GE

[mtber]

  On 22/09/2011 at 15:43, garethevans1986 said:

This may sound daft and doesn't answer your question but why the need to use VB6?

GE

I inheritad the application from another developer, The VB application currently retreives information from an access database, but access database is in the process of being replaced with a coldfusion application and the VB6 application still needs to have connectivity. VB6 is not my first choice for doing this but i don't have any other options untill the VB application is converted to coldfusion.

[Eric Veteran]

Is the web server and application set up for https?

Also, try using the FQDN for the server instead of the domain name.

This MSDN article may help even though it's a bit old.