Resolving Error 4294966746 - JET_errDatabaseInconsistent Error in Exchange Server

Is your Exchange Server database inaccessible due to corruption of the Information Store? Are you getting Jet Database Engine errors while restoring database from backup? Information Store is the most commonly affected Exchange Server component, when database corruption occurs. Corruption generally occurs in Priv.edb or Pub.edb, that are located in ExchSrvr\Mdbdata directory on server. EDB (Exchange Server Database) is an extension of Exchange Server database file. In case of corruption, the database becomes inconsistent and Exchange Server can not read data from it. It leads to significant data loss situations and needs EDB Recovery, if you do not have an updated backup in place.

Microsoft Exchange Server indicates Information Store corruption with a number of symptoms, which include:

1. You can not start Microsoft Exchange Server Information Store Service.

2. The Information Store Service can not be stopped.

3. The CPU (Central Processing Unit) usage level reaches at 100% and Information Store stops responding.

4. Clients can not send or retrieve emails. The problem persists even if you stop and restart Information Store service.

5. If you attempt to restore Microsoft Exchange Server database from offline backup and run Isinteg (Information Store Integrity) utility, you come across the below error message:

“Error 4294966746: JET_errDatabaseInconsistent”

How to Fix Information Store Corruption?

To rectify the Information Store damage and recover the private and public information stores:

1. Start the Information Store service.

2. Check the consistency of Information Store using Eseutil.exe tool.

3. Remove all .chk and .log files in ExchSrvr\Mdbdata folder.

4. Verify that Exchange Server databases are working, by starting Information Store service. If it starts successfully, stop the service.

5. Defragment the Exchange Server database that you repaired. You can defragment the database using Eseutil utility.

6. Run Isinteg.exe utility to repair the databases.

7. Restart Microsoft Exchange Server Information Store Service.

8. Run the DS/IS (Directory Service/Information Store) Consistency Adjuster.

If the above method can not help you to Recover EDB file, you need to restore database from the most recent backup. However, if the backup is either damaged or not updated, you need to repair and restore the database using third-party applications.

The EDB Recovery Software work in all cases of database corruption and successfully restore database in original state, without modifying the original data.

EDB Recovery Tool is the most advanced recover edb utility for assured recovery of your damaged EDB file. The software effectively repairs Corrupt EDB File and restores all EDB file objects, such as emails, notes, contacts, tasks, notes, calendar items, and journals. It is designed for Microsoft Exchange Server 2007, 2003, 2000, and 5.5.

Additional articles about Error 4294966746

About the author

Axel Culver has passion for writing Technical article. He is right now writing articles related to Product like EDB Recovery software and EDB Repair tool for MS Exchange Server.

Please Rate This Article

Select Rating Excellent Very Good Interesting Fair Could Use Improvement

Number of ratings: 0
Rating: 0