Semaphore Timeout Error When UseWriteBehind Disabled for Redirector

ID: Q169742

The information in this article applies to:

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.


RESOLUTION

To resolve this problem, obtain the latest service pack for Windows NT 4.0 or Windows NT Server 4.0, Terminal Server Edition. For additional information, please see the following article in the Microsoft Knowledge Base:

Q152734 How to Obtain the Latest Windows NT 4.0 Service Pack

Windows NT 3.51

A supported fix that corrects this problem is now available from Microsoft, but it has not been fully regression tested and should be applied only to systems experiencing this specific problem.

To resolve this problem, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone numbers and information on support costs, please go to the following address on the World Wide Web:
http://www.microsoft.com/support/supportnet/overview/overview.asp
The English version of this fix should have the following file attributes or later:

   Date      Time    Version      Size    File name     Platform
   -------------------------------------------------------------
   05/29/97  06:20p               259,920 Rdr.sys       (x86)
   05/29/97  05:19p               470,928 Rdr.sys       (Alpha)
   05/29/97  05:18p               430,160 Rdr.sys       (MIPS)

NOTE: If this product was already installed on your computer when you purchased it from the Original Equipment Manufacturer (OEM) and you need this fix, please call the Pay Per Incident number listed on the above Web site. If you contact Microsoft to obtain this fix, and if it is determined that you only require the fix you requested, no fee will be charged. However, if you request additional technical support, and if your no-charge technical support period has expired, or if you are not eligible for standard no-charge technical support, you may be charged a non-refundable fee.

For more information about eligibility for no-charge technical support, see the following article in the Microsoft Knowledge Base:
Q154871 Determining If You Are Eligible for No-Charge Technical Support


WORKAROUND

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


STATUS

Microsoft has confirmed this to be a problem in Windows NT 3.51, 4.0 and Windows NT Server 4.0, Terminal Server Edition. This problem was first corrected in Windows NT 4.0 Service Pack 4 and Windows NT Server 4.0, Terminal Server Edition Service Pack 4.

Additional query words: 4.00 3.51 wts tse event id 26 


Keywords          : NT4SP4Fix kbbug4.00 kbfix4.00 TSESP4Fix 
Version           : winnt:3.51,4.0
Platform          : winnt 
Issue type        : kbbug

Last Reviewed: July 2, 1999