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

Retired KB Content Disclaimer

View products that this article applies to.

This article was previously published under Q290505

Expand all | Collapse all

SYMPTOMS

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

Back to the top

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.

Back to the top

RESOLUTION

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 (http://support.microsoft.com/kb/260910/EN-US/ ) How to Obtain the Latest Windows 2000 Service Pack

Back to the top

STATUS

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.

Back to the top

APPLIES TO

Microsoft COM+ 1.0

Back to the top

kbbug kberrmsg kbfix kbwin2000presp2fix KB290505

Back to the top

Retired KB Content Disclaimer

This article was written about products for which Microsoft no longer offers support. Therefore, this article is offered "as is" and will no longer be updated.

Back to the top