Exchange note Resolves a mailbox database repair (ESEUTIL)

A netizen mistakenly deleted the log file of the mailbox database resulting in an error and the mailbox database could not be mounted.

Error:

Workaround:

First, the use of data recovery software to find the deleted log file and restore the following error: (can only hold the mentality of try, just delete may be useful it)

"Morning 2018/06/04 10:20:40
Information Store-mailbox database B (50196) Mailbox databases B: Because of a reference to "E:\Database\Mailbox db B.edb" that is not currently present, the number Database recovery failed with error-1216. The database will not be in a "clean shutdown" state until the database is deleted (or possibly moved or renamed). For this instance, the database engine does not allow the recovery process to complete until the lost database is reset. If the database is no longer available and is no longer needed, refer to the steps provided in the Microsoft Knowledge Base to resolve the error, or click the Details link at the bottom of this message. 》

Note: The Isinteg command mentioned below does not necessarily apply to a higher version of Exchange, nor is it necessary to repair a command.

TIPS: Isinteg is a useful tool for searching the offline information store for flaws in integrity. You can also fix problems detected by the Isinteg. Isinteg run at the command prompt.

Ii. repair using the Eseutil command

Execute ESEUTIL/MH < database absolute path, and see if state is Dirtyshutdown or Cleanshutdown.

1. If the clean shutdown State can perform a soft fix

Note: A basic assumption of the soft recovery process is that the failure did not move, delete, or destroy any database files or log files, and the administrator did not do so after the failure.

Run the EXEUTIL/R again, and then use Isinteg.exe to repair the PUB1 and PRIV1 database Isinteg-s (servername)-fix-test alltests, restart the Information Store service, mount the database.

2. If the Dirtyshutdown state requires a hard fix. (More of this state)

2.1 ESEUTIL/R

Even if you run a hard fix it is recommended that you first try to fix the next logical error by using the ESEUTIL/R command.

2.2 ESEUTIL/MH

Then execute the ESEUTIL/MH < database sentence to the path, and check the status

2.3 eseutil/p

cut all log, chk, temp.edb files in the database folder to a different folder and execute the eseutil/p < database absolute path > command until the repair is complete.

{Note: The eseutil/p can also be repaired directly, and then remove all files such as log, CHK, Temp.edb, etc when attempting to mount the file}

2.4 eseutil/d

Perform eseutil/d < database absolute path > defragment, which may cause database indexing and spatial allocation errors if not defragmented. (The production environment is recommended to be executed or skipped.)

2.5 isinteg-s (servername)-fix-testalltests (can be skipped, ex13\16 did not test this command)

You should be able to mount the database properly at this time. In order to perform the above command to repair the database at the application level, the database that executes this command must be offline and dismount the database if it is mounted.

After the Isinteg is complete, you should report 0 errors in the database. If the error count is greater than 0, run Isinteg again until the count becomes 0, or the count is no longer reduced in subsequent runs. If the error count cannot be zeroed, the database migration is recommended after hanging.

Third, repair completed, mount the database, restart information storage services.

Exchange note Resolves a mailbox database repair (ESEUTIL)