There are two (2) possible causes for this occurring;


The database file is severally damaged, corrupted or invalid.

RESOLUTION: Restore another copy of the database from backup and attempt access with DigiScope.

NOTE: To validate the state of the database;

  1. Obtain a copy of eseutil.exe for the version of the database being opened which can be found within the Microsoft Exchange/Bin directory of the Exchange Server. Copy that file into the same directory that contains the database.
  2. Open a command prompt and run a header dump of the db with the following command: Eseutil /mh Your_Database_Name.edb
  3. If you are not familiar with reading database header dumps Open an Open a New Support Ticket, explain your situation and include a copy of the Eseutil /MH output.


While rare this can occur if the database is being loaded from slow USB, external drives OR if you are attempting to load the database across a saturated or slow network connection.

RESOLUTION: Move the database files to a local drive on the DigiScope enabled machine OR install DigiScope on a machine that has direct access to the database files.

SUPPORT: If you experience issues, have questions or need assistance after following these instructions please  Open a New Support Ticket or if you already have a ticket open reply with details and we will be happy to assist.