Troubleshooting Errors with DTC Caused by Duplicate CIDs
KB000418
PRODUCTK2 blackpearl
K2 connect
SEE ALSO Configuring Microsoft Distributed Transaction Coordinator (DTC) to work through a firewallWarning: the CID values for both test machines are the same
DtcPing
LEGACY/ARCHIVED CONTENT
This article has been archived, and/or refers to legacy products, components or features. The content in this article is offered "as is" and will no longer be updated. Archived content is provided for reference purposes only. This content does not infer that the product, component or feature is supported, or that the product, component or feature will continue to function as described herein.
The Distributed Transaction Coordinator (MSDTC) service is a component of Microsoft Windows that is responsible for coordinating transactions that span multiple resource managers in a clustered environment. Errors may occur when duplicate CIDs exist in the same environment, or where virtual machines have been used to add capacity to an environment. Virtual machines that are mirrored often encounter this issue. This error may also be encountered in standalone environments without NETCARDs.
If this issue occurs, you may see errors such as "Dependancy could not be created: System.Transactions.TransactionManagerCommunicationException: Communication with the underlying transaction manager had failed".
If this issue occurs, you may see errors such as "Dependancy could not be created: System.Transactions.TransactionManagerCommunicationException: Communication with the underlying transaction manager had failed".
The steps discussed in this article for the MSDTC configuration should be applied to the individual machines. In the case where the K2 Server and the SQL Server are separate machines, they must each be configured as described in this article.
Resolution
Follow these steps to resolve the error. External tools provided by Microsoft to assist in the diagnosis process may be required; links to these tools can be found at the end of the article.
The steps below describe one scenario under which this error may occur. They are simplified and not all steps are described in detail.
Step 1: Uninstall Network DTC (these steps apply to Windows Server 2003)
- From the Control Panel, click Add or Remove Programs
- Click Add/Remove Windows Components
- Click Application Server
- Click the Details… button
- Uncheck Enable network DTC access
- Click OK, and then click Next
Step 2: Uninstall MSDTC using the command line:
- Click Run on the Start menu
- Type CMD and press Enter
- On the command line type MSDTC –uninstall and press Enter
Step 3: Remove Registry Keys
- Use the Windows Registry Editor (regedit.exe), delete the following keys and subkeys:
- HKLM/Software/Microsoft/ MSDTC
- HKLM/System/CurrentControlSet/Services/MSDTC
- HKEY_CLASSES_ROOTCID (if found)
- Reboot the computer
Step 4: Reinstall DTC
- Click Run on the Start menu
- Type CMD and press Enter
- On the command line, type MSDTC –install and press Enter
- Using Add or Remove Programs, add the Enable network DTC access feature again. Refer to the Step 1 above for details.
- Click Run on the Start menu
- Type CMD and press Enter
- On the command line, type net start msdtc and press Enter
Additional Resources
To further assist in the diagnostic process, the following Microsoft tools are available:
- DtcPing (http://www.microsoft.com/Downloads/details.aspx?FamilyID=5e325025-4dcd-4658-a549-1d549ac17644&displaylang=en) - needs to be downloaded on both machines you are attempting to test communications.
- DtCTester (http://support.microsoft.com/kb/293799)
