Resolving Error 1018 While Jet Database Operation In Exchange Server
Sign in
  • BLOG
  • Editor's Picks
  • |
  • Technology
  • |
  • Entrepreneurship
  • |
  • Business
  • |
  • Finance
  • |
  • Career
  • |
  • New India
  • |
  • Entertainment
  • |
  • Others

    • Resolving Error 1018 while Jet Database Operation in Exchange Server

    Axel Culver

    Data Recovery Expert
    You might receive several errors while performing a Jet database operation on an Exchange Server database. If the operation fails, one of the prime reason could be that the database is corrupt and requires Exchange Server Recovery. You can do so by restoring from the online backup or using a third-party tool to scan and repair the database.

    Consider that you perform a JET database operation and it fails with a JET_errReadVerifyFailure error that is recorded with number 1018. When you view Windows Event Viewer application log, you come across the below entry:

    Event ID: 23
    Source: EDB
    Type: Error
    Category: Database Page Cache
    Description: MSExchangeIS ((455)) Direct read found corrupted page error -1018 ((1:251563) (0-2295758), 251563 379225672 381322824). Please restore the database from a previous backup.

    Cause

    Exchange Server supports transaction logging i.e before committing any transaction to the Jet database, it writes this information to the transaction log files. The Jet engine performs page checksum calculation and writes the value so obtained in page header. It then sends the file system a request that it should write 4-KB page of data to the target database. The device driver of the hardware so involved reverts this information to the file system and then to the Jet engine. However, if the hardware or device driver is faulty, it may return a success message even when the data has not been successfully written.

    If you perform a Jet database operation, it makes a call to read 4-KB page of data from database and then write to the desired location. Before actually committing the data write, the process compares the checksum value of page to that has been returned by READ call. If these values don't match, the above -1018 error generates.

    Solution

    Following are some solutions that you can apply to solve the given problem:

    1. Restore the database from the last known good backup

    2. Use Eseutil.exe utility to defragment and check database consistency

    3. Use third-party Exchange Recovery utility to extract the user mailboxes. Exchange Server Recovery software are powerful products that scan and repair a damaged Exchange database while maintaining its integrity.

    Stellar Phoenix Mailbox Exchange Recovery is an advanced utility that employs high-end scanning algorithms to repair a damaged Exchange database. It supports Exchange Server 5.5, 2000 and 2003. It is a safe Exchange Recovery utility with impressive features. The tool extracts user mailboxes in .pst file format.

    start_blog_img