A fix for Exchange Server 2016Įffective October 17, 2018, Microsoft added a fix for Exchange Server 2016 to older KB articles with the Workaround for Exchange Server 2013. You should regularly empty the ActiveSync application pool for all servers to release individual (pending) commands.įor more information about configuring an application pool to automatically recycle at regular intervals, see the document ' Recycling Settings for an Application Pool ' on the Microsoft Docs Web site. Workaround for Exchange Server 2013įor Exchange Server 2013, Microsoft describes only a workaround. Microsoft classifies this as a known problem that occurs when ActiveSync ping commands get stuck in the application pool. The netstat -anob command can display many connections in a CLOSE_WAIT state.The counter W3SVC_W3WP/Active Requests for the instance MSExchangeSyncAppPool shows a steadily increasing value over several days or weeks.There is an exhaust of the TCP port due to the large number of requests in ActiveSync.NET CLR value Memory/% Time in the GC counter for the w3wp instance corresponding to the ActiveSync application pool is unusually high. The ActiveSync application pool consumes a lot of disk space.Event ID 4227 is logged within the system log of the Event Viewer.

In addition, the following behavior may occur: This problem occurs after the ActiveSync application pool has been running for some time, typically several weeks.

In addition, all features of the CAS role will no longer work. In a Microsoft Exchange Server 2016 or Exchange Server 2013 environment, ActiveSync clients will not be able to connect or there will be delays when users synchronize their mobile devices.

Microsoft describes a scenario that can occur in environments with Exchange Server 2016 or Exchange Server 2013 in conjunction with an Active Sync client in a KB article titled ActiveSync clients cannot connect or synchronizing is delayed in an Exchange Server environment (4456227).

Yesterday night on Twitter made me aware of an Exchange server issue and a kb article from Microsoft.ĪCTIVE SYNC CLIENT CONNECTION OR SYNCHRONIZATION ISSUES:

Microsoft activesync problem