Throughout Corruption problem, Exchange Administrators can exploit Eseutil/Isinteg command lines to repair inaccessible or corrupted Exchange database files. Both the utilities inbuilt attribute of MS Exchange Server & can execute both soft and hard recovery from offline Exchange Server. Default drive position of these utilities is shown below:
C:\Program Files\Exchsrvr\bin
Carry out the following directions before using Eseutil/Isinteg Utilities
Both the commands (Eseutil and Isinteg) only useful on offline Exchange database, so database should be dismounted from the MS Exchange Server before you execute these tools. You can also run the Exeutil.exe command from the DOC command prompt.
Follow the below steps to run Eseutil command line
Eseutil.exe tool has 2 repair modes “/r” and “p”.
Eseutil/r command is for soft recovery of Exchange Server database.
Apart from this if Exchange database are highly corrupted then you must be use Eseutil/p command line to repair inaccessible priv1.edb and pub1.edb files
Eseutil /p C:\Program files\Exchsvr\mdbdata\ primary name.EDB
When you effectively repaired the damaged Exchange database files by Eseutil/p command line then also run Eseutil/d command to defragment the repaired database
Now run the Eseutil.exe command for check reliability of repaired Exchange database, it will appear like below
Isinteg –s {Exchange Server name}-fix-test all tests
Conclusion: Facing corruption in Exchange EDB files at high level by jet engine failure or software out of order cannot be repair by Eseutil & Isinteg tools. So, you should be choosing a third party solution as Exchange Database Recovery Tool. Software has capable to repair, restore & convert healthy or offline database into Outlook PST/Live Exchange Server.