Microsoft KB Archive Search

Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

  1. Home
  2. FIX: The Microsoft Distributed Transaction Coordinator may crash, and the following error message is logged in the system event log: "The MS DTC Transaction Manager is in an inconsistent state and cannot proceed"

FIX: The Microsoft Distributed Transaction Coordinator may crash, and the following error message is logged in the system event log: "The MS DTC Transaction Manager is in an inconsistent state and cannot proceed"

View products that this article applies to.

Symptoms

The Microsoft Distributed Transaction Coordinator (MSDTC) may crash. Additionally, Event ID 4169 is logged in the system event log. The error message resembles to the following:
Application	01/03/2006 10:37
Error	4169
MSDTC	TM	ComputerName
The MS DTC Transaction Manager is in an inconsistent state and cannot proceed. 
Please contact 
Microsoft Product Support. \r\n(State address = 0x7c0cb784)\r\nFile: 
d:\nt\com\complus\dtc\dtc\tm\inc\TMSupTem.H, Line: ErrorNumber.\r\nVersion: 
5.2.3790.397\n\r\n + 0x7ffe0304\r\n
Note The error number in this error message differs depending on the operating system.

Many in-doubt transactions and many existing transactions stop responding. In this case, Microsoft SQL Server-based applications or Microsoft COM+-based applications may keep waiting indefinitely for the transaction to finish.

This problem frequently occurs when the MSDTC is used together with BEA WebLogic Server to perform a transaction under stress conditions. However, this problem is not limited to BEA WebLogic Server. Other servers that use XA transactions in a similar scenario may experience the same problem.

↑ Back to the top

Cause

This problem occurs because the MSDTC enters an inconsistent state. If the MSDTC receives an unauthorized set of XA commands, the MSDTC may enter an inconsistent state. Additionally, the MSDTC may enter an inconsistent state if an internal race condition occurs.

↑ Back to the top

Resolution

To resolve this problem, you must install a COM+ rollup package.

Microsoft Windows 2000

Install the Windows 2000 Post-Service Pack 4 COM+ 1.0 Hotfix Rollup Package 37. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
922667 Availability of Windows 2000 Post-Service Pack 4 COM+ 1.0 Hotfix Rollup Package 37

Microsoft Windows Server 2003

Install the Windows Server 2003 Post-Service Pack 1 COM+ 1.5 Hotfix Rollup Package 10. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
924729 Availability of the Windows Server 2003 Post-Service Pack 1 COM+ 1.5 Hotfix Rollup Package 10

↑ Back to the top

Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

↑ Back to the top

More information

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
The third-party products that this article discusses are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, regarding the performance or reliability of these products.

↑ Back to the top

Keywords: KB923871, kbqfe, kberrmsg

↑ Back to the top

Article Info
Article ID : 923871
Revision : 3
Created on : 10/9/2011
Published on : 10/9/2011
Exists online : False
Views : 265