The operation '{0}' could not be completed because the sessionful channel timed out waiting to receive a message. To increase the timeout, either set the receiveTimeout property on the binding in your configuration file, or set the ReceiveTimeout property on the Binding directly.
The one-way operation '{1}' on ServiceContract '{0}' is configured for transaction flow. Transactions cannot be flowed over ...
The only additional connection string keyword that may be used when requesting the context connection is the Type System ...
The open operation did not complete within the allotted timeout of {0}. The time allotted to this operation may have been ...
The opening handshake properties associated with the current WebSocket connection are not available. The most likely cause ...
The operation '{0}' could not be completed because the sessionful channel timed out waiting to receive a message. To increase ...
The operation '{0}' could not be invoked because the property '{1}' on the OperationContract is set to '{2}'. To invoke this ...
The operation '{0}' could not be loaded because it has a parameter or return type of type System.ServiceModel.Channels.Message ...
The operation '{0}' could not be loaded because it specifies "rpc-style" in "literal" mode, but uses message contract types ...
The operation '{0}' in implemented contract '{1}' requires transaction to be flowed, but the Receive activity is NOT in TransactedReceiveScope. ...