Article ID: 827164 - View products that this article applies to.
For a Microsoft .NET Framework 1.0 version of this article, see 827163
This article has been archived. It is offered "as is" and will no longer be updated.
If you store your references to single-threaded apartment (STA) objects in session state, and you set the AspCompat attribute to true, the references may become corrupted or may become lost when you try to gain access to the objects from the Session_End event.
Note Typically, this problem may occur if you run the application under high loads or if you use a stress tool such as Application Center Test (ACT) when you run the application. When this problem occurs, you receive a "0x8004e005 Error" error message in the event log.
The problem occurs because the Session_End event does not have to run on the same thread that the session was created on. Because the STA object is no longer on the same thread that the session was created on, marshaling is required to gain access to the object. This behavior causes slow performance.
You can store STA objects in session state. However, Microsoft does not recommend that you do so. For more information, see the "References" section of this article.
This hotfix adds a new configuration setting to the Machine.config file. After you install the hotfix, the following application configuration is available.
By default, apartmentThreading is set to false. If you set apartmentThreading to true, the following behavior occurs:
This hotfix works for STA objects that are stored directly in session state. This hotfix also works for an STA object that is nested one level deep such as a .NET object that is stored in session state and that has a reference to an STA object. However, this hotfix does not work for STA objects that are stored more than one level deep.
Important This hotfix contains two types of packages: a Microsoft Windows Installer package, and an Optional Component Manager package (OCM). If you use Microsoft Windows Server 2003, you must specify that you require the Windows Server 2003 (OCM) update, because Windows Server 2003 File Protection monitors the .NET Framework 1.1 files. If you use an operating system other than Windows Server 2003, you must continue to use the Windows Installer package.
The OCM version of this hotfix is available in the following languages:
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:
http://support.microsoft.com/contactus/?ws=supportNote 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 ------------------------------------------------------------------------ 18-Sep-2003 05:18 1.1.4322.947 258,048 Aspnet_isapi.dll 18-Sep-2003 05:18 1.1.4322.947 20,480 Aspnet_regiis.exe 18-Sep-2003 05:18 1.1.4322.947 32,768 Aspnet_state.exe 18-Sep-2003 05:18 1.1.4322.947 32,768 Aspnet_wp.exe 16-May-2003 01:49 33,522 Installpersistsqlstate.sql 16-May-2003 01:49 34,150 Installsqlstate.sql 18-Sep-2003 05:09 1.1.4322.947 94,208 Perfcounter.dll 19-Sep-2003 02:43 1.1.4322.947 1,216,512 System.dll 19-Sep-2003 02:40 1.1.4322.947 323,584 System.runtime.remoting.dll 19-Sep-2003 02:43 1.1.4322.947 1,253,376 System.web.dll 19-Sep-2003 02:42 1.1.4322.947 819,200 System.web.mobile.dll 19-Sep-2003 02:41 1.1.4322.947 569,344 System.web.services.dll 19-Sep-2003 02:44 1.1.4322.947 1,335,296 System.xml.dll 18-Sep-2003 05:13 14,472 Webuivalidation.js
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section of this article.
This hotfix package also includes a secondary hotfix. If you set AspCompat to true, and you set an STA object that is stored in session state to null, you may receive a "NullReferenceException" error message when you reload the page. To reproduce the secondary problem, paste the following code inside a Page_Load event.
When you visit this page the first time, the code runs correctly. However, if you reload the page, you receive a "NullReferenceException" error message from Microsoft ASP.NET and you cannot view the page again in the current session.
If you set AspCompat to false, this behavior does not occur.
[NullReferenceException: Object reference not set to an instance of an object.] System.Web.UnsafeNativeMethods.AspCompatOnPageStart(Object obj) +0 System.Web.Util.AspCompatApplicationStep.OnPageStartSessionObjects() +90 System.Web.UI.Page.ProcessRequestMain() +44
Steps to Reproduce the BehaviorTo reproduce the problem that appears in the "Symptoms" section of this article, follow these steps:
For additional information, click the following article numbers to view the articles in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/243543/ )INFO: Do Not Store STA Objects in Session or Application
(http://support.microsoft.com/kb/243815/ )PRB: Storing STA COM Component in Session Locks Session Down to Single Thread
(http://support.microsoft.com/kb/817005/ )FIX: Severe Performance Issues When You Bind Session State to Threads in ASPCompat Mode
Article ID: 827164 - Last Review: February 27, 2014 - Revision: 1.7