FIX: Managed applications may experience long delays when you suspend the .NET runtime

This article has been archived. It is offered "as is" and will no longer be updated.
Managed applications may experience long delays when you try to suspend the Microsoft .NET runtime. You may want to suspend the .NET runtime for garbage collection or for an application domain shutdown. You may receive HTTP 500 error messages when a Microsoft ASP.NET application is running.
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 .NET Framework 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:Note 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   ------------------------------------------------------------------------   11-Jul-2003  01:52  1.0.3705.439    200,704  Aspnet_isapi.dll   X86   11-Jul-2003  01:47                    4,169  Aspnet_perf.h   11-Jul-2003  01:52                  513,302  Aspnet_perf.ini   11-Jul-2003  01:52                  510,714  Aspnet_perf2.ini   11-Jul-2003  01:52  1.0.3705.439     28,672  Aspnet_rc.dll      X86   11-Jul-2003  01:52  1.0.3705.439     24,576  Aspnet_regiis.exe  X86   11-Jul-2003  01:52  1.0.3705.439     28,672  Aspnet_wp.exe      X86   11-Jul-2003  01:05  1.0.3705.439     69,632  Corperfmonext.dll  X86   11-Jul-2003  01:03  1.0.3705.439    303,104  Mscorjit.dll       X86   11-Jul-2003  13:39  1.0.3705.439  1,953,792  Mscorlib.dll       X86   11-Jul-2003  00:56                   10,284  Mscorlib.ldo   11-Jul-2003  01:04  1.0.3705.439  2,269,184  Mscorsvr.dll       X86   11-Jul-2003  01:04  1.0.3705.439  2,269,184  Mscorwks.dll       X86   23-Aug-2002  03:23                       15  Smartnav.htm   22-Oct-2002  21:41                    8,728  Smartnav.js   11-Jul-2003  13:41  1.0.3705.439  1,196,032  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.

Article ID: 824286 - Last Review: 01/17/2015 05:19:33 - Revision: 1.5

Microsoft .NET Framework 1.1

  • kbnosurvey kbarchive kbhotfixserver kbqfe kbhotfixserver kbqfe kbnetframe100presp3fix kbfix kbbug KB824286