ActiveSync clients cannot connect or synchronizing is delayed in an Exchange Server environment

Applies to: Exchange Server 2016Exchange Server 2013


In a Microsoft Exchange Server 2016 or Exchange Server 2013 environment, ActiveSync clients cannot connect or they experience delays when users synchronize their mobile devices. Besides, all functions of the CAS role will stop to work. This issue occurs after the ActiveSync application pool runs for some time, usually for several weeks. Additionally, you may experience the following behavior:

  • Event ID 4227 is logged in the System log of the Event Viewer.
  • The ActiveSync application pool consumes lots of memory.
  • The .NET CLR Memory/% Time in GC counter for the w3wp instance that corresponds to the ActiveSync application pool is unusually high.
  • TCP port exhaustion occurs because of the large number of requests in ActiveSync.
  • The W3SVC_W3WP/Active Requests counter for the MSExchangeSyncAppPool instance shows a steadily increasing value over several days or weeks.
  • The netstat -anob command may show many connections in a CLOSE_WAIT state.


This is a known issue that occurs when ActiveSync Ping commands become stranded in the application pool.


For Exchange Server 2013, to work around this issue, periodically cycle the ActiveSync application pool for all the servers to release the stranded commands.

For more information about how to configure an application pool to automatically recycle at regular intervals, see the "Recycling Settings for an Application Pool <recycling>" topic on the Microsoft Docs website.


For Exchange Server 2016, to resolve this issue, install Cumulative Update 11 for Exchange Server 2016 or a later cumulative update for Exchange Server 2016.


Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.


Learn about the terminology that Microsoft uses to describe software updates.