Still stuck? Or maybe you’d like to know more about how to fix this?
Go to Sysinternals and download Process Monitor. Download it on another PC and put it on thumbdrive.
Start Process Monitor. Setup a filter to include msdtc.exe.
Start msdtc.
The ProcMon window will catch up eventually. Wow that is a lot of activity! Look thru the output for the Access Denied, Permission Denied or other failure indicators. Go ahead. It’s in there somewhere. I’ll wait. Don’t skip right to end and expect it to be in your face. It will likely be closer to the end than the beginning though.
Found it? Good.
In my case it was a registry key, with I believe a permission denied. Firing up RegEdit, and fixing the permission on that key saved the day. Thankfully this worked after we had tried everything. The machine was only on my bench a week 
.
Right after that the rest of the pieces fell into my place and it was gone that afternoon. Ended up saving a definite reformat/reinstall which the customer specifically requested we not do in any circumstance.
Tags: wtf, Event ID: 4209, Sysinternals, ProcMon, Process Monitor, halp
April 13, 2010 at 3:39 pm |
[...] If those things don’t check out you may have other issues with MSDTC. I’ll show you how to figure them out in part 2. [...]