It could be caused by a race condition where the client is establishing a channel for receiving notifications from the server when the channel already exists. This issue is scheduled to be fixed in Exchange 2010 server update rollup 5.
 
 
Advertisements