%1 (%2) %3The database page read from the file “%4” at offset %5 for %6 bytes failed verification because it contains no page data. The read operation will fail with error %7. If this condition persists then please restore the database from a previous backup. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem.

Details
Product: Exchange
Event ID: 476
Source: ESE
Version: 6.5.0000.0
Message: %1 (%2) %3The database page read from the file “%4” at offset %5 for %6 bytes failed verification because it contains no page data. The read operation will fail with error %7. If this condition persists then please restore the database from a previous backup. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem.
   
Explanation

ESE Event ID 476 indicates that the database page read from information store database failed verification because it contains no

page data. The read operation will fail with error -1019. This essentially means

that the particular database page

referenced within the information store file named (such as priv1.edb) is

empty when it is expected to be in use. Event ID 476 is always associated with a -1019 error in the Description

section of the Event.

  • Error -1019 = 0xfffffc05 = JET_errPageNotInitialized = 

    Blank database page.  Error -1019  is reported when a page that is

    expected to be in use is uninitialized or empty. If the page number field on a

    page in use is 0x00000000, a -1019 error is reported instead of a -1018 error,

    even though the page might also fail its checksum test.

  • The methods to correct a -1019 error are the same

    as those to correct a -1018 error. ( NOTE: Error -1018 = 0xfffffc06 =

    JET_errReadVerifyFailure = Checksum error on a database page.)

  • Note that a -1019 issue may go undetected longer than a

    -1018 issue because -1019 issues are not detected by online backup.

  • Although the root cause of a -1018 error is very likely

    to be outside of Exchange, a -1019 error might be caused by Exchange if
    logical pointers or links between pages are invalid.

  • However, it is more common that a -1019 error is caused

    because the file system was corrupted or it mapped pages into the database file

    that do not belong in the file.

   
User Action

In general, resolve a -1019 error the same way you would resolve a -1018

error. In fact, exhaustively check the Application log for evidence of any

-1018 errors that would be found in the Description section ESE events.

The standard resolution of a -1018 error follows below. Use this method to

resolve -1019 errors.

Resolution of -1018 Errors

After a system administrator encounters a -1018 error, if the administrator

runs diagnostic hardware tests against the server and these tests report no

issues, the administrator might conclude that Exchange must be responsible for

the issue because the hardware passed the initial analysis. However, in case

after case, further investigation by Microsoft or hardware vendors uncovered

subtle issues in hardware, firmware, or device drivers that are actually

responsible for damaging the database file. Ordinary diagnostic tests might not

detect all of the transient faults for several reasons. Issues in firmware or

driver software might fall outside the capabilities of diagnostic programs.

Diagnostic tests might be unable to adequately simulate long run times or

complex loads. Also, the addition of diagnostic monitoring or debug logging

might change the system enough to prevent the issue from appearing again.

The first step is to use one of the three methods below to move the existing

datbases to new hardware:

  • Obtain new hardware and install a second server in the Adminstrative Group

    and use Move Mailbox to move the mailboxes to the new server.

  • ExMerge the mailboxes out to .pst files and then ExMerge in to a new

    machine with the same name.

  • If there is no backup and using Move Mailbox is not an option, the last resort

    will be to repair the database using Eseutil /P and Isinteg -fix. You

    will still need to ExMerge out all the data after the repair and ExMerge back

    into new hardware.

The second step is to diagnose and correct the original hardware problem by

checking the System log, and running extensive tests from the hardware

manufacturer on the hardware, firmware, raid controllers, and device drivers. 

Then you can use Move Mailbox to move the users back, or restore from online

back to the repaired machine.

Definitely do not simply repair the existing database or restore from online

backup until the hardware errors have been diagnosed and corrected. You

must diagnose and correct the hardware errors before repairing, restoring,

moving your mailboxes back, or ExMerging your data back or the -1018 errors will come back because the root cause has not been fixed.

Related:

Leave a Reply