Semaphore Timeout Error When UseWriteBehind Disabled for Redir

 Last reviewed: December 29, 1997
Article ID: Q169742
The information in this article applies to:
  • Microsoft Windows NT Workstation versions 3.51 and 4.0
  • Microsoft Windows NT Server versions 3.51 and 4.0

SYMPTOMS

When you disable write behind caching in Windows NT by setting the following parameter to 0 

   HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Rdr
    \Parameters\UseWriteBehind
and you then attempt to copy a file to a remote share, the following message appears: 

   Too many posts were made to a semaphore.

CAUSE

This error is caused by a problem in the redirector, which manipulates an operating system semaphore.

WORKAROUND

To work around this problem, do one of the following:

  • Re-enable write behind caching by setting UseWriteBehind to 1

    -or-

  • Apply the hotfix mentioned below.

STATUS

Microsoft has confirmed this to be a problem in Windows NT versions 3.51 and 4.0. A supported fix is now available, but is not fully regression- tested and should be applied only to systems experiencing this specific problem. Unless you are severely affected 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. 

Keywords          : kbbug3.51 kbbug4.00 NTSrvWkst nttcp kbnetwork kbbuglist
Version           : WinNT:3.51,4.0
Platform          : winnt
Issue type        : kbbug
Solution Type     : kbfix

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

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