{process name} ({process id}) The streaming page read from the file “{file name}” at offset {value} for {value} bytes failed verification due to a page checksum mismatch. The expected checksum was {value} and the actual checksum was {value}. The read operation will fail with error {error code}. If this condition persists then please restore the database from a previous backup.

Details
Product: Exchange
Event ID: 478
Source: ESE98
Version: 6.0
Component: Extensible Store Engine
Symbolic Name: SLV_PAGE_CHECKSUM_MISMATCH_ID
Message: {process name} ({process id}) The streaming page read from the file “{file name}” at offset {value} for {value} bytes failed verification due to a page checksum mismatch. The expected checksum was {value} and the actual checksum was {value}. The read operation will fail with error {error code}. If this condition persists then please restore the database from a previous backup.
   
Explanation
The streaming database specified in the message is corrupt.
   
User Action
Restore the database from backup media.

Related:

() The streaming page read from the file “” at offset for bytes failed verification due to a page checksum mismatch. The expected checksum was and the actual checksum was . The read operation will fail with error . If this condition persists then please restore the database from a previous backup.

Details
Product: Exchange
Event ID: 478
Source: ESE
Version: 6.5.6940.0
Component: Microsoft Exchange Extensible Storage Engine
Message: <process name> (<process id>) <storage group name>The streaming page read from the file “<file name>” at offset <value> for <value> bytes failed verification due to a page checksum mismatch. The expected checksum was <value> and the actual checksum was <value>. The read operation will fail with error <error code>. If this condition persists then please restore the database from a previous backup.
   
Explanation

The streaming database specified in the message is corrupt.

An online Exchange-aware backup fails to complete and you receive the following phrases in the event Description:

Information Store (number) The streaming page read from the file “[path]\priv1.stm” failed verification due to a page checksum mismatch. The read operation will fail with error -613 (0xfffffd9b). If this condition persists, restore the database from a previous backup.

  • Error -613 = 0xfffffd9b = JET_errSLVReadVerifyFailure = Checksum error in SLV file during backup. This issue occurs because in certain database operations, including but not limited to online backup, the backup routine makes a call to the operating system to read a 4-KB page of data from the database on disk and write the data to tape. Before the online backup process writes the data that is returned from the operating system call to the tape, the online backup process compares the checksum value in the page header (recorded when this page was written to disk) to that being returned from the READ call. If the checksum values do not match, the Exchange database engine detects this and returns the error -613. Error -613 (JET_errSLVReadVerifyFailure) is similar to error -1018 (JET_errReadVerifyFailure). Exchange logs error -613 for checksum errors on the .stm database file and logs error -1018 for checksum errors on the .edb database file.
  • Antivirus software — program settings such as manual scans and file level scans of database folders and drive M and settings for the antivirus software in the registry.
  • Third-Party programs such as anti-spam programs, SMTP disclaimer software packages, and mail archiving programs .
  • Problems with the hard disk subsystem or controllers of the system.
   
User Action
  • To resolve this issue, first determine the root cause of the corruption. To do so, check the system log, run chkdsk and perform other diagnostic tasks. If you do not determine and fix the root cause of the -613 error, the corruption problem may occur again, even if you repair the databases or restore the databases from a backup.
  • Try removing the antivirus software, or third-party software, for testing purposes.
  • Resolution 1 – Restore the Exchange database from the previous online backup.
  • Resolution 2 – Move the mailboxes to another server or mailbox store. If the public folder store is affected, replicate the content of the public folders to another server.
  • Resolution 3 – If there is no valid online backup and as a last resort, perform a repair using eseutil /p and then run the isinteg -fix. If the resolution requires a repair, you cannot repair the .stm file alone — you must repair the .edb file and its associated .stm file. After this procedure, the database might not be stable and reliable. Microsoft recommends that you immediately move the data out of the repaired database to a new database or rebuild the database.

Related:

%1 (%2) %3The streaming page read from the file “%4” at offset %5 for %6 bytes failed verification due to a page checksum mismatch. The expected checksum was %8 and the actual checksum was %9. The read operation will fail with error %7. If this condition persists then please restore the database from a previous backup.

Details
Product: Exchange
Event ID: 478
Source: ESE
Version: 8.0
Symbolic Name: SLV_PAGE_CHECKSUM_MISMATCH_ID
Message: %1 (%2) %3The streaming page read from the file “%4” at offset %5 for %6 bytes failed verification due to a page checksum mismatch. The expected checksum was %8 and the actual checksum was %9. The read operation will fail with error %7. If this condition persists then please restore the database from a previous backup.
   
Explanation

This Warning event indicates that the streaming database specified in the message is corrupted. The event description provides details about the error that occurred.

The following provides information about the most common error associated with this event:

