Exchange Server 2010 Corrupt Mailbox – Discover How May It Appear

By Author: bob pitt
Total Articles: 1
Comment this article

Communication is one of the most vital segments of an organization and Exchange Servers are rising as the most preferred brand to rely upon when looking for a trustworthy and capable source of communication for an entire organization. Meanwhile, Exchange Server is available in its very advanced 2010 edition which offers a wide range of utmost technical lineaments but the fact that the database still remains as prone to corruption as it was before doesn’t change at all. This segment discuses about the same and offers some significant information about one of the culprits that may be responsible for the corruption taken place within your 2010 Server database. You will get to know a lot about one of the strongest reasons which may lead to an Exchange Server 2010 corrupt mailbox.
What Could Hamper Exchange Server 2010 Mailbox?
Basically whenever depravation happens to take place within the Server database it mostly affects information store segment. As a matter of fact, the possibility of Pub.edb or Priv.edb corruption is always there within the information store. An error message will definitely be displayed to you ...
... as soon as the information store of the database gets damaged stating; ‘error 4294966746: JET_errDatabaseInconsistent’.
Consequences: The end results of such an issue are always inaccessibility of the MS Exchange information store services.
What To Do Next?
The first and foremost action that you are required to take is confirmation of the retention of your Exchange Server database by starting up the information store service. In order to check the same, you have to run the below mentioned command that will be available in the Bin folder.
‘c:\exchsrvr\bin>eseutil /mh ..\mdbdata\priv.edb” “c:\exchsrvr\bin>eseutil /mh ..\mdbdata\pub.edb’
Once you are done with that, if you come across a database which is actually not consistent then the problem has to be resolved and that is feasible via performing database soft recovery. But if the database still remains in the same condition, all you are required to do is use the built in solution offered by MS Exchange in the name of ‘Eseutil.exe’.
NOTE: You are required to be extremely technically inclined plus patient as the procedure executable for the recovery of EDB database in the affected Information Store tends to be quite lengthy.
Most of the times, users fail in receiving a reliable and successful solution via any of the above discussed ways of recovery; soft recovery or recovery via built in utility. Hence, it is strictly advised that one must always go for a third party application instead. Exchange Recovery program is one amongst them and as a matter of fact; a very good one indeed which can be used for executing the recovery of Exchange Server 2003 to 2010 mailbox database.