FIX: Race Condition on Pooled COM+ Transactional Object Causes System to Stop Responding

Article translations Article translations
Article ID: 290505 - View products that this article applies to.
This article was previously published under Q290505
This article has been archived. It is offered "as is" and will no longer be updated.
Expand all | Collapse all


When a pooled COM+ component is marked as transactional, the system may stop responding (hang) due to an internal race condition.


Under a particular sequence of events in a transactional component (primarily Bring Your Own Transaction [BYOT] transactions), the COM+ dispenser manager tries to reuse the ITransaction interface before it is properly released and while the dispenser manager is still cleaning it up.


To resolve this problem, obtain the latest service pack for Windows 2000. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
260910 How to Obtain the Latest Windows 2000 Service Pack


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 Windows 2000 Service Pack 2.


Article ID: 290505 - Last Review: November 2, 2013 - Revision: 2.0
Applies to
  • Microsoft COM+ 1.0
kbnosurvey kbarchive kbbug kbDSupport kberrmsg kbwin2000presp2fix kbWin2000SP2Fix KB290505

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from