The operation '{0}' in service contract '{1}' is different in '{2}' and '{3}'. Check the input, output and fault messages of the operation.
The operation '{0}' could not be invoked because the property '{1}' on the OperationContract is set to '{2}'. To invoke this ...
The operation '{0}' could not be loaded because it has a parameter or return type of type System.ServiceModel.Channels.Message ...
The operation '{0}' could not be loaded because it specifies "rpc-style" in "literal" mode, but uses message contract types ...
The operation '{0}' in implemented contract '{1}' requires transaction to be flowed, but the Receive activity is NOT in TransactedReceiveScope. ...
The operation '{0}' in service contract '{1}' is different in '{2}' and '{3}'. Check the input, output and fault messages ...
The operation '{0}' on callback contract '{1}' is configured with TransactionAutoComplete set to false. TransactionAutoComplete ...
The operation '{1}' on contract '{0}' is configured with TransactionAutoComplete set to false and the InstanceContextMode ...
The operation '{1}' on contract '{0}' is configured with TransactionAutoComplete set to false but SessionMode is not set ...
The operation '{1}' on contract '{0}' is configured with TransactionAutoComplete set to true and with TransactionScopeRequired ...