Exception in Push notification client

Sep 15, 2009 at 2:06 PM

I tried the push notification client sample on exchange 2010. I am getting the following exception,

System.ServiceModel.FaultException: The message with Action '' 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).

What is the cause of the exception? And how to resolve the exception?

Sep 15, 2009 at 2:53 PM

I haven't tested the component with Exchange 2010 yet... seems that Microsoft
hast changed the interface. I will try that soon.

Kind regards,
Nov 15, 2009 at 6:36 PM
Edited Nov 15, 2009 at 6:36 PM

Hi brahan,

I've now analyzed the problem and I believe there is a breaking change in how Exchange 2010 sends the notifications. It seems that Exchange does no longer send a SOAPAction header with its notification. In this case, WCF does not now which method handles the mesage.

Until I publish a new release you can fix this yourself by changing the line

[OperationContract(Action = "http://schemas.microsoft.com/exchange/services/2006/messages/SendNotification", ReplyAction = "*")]

in the file INotificationServicePort.cs in the InfiniTec.Exchange.Notifications folder to

[OperationContract(Action = "*", ReplyAction = "*")]

Kind regards,

Mar 22, 2010 at 6:28 PM

It seems that Exchange Server 2010 misses the SOAPAction header in the push event notifications package