Description:
Distributed Transaction Coordinator (MSDTC) coordinates transactions that are distributed across two or more databases, message queues, file systems, or other transaction protected resource managers.The service listens on TCP port 3372 along with a ephemeral TCP port (Above 1023).
Note one can disable the mutual authentication between the DTC services on different computers (In case the two computers are not on the same domain):
Related How to repair a broken MSDTC-log or reinstall MSDTC[HKEY_LOCAL_MACHINE \SOFTWARE \Microsoft \MSDTC \Security]
TurnOffRpcSecurity=dword:00000001
More Info MS KB827805
More Info MS KB555017
More Info MS KB243204
More Info MS KB250367
More Info MS KB252641
More Info MS KB290624
More Info MS KB817064
More Info MS KB899191
Recommended State:
- Manual, if on a simple home network.
Default State:
- Win8/Win7/Vista: Manual.
- Win2k3: Automatic.
- WinXP: Manual.
- Win2k Srv.: Automatic.
- Win2k Pro.: Manual.
Process Name:
- msdtc.exe (MSDTC)
Supports:
- None
IRT the DTC service, I have mine set to MANUAL too. I checked my Event Viewer Log and discovered that my ntbackup nightly scheduled job has not been running (better late than never!) because of this error:
"MS DTC log file not found. After ensuring that all Resource Managers coordinated by MS DTC have no indoubt transactions, please run msdtc -resetlog to create the log file."
I'm sure I prolly deleted the log as I've been doing some system cleanup/self-teaching as of late (yes, I do use Recovery from time to time) when I came across your post that DAC would recreate the log for me... but I am unable to pull DAC up on my XP Home box. I do have the msdtc exe along with several of its dll's etc. but cannot run it from Windows or a CMD window.
So...
I want to make sure my scheduled backup runs everynight but it looks like I do need the DTC service started but I can't start that because DAC doesn't work for me even though I do see the msdtc files in my system32 dir.
If I can get msdtc restarted so I can create the log, maybe that will suffice to turn off the DTC service again but one thing at a time.
Hope to hear back from you as this site looks like a fav keeper for me, we'll see. TIA.
I guess the full error is (EventId's are good to specify):
Maybe this solution is able to wake your DTC to life:
Just wanted to stop by and say THANKS for the tip (albeit simple one) to rename the msdtc.log file. My problem was that I no longer had that file and was going off of a directive from Bill's boys in the second paragraph here: http://msdn.microsoft.com/library/en-us/cossdk/htm/pgdtc_admin_99yr.asp
After 2 days of wrestling with it, your reply gave me the gumption to go ahead and just create a log file and see what happens (why didn't I do that in the first place?!!).
Anyway, checked my Event log this morning and with MSDTC back up & running, my scheduled ntbackup went off without a hitch last night.
Thanks again for the reply.... still livin and learnin!
P.S. have found out that the Shadow services are needed for ntbackup also... you can't believe everything you read about Services not being needed but I'm compiling a list thru trial & error (best way to learn anyway!). Peace.
IRT your request to post Event ID's, I came across http://www.eventid.net/ thanks for the advice.