Reason for the Occurrence of This Error:
Either both or one of the private and Public Exchange information stores is damaged.
Solution to Fix "Error 4294966746: JET_errDatabaseInconsistent" Error:
Before moving to the procedure below, we advise that you should take backup of all the information store database to avoid further any damage. Use the below mentioned steps to fix the above problem:
1. Read all error messages and events of Application log
2. Run eseutil / mh command line tool to verify the integrity of the Exchange databases (Priv.edb and Pub.edb). An inconsistent information store database indicates "Dirty Shutdown" status but it doesn't mean that it is corrupt. This condition can also appear if all the transaction logs have not yet been committed successfully.
3. Perform soft recovery (run eseutil /r) and replay all the transaction logs for the corrupted databases.
4. If soft recovery method does not work, perform hard recovery (run eseutil /p) and remove all .chk and .Log files
5. If eseutil /p (hard repair) command line tool work perfectly, then run eseutil /d and isinteg -pri -fix -test alltests commands in sequence to defragment and work around database issues respectively.
6. In situation, if the problem still persists, use a third party tool to handle this problem effectively. A third party recovery utility uses safe, secure, and quick analyzing algorithm to perform complete Exchange database recovery. This recovery program allows recovery of damaged data from both .edb as well as .stm files created in any version of MS Exchange Server.
Either both or one of the private and Public Exchange information stores is damaged.
Solution to Fix "Error 4294966746: JET_errDatabaseInconsistent" Error:
Before moving to the procedure below, we advise that you should take backup of all the information store database to avoid further any damage. Use the below mentioned steps to fix the above problem:
1. Read all error messages and events of Application log
2. Run eseutil / mh command line tool to verify the integrity of the Exchange databases (Priv.edb and Pub.edb). An inconsistent information store database indicates "Dirty Shutdown" status but it doesn't mean that it is corrupt. This condition can also appear if all the transaction logs have not yet been committed successfully.
3. Perform soft recovery (run eseutil /r) and replay all the transaction logs for the corrupted databases.
4. If soft recovery method does not work, perform hard recovery (run eseutil /p) and remove all .chk and .Log files
5. If eseutil /p (hard repair) command line tool work perfectly, then run eseutil /d and isinteg -pri -fix -test alltests commands in sequence to defragment and work around database issues respectively.
6. In situation, if the problem still persists, use a third party tool to handle this problem effectively. A third party recovery utility uses safe, secure, and quick analyzing algorithm to perform complete Exchange database recovery. This recovery program allows recovery of damaged data from both .edb as well as .stm files created in any version of MS Exchange Server.
No comments:
Post a Comment