Event ID: 53258 Source: MSDTC

Event ID/Source search

Keyword search

Example: Windows cannot unload your registry file

Event ID: 53258 Source: MSDTC

Source: MSDTC

Description:
MS DTC could not correctly process a DC Promotion/Demotion event. MS DTC will continue to function and will use the existing security settings. Error Specifics: d:\nt\com\complus\dtc\dtc\adme\uiname.cpp:8751 CmdLine: C:\WINNT\system32\msdtc.exe Pid: <PID>
No Callstack (0).

English: This information is only available to subscribers. An example of English, please!

Concepts to understand:
What is the role of the MSDTC service?

Comments:
Anonymous
I had this warning on a Windows 2003 R2 server after promoting it to a PDC. ME923977 fixed it in my case.
Click if the comment is good!

^{x
22}

LucaC
I had this error after removing SCOM 2007 agent on a Domain Controller. I fixed this by changing the registry key HKLM\Software\Microsoft\MSDTC, and giving to the "Network Service" account "Create Subkey" and "Set Value" Permissions.

Then from command line:

net stop msdtc
net start msdtc
Click if the comment is good!

^{x
17}

Iman Dastyar
Uninstall MSDTC service and install it again by using the steps listed below (it solved my problem).

In a command line prompt type:
msdtc -uninstall

Reboot your machine

In a command line prompt type:
msdtc -install

Manually start your msdtc service.
Click if the comment is good!

^{x
8}

Peter Van Gils
I had this error on a Win2003 R2 domain controller while extending the schema for Exchange Server 2007 on a virtual machine on which I was doing some tests. The server displayed an error about a lack of virtual memory. I increased the physical memory and rebooted. Afterwards, the schema extension worked correctly.
Click if the comment is good!

^{x
2}

EventID.Net
This issue can occur if Windows Server 2003 unsuccessfully tries to configure the Microsoft Distributed Transaction Coordinator (MS DTC) service to use the default security settings. See ME923977 for more information regarding this issue.
Click if the comment is good!

^{x
1}

Why bother deciphering Event logs when GFI EventsManager can do everything for you? Free trial here!

Anonymous
I received this event when I promoted the server to a PDC. I chose a different folder for the Active Directory logs (D:\WINDOWS\NTDS instead of the default C:\WINDOWS\NTDS). Giving the Network Service account read rights over the D:\WINDOWS\NTDS folder fixed this problem.
Click if the comment is good!

^{x
4}

Anonymous
I stopped this error by changing the COM+ System Application service from "disabled" to "manual".
Click if the comment is good!

^{x
2}

Chris Kratsch
I received this error after replacing a Windows 2000 DC with a Windows 2003 DC, and demoting the old DC without having changed the site license server setting in AD Sites & Services. After changing the site license server, I needed to restart the License Logging service and add my CALs to the Licensing interface.
Click if the comment is good!

^{x
2}

Anonymous
Try to reset the log with the following command: msdtc -resetlog.
Click if the comment is good!

^{x
3}

Anonymous
I had this error after upgrading from Win2k to Win2k3 and applying SP1. I fixed this by changing the registry key HKLM\Software\Microsoft\MSDTC, and giving to the Network Service account "Create Subkey" and "Set Value" Permissions.
Click if the comment is good!

^{x
13}

David Grant
I corrected the error by doing the following:
1. Click Start -> Administrative Tools -> Component Services.
2. Click the "+" next to Component services to expand it.
3. Right click "My Computer" in the right window pane and select Properties.
4. Click the MS DTC Tab.
5. Click the "Security Configuration" button, a dialog box appears. Click "OK".
6. Click "OK" on the "My Computer Properties" box; this will take you back to the console.
7. Right click "My Computer" and select "Stop MS DTC" (this stops the MSDTC service.
8. Again, right click "My Computer" and select "Start MS DTC".
By following the above steps, it appears that this sets the MS DTC defaults resolving the error messages. Check the event log to verify that the problem is gone. You might also want to restart the server to verify this.
Click if the comment is good!

^{x
130}

Private comment: Subscribers only. See example of private comment

Search: Google - Bing - Microsoft - Yahoo - EventID.Net Queue - More links...

Custom search for *****: Google - Bing - Microsoft - Yahoo

Feedback: Send comments or solutions - Notify me when updated

Printer friendly