Windows Server 2012 - Log service encountered a corrupted metadata file (KtmRm for Distributed Transaction Coordinator)

Maciej Szuchta 1 Reputation point


I have a problem with "KtmRM for Distributed Transaction Coordinator" service. My application needs that service in order to work properly. We've recently noticed that this service cannot be started at all. In event viewer we observe a a lot of logs saying

   - <Event xmlns="">  
   - <System>  
     <Provider Name="Service Control Manager" Guid="{555908d1-a6d7-4695-8e1e-26931d2012f4}" EventSourceName="Service Control Manager" />   
     <EventID Qualifiers="49152">7024</EventID>   
     <TimeCreated SystemTime="2022-10-31T12:56:08.653426500Z" />   
     <Correlation />   
     <Execution ProcessID="528" ThreadID="4996" />   
     <Security />   
   - <EventData>  
     <Data Name="param1">KtmRm for Distributed Transaction Coordinator</Data>   
     <Data Name="param2">%%2147949012</Data>   


I searched the web and found that 2147949012 error is

Log service encountered a corrupted metadata file.

I'm wondering what can cause this issue or how can I proceed to find the resolution.
Any advice will be useful.

Windows Server
Windows Server
A family of Microsoft server operating systems that support enterprise-level management, data storage, applications, and communications.
12,420 questions
0 comments No comments
{count} votes

1 answer

Sort by: Most helpful
  1. Wesley Li-MSFT 4,391 Reputation points Microsoft Vendor


    The Microsoft Distributed Transaction Coordinator (MSDTC) uses the Kernel Transaction Manager Resource Manager service (KtmRm) to coordinate transactions with the Windows Kernel Transaction Manager (KTM).

    The MSDTC agent calls the function, and the registry check fails during the process because the application process identifies an account in the Users group and does not have access to the registry.

    The workaround is to add the identity account of the application process to the Administrators group, before that you may need to restart the MSDTC service to perform these steps.

    Related Reference Documents:

    Best Regards,
    Wesley Li

    0 comments No comments