Tony Redmond's Microsoft Exchange Server 2003 with SP1

7.8: ESE Database Errors

7.8 ESE Database Errors

Three types of errors can occur in an Exchange database:

  • Application (Exchange or ESE) level

  • JET (database) level

  • Physical or page level

Table 7.7 describes the most common errors. See Microsoft Knowledge Base article 314917 for more information.

Table 7.7: Exchange Database Errors

Error

Meaning

Indication

1018 (JET_errReadVerifyFailure)

The checksum read from disk is not the same as the checksum that was originally written, or the page number does not match the page number that is expected.

Page-level corruption may have occurred.

?1019 (JET_errPageNotInitialized)

A page that is expected to be in use is not initialized or empty.

The page may be corrupt.

1022 (JET_errDiskIO)

A generic error indicating that the requested page cannot be read by ESE.

A physical disk error is probable.

A -1018 error occurs when the ESE engine makes a request to Windows to fetch a particular page from the database and ESE then returns unexpected data, normally a different page number or checksum. ESE flags the error to prevent further access to the page and to let administrators know that action is required. Continuing to attempt to access a damaged page (or damaged section of a database) usually results in even more data loss than may occur if you immediately notice a problem and take appropriate action. For example, if you take a backup of a flawed database, you will not be able to restore it.

Many different underlying problems can cause a wrong page to be...

UNLIMITED FREE
ACCESS
TO THE WORLD'S BEST IDEAS

SUBMIT
Already a GlobalSpec user? Log in.

This is embarrasing...

An error occurred while processing the form. Please try again in a few minutes.

Customize Your GlobalSpec Experience

Category: Parity Checkers and Generators
Finish!
Privacy Policy

This is embarrasing...

An error occurred while processing the form. Please try again in a few minutes.