Resetting the DTC Log File (Component PSDK)

 

Applies To: Windows 10, Windows 7, Windows 8, Windows 8.1, Windows Server 2008, Windows Server 2008 R2, Windows Server 2012, Windows Server 2012 R2, Windows Server Technical Preview, Windows Vista

While you must reset the DTC log file to relocate it to another device or to change its size, you should not do so under normal circumstances because the DTC might lose track of pending transactions, which could affect the consistency of the transaction-protected databases, message queues, and files coordinated by the DTC.

It is not necessary to reset the DTC log file to reclaim disk space within the file because the DTC does this automatically. When a transaction has successfully committed or aborted, the DTC notes that the log records are no longer needed and it eventually reuses the space for other transactions

Note

You cannot reset the DTC log file on a remote system. The Component Services administrative tool updates the DTC log file directly, and therefore it must run on the system where the log file resides. For step-by-step information about resetting the DTC log file or changing log file attributes, see the Help documentation for the Component Services administrative tool on your system.

Before altering the DTC log file, ensure that there are no transactions in the In Doubt, Cannot Notify Abort, or Cannot Notify Commit state. Refer to Transaction State Resolution After System Failure for more information.

See Also

Choosing the DTC Log File Location
DTC Log File Management
Restoring Damaged DTC Log Files