Microsoft Distributed Transaction Coordinator (MSDTC) recovery techniques in Windows 2000 Cluster Server
Article ID: 243204 - View products that this article applies to.
This article was previously published under Q243204
NoticeThis article applies to Windows 2000. Support for Windows 2000 ends on July 13, 2010. The Windows 2000 End-of-Support Solution Center
(http://support.microsoft.com/?scid=http%3a%2f%2fsupport.microsoft.com%2fwin2000)is a starting point for planning your migration strategy from Windows 2000. For more information see the Microsoft Support Lifecycle Policy
By default, the Microsoft Distributed Transaction Coordinator (MSDTC) service is installed by in Windows 2000. You cannot uninstall it by using Add/Remove Programs. This article describes how to recover from a problem with a Distributed Transaction Coordinator Resource in a Windows 2000 cluster. Typically, you experience this problem when you install a program that uses the DTC Resource. Programs such as Microsoft SQL Server, Microsoft Message Queuing, Microsoft Exchange 2000 Server, and Microsoft Exchange Server 2003 can use DTC when they are running in a server cluster.
Note Microsoft only supports running MSDTC on cluster nodes as a clustered resource. If SQL Server is clustered, only one clustered instance of MSDTC is required to support the maximum number of instances of SQL. The recommended procedure for installing an MSDTC Resource is to install it in its own resource group with its own disk and IP resources. If the MSDTC resource has already been installed, regardless of the location, and the applications that are using it are functioning correctly, we recommend that you leave it in that location. If the cluster is not yet in production, the following procedures can be used to move the MSDTC resource to a group other than the Cluster Group.
The MSDTC Cluster Resource will install in the first group that has a Physical Disk, IP Address and Network Name Resource configured and Online. Failure to make those resources available and online in a group other than the Cluster Group will cause the DTC Resource to be installed in the Cluster Group when you run the Comclust.exe command. By default, the Cluster Group contains the following resources:
Note In an Exchange 2000 cluster or in an Exchange 2003 cluster, it is a best practice to leave the clustered MSDTC resource in the cluster group. Exchange accesses this functionality only during the initial installation process and when any Exchange specific service packs are applied. For more information about SQL Server-specific instructions for moving or recovering the MSDTC resource on clustered SQL Server installations, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/294209/ )How to rebuild or move MSDTC used with a SQL failover cluster
Additionally, you may experience issues with the MSDTC log file that should be located on the first Physical Disk Resource in the group in which you installed the DTC Resource.
Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/322756/ )How to back up and restore the registry in Windows
If you experience issues with the MSDTC service, or a DTC Resource in a Windows 2000 cluster, you can use one of the procedures described in this section to recover.
MSDTC Cluster Resource Is Mistakenly Installed in the Cluster GroupIf the DTC Resource was mistakenly installed in the Cluster Group, follow these steps to move it to the correct group. You should not use the Change Group functionality in Cluster Administrator to accomplish this task.
MSDTC Log IssuesIf you suspect an issue with the MSDTC log, you can flush any existing packets in the MSDTC log by running the msdtc.exe -resetlog command.
Warning The msdtc -resetlog command is a dangerous operation; verify that you do not have active transactions when you perform this operation.