wcf - ContractFilter mismatch at the EndpointDispatcher exception

Question

I have the following scenario that I'm trying to test for:

1. A common WSDL
2. WCF endpoint that implements objects based on the WSDL and is hosted in IIS.
3. A client app that uses a proxy based off the WSDL to create requests.

When I make a web service call from the client to the service endpoint, I get the following exception:

{"The message with Action 'http://IMyService/CreateContainer' cannot be processed at the receiver, due to a ContractFilter mismatch at the EndpointDispatcher. This may be because of either a contract mismatch (mismatched Actions between sender and receiver) or a binding/security mismatch between the sender and the receiver. Check that sender and receiver have the same contract and the same binding (including security requirements, e.g. Message, Transport, None)."}

I started using MS Service Trace Viewer, but not sure where to look. While looking at classes in client and the endpoint, they appear identical.

How does one begin to debug this problem?

What are some possible causes to this exception?

Answer 1

A "ContractFilter mismatch at the EndpointDispatcher" means the receiver could not process the message because it did not match any of the contracts the receiver has configured for the endpoint which received the message.

This can be because:

• You have different contracts between client and sender.
• You're using a different binding between client and sender.
• The message security settings are not consistent between client and sender.

Have at look at the EndpointDispatcher class for more information on the subject.

So:

Make certain that your client and server contracts match.

• If you've generated your client from a WSDL, is the WSDL up-to-date?
• If you've made a recent change to the contract, have you deployed the right version of both client and server?
• If you've hand-crafted your client contract classes, make sure the namespaces, elements names and action names match the ones expected by the server.

Check the bindings are the same between client and server.

• If you're using a .config file to manage your endpoints, make sure the binding elements match.

Check the security settings are the same between client and server.

• If you're using a .config file to manage your endpoints, make sure the security elements match.