| An Exchange Server database is susceptible to | | | | consequences. Use the below steps in order to |
| different corruption problems, such as dirty | | | | solve the above problem: |
| database shutdown, antivirus scanning, log file | | | | 1. Analyze all the error message and events of |
| issues, and others. Thus an administrator might | | | | application event log that Exchange reports on |
| require different Microsoft Exchange Recovery | | | | attempting to start the Information Store |
| tools to solve such problems and to continue | | | | 2. Run eseutil /mh command to check the |
| working the e-mailing environment. | | | | integrity of Exchange databases (Priv.edb and |
| Further is a scenario that depicts a similar situation | | | | Pub.edb). An inconsistent database shows 'Dirty |
| of Exchange Server database corruption. As an | | | | Shutdown' state but is not always corrupt. This |
| Exchange Server administrator, you may observe | | | | state can also occur if all the transaction logs |
| one or more of the below symptoms: | | | | have not been committed yet. |
| 1. You cannot start and/or Information Store | | | | 3. Replay all the transaction log by performing soft |
| service | | | | database recovery. For this, execute eseutil /r |
| 2. Exchange clients lose the ability to send or | | | | command for the affected database(s). |
| receive e-mails. You cannot solve this issue by | | | | 4. Run hard database repair in case soft recovery |
| restarting the server | | | | doesn't work. Run eseutil/ p command and delete |
| 3. You restore the database from an offline | | | | all the .chk and .log files |
| backup but the database is still inconsistent. On | | | | 5. Check if the previously occurring symptoms go |
| running Isinteg utility (database integrity check), it | | | | away. If you can successfully work with the |
| gives the below error message on screen: | | | | database(s), they are repaired. Next, run eseutil |
| “Error 4294966746: | | | | d and isinteg -pri -fix -test alltests commands in |
| JET_errDatabaseInconsistent” | | | | sequence to defragment and fix database issues |
| Cause | | | | respectively. |
| Information Store is corrupt. Either both or one of | | | | 6. In case, the problem remains the same, use a |
| public store and private store is corrupted. | | | | third-party Exchange Server Recovery tool to |
| Solution | | | | diagnose and repair the database more |
| Before trying the below steps, you are | | | | effectively. A Microsoft Exchange Recovery utility |
| recommended to take the backup of the entire | | | | uses safe, yet powerful, scanning procedures and |
| Information Store to prevent any post-crash | | | | allows for easy database repair. |