XADM: Store Defrag Fails with Access Violation

 Last reviewed: July 15, 1997
Article ID: Q166629
The information in this article applies to:
  • Microsoft Exchange Server, version 5.0

SYMPTOMS

When you are defragmenting the Microsoft Exchange Server Information Store and you specify "EDBUTIL /d /ispriv," Microsoft Exchange Server stops responding. An access violation error message similar to the following appears: 

   EDBUTIL.EXE - Application Error

   The instruction at "0x<some-memory-address>" referenced memory at
   "0x00000000". The memory could not be written. Click OK to terminate
   or CANCEL to debug the application."
In addition, a Drwtsn32.log and User.dmp file are created if Dr. Watson is configured properly as the default system debugger.

CAUSE

While defragmenting the attachments table, even if data to be copied is zero-length, the utility assumes that it has traversed down the tree one level, and so it inappropriately "backs up" one level to continue defragmenting. This can result in the access violation.

STATUS

Microsoft has confirmed this to be a problem in Microsoft Exchange Server version 5.0. This problem was corrected in the latest Microsoft Exchange Server 5.0 U.S. Service Pack. 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.sp1 kbusage XADM
Version : 5.0
Platform : WINDOWS
Issue type : kbbug
Resolution Type : kbfix

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