The message could not be processed. This is most likely because the action '{0}' is incorrect or because the message contains an invalid or expired security context token or because there is a mismatch between bindings. The security context token would be invalid if the service aborted the channel due to inactivity. To prevent the service from aborting idle sessions prematurely increase the Receive timeout on the service endpoint's binding.
The message contains a callback context header with an endpoint reference for AddressingVersion '{0}'. Callback context can ...
The message contains a callback context message property. Callback context can be transmitted only when the ContextBindingElement ...
The message could not be dispatched because the service at the endpoint address '{0}' is unavailable for the protocol of ...
The message could not be dispatched because the transport manager has been stopped. This can happen if the application is ...
The message could not be processed. This is most likely because the action '{0}' is incorrect or because the message contains ...
The message could not be sent because its size ({0}) was larger than the maximum supported datagram size for this transport ...
The message could not be sent over the network adapter with index {0} because the index specified is invalid or the transport ...
The message could not be transferred within the allotted timeout of {0}. There was no space available in the reliable channel's ...
The message is not encrypted with a key derived from the encrypted key. The binding's token parameter '{0}' requires key ...