Incoming message for operation '{0}' (contract '{1}' with namespace '{2}') contains an unrecognized http body format value '{3}'. The expected body format value is '{4}'. This can be because a WebContentTypeMapper has not been configured on the binding. See the documentation of WebContentTypeMapper for more details.
In the Web Site Administration Tool, on the Provider tab, your first choice is whether you want to use the same provider ...
In this example, both debugging and trace are enabled, tracing is displayed on pages that are requested from the Web server ...
Include the specified assembly when resolving dependent assemblies during annotation. Reference assemblies are given priority ...
Incoming message does not contain a WebBodyFormatMessageProperty. This can be because a WebContentTypeMapper or a WebMessageEncodingBindingElement ...
Incoming message for operation '{0}' (contract '{1}' with namespace '{2}') contains an unrecognized http body format value ...
Incoming message for operation '{0}' (contract '{1}' with namespace '{2}') does not contain a WebBodyFormatMessageProperty. ...
Incoming message for operation '{0}' contains an unrecognized http body format value '{1}'. The expected body format value ...
Inconsistent sequencing: if used on one of the class's members, the '{0}' property is required on all particle-like members, ...
Incorrect mapping of composite key columns. {0} Columns ({1}) in table {2} are mapped to properties ({3}) in {4} and columns ...