SYMPTOMS You have installed a cluster service that is installed on a computer that is run...
You have installed a cluster service that is installed on a computer that is running Windows Server 2003. This cluster service is running in a two-node cluster configuration. Both of these nodes are domain controllers. When you change the primary domain controller (PDC) Emulator operations master role, also known as flexible single master operations or FSMO, to a different node in the cluster, the clustered Microsoft Distributed Transaction Coordinator (MSDTC) resource fails. On the node that is no longer the PDC Emulator, the cluster service unexpectedly quits. Additionally, an entry that is similar to the following is logged in the Cluster log:
000004b4.000004b8::2005/04/22-12:48:03.281 INFO [RM] RundownResources, terminate resource <MSDTC>.
000004b4.000004b8::2005/04/22-12:48:03.281 INFO Distributed Transaction Coordinator <MSDTC>: In call to CommonTerminate
000004b4.000004b8::2005/04/22-12:48:03.281 INFO Distributed Transaction Coordinator <MSDTC>: Offline request.
000004b4.00000a3c::2005/04/22-12:48:03.984 ERR Distributed Transaction Coordinator <MSDTC>: Failed to start service. Error: 1.
000004b4.00000a3c::2005/04/22-12:48:04.093 WARN [RM] RmpSetResourceStatus: Resource <MSDTC> not setting status since Terminate is called, lock owner=0x4b8, resource=MSDTC, state=14...
000004b4.000004b8::2005/04/22-12:48:04.093 INFO Distributed Transaction Coordinator <MSDTC>: Service died; status = 1062.
000004b4.000004b8::2005/04/22-12:48:04.093 INFO Distributed Transaction Coordinator <MSDTC>: Close request.
000004b4.000004b8::2005/04/22-12:48:04.093 INFO Distributed Transaction Coordinator <MSDTC>: In call to CommonTerminate
000004b4.000004b8::2005/04/22-12:48:04.093 INFO Distributed Transaction Coordinator <MSDTC>: Offline request.
000004b4.000004b8::2005/04/22-12:48:04.093 INFO Distributed Transaction Coordinator <MSDTC>: Setting Semaphore Cluster$MSDTCSemaphore2.
Additionally, events that are similar to the following are logged in the Application log:
Event ID: 4163
Source: MSDTC
Description: MS DTC log file not found. After ensuring all resource managers coordinated by MS DTC have no in doubt transactions, please run msdtc –resetlog to create the log file.
Event ID: 4185
Source: MSDTC
Description: MS DTC Transaction Manager start failed. LogInit returned error 0x15
Event ID: 4112
Source: MSDTC
Description: Could not start the MS DTC Transaction Manager.
Additionally, events that are similar to the following are logged in the System log:
Event ID: 7024
Source: Service Control Manager
Description: The Distributed Transaction Coordinator service terminated with service specific error 3221229584 (0xC0001010).
Event ID: 1073
Source: ClusSvc
Description: Cluster service was halted to prevent an inconsistency within the server cluster. The error code was 5.
Back to the top
CAUSE
This problem occurs if the MSDTC service tries to write to the cluster registry....
This problem occurs if the MSDTC service tries to write to the cluster registry. The specific key in the cluster registry is the resource GUID for the MSDTC resource. You can locate the resource GUID in the following registry key:
The MSDTC service runs under the Network Service account. This Network Service account has only Read access to the cluster registry. Because the write to the cluster registry operation fails, the cluster service quits to prevent an inconsistency in the cluster configuration.
HKEY_LOCAL_MACHINE\Cluster\Resources\<MSDTC resource GUID>
The MSDTC service runs under the Network Service account. This Network Service account has only Read access to the cluster registry. Because the write to the cluster registry operation fails, the cluster service quits to prevent an inconsistency in the cluster configuration.
RESOLUTION
Important This section, method, or task contains steps that tell you how to modi...
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:
To resolve this problem, grant the Network Service account the Write access to the MSDTC resource GUID in the cluster registry:
322756 (http://support.microsoft.com/kb/322756/ ) How to back up and restore the registry in Windows
To resolve this problem, grant the Network Service account the Write access to the MSDTC resource GUID in the cluster registry:
- Click Start, click Run, type regedit, and then click OK.
- Locate and then right-click the following registry subkey:
HKEY_LOCAL_MACHINE\Cluster\Resources\<MSDTC resource GUID>
- Click Permissions, and then click NETWORK SERVICE.
- In the Allow column of the Permissions for NETWORK SERVICE box, click to select the Full Control check box, and then click OK.
0 ความคิดเห็น:
แสดงความคิดเห็น