MSExchangeIS 9518 (0xfffffea8): Mismatched Database Time Stamp in the Database File
[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 https://go.microsoft.com/fwlink/?linkid=34707.]
Topic Last Modified: 2007-01-23
The Microsoft® Exchange Database Troubleshooter Tool detected one or more MSExchangeIS 9518 events with error code 0xfffffea8 in the Application log. This error occurs if the dbtime on the current page of the affected database is greater than the global database dbtime of the database.
Explanation
When this error occurs, the affected mailbox or public folder databases will not mount. The error is also identified as JET_errDbTimeCorrupted.
The error applies to the following versions of Exchange server:
Microsoft Exchange Server 2007
Microsoft Exchange Server 2003
Microsoft Exchange 2000 Server
User Action
To resolve the database time stamp mismatch, run the eseutil /d command to defragment the database that is experiencing this issue, and then mount the database. For more information about how to run eseutil /d, see How to Run Eseutil /D (Defragmentation). In addition, see Microsoft Knowledge Base article 328804, How to defragment Exchange databases.