msdtc.log can't repair

[buzznick]

014-04-05 08:32:19, Info                  CSI    0000004a [SR] Verifying 100 (0x0000000000000064) components
2014-04-05 08:32:19, Info                  CSI    0000004b [SR] Beginning Verify and Repair transaction
any clue as to how to fix this? File is there but empty.
 




2014-04-05 08:32:20, Info                  CSI    0000004c [SR] Cannot repair member file [l:18{9}]"MSDTC.LOG" of Microsoft-Windows-COM-DTC-Runtime, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, file is missing
2014-04-05 08:32:21, Info                  CSI    0000004d [SR] Cannot repair member file [l:18{9}]"MSDTC.LOG" of Microsoft-Windows-COM-DTC-Runtime, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, file is missing
2014-04-05 08:32:21, Info                  CSI    0000004e [SR] This component was referenced by [l:202{101}]"Microsoft-Windows-Foundation-Package~31bf3856ad364e35~amd64~~6.1.7601.17514.WindowsFoundationDelivery"
2014-04-05 08:32:22, Info                  CSI    00000050 [SR] Verify complete
2014-04-05 08:32:23, Info                  CSI    00000051 [SR] Verifying 100 (0x0000000000000064) components
2014-04-05 08:32:23, Info                  CSI    00000052 [SR] Beginning Verify and Repair transaction

[Shane]

Odd it is complaining about a log file.

Go to Windows\System32\Msdtc\ and see if the log file is there, if it is see if you can rename it to something else and then reboot and see if Windows will recreate it.

Shane