Error details: System.ServiceModel.CommunicationException: An error occurred while making the HTTP request to https://xxxxxxxxxxxx. This could be due to the fact that the server certificate is not configured properly with HTTP.SYS in the HTTPS case. This could also be caused by a mismatch of the security binding between the client and the server. ---> System.Net.WebException: The underlying connection was closed: An unexpected error occurred on a send. ---> System.IO.IOException: Received an unexpected EOF or 0 bytes from the transport stream.
I started with the wcf-basichttp and have also tried the wcf-custom transport types and various transport level security options with the same results. After some digging around and trying the same call through code, I replicated a similar error in code for the web service call and resolved it by adding the following:
ServicePointManager.SecurityProtocol = SecurityProtocolType.Ssl3;
From what I have understood from researching this issue, this has to do with Windows Vista/2008 automatically using TLS 1.0 during the SSL communication and if the end web service doesn't support it, windows will use SSL3. In some cases if the endpoint ends the connection and doesn't support this type of handshake, the above error is raised. Is there a way to setup the WCF send port with some custom binding to accommodate what the above line of code does? Any help would be appreciated
- Moved by Ben Cline1Moderator Sunday, October 11, 2009 2:37 AM Related to adapters (From:BizTalk Server General)