Corrupt .edb
Closed
peterweav880
Posts
1
Registration date
Thursday 18 December 2014
Status
Member
Last seen
21 December 2014
-
21 Dec 2014 à 04:00
johnwalt Posts 1 Registration date Saturday 27 December 2014 Status Member Last seen 27 December 2014 - 27 Dec 2014 à 02:16
johnwalt Posts 1 Registration date Saturday 27 December 2014 Status Member Last seen 27 December 2014 - 27 Dec 2014 à 02:16
Related:
- Corrupt .edb
- Hal.dll missing or corrupt - Guide
- Corrupt mp3 file - Guide
- How to repair corrupt usb - Guide
- System32 config system corrupt - Guide
- \Windows\system32\config\system is corrupt ✓ - Windows Forum
1 response
johnwalt
Posts
1
Registration date
Saturday 27 December 2014
Status
Member
Last seen
27 December 2014
27 Dec 2014 à 02:16
27 Dec 2014 à 02:16
First you need to stop your Information Store service and back up everything (edb, stm, and log files) to a different disk. You must ensure that you have sufficient amount of free disk space.
Now, follow the steps given below to get your database back to the clean shutdown state:
Initially, run the following command to verify your database consistency:
eseutil /mh "c:\program files\exchsrvr\mdbdata\priv1.edb"
If you find the database state to be 'Dirty Shutdown', perform a soft repair using the below command:
eseutil /r "c:\program files\exchsrvr\mdbdata\priv1.edb"
This command replays the transaction log files to make sure that all the database operations are successfully completed.
Perform a hard repair of your database using 'Eseutil /p' as follows:
eseutil /p "c:\program files\exchsrvr\mdbdata\priv1.edb"
Defrag your database stores by using the 'Eseutil /d' command-line utility.
Finally check the database integrity by running the 'Isinteg' utility from the BIN folder as follows:
'isinteg -s servername -fix -test alltests'
If doesn't help, look here: https://www.codeproject.com/Questions/843332/Trouble-reading-files-error-service-transaction-er
Now, follow the steps given below to get your database back to the clean shutdown state:
Initially, run the following command to verify your database consistency:
eseutil /mh "c:\program files\exchsrvr\mdbdata\priv1.edb"
If you find the database state to be 'Dirty Shutdown', perform a soft repair using the below command:
eseutil /r "c:\program files\exchsrvr\mdbdata\priv1.edb"
This command replays the transaction log files to make sure that all the database operations are successfully completed.
Perform a hard repair of your database using 'Eseutil /p' as follows:
eseutil /p "c:\program files\exchsrvr\mdbdata\priv1.edb"
Defrag your database stores by using the 'Eseutil /d' command-line utility.
Finally check the database integrity by running the 'Isinteg' utility from the BIN folder as follows:
'isinteg -s servername -fix -test alltests'
If doesn't help, look here: https://www.codeproject.com/Questions/843332/Trouble-reading-files-error-service-transaction-er
