FIX: You receive a "Server Application Unavailable" error message when you request an ASP.NET page on a computer that has multiple processors (818706)


The information in this article applies to:

  • Microsoft .NET Framework 1.1
  • Microsoft Visual Studio .NET (2003), Enterprise Architect Edition
  • Microsoft Visual Studio .NET (2003), Enterprise Developer Edition

SYMPTOMS

On a computer that has multiple processors, you receive the following error message when you request a Microsoft ASP.NET page:
Server Application Unavailable
You may also receive the following error message in the browser or in the Microsoft Internet Information Services (IIS) event log:
HTTP 500 - Internal server error

CAUSE

This problem occurs if the following conditions are true:
  • You use the /BASE switch to compile a DLL in Microsoft Visual Studio .NET 2003.
  • You set the address location to 0x33A20000.

RESOLUTION

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

885055 How to obtain Microsoft .NET Framework 1.1 Service Pack 1

Hotfix information

Important This hotfix contains the following two types of packages:
  • A Microsoft Windows Installer package
  • An Optional Component Manager (OCM) package
If you use Microsoft Windows Server 2003, you must specify that you require the Windows Server 2003 (OCM) update. If you use an operating system that is different from Windows Server 2003, you must use the Windows Installer package. For Windows Server 2003, Windows File Protection monitors the .NET Framework 1.1 files.

File information

The English version of this software has the file attributes (or later file attributes) 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-Jun-2003  23:17  1.1.4322.915     77,824  Corperfmonext.dll
   24-Jun-2003  14:13  1.1.4322.915  2,088,960  Mscorlib.dll
   23-Jun-2003  23:07                   10,728  Mscorlib.ldo
   23-Jun-2003  23:15  1.1.4322.915  2,494,464  Mscorsvr.dll
   23-Jun-2003  23:16  1.1.4322.915  2,486,272  Mscorwks.dll

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. This problem was first corrected in Microsoft .NET Framework 1.1 Service Pack Service Pack 1.

MORE INFORMATION

The order that the DLLs are loaded in affects this problem. If the DLL that uses the 0x33A20000 address space is loaded in a process after ASP.NET is invoked, ASP.NET continues to work correctly.

This problem may also occur if you use ASP.NET with other Microsoft products. For example, the problem may occur if the following conditions are true:
  • You use Microsoft Content Management Server (MCMS) 2002 sites in the same application pool as ASP.NET.
  • You visit the MCMS sites before ASP.NET is invoked.
Although you can rebase the DLL, rebasing the DLL may not be a reliable solution.

REFERENCES

For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

824684 Description of the standard terminology that is used to describe Microsoft software updates

Modification Type:MinorLast Reviewed:5/20/2005
Keywords:kbBug kbfix kbNetFrame110preSP1fix KB818706 kbAudDeveloper kbAudITPRO
©2004 Microsoft Corporation. All rights reserved.