The remote endpoint of the socket ({0}) did not respond to a close request within the allotted timeout ({1}). It is likely that the remote endpoint is not calling Close after receiving the EOF signal (null) from Receive. The time allotted to this operation may have been a portion of a longer timeout.
The remote endpoint has sent an fault message with an unexpected sequence identifier over a session. The fault may be intended ...
The remote endpoint has sent an unrecognized fault with namespace, {0}, name {1}, and reason {2}. The channel could not be ...
The remote endpoint has sent an unrecognized fault with namespace, {0}, name {1}, and reason {2}. The reliable session was ...
The remote endpoint no longer recognizes this sequence. This is most likely due to an abort on the remote endpoint. {0} The ...
The remote endpoint of the socket ({0}) did not respond to a close request within the allotted timeout ({1}). It is likely ...
The remote endpoint replied to a request for a one way session with an offer for a two way session. This is a WS-ReliableMessaging ...
The remote endpoint replied to a request for a two way session with an offer for a one way session. This is a WS-ReliableMessaging ...
The remote endpoint replied to a request for a two way session with an offer for a one way session. This is likely caused ...
The remote endpoint replied to the request for a sequence with a response that could not be parsed. See inner exception for ...