Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

XADM: Erroneous -1018 Error Returned During Online Backup


View products that this article applies to.

Symptoms

When you perform an online backup of the Exchange Server directory or information store on a single-processor computer, a -1018 error (JET_errReadVerifyFailure) may be returned even though the corresponding database is not actually damaged. Note that this problem only occurs if you are running version 5.5.2608.0 of the Ese.dll file.

↑ Back to the top


Cause

This problem occurs when the buffer for the Windows NT Backup program is set to a value greater than 512 KB.

↑ Back to the top


Resolution

To resolve this problem, obtain the latest service pack for Exchange Server version 5.5. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
191014 XGEN: How to Obtain the Latest Exchange Server 5.5 Service Pack
The English version of this fix should have the following file attributes or later:

Component: Exchange Database Engine

File nameVersion
Ese.dll5.5.2635.0

↑ Back to the top


Workaround

Set the buffer to 512 KB or less. To do so, use the following steps.

WARNING: If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.
  1. Start Registry Editor (Regedt32.exe).
  2. Locate the Max Buffer Size value under the following key in the registry:
    HKEY_CURRENT_USER\Software\Microsoft\NTBackup\Backup Engine
  3. On the Edit menu, click DWORD, type a value no greater than 512, and then click OK.
  4. Quit Registry Editor.

↑ Back to the top


Status

Microsoft has confirmed that this is a problem in Microsoft Exchange Server version 5.5. This problem was first corrected in Exchange Server 5.5 Service Pack 3.

↑ Back to the top


Article Info
Article ID : 237953
Revision : 5
Created on : 1/1/0001
Published on : 1/1/0001
Exists online : False
Views : 275