MSDTC version conflicts can occur during the NTOP installation on a clustered server. The NTOP installs an older version of the MSDTC. If the clustered server has Windows NT Service Pack 4 or later, the NTOP installation may fail and the MSDTC may not function correctly after the installation. When SQL Server is installed prior to the NTOP, similar problems with the MSDTC may occur.
If one of the following situations describes your problem, use the steps in the "Workaround" section of this article.
The NTOP cannot be installed because Windows NT SP4 or later is installed on the system.
The NTOP is installed, but the MSDTC resources fail under Cluster Administrator.
SQL Server and the NTOP are both installed on a clustered server and the MSDTC is the only resource failing.
WORKAROUND:
Remove the MSDTC resource group from cluster server.
Delete the following registry keys on the MSDTC:
HKLM\software\Microsoft\MSDTC
and
HKLM\SYSTEM\CurrentControlSet\Services\MSDTC
Remove the shared MSDTCLog folder on the shared drive.
Install the standalone version of the MSDTC from the following location:
ftp://ftp.microsoft.com/bussys/distapps/MTS/Public-Fixes/usa/DTC/SvcPack/
Stop and restart the cluster services on both nodes in the following order:
Stop CLSSVC on node B
Stop CLSSVC on node A
Start CLSSVC on node A
Start CLSSVC on node B
Test failover of the MSDTC group. If it works, the workaround was successful.
If theerrors persist, use the DTCremove utility (not supported), and then run DTCSetup.exe again as described above.
If SQL Server is installed, you may need to remove SQL Server first.
Best of luck and have a GREAT 2002!
Maxwell
