JET_errRecordNotFound, The key was not found – Guide to Fix the Error

Exchange Server has some errors, which may interrupt the database processing and as a result, server may freeze. Amongst these several errors of Exchange server, one such error is JET_errRecordNotFound, The key was not found. In this blog, we are going to discuss about this issue (in detail), reasons behind its occurrence and multiple workarounds to get rid of such issue.

In the upcoming segment, we will elaborate the below mentioned concepts:

About JET_errRecordNotFound

This problem is an Exchange JET error, which occurs when a user mounts the Exchange database and tries to access mailboxes from Exchange server. Depending upon several parameters, this error is being assigned with two error codes, i.e. 1601 and 1605. Occurrences of such errors are common in Exchange server because they are built on JET Blue engine technology. The following message displays when one encounters this issue: ‘Operation terminated with error -1601 (JET_errRecordNotFound, The key was not found) after 2.354 seconds.’

jet_errrecordnotfound the key was not found

Below-mentioned are the reasons due to which such common JET errors occur:

  • The Exchange transaction log files or databases are corrupted or damaged and hence, cannot be accessed.
  • In Exchange server, if user uses ESEUTIL utility for some purpose, then it could damage the STM file structure. The structure is manipulated because the utility does not ensure that it will work correctly with any version of database.


Workarounds to Resolve JET_errRecordNotFound, The key was not found

In order to fix the problem, user will have to perform some workarounds that will recover data from their corrupted database in its healthy state. User can go for one of the three workarounds mentioned below to resolve the problem:

Solution 1: Extract Data from Backup File

If end-user have created and continuously modified the backup file, then the best approach would be to extract database from that backup. This file will extract all the log files in healthy state and hence, reduce chances of error occurrence in future.

Solution 2: Using ESEUTIL & ISINTEG Utility Command

The most widely used approach for repairing corrupted database files is to execute ESEUTIL and ISINTEG utility based commands.

  • First, user will use ESEUTIL utility command. They can use one of the following shown ESEUTIL switches to resolve their problem:
  • jet error 1601
  • After executing ESEUTIL command, go for ISINTEG utility, which will rebuild & fix the JET error named as JET_errRecordNotFound, The key was not found, after repairing and extracting the data.

Solution 3: Using a Third Party Application

If the above-mentioned workarounds are not solving your problem, then go for a third party application. Such applications allow users to recover mailboxes of Exchange without any complications. One such tool is Exchange Recovery tool, which is used to recover Exchange mailboxes from corrupted databases to MS Outlook and Live Exchange Server. The application processes the STM files for any errors, converting the damaged structure of STM file into its original file structure. Moreover, it has multiple productive features embedded with it, providing end-users to fix their problem effortlessly.

Conclusion: After having a discussion about JET error (JET_errRecordNotFound) and solutions for fixing it, one could conclude with the fact that such problems can easily be handled by both technical experts and non-technical users. If user has created the backup, then it would be the best solution to restore from the backup file. Moreover, if backup were not available, then best approach would be to use Exchange mailbox repair software because it will fix the error by recovering database files or transaction log files in a user-friendly manner.