The incoming message was signed with a token which was different from what used to encrypt the body. This was not expected.
The importing constructor on type '{0}' is using ImportManyAttribute on parameter '{1}' with a non-assignable type. On constructor ...
The incoming HTTP message, with content type '{0}', was mapped to an unknown content format '{1}' by the ContentTypeMapper. ...
The incoming message contains a SOAP header representing the WS-Addressing '{0}', yet the HTTP transport is configured with ...
The incoming message has an unexpected message format '{0}'. The expected message formats for the operation are {1}. This ...
The incoming message was signed with a token which was different from what used to encrypt the body. This was not expected. ...
The incoming message with action '{0}' contains a callback context header with name '{1}' and namespace '{2}'. Callback context ...
The incoming message with action could not be processed because it is targeted at a request-reply operation, but cannot be ...
The incoming policy contains options which are not supported by this version of Windows CardSpace. For more information, ...
The incoming transaction cannot be deserialized. The transaction header in the message was either malformed or in an unrecognized ...