Identity check failed for outgoing message. The expected DNS identity of the remote endpoint was '{0}' but the remote endpoint provided DNS claim '{1}'. If this is a legitimate remote endpoint, you can fix the problem by explicitly specifying DNS identity '{1}' as the Identity property of EndpointAddress when creating channel proxy.
Identity certificate with subject name '%1' and thumbprint '%2' does not provide '%3' among its EnhancedKeyUsages. Process ...
Identity certificate with subject name '%1' and thumbprint '%2' does not provide '%3' among its KeyUsages. Process Name: ...
Identity certificate with subject name '%1' and thumbprint '%2' does not provide '%3' among its KeyUsages. Process Name: ...
Identity check failed for incoming message. The expected DNS identity of the remote endpoint was '{0}' but the remote endpoint ...
Identity check failed for outgoing message. The expected DNS identity of the remote endpoint was '{0}' but the remote endpoint ...
IDictionary parameter contains at least one entry that is not valid. Ensure all values are consistent with the object's properties. ...
If a data source does not return ICollection and cannot return the total row count, it cannot be used by the {0} to implement ...
If a document-literal binding in a DESCRIPTION does not specify the parts attribute on a soapbind:body element, the corresponding ...
If a virtual method has a LinkDemand, in many cases, so should any override of it, and if an override has a LinkDemand, so ...