These days, many organizations are using MS Exchange Server as their email server application. This powerful email tool helps in storing and managing all e-mails transactions of the entire organization. MS Exchange Server uses database files to store all the emails, contacts, calendar entries, notes, tasks etc, included in individual mailboxes. If any time this Exchange database gets corrupt, all these email objects and other data will simple become inaccessible to users. However, you can use an Exchange recovery utility to repair the corrupt Exchange database and recover all your precious mail objects back.

An Exchange Server database is divided in several tables, which are further divided into multiple records and columns. These records and columns hold the data related to the mailboxes and are recognized by MAPI properties. Sometimes, when the database file gets corrupt, it simply fails to recognize these tables and declare them as invalid. When you try to access mail or any other component, the Exchange Server throws error messages and the same is logged in the Exchange event log file.

In such scenarios of database corruption, one of the event ID, which is viewed in the application event log of your Exchange Server can be read as:

”Information Store (2412) Data inconsistency detected in table X11 of Database Putu_Performa”

Note: Here ‘X11’ is the Table_Name and ‘Putu_Performa’ is the Exchange Server database name.

After encountering the above error message, if you run the ‘eseutil/g’ command to check the integrity of the database, it also fails with the below error message:

”The Database is corrupted.”

Reason:

From the above message, it is quite clear that the Exchange Server database has been corrupted. There are many possible reasons behind the corruption of the database, including bad sectors in the server drives, contradiction with other software/hardware, virus attack etc.

How to Fix:

In order to resolve the problem, first look into the system log. There you will get more clear idea about the reason behind the problem. Below options will help you resolve the problem:

• Run the ‘eseutil/p’ command to repair the database. Then, run ‘eseutil /d’ to defrag the same and finally execute the command ‘isinteg –fix’.
• If the above process fails to resolve the problem, export all the data in the Exchange database using the command, ‘Exmerge’, create a blank store, then again import the data using the same command.

However, if the problem still persists, take the help of any advanced Exchange Server recovery software to repair the damaged Exchange Server database and recover the data back. These utilities are completely read-only in their recovery operations and retrieve all your precious mailboxes in their original format.