If the repair count attribute in the output is 0 (zero), the eseutil /p command was not run on the database. If the repair count attribute in the output is a number other than 0 (zero), the eseutil /p command was run on the database.
Check the consistency (state) of the information store databases to determine if you have to remove the Eseutil log files. To do so, view the output from the command you ran in step 1.
The database is consistent if the output lists the database state as Clean Shutdown. All the log files have been committed to the information store.
The database is not consistent if the output lists the database state as Dirty Shutdown. This state may occur as a result of corruption or it may occur if the log files have not been committed to the information store yet. To determine if this state occurs because the log files have not been committed to the information store, wait a few minutes, and then run the command again.
If the database state is listed as Clean Shutdown, remove all the log files from the Mdbdata folder. Put these files in a backup folder.
Mount the information store. To do so:
Start Exchange System Manager. To do so, click Start, point to Programs, point to Microsoft Exchange, and then click System Manager.
Double-click ServerName, right-click Mailbox Store, and then click Mount Store.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.
For additional information about disaster recovery and related issues and utilities, click the following article numbers to view the articles in the Microsoft Knowledge Base:
Microsoft Exchange Server 2003 Enterprise Edition, Microsoft Exchange Server 2003 Standard Edition, Microsoft Windows Small Business Server 2003 Premium Edition, Microsoft Windows Small Business Server 2003 Standard Edition