Article ID: 237953 - View products that this article applies to.
This article was previously published under Q237953
This article has been archived. It is offered "as is" and will no longer be updated.
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:
(http://support.microsoft.com/kb/256986/EN-US/ )Description of the Microsoft Windows Registry
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.
This problem occurs when the buffer for the Windows NT Backup program is set to a value greater than 512 KB.
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:
191014The English version of this fix should have the following file attributes or later:
(http://support.microsoft.com/kb/191014/EN-US/ )XGEN: How to Obtain the Latest Exchange Server 5.5 Service Pack
Component: Exchange Database Engine
Collapse this tableExpand this table
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.
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.
Contact us for more help