XADM: EDB File Size Not Updated

 Last reviewed: March 9, 1998
Article ID: Q180011
The information in this article applies to:
  • Microsoft Exchange Server, versions 4.0, 5.0, and 5.5

SYMPTOMS

When you view the file size and properties of an Exchange Server database stored on an NTFS partition, the file size does not reflect the current size, date, or time until the database service (directory, information store, and/or directory synchronization) is stopped and restarted.

CAUSE

Because the *.EDB files are locked open, the file properties cannot be updated. The properties of the drive are reported correctly.

WORKAROUND

To work around this problem, stop and restart the corresponding service (directory, information store, and/or directory synchronization).

STATUS

This is a known problem with Windows NT NTFS partitions and the following Exchange JET databases: 

   Dir.edb, Priv.edb, Pub.edb, and Xdir.edb.
We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.

MORE INFORMATION

Even though the size of the file in question is not updated, the free space on the drive will be updated.

If you are monitoring the file size to determine low disk space conditions, it is recommended that the free space on the drive be monitored and not the size of the Exchange database files. 

Keywords          : XADM
Version           : WINDOWS:4.0,5.0,5.5
Platform          : WINDOWS
Solution Type     : kbworkaround

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

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