Forum Discussion
VincentBurle83
Feb 25, 2022Copper Contributor
Lot of eventID 4999 related to ActiveSync on my Exchange Servers
Hello all, I'm Vincent and I'm Exchange administrator in my International Research Organization. Our Exchange farm is composed of 4 Exchange Server 2016 Enterprise CU 22. I recently noticed a l...
cmillerLCE
Apr 27, 2022Brass Contributor
I'm seeing the same exact errors with Exchange 2016 CU22. I recently upgraded to CU22 with the naive optimism that it would be resolved with that CU but no dice. Has anyone else found a fix for these errors? I'm not getting any complaints but if that AppPool is indeed crashing and restarting repeatedly through the day I can't imagine that's a good thing.
- BroBiasNov 01, 2022Copper ContributorSame issue here with MSExchangeSyncAppPool, crashing & recycling 100-120 times a day without a followable reason. Would be nice to get some experience exchange on troubleshooting this 😕 ...
- BroBiasNov 01, 2022Copper ContributorVincentBurle83
Sry, have 2 similar accounts here 😄
Yes, i can confirm this as well. ActiveSync is healthy in general. However, i also discovered a bunch of 1040 events which result of conflicts between http(s)_responses for heartbeat intervalls. timeout on FW is lower than on EXCH which results in 1040 events and maybe connection overloads on the MSEchangeSyncAppPool which then results in 4999 -> recycling.
My best logical conclusion at the moment. However, i cannot adapt http_response_timeout on our fw only for a dedicated target (activesync-url) and it's not an option to change this for entire http_proxy.
Any help is welcome ^^