FIX: "Server Application Unavailable" error message if a DLL is loaded in the 0x33A20000 address space and you request an ASP.NET page

On a multi-processor computer that has a DLL loaded at the 0x33A20000 address space, if you make any request in your Web browser that Microsoft ASP.NET handles, you receive the following error message from ASP.NET in your browser window: Additionally, you may receive an "HTTP 500 Error" error message in the browser or in the Microsoft Internet Information Services (IIS) event log.

This behavior occurs if you use the /BASE switch when you compile a DLL in Microsoft Visual Studio .NET and if you have the address location set to 0x33A20000. The DLL is loaded in a process before ASP.NET is invoked and before the associated .dll files and other files are loaded.

Because the 0x33A20000 address space is almost in the middle of the 2-gigabyte (GB) virtual address space, the common language runtime cannot find a clean, contiguous 1-GB space to use for the garbage-collected heaps.

Also, the order that the DLLs are loaded appears to affect this behavior. If the DLL that uses the 0x33A20000 address space is loaded in a process after ASP.NET has been invoked, ASP.NET will continue to work correctly. Although you can rebase the DLL, this may not be a reliable solution for this behavior.

This problem may occur if you use ASP.NET in conjunction with other currently available Microsoft products. For example, if you use Microsoft Content Management Server 2002 (MCMS) sites in the same application pool as ASP.NET, but you visit the MCMS sites first, you will always experience the behavior that the "Symptoms" section describes.

To resolve this problem, install this hotfix on the Web server.

Hotfix information

This hotfix is only for the Microsoft .NET Framework 1.1 version.

Important This hotfix contains 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.

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 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.

Hotfix file information

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.

Hotfix installation information

On a 32-processor server, you must install this hotfix before you install Microsoft SharePoint Portal Server 2003.

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