Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

A few times a day, our (IIS 6.0) website is randomly throwing the following error and becomes completely unavailable for 5-15 minutes at a time while the application is recycled:

ISAPI 'c:\windows\\framework\v2.0.50727\aspnet_isapi.dll' reported itself as unhealthy for the following reason: 'Deadlock detected'.

The website ran for months on the exact same server in beta without problem - but the problem started over the weekend when we made the site live. The live site is under some load but less than many of our other production websites.

How should I attack this problem? I've looked into orphaning the worker process and creating a dump file - but I'm not sure how to analyze that. Any advice or information is appreciated. Thanks, Shane

share|improve this question
Refer to if you haven't already. – Chris W. Rea May 25 '10 at 14:15

Here is a good article on starting with analyzing dumps Hang caused by GC - XML Deadlock. You can also look for some examples here

share|improve this answer
+1 for any articles that link to Tess Ferrandez :) The goddess of debugging! – Pure.Krome May 25 '10 at 14:55

I would suggest upgrading the OS to 2008 R2 and IIS 7.5

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.