Home > BizTalk Configuration > BizTalk configuration issue:Same CID value for MSDTC on both the BizTalk and SQL Server machine.

BizTalk configuration issue:Same CID value for MSDTC on both the BizTalk and SQL Server machine.

There could be a lot of reason for not able to successfully configure BizTalk on your machine. But in most of the cases these issues are related to MSDTC.

To troubleshoot problems with MSDTC,
you can refer to MSDN Troubleshooting Problems with MSDTC .

Once I had faced strange problem while configuring BizTalk server on multi server installation. I did all the tricks mentioned on MSDN but not able to solve the problem. Finally uninstalling MSDTC and then reinstalling MSDTC in one machine solved my problem.

Actually problem was there with the same CID value for MSDTC on both the BizTalk and SQL Server. And the reason for same CID value was there because both the machines were cloned from the same one. Reinstalling of MSDTC generates a new CID value.

Steps to solve the problem:

Do this on any of the two machines(either on BizTalk machine or on SQL Server machine)
      1. Stop the Distributed Transaction Coordinator service.
      2. Go to command line and run:
              MSDTC –uninstall
              MSDTC -install
      3. Start the Distributed Transaction Coordinator service.

I hope this trick would save a lot of time for others.

Advertisements
  1. No comments yet.
  1. No trackbacks yet.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: