Biztalk Configuration Error: Cloned Machines

Posts: 32
Comments: 96
Trackbacks: 0

<< Motorola Cable Box and DVI Error | Home | Java Web Service Interop with a .NET Client >>

Biztalk Configuration Error: Cloned Machines

I recently ran into an error attempting to configure a Biztalk 2006 R2 instance on a virtual machine. I had a virtual services box (where Biztalk was installed) and another virtual SQL box (where the Biztalk configuration was kept). However, I kept getting an error during the configuration deployment step:

Exception of type 'System.EnterpriseServices.TransactionProxyException' was thrown.

After googling for a bit, I ran into an excellent article by Wade Wegner explaining that the two virtual machines appeared to have the same CID value (basically, a unique machine identifier for MSDTC). This can occur when a virtual machine is a clone of another and the CID value isn't made unique after the clone.

I don't know the exact situation for these virtual machines, as someone else on the dev team created the virtual machines, but I do know these two virtual machines were clones of each other (or possibly another box?). I don't know if NewSid or SysPrep actually modifies this value for MSDTC, but I suspect neither was run on these virtual machines after the clone, so I suppose it doesn't really matter in my case. If anyone has confirmation on this, feel free to comment.

What I do know is that Wade's article was spot-on for resolving my issue. I followed his instructions exactly and it solved the problem. Thanks, Wade!