Log Generation Discrepancy

[This topic is intended to address a specific issue called out by the Exchange Server Analyzer Tool. You should apply it only to systems that have had the Exchange Server Analyzer Tool run against them and are experiencing that specific issue. The Exchange Server Analyzer Tool, available as a free download, remotely collects configuration data from each server in the topology and automatically analyzes the data. The resulting report details important configuration issues, potential problems, and nondefault product settings. By following these recommendations, you can achieve better performance, scalability, reliability, and uptime. For more information about the tool or to download the latest versions, see "Microsoft Exchange Analyzers" at http://go.microsoft.com/fwlink/?linkid=34707.]  

Topic Last Modified: 2005-11-18

The Microsoft® Exchange Server Analyzer Tool has determined that you have a log file generation discrepancy. This error indicates that a transaction log file has been renamed with an inappropriate sequence number.

Exchange transaction log files are named according to the following format: EnnXXXXX.log

  • XXXXX = A five digit hexadecimal sequence number. When a new set of transaction log files is generated, the first log in the sequence will be 000001, and the next log will be 00002, and so on. Because each transaction log records its own sequence number in its header, you can determine whether the log filename has been changed.

  • Enn = The log prefix, which is a three character sequence shared by every transaction log for this storage group. Typically, the prefix will be E00, E01, E02, E03 or R00 (for a recovery storage group).

The current log being written to is named only with the log prefix. This log does not acquire a sequence number until it has been closed and a new current log is generated. Therefore, the current log file may be named E00.log. When this log file is full, it may be renamed E0012345.log. A new E00.log would be generated with an internal sequence number of 12346.

To correct this error
  • Rename the log file to the appropriate sequence number.

To view the internal sequence number
  • Run the following command:

    C:\Program Files\Exchsrvr\Bin\Eseutil.exe /ML [log filename]

    The lGeneration value in the output of this command lists the actual sequence number of the log file.


Community Additions