| Event Id | 53313 |
| Source | MSDTC |
| Description | XATM log object failed to set log encryption key:File=d:\viper\src\dtc\xatm\src\xatmlog.cpp Line=793. |
| Event Information | According to Microsoft: CAUSE: The Microsoft Distributed Transaction Coordinator (MSDTC) is not properly installed or is malfunctioning on one or both nodes on the Cluster Server computer. RESOLUTION: To resolve this issue, proceed through the following checklist of items on the Cluster Node that the MSDTC fails to start on. If none of the items in the checklist help resolve the issue, then you will have to remove and reinstall the MSDTC on the Cluster Server computer. Before performing the following steps, take the MSDTC service offline if it is not already. It is also advisable to set the Advanced Properties of the MSDTC Cluster Resource to "Do Not Restart," and then move the Resource Group with the MSDTC Resource in it to the Node on which the MSDTC Resource fails to start. 1. From a command line, type the following:DAC This should launch the MSDTC Admin Console. From the Admin Console, click the Advanced Tab.Verify that the Drive and Location for the MSDTC log is correct.If the MSDTC Admin Console does not run, then proceed directly to Removing the MSDTC. 2. Make sure the Msdtc.log file exists in the MSDTC Log directory location determined from Item 1. If this directory does not exist, then create it manually. 3. Check permissions to the MSDTC LOG directory and files (Everyone Full Control). 4. Delete the Dtcxatm.log file. 5. If the MSDTC Admin Console is still open, close it. |
| Reference Links | Event Log Error 3221229574 from Service Control Manager |
Catch threats immediately
We work side-by-side with you to rapidly detect cyberthreats
and thwart attacks before they cause damage.