How to Disable Network Redirector File Caching

Last reviewed: February 17, 1998
Article ID: Q163401
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

While data is being transferred to a remote server, you may experience one of the following error messages:

   Event ID 26:
   Application popup: System process-lost delayed write data:
   the system was attempting to transfer file data from buffers to
   <filename path>. The write operation failed and only some of the
   data may have been written to the file.

   -or-

   Event ID 26
   Application popup: System process-lost delayed write data:
   the system was attempting to transfer file data from buffers to
   <network share>. The write operation failed and only some of the
   data may have been written to the file.

These popup messages may also be accompanied by one or more of the following event log messages:

   Event ID: 3013
   Description: The redirector has timed out to <Servername>

   -or-

   Event ID: 8007
   Description: NetWare redirector timed out its request to server
   <Servername>


CAUSE

By default, when the Windows NT redirector opens a file for read or read/write access, the redirector utilizes the Windows NT system cache. Therefore, when data is written to the file, it is written to the cache and not immediately flushed to the redirector. The cache manager flushes the data at a later time. If an unrecoverable network error occurs while the data is being transferred to the remote server, it may cause the write request to fail and the above application popup to occur.

RESOLUTION

WARNING: This procedure should first be tested in a non-critical environment before being implemented into a production environment. In general, this change will slow down network I/O.

You can disable Network Redirector File Caching by performing the following steps:

WARNING: Using Registry Editor incorrectly can cause serious, system-wide problems that may require you to reinstall Windows NT to correct them. Microsoft cannot guarantee that any problems resulting from the use of Registry Editor can be solved. Use this tool at your own risk.

  1. Start Registry Editor (Regedt32.exe) and go to the following subkey:

          HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Rdr\Parameters
    

  2. Click Add Value on the Edit menu.

  3. Enter the following:

          Value Name: UseWriteBehind
          Data Type:  REG_DWORD
    
          Data:       0
    
          1-true 0-false (default: 1)
    
          UseWriteBehind - Enables the write-behind optimization for write
          Only files.
    
    

  4. Go to the following subkey:

          HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services
    
             \Lanmanworkstation\parameters
    
    

  5. Click Add Value on the Edit menu.

  6. Enter the following:

          Value Name: UtilizeNTCaching
          Data Type:  REG_DWORD
    
          Data:       0
    
          1-true 0-false (default: 1)
    
          UtilizeNTCaching - Indicates whether the redirector uses the cache
          manager to cache the contents of files. Disable this parameter only
          to guarantee that all data is flushed to the server immediately after
          it is written by the application.
    
    

  7. Shut down and restart your computer.


Additional query words: 4.00 3.51 prodnt nts
Keywords : nthowto ntregistry NTSrvWkst kberrmsg kbhowto
Version : 3.51 4.0
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: February 17, 1998
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.