Article ID: 814687 - View products that this article applies to.
The Microsoft ASP.NET worker process stops responding. When you view the user dump file of the process, you notice that many threads are waiting for an mscorsvr critical section. The owner thread of the critical section is idle and the call stack is similar to the following:
A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Only apply it to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next Microsoft .NET Framework 1.0 service pack that contains this hotfix.
To resolve this problem immediately, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:
http://support.microsoft.com/contactus/?ws=supportNote In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.
The English version of this hotfix has the file attributes (or later) that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.
Date Time Version Size File name Platform ------------------------------------------------------------------------ 01-May-2003 12:38 1.0.3705.404 196,608 Aspnet_isapi.dll X86 01-May-2003 12:38 4,169 Aspnet_perf.h 01-May-2003 12:38 20,468 Aspnet_perf.ini 01-May-2003 12:38 20,342 Aspnet_perf2.ini 01-May-2003 12:38 1.0.3705.404 24,576 Aspnet_regiis.exe X86 01-May-2003 12:38 1.0.3705.404 28,672 Aspnet_wp.exe X86 01-May-2003 12:38 1.0.3705.404 69,632 Corperfmonext.dll X86 01-May-2003 12:38 1.0.3705.404 303,104 Mscorjit.dll X86 01-May-2003 12:38 1.0.3705.404 1,953,792 Mscorlib.dll X86 01-May-2003 12:38 10,284 Mscorlib.ldo 01-May-2003 12:38 1.0.3705.404 2,269,184 Mscorsvr.dll X86 01-May-2003 12:38 1.0.3705.404 2,269,184 Mscorwks.dll X86 01-May-2003 12:38 15 Smartnav.htm 01-May-2003 12:38 8,728 Smartnav.js 01-May-2003 12:38 1.0.3705.404 1,191,936 System.web.dll X86
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section of this article.
For additional information about the terminology that is used to describe Microsoft product updates, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/824684/ )Description of the Standard Terminology That Is Used to Describe Microsoft Software Updates