SFM Does Not Unlock Record After PC Releases Lock

Last reviewed: November 17, 1997
Article ID: Q159994
The information in this article applies to:
  • Microsoft Windows NT Server versions 3.5 and 3.51

SYMPTOMS

A file lock may not appear to be free on a Macintosh computer attached to a MAC Volume when the following occurs:

  1. A personal computer-based application locks a record in the file on a Macintosh Volume.

  2. The Macintosh attempts to lock the same record and gets a return code indicating that the record is already locked.

  3. The personal computer-based application releases its lock on the record.

  4. The record still appears to be locked when viewed from the Macintosh even though it is not locked.

CAUSE

The cached information for the lock in Services for Macintosh is not cleared out when the personal computer lock is removed.

STATUS

Microsoft has confirmed this to be a problem in Windows NT version 3.51. A supported fix is now available, but has not been fully regression tested and should be applied only to systems experiencing this specific problem. Unless you are severely impacted by this specific problem, Microsoft recommends that you wait for the next Service Pack that contains this fix. Contact Microsoft Product Support Services for more information.


Additional query words: sfm
Keywords : kbbug3.51 ntmac NTSrv kbnetwork
Version : WinNT:3.5,3.51
Platform : winnt


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