Fix: "Access Violation" Error Message in Aspnet_wp.exe (822878)



The information in this article applies to:

  • Microsoft .NET Framework 1.1

SYMPTOMS

If the ASPNet_wp process does not shut down through the EEShutdown method, and a new ASPNet_wp process is created that uses the same pidA, the new process may quit unexpectedly ("crash") and you may receive an "Access Violation" error message.

RESOLUTION

To resolve this problem, obtain the hotfix rollup package for the Microsoft .NET Framework 1.1. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

817703 INFO: Combined Installation Package for the .NET Framework 1.1 - Hotfixes 818981, 818982, and 822878

Hotfix Information

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 Version 1.1 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 fix 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
   ---------------------------------------------------------------------------------------------
   23-Oct-2003  00:48  1.0.3705.465    200,704  Aspnet_isapi.dll
   23-Oct-2003  00:02  1.0.3705.465     69,632  Corperfmonext.dll
   23-Oct-2003  00:01  1.0.3705.465    303,104  Mscorjit.dll
   23-Oct-2003  23:56  1.0.3705.465  1,953,792  Mscorlib.dll
   23-Oct-2003  00:01  1.0.3705.465  2,273,280  Mscorsvr.dll
   23-Oct-2003  00:02  1.0.3705.465  2,269,184  Mscorwks.dll
   23-Oct-2003  00:46  1.0.3705.465     20,480  Perfcounter.dll
   23-Oct-2003  23:49  1.0.3705.465  1,179,648  System.data.dll
   23-Oct-2003  23:56  1.0.3705.465  1,695,744  System.design.dll
   23-Oct-2003  23:48  1.0.3705.465  1,175,552  System.dll
   23-Oct-2003  23:47  1.0.3705.465    241,664  System.messaging.dll
   23-Oct-2003  23:47  1.0.3705.465    311,296  System.runtime.remoting.dll
   23-Oct-2003  23:42  1.0.3705.465    131,072  System.runtime.serialization.formatters.soap.dll
   23-Oct-2003  23:49  1.0.3705.465  1,196,032  System.web.dll
   23-Oct-2003  23:47  1.0.3705.465    507,904  System.web.services.dll
   23-Oct-2003  23:56  1.0.3705.465  1,994,752  System.windows.forms.dll
   23-Oct-2003  23:49  1.0.3705.465  1,302,528  System.xml.dll

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section of this article.

Modification Type:MinorLast Reviewed:10/5/2005
Keywords:kberrmsg kbQFE kbNetFrame100preSP3fix kbfix kbbug KB822878 kbAudDeveloper