Corrupted Information Store: Error 4294966746: JET_errDatabaseInconsistent

Database is an integral part of any application. When working with Microsoft Exchange, it is something which can’t be parted with. The database contains all the mails, contacts, user data and a lot of other information. A lot of corruption problems can occur due to an Exchange Database such as log file issues, antivirus scanning, database shutdown etc. Hence to ensure a speedy recovery and smooth functioning of the database and thus the server, a system administrator has to use some Microsoft Exchange Server Recovery tools.

Here is a scenario illustrating the corruption of Microsoft Exchange Server Database. Remember if working as an Administrator of Exchange Server you have encountered the following situations:

• You are unable to start Information Store Service.
• Clients are unable to send/receive emails and even the server restart does not solve the problem.
• You have restored the database from a backup which was offline but the database is still not consistent.
• When you run database integrity check – Isinteg, the following error message displays on the screen:

“Error 4294966746: JET_errDatabaseInconsistent”

Cause of the error:

The information store has got corrupted. Either one or both of the private store and public store have got corrupted.

Solution to the error:

Before you begin solving the problem, it is recommended that you take entire backup of Information Store. This will help you to cope up with the situation if Information Store crashes. Now just follow the following simple steps:

• When you try to start the Information Store, some error messages application event logs occur, generated by Exchange Server. Analyze all those messages and logs.
• To check the Exchange Database’s integrity (Pub.edb and Priv.edb), run eseutil/mh command. If database is inconsistent, it shows ‘Dirty Shutdown’ state but this doesn’t ensure that database is corrupt. The state can also appear if all of the logs of transaction were not committed.
• Perform a soft database recovery and do a replay of all the transaction logs. To perform this task for the effected database, run eseutil/r command.
• If soft recovery doesn’t give the desired results, run hard database repair. Run eseutil/p and delete whole of the .log and .chk files.
• Now you have to check for the previously stated symptoms. They should not occur now. If you are able to work successfully with the database, then it is repaired. Next, you have to defragment and fix database issues, so run the following commands in sequence – eseutil /d and isinteg -pri -fix –test alltests
• But if the problem is unresolved and you are not able to work with the database, then you will have to switch to a 3rd party Exchange Server Recovery tool, so that you can diagnose the database and repair it properly and more effectively. A Microsoft Exchange’s recovery utility allows for an easy database repair while using safe and yet powerful procedures of scanning.

Microsoft Exchange Recovery Tool: It is a professional tool to repair corrupted Exchange databases. It extracts the mailboxes in .pst files. The tool is easy to use and advanced recovery features are provided in it. It can also be used to recover the mailboxes which are deleted and inaccessible STM data.

No related posts.