Hello, I am having a few problems with my App Pools in MS Exchange not recyling properly and I am not sure how to resolve/troubleshoot the issue. I am getting the following two errors in my event logs:Log: SystemSource: WASID: 5013A process serving application pool 'MSExchangeSyncAppPool' exceeded time limits during shut down. The process id was '8872'. Log: ApplicationSource: IIS-W3SVC-WPID: 2262ISAPI 'C:\Windows\Microsoft.NET\Framework64\v2.0.50727\aspnet_isapi.dll' reported itself as unhealthy for the following reason: 'Deadlock detected'.Any thoughts on how to resolve this? This happens anywhere from 5-20 times a day. Thoughts? Thanks!

It should definitely *not* need to be recycled 5 - 20 times per day. What version of Exchange? Service Pack? Are hot fixes applied?Jim McBee - Blog - http://mostlyexchange.blogspot.com

Thanks for the reply! Okay, yeah,it didn't seem right to me (it did it ungracefully 10 times just over the night last night). I am running Exchange 2007 SP1 with Update Rollup 8 applied (should be the latest that i am aware of). The OS is Windows Server 2008 x64 SP2.There are not any specific hotfixes applied. Thanks!

Hi, This problem might occur because ASP.NET limits the number of worker threads and completion port threads that a call can use to execute requests. I think it could be a asp.net related issue. I recommend you to follow the steps in kb 828222 to generate the dump file and then post the issue in IIS.net forum to get relevant help. Note: Please ensure that theres no other web application installed on the IIS server. We may need to perform a clean-boot to see if the issue caused by the 3rd party applications. 828222 How to generate a dump file when ASP.NET deadlocks in IIS 6.0http://support.microsoft.com/default.aspx?scid=kb;EN-US;828222 Microsoft IIS forum http://forums.iis.net/ More information to share with you: Contention, poor performance, and deadlocks when you make Web service requests from ASP.NET applications http://support.microsoft.com/kb/821268 ASP.NET Thread Usage on IIS 7.0 and 6.0http://blogs.msdn.com/tmarq/archive/2007/07/21/asp-net-thread-usage-on-iis-7-0-and-6-0.aspx 1. Set the values of the maxWorkerThreads parameter and the maxIoThreads parameter to 100. 2. Set the value of the maxconnection parameter to 12*N (where N is the number of CPUs that you have). 3. Set the values of the minFreeThreads parameter to 88*N and the minLocalRequestFreeThreads parameter to76*N. 4. Set the value of minWorkerThreads to 50. Note: minWorkerThreads is not in the configuration file by default. You may need to add it. Regards, Xiu

I'm faced with the same problem and try to understand the basics (IIS for exchange server) involved here. Is there a document that described the optimal settings for IIS (ASP.NET) for exchange (2010 SP1 on Server 2008R2 SP1)? In the above mentioned document are (atleast for me) too many exchange-IIS unknows (asynchronous request, versions of framework,...). Regards Daniel