| <!-- @page { margin: 0.79in } P { | | | | c104173c "The Information Store is Busy"' |
| margin-bottom: 0.08in } A:link { so-language: zxx } | | | | This error is one among the clear indications that |
| --> | | | | one or both of EDB database files is/are |
| Microsoft Exchange Server Information Store is | | | | corrupted. |
| comprised of four basic database files: Priv1.edb, | | | | Solution |
| Priv1.stm, Pub1.edb, and Pub1.stm. When the | | | | Pre-assuming few attributes like, single site and |
| Information Store is corrupted, typically one or | | | | server issue, KM Manager not being used, and |
| both of the EDB files, which are located in | | | | existence of an offline database backup (either on |
| Program Files\Exchsrvr\Mdbdata folder, are | | | | same drive or external storage media), following |
| involved. These database files comprise stored | | | | is the solution that can help you isolate database |
| and in-process non-SMTP e-mails and thus their | | | | corruption: |
| corruption leads to data unavailability for the users. | | | | Run eseutil /mh command to check the database |
| To correct such instances of database corruption, | | | | consistency while making sure that Information |
| an Exchange administrator requires applying an | | | | Store service is not running. |
| updated, healthy copy of affected database or | | | | If state of one or both of databases is dirty, |
| otherwise, running edb recovery solutions. | | | | replay the uncommitted transactions using soft |
| An Exchange database corruption can be | | | | recovery command- eseutil /r. In case, the |
| detected by different symptoms that server | | | | command fails, you need to run hard database |
| generates. For example, consider a scenario when | | | | recovery using eseutil /p command, delete all the |
| an Exchange administrator accesses the Exchange | | | | .chk and temp.edb files, run off line |
| System Manager and tries to mount the mailbox | | | | defragmentation with eseutil /d command, and |
| store. The administrator finds that it cannot | | | | then run Isinteg.exe utility. |
| complete the database mount operation and | | | | If database(s) appear to be consistent and are still |
| receives the below mentioned error message: | | | | in unmountable state, you can run hard database |
| 'Unable to Mount the Mailbox Store with error | | | | recovery, as described above. |