Article ID: 261947 - View products that this article applies to.
This article was previously published under Q261947
This article has been archived. It is offered "as is" and will no longer be updated.
This article describes how to determine if your database has been repaired by using the Eseutil /p command.
To see if your database has been repaired by using the Eseutil /p command, dump the header using one of the following commands for the private information store:
ESEUTIL /mh x:\exchsrvr\mdbdata\priv.edb |more
ESEUTIL /mh x:\exchsrvr\mdbdata\pub.edb |moreThe output looks similar to the following example:
Microsoft(R) Windows NT(TM) Server Database UtilitiesIf the database has not been repaired, the repair count is zero and the repair date is 1/1/1900 00:00.
Copyright (C) Microsoft Corporation 1991-1999. All Rights Reserved.
Initiating FILE DUMP mode...
Format ulMagic: 0x89abcdef
Engine ulMagic: 0x89abcdef
Format ulVersion: 0x620,2
Engine ulVersion: 0x620,2
DB Signature: Create time:4/5/2000 17:48:52 Rand:769046 Computer:
Last Objid: 184
Scrub Dbtime: 0
Scrub Date: 00/00/1900 00:00:00
Repair Count: 1
Repair Date: 2/20/2000 10:48:50
Note If you run the Eseutil /p on a database that is not damaged or on a database that is damaged on a page that does not contain data (may contain only white space), the repair count is not incremented. The Repair Count=0 output indicates that no repairs have been made to the database, even if Eseutil /p has been run.