XADM: Information Store Crashes in JetMove

 Last reviewed: March 6, 1998
Article ID: Q181931
The information in this article applies to:
  • Microsoft Exchange Server, version 5.5

SYMPTOMS

The Microsoft Exchange information store may stop unexpectedly and record the following error in the Application event log: 

   2/6/98  6:33:11  DrWatson  Information  None  4097  N/A
   The application, exe\store.dbg, generated an application error. The
   error occurred on 2/6/1998 @ 3:33:10.437 The exception generated was
   c0000005 at address 6fe951f0 (JetMove)

CAUSE

A page at an internal level of the Jet b-tree became corrupted. This prevents the information store from successfully starting and prevents the Exchange Information Store Integrity Checker (Isinteg.exe) from completing successfully.

STATUS

Microsoft has confirmed this to be a problem in Microsoft Exchange Server version 5.5. A supported fix is now available, but has not been fully regression-tested and should be applied only to systems experiencing this specific problem. Unless you are severely impacted by this specific problem, Microsoft recommends that you wait for the next Service Pack that contains this fix. Contact Microsoft Technical Support for more information.

MORE INFORMATION

Isinteg.exe has been strengthened to avoid the crash. 

Keywords          : XADM
Version           : WINNT:5.5
Platform          : winnt
Issue type        : kbbug

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

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: March 6, 1998
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.