How To Resolve Exchange Error “-1605 0xfffff9bb Jet_errkeyduplicate”?

By Author: tom.russel
Total Articles: 2
Comment this article

Jet errors are quite widespread in MS Exchange Server. Every Exchange user might have come across one or many jet error sometimes. Exchange's jet errors pose great trouble for the users as EDB database falls prey to corruption leaving all user mailboxes inaccessible.

Exchange's major features consist of electronic email, calendaring, contacts, tasks, etc. and what when such major operations get in vain due to database corruption issues? One should not lose hope in such times and must go for efficient tool to repair Exchange database.

This article throws light on one such Exchange JET error that result in inaccessibility of EDB database. 0xFFFFF9BB JET_errKeyDuplicate is the name of jet error, which turns out to be lethal for Exchange database. Actually what happens is when Exchange database gets corrupt or damaged, you start getting Jet errors once you try to access the database. Many Jet errors are irreparable and one needs efficient Exchange disaster recovery software to recover corrupt Exchange database file.

You may receive the below Jet error while working on Exchange Server or trying to repair the ...
... database using ESEUTIL utility:
-1605 0xFFFFF9BB JET_errKeyDuplicate Illegal duplicate key 4294965691

When the above error message is encountered, you can't continue using the Exchange Server database .EDB file. This error indicates that EDB file is severely damaged and thus immediate recovery of corrupted database is required.
ESEUTIL.exe is recommended first for fixing up corruption in EDB database. It's an inbuilt utility by MS Exchange Server which handles database inconsistency and corruption issues.

However, when the corruption degree is quite high, this tool fails and turns out be spoilsport. Sometimes, using Eseutil.exe, changes are not committed to Exchange Server Information Store or database, instead it modifies the database without displaying any sort of prior information. It can apply changes to database even if it shows that database is not repairable. This is harmful for our valuable Exchange data.

So for safer side, it's good to restore corrupt database using valid and updated backup. Latest backup proves to be elixir in times of Exchange data crisis. If you have valid and updated backup, you can easily restore your database from the backup and save your time and data. However, if the backup is either damaged or not updated then what could be done at that time?

Well you can take help of third party professional tool to repair Exchange database in most effective and prudent manner. It's an effective and powerful tool that systematically scans the damaged EDB file using advanced scanning techniques and extracts damaged data from it and saves them to working PST file. Repair Exchange software supports MS Exchange Server 5.0, 5.5, 2000, 2003, 2007 and 2010 and is compatible with Windows 7, Vista, XP, 2003, 2002 & 2000 operating systems.

Author of this article possess specialization in providing Exchange Server tips that include topics like repair Exchange database, Exchange mailbox repair, Exchange recovery and many more. His articles enlighten the way to resolve various Exchange Server issues.