Article ID: 922430 - View products that this article applies to.
Important This article contains information about how to modify the registry. Make sure to back up the registry before you modify it. Make sure that you know how to restore the registry if a problem occurs. For more information about how to back up, restore, and modify the registry, click the following article number to view the article in the Microsoft Knowledge Base:
(https://support.microsoft.com/kb/256986/ )Description of the Microsoft Windows registry
Consider the following scenario. You have a client computer that communicates with a server computer. Microsoft Distributed Transaction Coordinator (MS DTC) is installed on both computers. One or more of the following conditions are true:
Additionally, the first transaction fails. The subsequent transactions succeed for a while. However, the subsequent transactions may fail again. If the subsequent transactions fail, you receive the following error message:
New transaction cannot enlist in the specified transaction coordinator (0x8004d00a)
Note This problem is more likely to occur when you use Microsoft Windows Server 2003 Service Pack 1 (SP1) together with Kerberos authentication.
New transaction cannot enlist in the specified transaction coordinator (0x8004d00e)
This problem may occur when the MS DTC connection between the client computer and the server computer is closed. For example, an idle time-out, a remote procedure call (RPC) time-out, or the firewall may close the MS DTC connection between the client computer and the server computer. When a new transaction request occurs, the client computer must reestablish the MS DTC connection with the server computer.
When the client computer tries to reestablish the MS DTC connection with the server computer, the client computer sends a packet. Then, the client computer waits for a bind packet response from the server computer. By default, the client computer stops the transaction if the client computer does not receive a response from the server computer in 4 seconds. The response from the server computer may be delayed because of network latency issues or authentication delays. When the response from the server computer does finally reach the client computer, the subsequent transactions succeed.
Additionally, the first transaction may take a long time, and then a later request to do a distributed transaction may finish immediately. This problem may occur when the client-side of MS DTC has a problem communicating with the Kerberos (KDC) server. Typically, this problem occurs if the client and the server are in different domains that have a firewall between them.
For example, this problem occurs in the following scenario:
Warning Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall your operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.
To make sure that you are experiencing the problem that is described in this article, confirm that the MS DTC transaction trace log file contains the following data:
;eventid=TRANSACTION_PROPOGATION_FAILED_CONNECTION_DOWN_FROM_REMOTE_TM ;tx_guid=f11cd9c9-7b8a-41e3-a904-4840123bacf7 ;"failed to propogate transaction to child node 'ComputerName' because the connection with the remote transaction manager went down"
The error messages that are mentioned in the "Symptoms" section may have other causes. If the steps that are provided in the "Resolution" section do not resolve the problem, you may be experiencing the problem that is described in Microsoft Knowledge Base article 913957. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
913957If you still cannot resolve the problem, you can enable MS DTC connection manager tracing to better troubleshoot the problem. For more information about how to enable MS DTC connection manager tracing on a computer that is running Microsoft Windows 2000, click the following article number to view the article in the Microsoft Knowledge Base:
(https://support.microsoft.com/kb/913957/ )FIX: A 0x6be exception may occur when you quickly make multiple remote procedure calls to a server that is running Windows Server 2003
898918For more information about how to enable MS DTC connection manager tracing on a computer that is running Windows XP or Windows Server 2003, click the following article number to view the article in the Microsoft Knowledge Base:
(https://support.microsoft.com/kb/898918/ )Information about transaction tracing and CM error tracing in MSDTC on a Windows 2000-based computer
(https://support.microsoft.com/kb/899115/ )How to enable diagnostic tracing for MSDTC on a computer that is running Windows XP or Windows Server 2003
Article ID: 922430 - Last Review: March 22, 2011 - Revision: 4.0