Solving Jet Error - "JET_errRecordNotFound,the key was not found" in Exchange Server

When EDB file get corrupted, you can't mount the Exchange database and also unable to access your emails & other items from Exchange server. These situations may occur due to various reasons like suddenly exiting the Exchange Server,corruption in the database header, virus infections and hardware related issues etc.

Such problems can be handled by using in-built eseutil.exe utility. However when edb file is badly corrupted, you may receive Error "JET_errRecordNotFound". In this case the inbuilt utility may fails to perform the expected tasks which makes the database inaccessible and leads to data loss.

In order to solve this problem you need to install the latest service pack of the MS Exchange server. If it does not resolves the issue then it is necessary to use the third-party Exchange Recovery software such as Stellar Phoenix Mailbox Exchange Recovery tool to repair and restore the damaged exchange database (EDB) files.

Download the most trusted free EDB repair Software for MS Exchange Server 5.5, 2000, 2003, 2007 and 2010 from http://exchange.stellarservertools.com/

Inconsistent Database Backup when Exchange Server is Running

Exchange Server databases are consisted of .edb files (database files) and .log files (database logs). All the transactions that occur for Exchange databases are first written to .log files before actually been written to database files. A database is inconsistent if all transaction log files have not been committed to the database files. But if you shut down the information service, Exchange writes all the log files to .edb files and the database comes to a completely consistent state. Thus, if you backup the database while information service is running, it will not be consistent. If your EDB files become corrupt and you try to restore from such a backup, it will give errors and the information service might fail to start. This creates an unavoidable situations of using an EDB Repair solution for your corrupted database files.

For example, consider your Exchange database files are corrupted. When you try to start Exchange Server services after restoring from a backup, you may encounter the below error in application log or on screen:


“Error -550 has occurred”

You cannot start the Exchange Server services.

Cause

You have used the backup software when Exchange Server was online. As a result, the backup is inconsistent and has failed to perform successful restore.



Solution


To prevent such errors from occurring, you are suggested to perform the database backup after stopping all the directory and information store services. Alternatively, you can look for backup solutions that are exclusively built to perform Exchange databases' backup in online state.

However, to recover the data from corrupted database files, you need to use these tools:

1. Eseutil /r command to perform soft database recovery
2. Eseutil /p command for hard repair
3. Third-party EDB Repair Tool

The hard recovery option of Exchange deletes the corrupted pages, which is not safe. Thus, you should use EDB Repair utilities if soft recovery fails. These software bring you the most effective and safe scanning algorithms for repairing damaged Exchange databases. Due to the interactive user interface they provide, these applications are easy to implement

EDB Repair Software is a feature-rich utility that employs powerful scanning algorithms to repair a damaged Exchange database. It supports Exchange Server 5.5, 2000 and 2003. It is a safe and advanced EDB Repair Tool with impressive set of features. The tool extracts user mailboxes in individual .pst file format files without affecting the original contents and view.

How to Solve when Exchange Database Fails to Mount with (hr=0x80004005, ec=-528) Error?

Transaction log files record all the modifications to an Exchange Server database and are crucial for the proper functioning of Exchange. If you remove a log file that has not been written to the associated database, it can bring several issues, the most common being that the database may fail to mount. You can solve this problem by removing all the log files, but you first need to check the database consistency. If it exists in inconsistent state, the solution is to restore from backup or apply an EDB Repair technique. For instance, consider a scenario in Exchange Server. You try to mount a mailbox store, but the operation fails with the below error message.