FIX: You experience activity deadlocks in a COM+ application

This article has been archived. It is offered "as is" and will no longer be updated.

SYMPTOMS
You may experience activity deadlocks in a Microsoft COM+ application. This problem occurs when a COM+ activity makes an Out-Of-Apartment (OOA) call. Typically, the activity deadlocks occur when a transaction is aborted and that transaction has COM+ components from multiple apartments or processes.
CAUSE
This problem occurs because a bug in the COM+ activity lock code lets a thread deadlock when the thread tries to re-enter an activity.
RESOLUTION

Hotfix rollup package information

This problem is fixed in the COM+ hotfix rollup package that is discussed in Microsoft Knowledge Base article 897697.

For more information about the COM+ hotfix rollup package that is discussed in Microsoft Knowledge Base article 897697, click the following article number to view the article in the Microsoft Knowledge Base:
897697 Availability of Windows 2000 Post-Service Pack 4 COM+ 1.0 Hotfix Rollup Package 34

Hotfix information

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 Microsoft Windows 2000 hotfix rollup package 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.

STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
WORKAROUND
To work around this problem, run the remote components in the same process. When you run the remote components in the same process, activities do not make OOA calls. OOA calls may create activity stacking and cause the deadlock.
STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
MORE INFORMATION
For more information about how hotfix packages are named, click the following article number to view the article in the Microsoft Knowledge Base:
816915 New file naming schema for Microsoft Windows software update packages
For more information, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates
Properties

Article ID: 899751 - Last Review: 01/17/2015 10:50:49 - Revision: 2.0

  • Microsoft COM+ 1.0
  • kbnosurvey kbarchive kbbug kbfix kbqfe KB899751
Feedback