IIS 5 & IIS 6
ASP.NET not working (Deadlock?)
Last post Jan 27, 2009 05:17 AM by Paul Lynch
May 24, 2008 01:25 AM|JohnGesch|LINK
This just happened last night and I'm running in circles trying to fix it.
It seems everything is working on the server except ASP.NET. Websites all completely down that use this (others/static work though).
I am using Windows Server 2003, IIS6 and ASP.NET 1, 2 & 3.5.
The only errors I've been able to see in the Event log are:
Description: ISAPI 'c:\windows\microsoft.net\framework\v2.0.50727\aspnet_isapi.dll' reported itself as unhealthy for the following reason: 'Deadlock detected'.
Description: A process serving application pool 'DefaultAppPool' exceeded time limits during shut down. The process id was '2712'.
I've seen http://support.microsoft.com/kb/821268 and applied the recommendations - but it's made no obvious difference.
Starting to tear my hair out on this. Any help at all would be great.
May 24, 2008 07:27 AM|JohnGesch|LINK
I ended up having to complete clear ASP.NET 2+ and reinstall it. There was some software I needed to do this to do a clean up of ASP.NET to remove it properly first but now everything is ok.
Jun 03, 2008 08:47 AM|Terry8|LINK
Are you still having problems with deadlock?
Jun 09, 2008 12:42 PM|rfwilliams777|LINK
You did set up different AppPools for the different versions of ASP.NET, correct? We have ours set up with the default app pool for .Net 1.1. Then we created an AppPool for .net 2.0 and also others for other sites/or needs.
Jun 09, 2008 01:09 PM|JohnGesch|LINK
Hi Robert Thanks for replying.
I've certainly had the AppPools setup separately... and it was working fine - and still can't see why it stopped though a few times simply removing and reinstalling the .NET framework had the websites working again.
Unfortunately the answer is not at all a simple one, and I have had an MCSE look at it and was unable to fix it... or even explain why it was acting the way it was.
Have even wiped and reinstalled Windows Server 2003 - again, got the website working - for about 10 hours but then stopped again with pretty much no error messages. Reinstalled IIS6 - but now that's not even working! It sees the files on the websites (eg.
images) but not the default pages which are there.
I have yet another person about to look into it in more depth. If they can't get it sorted I will be left with next to no options as the 3 weeks our online membership-based business has been down has left us near crippled.
Jun 09, 2008 01:16 PM|rfwilliams777|LINK
How "robust" is your web application or applications? A web server shouldn't be going down that quickly and that often. I've seen them slow down, but not like what you're talking about. Let us know if you need any help.
Jan 27, 2009 12:08 AM|GEORGEPLAZAR|LINK
I am also facing the same problem can you please help me out ,
Jan 27, 2009 05:17 AM|Paul Lynch|LINK
There's no simple fix for this issue, you need to find out why your code is causing this to happen. These articles should help get you started :
Contention, poor performance, and deadlocks when you make Web service requests from ASP.NET
How to generate a dump file when ASP.NET deadlocks in IIS 6.0