How to Enable Tracing for the LogTruncator Component

Exchange 2007

Microsoft Exchange Server 2007 will reach end of support on April 11, 2017. To stay supported, you will need to upgrade. For more information, see Resources to help you upgrade your Office 2007 servers and clients.


Applies to: Exchange Server 2007 SP3

Topic Last Modified: 2016-11-10

This topic explains how to use the Microsoft Exchange Troubleshooting Assistant (ExTRA) program to enable tracing functionality for the LogTruncator component in Microsoft Exchange Server 2007.

To perform this procedure, the account that you use must be delegated the following:

  • Exchange Server Administrator role

  • Local Administrator rights on the Exchange server

Also, before you perform this procedure, you must have one of the following updates installed:

  • Update Rollup 8 for Exchange 2007 Service Pack 1 or a later update rollup.

  • Exchange Server 2007 Service Pack 3 (SP3).

For more information about permissions, delegating roles, and the rights that are required to administer Exchange 2007, see Permission Considerations.

  1. Start the ExTRA.exe program. By default, this program is located in the %PROGRAMFILES%\Microsoft\Exchange Server\Bin folder.

  2. In ExTRA, click Select a task, and then click Trace Control.

  3. On the warning message that you receive, click OK.

  4. Click Set manual trace tags.

  5. In the Components to trace list, click Cluster.Replay.

  6. Under Trace Tags, click LogTruncator.

The LogTruncator is a component of the Exchange 2007 Replication service. The Replication service uses several components to provide continuous replication between an active storage group and one or more copies of the active storage group. The LogTruncator deletes log files that have been successfully replayed into the database copy. You can use log tracing with the Exchange Troubleshooting Assistant to troubleshoot a log truncation issue in a Standby Continuous Replication (SCR) environment.

For more information about Replication service components, see the Continuous Replication Deep Dive white paper.