FIX: The MSDTC service does not start in a stand-alone cluster after you install Windows Server 2003 with SP1

After you install Microsoft Windows Server 2003 with Service Pack 1 (SP1) on a stand-alone cluster, the Microsoft Distributed Transaction Coordinator (MSDTC) service does not start when a local quorum resource is used. When this problem occurs, the following Error event is logged in the Application log:

Event Type: Error
Event Source: MSDTC
Event Category: Cluster
Event ID: 4394
Description:
MS DTC's log information has not been configured correctly in the shared cluster registry. Error Specifics: d:\srvrtm\com\complus\dtc\shared\mtxclu\mtxclusetuphelper.cpp:557, Pid: 3292, CmdLine: C:\WINDOWS\system32\msdtc.exe

Additionally, the following Error events are logged in the System log:

Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7034
Description:
The Distributed Transaction Coordinator service terminated unexpectedly. It has done this 1 time(s).

Event Type: Error
Event Source: ClusSvc
Event Category: Failover Mgr
Event ID: 1069
Description:
Cluster resource 'MSDTC' in Resource Group 'Cluster Group' failed

This problem occurs because MSDTC does not correctly identify the local quorum resource in the stand-alone cluster.

Service pack information

To resolve this problem, obtain the latest service pack for Windows Server 2003. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

Hotfix information

This problem is fixed in the Windows Server 2003 COM+ 1.5 Rollup Package 6. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. This problem was first corrected in Windows Server 2003 Service Pack 2.