FIX: ASP.NET Worker Process Does Not Start on Computers with the /3GB Boot Switch

This article has been archived. It is offered "as is" and will no longer be updated.
If you have the /3GB boot switch enabled, the ASP.NET worker process (Aspnet_wp.exe) does not start. If you request an ASP.NET page, you receive one of the following error messages in the browser:
HTTP 500 - Internal server error
A dynamic link library (DLL) initialization routine failed
To resolve this problem, obtain the latest service pack for the Microsoft .NET Framework. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
318836 INFO: How to Obtain the Latest .NET Framework Service Pack

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   --------------------------------------------------------------   21-Apr-2002  12:15  1.0.3705.258      192,512  Aspnet_isapi.dll     21-Apr-2002  12:10                     19,332  Aspnet_perf.ini   21-Apr-2002  12:15  1.0.3705.258       24,576  Aspnet_regiis.exe     21-Apr-2002  12:15  1.0.3705.258       28,672  Aspnet_wp.exe   05-Apr-2002  12:07                      8,709  Smartnav.js   05-Apr-2002  12:07                      7,003  Smartnavie5.js   22-Apr-2002  00:39  1.0.3705.258    1,183,744  System_web.dll				
NOTE: After applying the fix, add an environment variable named ASPNETENABLE3GB and set the value to 1 to start the ASP.NET worker process. Otherwise, the problem that is mentioned in the "Symptoms" section still occurs. Although the ASP.NET Worker Process will now run on a computer with the 3GB switch enabled, ASP.NET does not utilize the extra memory.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article. This problem was first corrected in the Microsoft .NET Framework Service Pack 2.

Article ID: 320353 - Last Review: 06/19/2014 14:41:00 - Revision: 7.0

Microsoft ASP.NET 1.0

  • kbnosurvey kbarchive kbproductlink kbhotfixserver kbqfe kbbug kbfix kbnetframe100presp2fix kbnetframe100sp2fix KB320353