Share via

How to Configure Routing Table Logging

  • Article

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, Exchange Server 2007 SP1, Exchange Server 2007 SP2, Exchange Server 2007 SP3

This topic explains how to configure routing table logging in Microsoft Exchange Server 2007.

Routing table logging periodically records a snapshot of the routing table that is used by the Exchange 2007 server that has the Hub Transport server role or Edge Transport server role installed. The routing table is used to route messages to their destinations.

Before You Begin

To perform the following procedures, the account you use must be delegated the following:

  • Exchange Organization Administrator role

To perform the following procedures on a computer that has the Edge Transport server role installed, you must log on by using an account that is a member of the local Administrators group on that computer.

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

Note

You cannot configure the routing table logs by using the Exchange Management Console. To configure the routing table logs, you must use the Exchange Management Shell. For more information about how to use the Exchange Management Shell, see Using the Exchange Management Shell.

Configuring the Location of the Routing Table Logs

By default, the routing table logs are stored in the C:\Program Files\Microsoft\Exchange Server\TransportRoles\Logs\Routing directory. The directory must be local to the Exchange 2007 computer.

To use the Exchange Management Shell to change the location of the routing table logs

  • Run the following command:

    Set-TransportServer <Identity> -RoutingTableLogPath <LocalFilePath>

    For example, to change the location of the routing table log to C:\Routing Table on an Exchange 2007 computer that is named Exchange01, run the following command:

    Set-TransportServer Exchange01 -RoutingTableLogPath "C:\Routing Table"

When you change the location of the routing table log directory, this change does not copy any existing log files from the old directory to the new directory. The new routing table log directory is active almost immediately after the configuration change, but any existing log files are left in the old directory.

The following permissions are required on the routing table log directory:

  • Administrator: Full Control

  • System: Full Control

  • Network Service: Read, Write, and Delete Subfolders and Files

By default, the Microsoft Exchange Transport service uses the security credentials of the Network Service user account to create the new routing table log directory and apply the correct permissions as follows:

  • If the new routing table log directory does not already exist, and the Network Service account has the rights that are required to create folders and apply permissions at the new location, the new routing table log directory is created and the correct permissions are applied to the new directory.

  • If the new routing table log directory already exists, the existing folder permissions are not checked.

Whenever you move the routing table log directory by using the Routing TableLogPath parameter with the Set-TransportServer cmdlet, it is a good idea to verify the new routing table log directory and to make sure that the new directory has the correct permissions applied to it. If your change to the routing table log directory is not successful, you can create the new routing table log directory and apply the correct permissions to it before you use the RoutingTableLogPath parameter with the Set-TransportServer cmdlet.

Configuring the Interval for Automatic Recalculation of the Routing Table

The routing table is recalculated and logged after a routing configuration change, or after a specified time interval has passed if no changes are detected. By default, the routing table is automatically recalculated every 12 hours. However, a regular routing configuration change occurs on every Hub Transport server and Edge Transport server when the server renews its Kerberos token with an Active Directory directory service domain controller. With this renewal, the routing table is recalculated and a new routing table log is created. The Kerberos token is renewed every six hours.

The interval for automatic recalculation of the routing table is controlled by the RoutingConfigReloadInterval parameter in the EdgeTransport.exe.config file that is located in C:\Program Files\Microsoft\Exchange Server\Bin. The EdgeTransport.exe.config file is an XML application configuration file that is associated with the EdgeTransport.exe file. EdgeTransport.exe and MSExchangeTransport.exe are the executable files that are used by the Microsoft Exchange Transport service. This service runs on every Hub Transport server or Edge Transport server. Changes that are made to the EdgeTransport.exe.config file are applied after the Microsoft Exchange Transport service is restarted.

The following example shows the typical structure of the EdgeTransport.exe.config file:

<configuration>

<runtime>

<gcServer enabled="true" />

</runtime>

<appSettings>

<add key="Configuration Option" value="Value" />

...

</appSettings>

</configuration>

