PRB: Event Log Does Not Resize Without Clearing

Last reviewed: March 16, 1998
Article ID: Q142032

The information in this article applies to:

Microsoft Windows NT Server versions 3.5, 3.51, and 4.0

SYMPTOMS

If you attempt to change the system log file size, the change may not seem to take effect.

For instance, with overwrites turned off, if the log filled up at the default size of 512K and the maximum size is changed to 1024K, messages will still appear, warning that the log is full. Alternatively, if the maximum log size setting is decreased, the real log size does not change.

CAUSE

Increasing or decreasing the maximum log size doesn't take effect until the log is cleared.

RESOLUTION

Archive the log if you want to keep the log details. Then clear the log to allow the new size to take effect.

STATUS

This behavior is by design.

Additional query words: prodnt 3.50 3.51
Keywords : ntgeneral kbprb kbusage
Version : 3.50 3.51
Platform : WINDOWS

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