Read time 6 minutes

Summary: Microsoft Exchange Server uses ESE (Extensible Storage Engine) to function and JET (Joint Engine Technology) to upgrade the Exchange Server’s capability. When the built-in utility EseUtil fails, it tends to display the error JET_errKeyDuplicate Illegal duplicate key 4294965691. In this article, we’ll learn ways to prevent this JET database error while fixing it. You’ll also learn about the Exchange Server recovery tool that helps you restore your corrupted or damaged mailbox database.

When a Microsoft Exchange Server database file becomes corrupted, it can trigger a range of JET engine errors, each unique to the underlying cause of the corruption. Fortunately, many of these JET engine errors can be effectively addressed by utilizing eseutil.exe, an essential built-in utility within Exchange Server explicitly designed for resolving common issues related to MS Exchange Server databases. This utility meticulously examines the database file, actively identifying and rectifying errors where possible. However, it’s worth noting that certain JET engine errors elude resolution through the eseutil.exe utility. One such elusive error is:

-1605 0xFFFFF9BB JET_errKeyDuplicate Illegal duplicate key 4294965691

When the error message mentioned earlier surfaces, it disrupts your ability to proceed with MS Exchange Server operations. This error typically occurs when the Eseutil tool inaccurately reconstructs B-trees, leading to a situation where the Exchange database cannot be remounted.

Actual reason behind the error

The issue at hand cannot be resolved using the Eseutil.exe tool. In fact, persistently attempting to use Eseutil.exe after encountering this error message can potentially lead to data loss and wasted time, exacerbating the problem rather than solving it. This occurs because the /p switch within the Eseutil utility attempts to repair all system tables and indexes. When encountering severely corrupted tables or indexes, the repair process discards them. As a consequence, ESE Event IDs are generated, indicating the loss of data pages during the repair operation. This data loss is irrevocable and is likely to intensify existing issues.

Solution to JET_errKeyDuplicate Illegal Duplicate Key error
  1. In EseUtil.exe, run the following command in Exchange Management Shell first to check the status of your database.
  2. Get-MailboxDatabase –Status
  3. Now, run the below command and check if the Exchange Server is in a ‘Dirty Database Shutdown’ state or a ‘Clean Database Shutdown’.
  4. eseutil /mh
    For e.g.: eseutil /mh C:\folder_name\folder_name.edb
  5. Run the eseutil /p command to send Exchange in repair mode

Once the process is done, use eseutil /d to defragment the database and run isinteg -s “servername” –alltests to ensure database integrity.

Note: If you have a Microsoft Exchange 2013 Server with Service Pack 1 or later, use the New-MailboxRepairRequest PowerShell cmdlet. Remember that if you execute the command, it won’t stop without damaging the database. The only way to halt the process is to unmount the database.

Why does the manual solution fail?

When users try repairing the error with the help of the built-in utility, ESEUTIL, there is a high chance that it fixes the error. However, the users might end up with intensive data loss or even worse.

Exchange Server experts highly advise the creation of comprehensive backups for Exchange Server database files. This proactive measure ensures that in the event of JET errors, data recovery becomes a straightforward process. If you possess a complete backup of the afflicted Exchange Server database file, restoring it allows you to resume working with the Exchange Server seamlessly, free from any data loss concerns. However, should you lack a backup, the assistance of third-party Exchange Database Recovery software becomes essential.

How does Exchange Recovery software help?

EDB Recovery software performs a thorough scan of corrupted Exchange Server database files, even in the presence of Jet Engine errors, and proficiently restores them to their original state. Once the scanning process is completed, the software allows users to save the recovered data to a location of their choice. Kernel for Exchange Server Recovery is a powerful third-party software solution meticulously crafted to offer comprehensive Exchange Server database recovery services. It is compatible with nearly all versions of MS Exchange Server, spanning from Exchange Server 5.0 to 2019, ensuring a wide range of support for various environments and scenarios.

Conclusion

Certain Exchange errors, such as “JET_errKeyDuplicate Illegal duplicate key,” are beyond the scope of repair using the eseutil utility due to the inherent risk of data loss. In such critical situations, the optimal solution is to employ a robust recovery tool like Kernel for Exchange Server. The Exchange Recovery tool doesn’t cause any downtime, and you can extract your mailboxes as PST files to your system.

Kernel for Exchange Server