IIS 5 & IIS 6
IIS 6 'Deadlock Detectd'
Last post Sep 12, 2008 05:44 AM by WenJun Zhang - MSFT
Sep 06, 2008 04:50 AM|ksivasenthil|LINK
I have browsed through list of similar posting on the 'Deadlock Detected' and 'aspnet_isapi.dll' reporting itself unhealthy.
All of them point to the Microsoft KB Article 828222 and 821268.
We tried both of them.
Solution proposed in the KB 821268 - i.e. changes to connection limits and thread limits
did not bring any significant change to the problem that we are trying to solve. The 'deadlock' is still occurring.
Solution proposed in the KB 828222 - i.e. attach the 'cdb' debugger to the IIS worker process and enable the OrphanWorkerProcess Thread
did not generate the desired dump file. We double checked for the Write access in the drive where the dump file was supposed to be saved. It had all the required permissions. What we observed in this exercise was - The log.txt file is written
to the disk in C:\ drive (This is where the dump was also supposed to be generated). The log.txt contains the 'cdb' command that was issued with the dump file name and the process id. However, the C:\ location
does not have any dump file.
We are running out of ideas in troubleshooting the issue.
Can anybody suggest what could be an alternative approach to crack the problem?
Is there anything that can be done to generate the dump file as described in the KB article 828222.
In the meanwhile will be a good idea to use the 'DebugDiag' tool on the server to create a Hang/Crash rule for IIS process?
Details about the environment is as follows -
Windows 2003 Server
Looking anxiously for a reply on this issue.
P.S - Moderators and people who does not like a duplicated thread -
Please understand that this is the same issue that many have faced and have asked but however, I couldn't find any thread that discusses what to do in case the dump file is not getting generated. There is no thread that discusses on alternative approach
if any apart from these two KB articles as mentioned above. If there isn't any such "alternative approach", is it that we have to live IIS 6 getting hung with those 'Deadlock detected' messages?
IIS 6.0 hang Deadlock
Sep 07, 2008 01:53 PM|ma_khan|LINK
Should work... Haven't done it in a long time but that KB should work ... but I remember I was running a ASP .Net 1.1 app... that seems to be the only difference ... but not sure if that will make a difference ... :(
You can use DebugDiag to troubleshoot deadlock issues as well..
Sep 12, 2008 05:44 AM|WenJun Zhang - MSFT|LINK
You can use DebugDiag to gather the dump file instead of ADPlus. It's a more user friendly tool.
Debug Diagnostic Tool v1.1