Log Filename does not Match Log Generation Number
[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: 2006-07-07
The Microsoft® Exchange Server Analyzer Tool compares the value of the lGeneration internal generation number from the transaction log file header against the file name of the transaction log file to determine whether they match.
If the internal generation number from the transaction log file does not match the representation of the internal generation number in transaction log file name, the Exchange Server Analyzer displays an error.
Unless a log file is the current log, the newest available log file must have a file name that matches its generation number. If a log file is the current log, its file name should not contain its generation number, but only the log prefix for the storage group. For example, previous transaction logs in a series might be named E0154321.LOG, E0154322.LOG, E0154323.LOG, and so on, with the current log named E01.LOG.
You can use the Eseutil /ML LOGFILE command to display the internal lGeneration value for a log file.
For more information about Exchange Server transaction logging, see "Exchange Transaction Logging in Exchange Server 2003" in Using Recovery Storage Groups in Exchange Server 2003 (http://go.microsoft.com/fwlink/?LinkId=47589).