There are 4 different and important database files called Pub1.edb, Priv1.edb, Pub1.stm and Priv1.stm in the Exchange Server. When any of these files gets corrupted, not single information in the database is available to the users. In order to fix this kind of problem, it is essential that the user is able to apply a new copy of the database that has been affected or use any 3rd party Exchange Server Recovery tool to fix the corrupted items. There are ample reasons for the database to get corrupted and different symptoms are generated by the server as a result of the corruption.

Imagine a situation that you try to access the System Manager in Exchange Server and try to mount the mailbox store. But before things start working out, the database fails to get mounted with the following error blinking in front of the computer screen:

'Unable to Mount the Mailbox Store with error c104173c "The Information Store is Busy”'

The aforesaid error message is evident of the fact that the EDB database is corrupted and no matter how hard you try all the files, folders and other data located in it would no longer be accessible to the user. There are many reasons for the EDB files to get corrupted like abnormal termination of the system, virus attack, server problem etc. If there is some kind of backup available, then the situation can be tackled. But the problem becomes a grave one where there is not any kind of backup available of those important files and folders.

In that kind of circumstance, users need not have to panic. The first thing that you need to do is to check for the database inconsistency by running the eseutil /mh command. When you are implementing this command, make sure that the Information Store is not running. If the command fails, then replace the command with eseutil /p and delete all the temporary EDB files and .chk files. After that using the eseutil /d command perform online defragmentation and finally run the Isinteg.exe utility. If the Exchange Mailbox Store Error c104173c continues to erupt, then the best solution is to opt for any good 3rd party Exchange Server Recovery tool that can fix the corruption and remove all the infected items using powerful algorithm and scanning methods.