The information in this article applies to:
SYMPTOMSThe client program opens a file on the server and locks 0 bytes at position (0). After this "lock_0_bytes_at_position_0," the same client cannot lock any other byte_range of that file (lock_i_bytes_at position_j, with i>0, j>0). CAUSE
The locking mechanism incorrectly calculated the lock to be the entire
file, instead of 0.
RESOLUTION
Run a different application that can lock a byte range other than 0 bytes
at location byte 0 before running the application that will lock 0 bytes at
byte 0. This will then cause the 0 byte locking application to function
correctly.
STATUSMicrosoft has confirmed this to be a problem in Windows NT version 4.0. This problem was corrected in the latest Microsoft Windows NT 4.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 Additional query words: prodnt NTFS
Keywords : kbnetwork kbbug4.00 kbfix4.00.sp3 ntfilesys NTSrvWkst |
Last Reviewed: February 4, 1999 © 2000 Microsoft Corporation. All rights reserved. Terms of Use. |