In a Microsoft ASP.NET Web application that is configured to run under the Microsoft .NET Framework 2.0, the first common language runtime (CLR) thread pool worker thread is never initialized for Microsoft COM+. ASP.NET uses an unmanaged thread pool API, and the CLR is not initiated yet when ASP.NET queues the first work item.
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 2.0 service pack that contains this hotfix.
To resolve this problem immediately, contact Microsoft Customer Support Services to obtain the hotfix. For a complete list of Microsoft Customer 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.
You must have the .NET Framework 2.0 installed before you apply this hotfix.
You do not have to restart the computer after you apply this hotfix.
Hotfix replacement information
This hotfix does not replace any other hotfixes.
The English version of this hotfix 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 item in Control Panel.
Collapse this tableExpand this table
|File name||File version||File size||Date||Time|
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
This problem provides an opportunity for any unmanaged code on the thread to initialize the thread to the single-threaded apartment (STA) by calling the CoInitialize
function. After the unmanaged code initializes the thread to the STA, the CLR behaves as if the thread is still initialized to the multithreaded apartment (MTA). Therefore, the CLR does not pump messages as expected, and the CLR may block the finalizer thread indefinitely. When the finalizer thread is blocked indefinitely, out-of-memory (OOM) errors may occur. Additionally, the Comsvcs.dll file may cause an access violation if the thread is changed to the STA in the middle of a COM+ call.
All the other thread pool worker threads are explicitly initialized to the MTA. On those threads, a call to the CoInitialize
function fails instead of actually initializing the thread to the STA.Note
When a call to the CoInitialize
function fails, it is common for the unmanaged code to try to initialize the thread to the STA first and then to try to initialize the thread to the MTA.
For more information, click the following article number to view the article in the Microsoft Knowledge Base:
Description of the standard terminology that is used to describe Microsoft software updates