EDB files are the pivot around which the major functions of Exchange Server revolve. Its importance resides in its ability to hold the mails sent or received. Whenever a set of EDB files go corrupt a shockwave of data crisis is generated. The losses suffered from the damages can be unliquidated but the blockage can definitely hamper the working of Microsoft Exchange. If the damage is of minute nature then it can be healed with the Microsoft Utilities – Eseutil, Isinteg and PFDAVAdmin.
Restore Exchange by using the Eseutil & Isinteg utilities:
Note: Here we have taken the example of Jet Engine Error i.e. Error 4294966746.
The Eseutil utility can be accessed by running the C:\Program Files\Exchsrvr\Bin command. But before using this utility ensure to have at least 20% of spared disk space in exchange database. With Eseutil a user can generate various commands like Defragmentation: /D, Repair: /P, Restore: /C, Recovery: /R, Integrity: / G, File Dump: /M, Checksum: /K, Copy File: /Y, etc. These are the steps for trying it:
Open the information store and register the error or ID messages. Run the Eseutil.exe utility for checking the consistency of Private and Public EDB files. For Private EDB files Run c:\exchsrvr\bin>eseutil /mh…\mdbdata\priv.edb command. For public EDB files run c:\exchsrvr\bin>eseutil /mh..\mdbdata\pub.edb command. After that provide the output in a text file:
- For Private EDB files c:\exchsrvr\bin>eseutil /mh ..\mdbdata\priv.edb > mypriv.txt.
- For Public EDB files c:\exchsrvr\bin>eseutil /mh ..\mdbdata\pub.edb > mypub.txt.
Note: Kindly enter the full path of EDB files.
In case if the files are residing in MBD folders then try the Swift Recovery process.
- c:\exchsrvr\bin>eseutil /r /ispriv
- c:\exchsrvr\bin>eseutil /r /ispub
Now conduct full recovery with the eseutil /mh command then try hard repair for any discrepancy.
- c:\exchsrvr\bin>eseutil /p /ispriv for private EDB files.
- c:\exchsrvr\bin>eseutil /p /ispub for public EDB files.
Also, remove the Temp.edb files in ExchSrvr\Mdbdata. Now check the Microsoft Exchange Information Store service and close the program if they are working normally. Simultaneously run the Defragment (eseutil/d) and repair (Isinteg) command on the private and public EDB files. Repeat this process unless zero error errors are reported.
For avoiding this cumbersome process and saving time use the reliable Exchange Server Recovery software. This restore EDB tool can quickly restore the corrupt and damaged EDB files into accessible PST files.