MSDTC does not function when used with Windows Server.
Ensure that you have enabled DTC on the local host server. Additionally, review the troubleshooting information in Configuration fails when BizTalk Server and SQL Server are installed on separate computers.
If you are using the DTCPing tool to troubleshoot and encounter the following transaction exception message:
WARNING: the CID values for both test machines are the same while this problem won't stop DTCping test, MSDTC will fail for this
it is because you cloned machines from the same source image.
To resolve, you must uninstall and reinstall MSDTC:
- In Server Manager, click Roles.
- In the Application Server section, click Remove Role Services.
- Clear the Distributed Transactions check box.
- Running Windows PowerShell as an administrator, issue the MSDTC uninstall command "msdtc -uninstall"(see http://msdn.microsoft.com/en-us/library/aa561924(v=bts.70).aspx for more information).
Using regedit32.exe, delete all MSDTC registry entries from Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSDTC node.
Modify the registry at your own risk. Incorrectly editing the Windows registry can cause serious problems that may require you to reinstall your operating system. Be sure to back up the registry before making any changes to it.
- Restart the server.
- In Server Manager, click Add Role Services.
Select the following check boxes:
TCP Port Sharing
Windows Process Activation Service Support
- Running Windows PowerShell as an administrator, issue the MSDTC uninstall command "msdtc -install".
- In Server Manager | Roles | Application Server, select Distributed Transaction Coordinator.
- Right-click Local DTC and select Properties.
- In the Local DTC Properties dialog box, select the Security tab.
- Reset all of the security settings.
- Update the Distributed Transaction Coordinator service to start automatically on boot.
- Reboot the server.