WCF-WSHttp Adapter issue

Kumar, Chandra [OCIO] 1

Hi,
I am getting this error with Biztalk 2020 while consuming the wcf service , WCF service is returning the data successfully but BizTalk is generating this error.

A message sent to adapter "WCF-WSHttp" on send port "" with URI "" is suspended.
Error details: System.ServiceModel.CommunicationException: The underlying connection was closed: A connection that was expected to be kept alive was closed by the server. ---> System.Net.WebException: The underlying connection was closed: A connection that was expected to be kept alive was closed by the server. ---> System.IO.IOException: Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host. ---> System.Net.Sockets.SocketException: An existing connection was forcibly closed by the remote host
at System.Net.Sockets.Socket.EndReceive(IAsyncResult asyncResult)
at System.Net.Sockets.NetworkStream.EndRead(IAsyncResult asyncResult)
--- End of inner exception stack trace ---
at System.Net.Sockets.NetworkStream.EndRead(IAsyncResult asyncResult)
at System.Net.Connection.ReadCallback(IAsyncResult asyncResult)
--- End of inner exception stack trace ---
at System.Net.HttpWebRequest.EndGetResponse(IAsyncResult asyncResult)
at System.ServiceModel.Channels.HttpChannelFactory`1.HttpRequestChannel.HttpChannelAsyncRequest.CompleteGetResponse(IAsyncResult result)
--- End of inner exception stack trace ---

Colin Dijkgraaf 1,346 Reputation points

2021-11-07T19:57:16.2+00:00

Usually that sort of error is caused at the API you are connecting to, for some reason it is closing the connection. So you will probably have to look at the API end, rather than the BizTalk end. The most you can do at the BIzTalk end is enable WCF Logging see How to Diagnose Problems with the WCF Adapters
Amit Patel 1 Reputation point

2023-04-20T06:37:24.9633333+00:00

I am not using api for this we are sending this data to blob storage still we are getting this error. any reason for this
Colin Dijkgraaf 1,346 Reputation points

2023-04-20T20:26:38.83+00:00

I've usually seen that sort of error where the TLS version being used was lower that what was supported. Sometimes you have to configure .Net to use the correct version of TLS, see https://www.biztalk360.com/blog/configure-tls-1-2-on-biztalk-server-with-powershell/