The received message type '{2}' is invalid after calling {0}. {0} should only be used if no more data is expected from the remote endpoint. Use '{1}' instead to keep being able to receive data but close the output channel.
The ReceiveContext delete operation failed because the message with Id '{0}' could not be received from the lock subqueue. ...
The ReceiveContext unlock operation failed because the message with Id '{0}' could not be moved from the lock subqueue to ...
The received derived key token has a invalid generation value specified. Value: {0}. The value should be greater than or ...
The received derived key token has a invalid offset value specified. Value: {0}. The value should be greater than or equal ...
The received message type '{2}' is invalid after calling {0}. {0} should only be used if no more data is expected from the ...
The received message type is invalid after calling {0}. {0} should only be used if no more data is expected from the remote ...
The received transaction has an isolation level of '{0}' but the service is configured with a TransactionIsolationLevel of ...
The receiver returned an error indicating that the content type was missing on the request to {0}. See the inner exception ...
The recipient did not provide its certificate. This certificate is required by the TLS protocol. Both parties must have access ...