XADM: Erroneous -1018 Error Returned During Online Backup (237953)

IMPORTANT: This article contains information about modifying the registry. Before you modify the registry, make sure to back it up and make sure that you understand how to restore the registry if a problem occurs. For information about how to back up, restore, and edit the registry, click the following article number to view the article in the Microsoft Knowledge Base:

256986 Description of the Microsoft Windows Registry

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.

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 name	Version
Ese.dll	5.5.2635.0

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.

Start Registry Editor (Regedt32.exe).
Locate the Max Buffer Size value under the following key in the registry:
HKEY_CURRENT_USER\Software\Microsoft\NTBackup\Backup Engine
On the Edit menu, click DWORD, type a value no greater than 512, and then click OK.
Quit Registry Editor.

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.