You cannot start the Microsoft Distributed Transaction Coordinator (MSDTC) service on your Windows 2000 Server-based computer that is part of a server cluster (867520)

RESOLUTION

1. Connect to both nodes by using a Terminal Services client or at the console.
2. Move all resources to one node. This node becomes the active node.
3. On both nodes, use Registry Editor to delete the following registry subkeys:
   • HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSDTC
   • HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSDTC
   • HKEY_CLASSES_ROOT\CID
   To do this, follow these steps:
   1. Click Start, click Run, type regedit, and then click OK.
   2. Locate and then right-click the following registry subkey:

      HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSDTC

   3. Click Delete.
   4. Click Yes to confirm the deletion.
   5. Repeat steps a through d for the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSDTC subkey and the HKEY_CLASSES_ROOT\CID subkey.
   6. Quit Registry Editor.
4. On the active node, create the "DTClog" folder on the quorum drive. For example, create the Q:\DTClog folder.
5. If you cannot see the quorum drive in Windows Explorer or at the command prompt, use the DCOMCNFG utility (Dcomcnfg.exe) to verify the configuration. To use the DCOMCNFG utility, follow these steps:
   
   Note If you have Oracle installed, this procedure may reset the values and lock out the administrator accounts and the system account.
   1. Click Start, click Run, type dcomcnfg, and then click OK.
   2. Click the Default Security tab.
   3. Under Default Access Permissions, click Edit Default.
   4. Verify the following default access permissions:
      • SYSTEM Allow Access
      • INTERACTIVE Allow Access
      • Administrators Allow Access
      If an entry is missing, click Add, click the account that you want to add, click Add, and then click OK.
      
      Note You may also see an account for the cluster administrator account. This account is part of the administrators group. For example, if your cluster administrator account is named CLUSADMIN, you may see CLUSADMIN Allow Access.
   5. When you are finished, click OK.
   6. Under Default Launch Permissions, click Edit Default.
   7. Verify the following permissions:
      • SYSTEM Allow Launch
      • INTERACTIVE Allow Launch
      • Administrators Allow Access
      If an entry is missing, click Add, click the account that you want to add, click Add, and then click OK.
   8. When you are finished, click OK two times.
   9. If you change the DCOMCNFG utility settings, you must log off and then log on to gain the access permissions.
6. On both nodes, stop the MSDTC service. To do this, type the following command at a command prompt, and then press ENTER:

   net stop msdtc

   Verify that a message is displayed that indicates that the MSDTC service was stopped successfully.
7. On both nodes, remove MSDTC. To do this, type the following command at a command prompt, and then press ENTER:

   msdtc -uninstall

8. On both nodes, verify that the Distributed Transaction Coordinator service was removed from the Services snap-in. To start the Services snap-in, click Start, click Run, type services.msc, and then click OK.
9. Install MSDTC as a clustered resource on both the active node and the passive node. First, install MSDTC on the active node. Then, install MSDTC on the passive node. To do this, follow these steps:
   1. On the active node, type the following command at a command prompt, and then press ENTER:

      comclust

      After the COM Cluster Wizard (Comclust.exe) has finished running, the program returns you to the command prompt. Do not close the command prompt.
   2. On the passive node, type the following command at a command prompt, and then press ENTER:

      comclust

      After the COM Cluster Wizard has finished running, the program returns you to the command prompt.
   3. Close the command prompt on the passive node. You must close the command prompt on the passive node first.
   4. Close the command prompt on the active node.
   For additional information about how to install MSDTC as a clustered resource in a Windows 2000 environment, click the following article number to view the article in the Microsoft Knowledge Base:

   290624 How to configure MSDTC in a Windows 2000 cluster environment

10. Verify that no errors messages appear and that the MSDTC service is installed. Also, verify that the MSDTC resource is added to the cluster group.
    
    Note If you receive the following error message, restart all nodes and then try step 9 again:
    
    C:\Documents and Settings\Administrator>comclust Setting up MS DTC. Setup found that the current configuration of the cluster does not contain any resource groups in which the MS DTC resource can be created. Setup of MS DTC requires that the cluster contain at least one resource group that contains both a network name resource and a shared disk resource. Setup also requires that this resource group be owned by the first node in the cluster on which setup is run. Please re-run setup after the appropriate changes to the cluster configuration have been made.
11. Make sure that the MSDTC clustered resource is working correctly. To do this, try the following:
    1. Verify that you can move the cluster group from one node to another and then back again.
    2. Verify that you can run the Component Services snap-in without errors. To do this, click Start, point to Programs, point to Administrative Tools, and then click Component Services. In the Component Services snap-in, expand Component Services, expand Computers, expand My Computer, and then expand COM+ Applications.
    3. Use Event Viewer to examine the system event log and the application event log for related errors messages.