Export (0) Print
Expand All
Expand Minimize

Log Sequence Signature Mismatch

[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 a log file's Signature against the subsequent log file's Signature value to determine whether they match.

If the value of the log file's Signature value does not match the value of the subsequent log file's Signature, the Exchange Server Analyzer displays an error.

Exchange uses a series of log files, each exactly five megabytes, instead of writing all log information to a single large file. When a log file is full, Exchange closes it and renames it with a sequence number.

When a new sequence of transaction log files for an Exchange storage group is initialized, a Signature is written into the first log file, and copied into every subsequent log file. The Signature uniquely identifies a particular log file as a member of a particular log sequence.

There is never a case where log files that have different signatures should be found in the same folders. If this occurs, it indicates that foreign log files have been copied into the storage group or that the log files were reset without deleting all previous log files first.

The command Eseutil /ML LOGFILE can be used to display the Signature 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).

 
Was this page helpful?
(1500 characters remaining)
Thank you for your feedback

Community Additions

ADD
Show:
© 2014 Microsoft