Article ID: 304017 - Last Review: June 5, 2003 - Revision: 2.0

SQL Server Causes Duplicate GUID Errors When You Connect to MS DTC After Failover

View products that this article applies to.

System TipThis article applies to a different operating system than the one you are using. Article content that may not be relevant to you is disabled.

This article was previously published under Q304017

Expand all | Collapse all

SYMPTOMS

When a clustered system is running a workload with many Microsoft Distributed Transaction Coordinator (MS DTC) transactions between multiple SQL Servers in the cluster, if one of the virtual servers moves from one node to another, the Remote Procedure Call (RPC) connection to the server may not always end.

As a result, MS DTC assumes that two SQL Servers with the same globally unique identifier (GUID) are trying to connect to the same MS DTC. This causes SQL Server to fail to connect to MS DTC, and an event with the error message "Failed to Enlist" is logged in the event log. In some cases, the databases cannot recover from failover.

The following error messages are logged in the SQL log:

<date> <time> server Attempting to initialize Distributed Transaction Coordinator.

<date> <time> server Resource Manager Creation Failed: Result Code = 0x8004d102

Back to the top

RESOLUTION

To resolve this problem, obtain Microsoft COM+ Rollup Hotfix 12. For additional information, please see the following article in the Microsoft Knowledge Base:

297536 (http://support.microsoft.com/kb/297536/EN-US/ ) INFO: Availability of Windows 2000 Post-Service Pack 2 COM+ Hotfix Rollup Package 12

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