XADM: Information Store Stops Unexpectedly

 Last reviewed: February 12, 1998
Article ID: Q176627
The information in this article applies to:
  • Microsoft Exchange Server version 5.0

SYMPTOMS

If you are running German Microsoft Windows NT Server and you attempt to start a service, the information store may stop unexpectedly.

CAUSE

This problem can occur when the Edb.chk file is missing. When this occurs, Exchange Server attempts to locate the most recent information store transaction log (Edb.log or Edb<xxxxx>.log, where <xxxxx> is a series of hexadecimal digits). When you are running German Microsoft Windows NT Server, the transaction log file name that is returned contains lowercase characters. In this case, Exchange Server does not properly handle transaction log file names that contain lowercase characters.

STATUS

Microsoft has confirmed this to be a problem in Microsoft Exchange Server version 5.0. This problem has been corrected in the latest U.S. Service Pack for Microsoft Exchange Server version 5.0. For information on obtaining the Service Pack, query on the following word in the Microsoft Knowledge Base (without the spaces): S E R V P A C K 

Keywords          : kbbug5.00 kbfix5.00.sp2 XADM
Version           : winnt:5.0
Platform          : winnt
Issue type        : kbbug
Solution Type     : kbfix kbpatch

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

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