Microsoft KB Archive/811987

= BUG: SOAP Toolkit 2.0 Client Does Not Respond When it Makes a Secure Sockets Layer Connection to a Port Other than to Port 443 =

Article ID: 811987

Article Last Modified on 5/30/2007

-

APPLIES TO

 Microsoft SOAP Toolkit 2.0, when used with:  Microsoft Windows NT 4.0 Service Pack 6a

 Microsoft Windows 2000 Standard Edition 

-



SYMPTOMS
When a Microsoft SOAP client that is implemented with the SOAP Toolkit 2.0 tries to make a Secure Sockets Layer (SSL) connection to communicate with a secure SOAP Service on a port other than the default SSL port 443, the SOAP client does not respond. You receive the following error message:

C++ HRESULT: 0x800A151E, HTTP_CONNECTION_FAILED

VB Error: Run-time error '5406': Application defined or object defined error.

If you use the high-level API in this scenario, the SoapClient object has the following Detail property:

Client:Sending the Soap message failed or no recognizable response was received HRESULT=0x800A151E - Client:Connection failed.

HRESULT=0x800A151E



CAUSE
The SOAP Toolkit 2.0 HttpConnector implementation on Microsoft Windows 2000 and Microsoft Windows NT 4.0 ignores the port information that an https URL provides. The HttpConnector implementation always tries to make the SSL connection on the default SSL port 443.



STATUS
Microsoft has confirmed that this is a bug in the Microsoft products that are listed at the beginning of this article.

