Tuesday 11 September 2012

DTC Error - Warning - The CID values for both machines are the same

In my experience this issue is generally caused by either physical servers that have been cloned from an Image, or virtual machines that have been deployed from a template.

DTCPing is a very useful tool in diagnosing issues with DTC Communication, and can be found here:

http://www.microsoft.com/en-us/download/details.aspx?id=2868

If for any reason the above link changes this tool can be found in the Microsoft Download Centre.

The error with the DTC Communication in this instance is caused by duplicate CIDs. This can be confimed by checking the registry for the following Key:

HKEY_CLASSES_ROOTCID

If these keys are identical on both machines then follow the following steps:


  1. Use Add Windows Components, and remove Network DTC.
  2. Go to the command line and run: MSDTC -uninstall
  3. Go to the registry and delete the MSDTC keys in HKLM/Software/Microsoft/Software/MSDTC, HKLM/System/CurrentControlSet/Services/MSDTC, and HKEY_CLASSES_ROOTCID (if they’re still there).
  4. Reboot
  5. Go to the command line and run: MSDTC -install
  6. Use Add Windows Components, and add Network DTC.
  7. Go to the command line and run: net start msdtc 
The above information has worked for me, and the relevant information was taken from Wade Wegner's Blog:

http://www.wadewegner.com/2007/08/warning-the-cid-values-for-both-test-machines-are-the-same/ 

 You can sometimes get away with just doing the following, and I've found it works every time on Server 2008r2

     1.  Run a command prompt with administrative privileges.
     2.  At the command line run: MSDTC -uninstall (Unfortunately you don't get any messages)
     3.  Reboot the server.
     4.  Run a command prompt with administrative privileges.
     5.  At the command line run: MSDTC -install
     6.  At the command line run: sc config msdtc start= auto  (NOTE the space after the =)
     7.  At the command line run: sc start msdtc


No comments:

Post a Comment

Note: only a member of this blog may post a comment.