The RM destination received a CreateSequenceResponse message. The RM destination does not process CreateSequenceResponse messages.
The return value of type {0} on method {1} of interface {2} is not web services compliant due to the following reason: {3} ...
The returned wsrm:{0}Response message was missing the required wsa:RelatesTo header. This is a violation of the WS-Addressing ...
The returned {0}Response was carrying the a wsa:RelatesTo header that does not correlate with the wsa:MessageId header on ...
The Revision number (4th part) in Version field of Microsoft Common Language Runtime dependency section must be zero: {0}. ...
The RM destination received a CreateSequenceResponse message. The RM destination does not process CreateSequenceResponse ...
The RM destination received a TerminateSequenceResponse message. The RM destination does not process TerminateSequenceResponse ...
The RM destination received an CloseSequenceResponse message. The RM destination does not process CloseSequenceResponse messages. ...
The RM Destination requires the WS-SecureConversation protocol in the binding. This is likely caused by a binding mismatch. ...
The RM source does not support an RM destination initiated close since messages can be lost. The reliable session cannot ...