The transport configured on this binding does not appear to support the CompressionFormat specified ({0}) on the message encoder. To resolve this issue, set the CompressionFormat on the {1} to '{2}' or use a different transport.
The transaction associated with this session channel has been rolled back because Abort was called on the session channel ...
The transaction cannot begin. The current data connection does not support transactions or the current state is not allowing ...
The transaction header '{0}' within the namespace '{1}' was not understood by the service. The client and the service must ...
The transport channel detected a poison message. This occurred because the message exceeded the maximum number of delivery ...
The transport configured on this binding does not appear to support the CompressionFormat specified ({0}) on the message ...
The TransportBindingElement of type '{0}' in this CustomBinding returned a null or empty string for the Scheme. TransportBindingElement's ...
The two ends of a ResourceAssociationSet cannot both have the same ResourceType and ResourceProperty. If this is a self-referencing ...
The type '%2!ls!' in '%1!ls!' conflicts with the imported namespace '%4!ls!' in '%3!ls!'. Using the type defined in '%1!ls!'. ...
The type '%3!ls!' must be a non-nullable value type in order to use it as parameter '%2!ls!' in the generic type or method ...