This article has been archived. It is offered "as is" and will no longer be updated.
When you perform an online backup of a storage group, a mailbox store, or a public folder store, the operation may be unsuccessful. Additionally, an error -613 : JET_errSLVReadVerifyFailure occurs (mismatch Checksum in SLV file during backup) and the following event ID messages may be logged in the Application event log:
Event Type: Information Event Source: NTBackup Event ID: 8000 Description: Begin Backup of 'MAILMASTER\Microsoft Information Store\'First Storage Group' Verify: Off Mode: Append
Type: Normal Event Type: Information Event Source: ESE Event ID: 210 Description: Information Store (1812) e85d4e03-5bb3-44c5-bd2f-1343972a1b1a: A full backup is starting.
Event Type: Information Event Source: ESE Event ID: 220 Description: Information Store (1812) e85d4e03-5bb3-44c5-bd2f-1343972a1b1a: Beginning the backup of the file D:\Programme\Exchsrvr\mdbdata\priv1.stm (size 2850 Mb).
Event Type: Error Event Source: ESE Event ID: 478 Description: Information Store (1812) The streaming page read from the file "D:\Programme\Exchsrvr\mdbdata\priv1.stm" at offset 693297152 (0x000000002952e000) for 4096 (0x00001000) bytes failed verification due to a page checksum mismatch. The expected checksum was 3505519770 (0xd0f1fc9a) and the actual checksum was 3505518746 (0xd0f1f89a). The read operation will fail with error -613 (0xfffffd9b). If this condition persists then please restore the database from a previous backup.
Event Type: Error Event Source: ESE Event ID: 217 Description: Information Store (1812) e85d4e03-5bb3-44c5-bd2f-1343972a1b1a: Error (-613) during backup of a database (file D:\Programme\Exchsrvr\mdbdata\priv1.stm). The database will be unable to restore. Event Type: Information Event Source: ESE Event Category: (3) Event ID: 222 Description: Information Store (1812) e85d4e03-5bb3-44c5-bd2f-1343972a1b1a: Ending the backup of the file D:\Programme\Exchsrvr\mdbdata\priv1.stm. Not all data in the file has been read (read 693239808 bytes out of 2988449792 bytes).
Event Type: Error Event Source: NTBackup Event ID: 8012 Description: The 'Microsoft Information Store' returned error from ESE function call (d).from a call to 'HrESEBackupRead additional data
This problem may occur when you use a Web Distributed Authoring and Versioning (WebDAV) client to send messages to distribution lists and the distribution lists have one of the following options selected on the Exchange Advanced tab:
Send delivery reports to group owner
Do not send delivery reports
To view the Exchange Advanced tab:
Start Active Directory Users and Computers.
On the View menu, click Advanced Features.
Right-click the distribution list, and then select the Exchange Advanced tab.
Cumulative Rollup Information
To resolve this problem, obtain the September 2003 Exchange 2000 Server Post-Service Pack 3 (SP3) Rollup. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
824282 September 2003 Exchange 2000 Server Post-Service Pack 3 Rollup
A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem.
If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, submit a request to Microsoft Customer Service and Support to obtain the hotfix.
Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site:
Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.The English version of this hotfix has the file attributes (or later) that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel. Component: Transport Core
Date Time Version Size File name -------------------------------------------------------------- 12-May-2003 22:33 6.0.6465.0 131,072 Drviis.dll 12-May-2003 22:37 6.0.6465.0 307,200 Exsmtp.dll 12-May-2003 22:29 6.0.6465.0 94,208 Peexch50.dll 12-May-2003 22:31 6.0.6465.0 393,216 Phatcat.dll
Note Because of file dependencies, this update requires Microsoft Exchange 2000 Server Service Pack 3 (SP3). For additional information, click the article number below to view the article in the Microsoft Knowledge Base:
301378 How to Obtain the Latest Exchange 2000 Server Service Pack
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.
The backup routine makes a call to the operating system to read a 4-kilobyte (KB) page of data from the database on a disk and writes it to tape. Before the data that is returned from the operating system call is committed to the tape, the online backup process compares the checksum value in the page header to the header that is being returned from the READ call (the checksum value in the page header is recorded when this page is written to disk). When the Exchange 2000 database engine detects that the checksum values do not match, it returns an error -613.
When you run eseutil /k, the following output about the database is returned:
- Summary on priv1.edb File: D:\Program Files\Exchsrvr\Mdbdata\priv1.edb Checksum Status (% complete) 0 10 20 30 40 50 60 70 80 90 100 |----|----|----|----|----|----|----|----|----|----| ................................................... 1563234 pages seen 0 bad checksums 19857 uninitialized pages 0 wrong page numbers
- Summary on priv1.stm File: D:\Program Files\Exchsrvr\Mdbdata\priv1.STM Checksum Status (% complete) 0 10 20 30 40 50 60 70 80 90 100 |----|----|----|----|----|----|----|----|----|----| .............. ERROR: SLV checksum mismatch: Page 18149 (owned by 19:281:7f 01 00 00 00 00 8e e4 1d 08). Checksum length 4096 bytes. Expected checksum 0xf4aca7b5. Actual checksum 0xe881e6ff. ERROR: SLV checksum mismatch: Page 18150 (owned by 19:281:7f 01 00 00 00 00 8e e4 1d 08). Checksum length 4096 bytes. Expected checksum 0xf5f6ddef. Actual checksum 0xddcea6c9. ERROR: SLV checksum mismatch: Page 18151 (owned by 19:281:7f 01 00 00 00 00 8e e4 1d 08). Checksum length 1301 bytes. Expected checksum 0xf297edbf. Actual checksum 0xdcc4fa9d. 64512 pages seen 127 bad checksums 49276 uninitialized pages
How to Troubleshoot This Problem
Use the following procedure to find the cause of the problem:
Save a database that does not have a mismatched checksum value (a correct database).
Perform a typical online backup. After you finish the backup, leave the transaction logs on the disk.
Wait for the next occurrence of the mismatched checksum value that occurs during online backup.
Send the following items to Microsoft Product Support and Services (PSS):
The copy of the database that you saved in step 1
The database that is experiencing the problem
All the logs that have been created
Replay the logs on the database you saved in step 1.
Look for mismatched checksum values. You can run the eseutil /k db.edb command. This command automatically checks the .edb file and .stm file and returns the page number that has the mismatched checksum value.
If a mismatched checksum value does not occur on the new correct database, compare the pages that have a mismatched checksum value between the incorrect database and the correct database. To do so, run the following command to dump the content of the page number n:
esefile /d db.stm n
After you run the command, review the output to find where the differences are in the message. The output may help you find a systematic method to reproduce the error.