I'm having a problem using a WCF call from a Windows service to my WCF service running on my web server. This call has been working for a number of weeks, but then stopped working all of a sudden, and has not worked since.
The exception I'm getting is:
General Error Occurred System.ServiceModel.CommunicationException: An error occurred while making the HTTP request
and then it says
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.
The security I'm using on both ends is wsHttpBinding, without any kind of encryption. It also is just using HTTP - not HTTPS, so I'm not sure why it's complaining about HTTPS.
The rest of the inner exception stack is:
SystemNet.WebException: The underlying connection was closed: An unexpected error occurred on a send. ---> System.IO.IOException: Unable to write data to the transport connection: An invalid argument was supplied. ---> System.Net.Sockets.SocketException: An invalid argument was supplied at System.Net.Sockets.Socket.MultipleSend(BufferOffsetSize[] buffers, SocketFlags socketFlags) at System.Net.Sockets.NetworkStream.MultipleWrite(BufferOffsetSize[] buffers)
I should also note that the point in my program where this occurs is on the "Execute" line of the call to the web service - that is, right as soon as I call the web service and pass it the wrapped up DataContract object, it blows up.
All this service is doing is getting passed a large amount of XML (passed as a .NET object to the call on the client side), which it then does some work with. Probably about 100-200k of XML is being transmitted. I've raised the limits for the data sizes on both ends to over 6 megs, but that didn't seem to help.
Instant Notification Error: Your message has been created but instant notification failed. Recipients may be delayed in receiving this message.
-Could not establish trust relationship for the SSL/TLS secure channel with authority 'localhost'.
ERROR::2018-04-20 15:49:10.776::2018-04-20 07:49:10.776::An error occurred while making the HTTP request to https://lvs-gstqa-001/xxx/xxx.svc. 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.
-ex1 {"An error occurred while making the HTTP request to https://lvs-gstqa-001/xxx/xxx.svc. 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.Exception {System.ServiceModel.CommunicationException}
-InnerException {"The underlying connection was closed: An unexpected error occurred on a send."} System.Exception {System.Net.WebException}
+InnerException {"Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host."} System.Exception {System.IO.IOException}
+InnerException {"An existing connection was forcibly closed by the remote host"} System.Exception {System.Net.Sockets.SocketException}
Any ideas?
Solution:
We had this issue as the host server had been updated to use TSLV1.2 and we were connecting using standard SSL. This was an update made as part of pen testing of the sites. We saw the issue in code connection, but not browsers going to the wsdl. Below code resolved:
if (System.Net.ServicePointManager.SecurityProtocol == (SecurityProtocolType.Ssl3 | SecurityProtocolType.Tls))
System.Net.ServicePointManager.SecurityProtocol = SecurityProtocolType.Tls | SecurityProtocolType.Tls11 | SecurityProtocolType.Tls12;
Taken from here: How do I disable SSL fallback and use only TLS for outbound connections in .NET? (Poodle mitigation)