A SafeHandle or CriticalHandle of type '%1$s' failed to properly release the handle with value 0x%2$p. This usually indicates that the handle was released incorrectly via another means (such as extracting the handle using DangerousGetHandle and closing it directly or building another SafeHandle around it.)
A response message was received, but there are no outstanding requests waiting for this message. The message is being dropped. ...
A response was received from a one-way send over the underlying IRequestChannel. Make sure the remote endpoint has a compatible ...
A return sequence was not offered by the create sequence request. The create sequence response cannot accept a return sequence. ...
A return sequence was offered by the create sequence request but the create sequence response did not accept this sequence. ...
A SafeHandle or CriticalHandle of type '%1$s' failed to properly release the handle with value 2$p. This usually indicates ...
A SamlAssertion requires at least one statement. Ensure that you have added at least one SamlStatement to the SamlAssertion ...
A security policy was imported for the endpoint. The security policy contains requirements that cannot be represented in ...
a security transparent member, uses security critical attribute constructor {1}. Mark this target as security critical or ...
a security transparent member, uses security critical attribute field {1}. Mark this target as security critical or security ...