Excessive Server Manager File Lock Counts

Last reviewed: November 20, 1997
Article ID: Q125574

The information in this article applies to:
  • Microsoft Windows NT Workstation version 3.5
  • Microsoft Windows NT Server version 3.5

SYMPTOMS

In Server Manager, or Control Panel Server, the value for File Locks is very large (over four billion).

CAUSE

The Server service does not increment the File Locks count after successfully locking a byte range in response to a Lock&Read Server Message Block (SMB) (typically issued by a LAN Manager version 2.2c client (either MS-DOS- or OS/2)- based). However, the Server service does correctly decrement the File Lock count in response to a later Lock&X SMB which unlocks the same byte range. As a result, the zero File Lock count is decremented to 0xFFFFFFFF. Because is an unsigned value, it is displayed as 4294967295.

STATUS

Microsoft has confirmed this to be a problem in Windows NT version 3.5. A fix to this problem is in development, but has not been regression-tested and may be destabilizing in production environments. Microsoft does not recommend implementing this fix at this time. Contact Microsoft Product Support Services for more information on the availability of this fix.


KBCategory: kbnetwork kbbug3.50
KBSubcategory: ntnetserv ntinterop
Additional reference words: 3.50 prodnt 4,294,967,295 Usage Summary Open
Resources dialog box In Use


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