How to resolve EDB file error, “Database page read failed verification because of a -1018 error”

Make efficient recovery for frequent EDB file error

It’s quite consistent that Exchange Server users and network administrators confront with varied EDB file errors. Each time any sort of error message hits the EDB database users are on the verge of losing their important data. Now, the situation can turn rather serious when users have already lost their precious data due to corruption and damage in EDB files.

EDB files can get prone to corruption due to varied reasons, some of which include improper server shutdown, virus invasion, and physical damage to storage media, abrupt application shutdown, hardware failure etc. In many cases, when the when Exchange Server database file gets corrupt or damaged, MS Outlook does not allow the user to access user’s email, calendar and other data from it. The situation occurs when MS Outlook is also unable to bring back data from EDB database on the Exchange Server.

Let us now consider a real time scenario; user might come across the following error at the time of reading an EDB file:

Database page read failed verification because of a -1018 error” (page checksum mismatch)

When making comparison to the error -18111 (hexadecimal 0xFFFFF8ED) stands for JET_errFileNotFound and stands for File not found. This error message indicates that the database page displayed failed verification because of some page checksum mismatch. This specific database page is a file in Exchange Store and thus error specifies that the individual file (may be priv1.edb) is damaged or corrupt. This error can create troublesome situation and users are bound to face situations listed below at the time of working with EDB file.

  • User is not able to send and receive email.

  • Users are not allowed to access MS Outlook on the system.

  • There is a failed online backup and a 1018 checksum error is displayed.

  • Online defragmentation report creates -1018 checksum mismatch error.

However, users can easily resolve the situation by choosing one or more ways listed below:

  1. Whenever the -1019 error code in event description is displayed, try to acquire solutions provided by Microsoft.

  2. Choose migration to some other system or try utilizing different hardware.

  3. Try upgrading disk controller BIOS and firmware.

  4. Run system diagnostic test.

  5. Repair EDB with the eseutil /P and eseutil /D and then isinteg –fix.

No matter how much utilities are offered by Microsoft for the purpose for EDB file repair, they hardly deliver any good. Hence the most ideal solution is to make use of third party Exchange repair tool. Kernel for Exchange Server recovery allows users to retrieve their entire corrupt EDB data and make it accessible with Outlook.

Some key features of the tool are listed below:

  • Make flawless recovery for EDB and STM files.

  • Make recovery for Priv1.edb database files with ease.

  • Resolve Dirty shutdown errors.

  • The recovered data can be saved in PST and EDB file format.

  • Make efficient recovery for large sized EDB files.

  • User deleted mailboxes can be retrieved.

  • The recovered data is displayed in a tree like format.

  • The tool will first make preview of selected email items.

Along with such output driven feature in Kernel for Exchange Server recovery tool, users can give for the free evaluation version. The demo version provide in-depth idea of the software working expect the fact that recovered data cannot be saved onto the user system. To save the repaired EDB data into PST users have to make purchase for complete version of the tool.

Supported platform by the tool are:

Microsoft Exchange Server 5.0, 5.5, 2000, 2003, 2007 and 2010

Microsoft Outlook 97, 98, 2000, XP, 2003, 2007 and 2010

Hence, there is no doubt in saying that Kernel for Exchange Server Recovery is a one-step solution for entire recovery need for EDB file data.

Comments 1 comment

profile image

BrendonTaylor57 4 years ago

LEM is the exceptional software that can extract and restore only selected items from the available backup without requiring brick level backup. The software offers efficient Exchange disaster recovery which helps the user in recovering Exchange database.

    0 of 8192 characters used
    Post Comment

    No HTML is allowed in comments, but URLs will be hyperlinked. Comments are not for promoting your articles or other sites.

    Click to Rate This Article