Site Sections
Posts
27
Comments
59
Trackbacks
0
March 2008 Entries
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!
posted @ Tuesday, March 25, 2008 1:32 PM | Feedback (1)
Motorola Cable Box and DVI Error
I upgraded to HD from Comcast a few weeks ago.  I received a new HD box (Motorola DCH-3200) to be able to get 1080i programming.  However, when I plugged in the HDMI cable into the TV and cable box, the cable box would always power on, go through the power on self-tests, and then lock up, displaying DUI / DU1 in the display.  This, I found out, is the digital display of the word 'DVI'.  I googled the error, and only found a few people who experienced it, although there was enough information to infer that this appeared to be some sort of handshake issue between the components.  Since HDMI is a digital spec (complete with copyright management -- yay), there is more than just a signal output from the box to the TV.  The two have to speak with each other before it will work.

I'd seen issues with people putting a receiver in between the cable box and the TV, and that causing issues because the receiver didn't propagate the signal correctly between devices, but I had a straight connection.  However, after much fussing and the arrival of the Comcast technician, we did try an alternate HDMI input on the back of the TV, and that worked like a champ.

I have no idea why another input would work.  There is no mention of different specs for the various HDMI inputs on my TV, but all I know is HDMI1 doesn't work, while HDMI2 does.  Incidentally, HDMI1 works with my DVD player, just not with the cable box.  By the way, I have a Phillips LCD (I forget the exact model number).

/shrug
posted @ Monday, March 24, 2008 9:55 AM | Feedback (12)
Archives
Post Categories
News
Comment and opinions are my own and do not reflect on my company in any way.