Home » Topic » How to resolve Jet Error Codes 1601 & 1605 from Exchange Server

How to resolve Jet Error Codes 1601 & 1605 from Exchange Server

Edwin J Hoffer ~ Modified: October 31st, 2017 ~ ~ 1 Minute Reading

Home Forums How to resolve Jet Error Codes 1601 & 1605 from Exchange Server

Viewing 5 posts - 1 through 5 (of 5 total)
  • Author
    Posts
  • #5609 Score: 0
    Edwin J Hoffer
    Moderator

    I have been using Exchange Server 2013 on my system and facing some issues. Every time When I try to open Exchange Server I am getting the error message “Operation Terminated with Error -1601 (JET_errRecordNotFound, The Key was Not Found) after 2.354 seconds”. Can anyone help me to get rid of this error?

    #5615 Score: 0
    Sandra Diaz
    Moderator

    Hi,
    There could be some of the reasons due to which your Exchange Server has become corrupted. Exchange Database Corruption may be caused due to any one of the following reason:

    • Corrupted EDB files in Exchange Server Database
    • When EDB and SMT files have dissimilar structure
    • Incase of irregular B-Tree formation

    Did any of the above-mentioned event took place in your system?

    #5630 Score: 0
    Edwin J Hoffer
    Moderator

    Hi Sandra,
    Since you have explained the reasons for this error, I think the reason for this error in Exchange Server is corruption in EDB files. Can anything be performed manually to resolve this error?

    #5634 Score: 0
    Sandra Diaz
    Moderator

    Hi,
    There is no Manual Method which can resolve Jet Error codes 1601 & 1605 because there are no methods that guarantee to restore corrupted Exchange Server files. Therefore, you can try a professional third-party tool like SysTools Exchange Recovery Software to recover corrupted Exchange server files. In this way, you can resolve the error.

    For more info: https://www.systoolsgroup.com/exchange-recovery.html

    Let me know if this tool helps you to resolve the error.

    #5638 Score: 0
    Edwin J Hoffer
    Moderator

    Hi,
    Thanks for this amazing software as it helped me to get rid of this error and restore my Exchange Server files effectively and reliably. Thanks!!

Viewing 5 posts - 1 through 5 (of 5 total)
  • You must be logged in to reply to this topic.