Error -613 = 0xfffffd9b = Jet_errSLVReadVerifyFailure = Checksum error in SLV file during backup. Error -613 resembles error -1018. Exchange logs error -613 for checksum errors on the .stm database file and logs error -1018 for checksum errors on the .edb database file. Checksums for pages in the .stm file are stored in a table in the .edb file. The .edb and .stm files may be out of sync. An older copy of the .stm file may be in use, and the checksum table in the .edb file is therefore out of date. A program may have altered the .stm file without updating the checksums in the .edb file. There could be problems with the hard disk subsystem or controllers of the system.

   
User Action

To resolve this warning, do the following:

  • Determine the root cause of the corruption. To do this, check the System log, run Chkdsk and perform other diagnostic tasks. If you do not determine and fix the root cause of this warning, the corruption problem may occur again, even if you repair the databases or restore the databases from a backup.

  • Temporarily disable or remove the antivirus software or third-party software. This may help identify the root cause of this event.

  • Restore the Exchange store from the previous online backup.

  • Move the mailboxes to another server or mailbox store. If the public folder store is affected, replicate the content of the public folders to another server.

  • If there is no valid online backup and as a last resort, perform a repair using Eseutil /p and then run the isinteg -fix. If the resolution requires a repair, you cannot repair the .stm file alone. You must repair the .edb file and its associated .stm file. After this procedure, the database may not be stable and reliable. You should immediately move the data out of the repaired database to a new database or rebuild the database.

If you are not already doing so, consider running the tools that Microsoft Exchange offers to help administrators analyze and troubleshoot their Exchange environment. These tools can help you make sure that your configuration is in line with Microsoft best practices. They can also help you identify and resolve performance issues, improve mail flow, and better manage disaster recovery scenarios. Go to the Toolbox node of the Exchange Management Console to run these tools now. For more information about these tools, see Toolbox in the Exchange Server 2007 Help.

Related:

process name (process id) file nameThe streaming page read from the file “value” at offset value for error code bytes failed verification due to a page checksum mismatch. The expected checksum was value and the actual checksum was %9. The read operation will fail with error value. If this condition persists then please restore the database from a previous backup.

Details
Product: Exchange
Event ID: 478
Source: ESE
Version: 6.5.0000.0
Message: process name (process id) file nameThe streaming page read from the file “value” at offset value for error code bytes failed verification due to a page checksum mismatch. The expected checksum was value and the actual checksum was %9. The read operation will fail with error value. If this condition persists then please restore the database from a previous backup.
   
Explanation

The streaming database specified in the message is corrupt.

An online Exchange-aware backup fails to complete and you receive the following phrases in the event Description:

Information Store (number) The streaming page read from the file

“[path]\priv1.stm” failed verification due to a page checksum mismatch. The read

operation will fail with error -613 (0xfffffd9b). If this condition persists,

restore the database from a previous backup.

  • Error -613 =  0xfffffd9b = JET_errSLVReadVerifyFailure = Checksum error

    in SLV file during backup. This issue occurs because in certain database

    operations, including but not limited to online backup, the backup routine makes

    a call to the operating system to read a 4-KB page of data from the database on

    disk and write the data to tape. Before the online backup process writes the

    data that is returned from the operating system call to the tape, the online

    backup process compares the checksum value in the page header (recorded when

    this page was written to disk) to that being returned from the READ call. If the

    checksum values do not match, the Exchange database engine detects this and

    returns the error -613. Error -613 (JET_errSLVReadVerifyFailure) is

    similar to error -1018 (JET_errReadVerifyFailure). Exchange logs error -613

    for checksum errors on the .stm database file and logs error -1018 for checksum
    errors on the .edb database file.

  • Anti-virus software — program settings such as manual scans and file

    level scans of database folders and the M: drive and settings for the

    anti-virus software in the Registry.

  • 3rd Party programs such as anti-spam programs, SMTP disclaimer software packages,

    and mail archiving programs .

  • Problems with the hard disk subsystem or controllers of the system.
   
User Action
  • To resolve this issue, first determine the root cause of the corruption. To

    do so, check the system log, run chkdsk and perform other diagnostic tasks. If

    you do not determine and fix the root cause of the -613 error, the corruption

    problem may occur again, even if you repair the databases or restore the

    databases from a backup.

  • Try removing the anti-virus software, or 3rd party software, for testing

    purposes.

  • Resolution 1 – Restore the information store from the previous online

    backup.

  • Resolution 2 – Move the mailboxes to another server or mailbox store.

    If the public folder store is affected, replicate the content of the public folders to another server.

  • Resoluton 3 – If there is no valid online backup and as a last resort ,

    perform a repair using eseutil /p and then run the isinteg -fix.

    If the resolution requires a repair, you cannot repair the .stm file alone —

    you must repair the .edb file and its associated .stm file. After this

    procedure, the database may not be stable and reliable. Microsoft

    recommends that you immediately move the data out of the repaired database to

    a new database or rebuild the database.

Related: