Monitor unlimited number of servers
Filter log events
Create email and web-based reports

Direct access to Microsoft articles
Customized keywords for major search engines
Access to premium content

Event ID: 53313 Source: MSDTC

XATM log object failed to set log encryption key: File=d:\viper\src\dtc\xatm\src\xatmlog.cpp Line=793.
Microsoft Distributed Transaction Coordinator (MSDTC) maintains information in the security-enhanced part of the Windows NT registry or the Windows 2000 registry. MSDTC uses this information when it performs recovery with XA-compliant databases, including Oracle. If you change the user ID under which MSDTC runs, you must make sure that MSDTC can still access the information that it previously stored in the security-enhanced part of the registry. If you change the MSDTC user ID, and MSDTC cannot access the information in the security-enhanced registry, you receive this event in the event log. See ME193893 to correct this problem.
As per Microsoft: "The Microsoft Distributed Transaction Coordinator (MSDTC) is not properly installed or is malfunctioning on one or both nodes on the Cluster Server computer". See ME223397 for more details.

Windows Event Log Analysis Splunk App

Build a great reporting interface using Splunk, one of the leaders in the Security Information and Event Management (SIEM) field, linking the collected Windows events to



Cisco ASA Log Analyzer Splunk App

Obtain enhanced visibility into Cisco ASA firewall logs using the free Firegen for Cisco ASA Splunk App. Take advantage of dashboards built to optimize the threat analysis process.