XADM: Edb.chk File May Need to Be Removed to Enable Recovery

Last reviewed: December 18, 1997
Article ID: Q176239

The information in this article applies to:

Microsoft Exchange Server, version 5.5

SYMPTOMS

When the Edb.chk file is locked open and circular logging on, ESE97 updates the internal checkpoint although Edb.chk cannot be updated. This results in circular logging reusing the old log files even though Edb.chk cannot be updated. The log generations change, although the number of log files does not.

In this state, if the system stops responding (hangs) and a recovery is initiated using ESEUTIL /r, you will get an error -1811.

CAUSE

Soft recovery fails because the checkpoint still points to the old log file, which was reused by circular logging.

RESOLUTION

Remove the Edb.chk file to allow recovery to run properly.

Keywords          : XADM kbusage
Version           : WINDOWS:5.5
Platform          : WINDOWS
Issue type        : kbinfo

================================================================================

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: December 18, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.