The message with Action '{0}' cannot be processed at the receiver, due to a ContractFilter mismatch at the EndpointDispatcher. This may be because of either a contract mismatch (mismatched Actions between sender and receiver) or a binding/security mismatch between the sender and the receiver. Check that sender and receiver have the same contract and the same binding (including security requirements, e.g. Message, Transport, None).
The message time to live (TTL) is too large. The message cannot be sent. The message TTL cannot exceed the Int32 maximum ...
The message type '{0}' is not allowed for the '{1}' operation. Valid message types are: '{2}, {3}'. To close the WebSocket, ...
The message version of the outgoing message ({0}) does not match that of the encoder ({1}). Make sure the binding is configured ...
The message with Action '{0}' cannot be processed at the receiver because this Action is reserved for the connection opening ...
The message with Action '{0}' cannot be processed at the receiver, due to a ContractFilter mismatch at the EndpointDispatcher. ...
The message with To '{0}' cannot be processed at the receiver, due to an AddressFilter mismatch at the EndpointDispatcher. ...
The MessageFilterTable has not been configured for this RoutingService. Verify that either the routing behavior filterTableName ...
The metadata document has Schema elements in the '{0}' and '{1}' namespaces, but only a single namespace per document is ...
The metadata for this file is corrupted. Invalid metadata token. Seek to row {0}, but table {1} ({2}) only has {3} rows. ...