You can add new configuration options or modify existing configuration options in the <appSettings> section. Many configuration options available are completely unrelated to the routing table. Any configuration options that don't involve the routing table are outside the scope of this topic.

Note

The parameter names in the <add key=../> section are case sensitive.

To configure the interval for automatic recalculation of the routing table

  1. Open the following file by using Notepad: C:\Program Files\Microsoft\Exchange Server\Bin\EdgeTransport.exe.config.

  2. Modify the following line in the <appSettings> section:

    <add key="RoutingConfigReloadInterval" value="<interval>" />

    For example, to change the interval for automatic recalculation of the routing table to 10 hours, modify the RoutingConfigReloadInterval parameter as follows:

    <add key="RoutingConfigReloadInterval" value="10:00:00" />

  3. Save and close the EdgeTransport.exe.config file.

  4. Restart the Microsoft Exchange Transport service.

To specify an age value, enter it as a time span, as follows: hh:mm:ss, where h = hours, m = minutes, and s = seconds.

The routing table will be recalculated and logged earlier than the value that is specified by the RoutingConfigReloadInterval parameter if any of the following conditions occur:

  • A routing configuration change is detected. For example, a Send connector or a Receive connector is added, removed, or modified, or the 6 hour Kerberos token renewal occurs.

  • The Microsoft Exchange Transport service is started.

Configuring the Maximum Size of the Routing Table Log Directory

By default, the maximum size for the whole routing table log directory is 50 MB. Circular logging deletes the oldest routing table log files if either of the following conditions is true:

  • The routing table log directory reaches its specified maximum size.

  • A routing table log file reaches its specified maximum age.

Note

By default, the transport logging process has a logging level value of 0 (Lowest). If you want Microsoft Exchange to write an event log entry when circular logging removes a log file, you must change the logging level value of the transport logging process to 5 (Maximum) or 7 (Expert). For more information, see How to Change Logging Levels for Exchange Processes.

To use the Exchange Management Shell to change the maximum size of the routing table log directory

  • Run the following command:

    Set-TransportServer <Identity> -RoutingTableLogMaxDirectorySize <DirectorySize>

    For example, to set the maximum size of the routing table log directory to 70 MB on an Exchange 2007 computer that is named Exchange01, run the following command:

    Set-TransportServer Exchange01 -RoutingTableLogMaxDirectorySize 70MB

When you enter a value, qualify the value with one of the following units:

  • B (bytes)

  • KB (kilobytes)

  • MB (megabytes)

  • GB (gigabytes)

  • TB (terabytes)

Unqualified values are treated as bytes. The valid input range for this parameter is 1 to 9223372036854775807 bytes.

Configuring the Maximum Age for the Routing Table Logs

By default, the maximum age for any routing table log file is 7 days. Circular logging deletes the oldest routing table log files if either of the following conditions is true:

  • The routing table log directory reaches its specified maximum size.

  • A routing table log file reaches its specified maximum age.

Note

By default, the transport logging process has a logging level value of 0 (Lowest). If you want Microsoft Exchange to write an event log entry when circular logging removes a log file, you must change the logging level value of the transport logging process to 5 (Maximum) or 7 (Expert). For more information, see How to Change Logging Levels for Exchange Processes.

To use the Exchange Management Shell to change the maximum age for a routing table log file

  • Run the following command:

    Set-TransportServer <Identity> -RoutingTableLogMaxAge <Age>

    For example, if you want to change the maximum age of a routing table log file to 45 days on an Exchange 2007 computer that is named Exchange01, run the following command:

    Set-TransportServer Exchange01 -RoutingTableLogMaxAge 45.00:00:00

To specify an age value, enter it as a time span, as follows: dd.hh:mm:ss, where d = days, h = hours, m = minutes, and s = seconds. The valid input range for this parameter is 00:00:00 to 24855.03:14:07. Setting the value of the RoutingTableLogMaxAge parameter to 00:00:00 prevents the automatic removal of routing table log files because of their age.

For detailed syntax and parameter information, see Set-TransportServer.

For More Information

For more information about routing table logging, see Managing Connectivity Logging.