You are currently offline, waiting for your internet to reconnect

Shared file access is delayed if the file is open on another computer

Support for Windows XP has ended

Microsoft ended support for Windows XP on April 8, 2014. This change has affected your software updates and security options. Learn what this means for you and how to stay protected.

Support for Windows Server 2003 ended on July 14, 2015

Microsoft ended support for Windows Server 2003 on July 14, 2015. This change has affected your software updates and security options. Learn what this means for you and how to stay protected.

This article was previously published under Q150384
IMPORTANT: This article contains information about modifying the registry. Before you modify the registry, make sure to back it up and make sure that you understand how to restore the registry if a problem occurs. For information about how to back up, restore, and edit the registry, click the following article number to view the article in the Microsoft Knowledge Base:
256986 Description of the Microsoft Windows Registry
If you try to open a file on a computer that is running Windows NT over thenetwork and the file is open on another client computer that has sharingrestrictions, there is a delay of approximately one second before thesharing violation error message is returned. If the client application isaccessing a number of files on the server, this delay may becomesignificant. These symptoms can be easily seen with any multi-user, file-based application, such as the Jet database engine that has shared database files.

NOTE: This behavior is not observed when accessing files on LAN Manager or Windows for Workgroups shares.

This issues occurs because an optimization in the Windows NT Server service delays returning a status to the client while it tries to internally resolve the sharing violation.
To resolve this issue, it may be best to turn off this optimization. Todo so, you must make the following two registry additions.

WARNING: If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.
  1. Start Registry Editor.
  2. Locate the following registry key:
  3. Add the following information:
    Value Name: SharingViolationDelay
    Data Type: REG_DWORD
    Data: 0 (Default: 200)
    Value Name: SharingViolationRetries
    Data Type: REG_DWORD
    Data: 0 (Default: 5)
  4. Quit Registry Editor, and then restart the computer.
If the Server service receives a request for file that is already open, it receives a sharing violation from the local server. The service then waits for a short period before trying to access the file again. This process isrepeated a number of times, internally to the server, to try toresolve the problem before returning to the client.

This feature is controlled by the following two registry values:
  • SharingViolationDelay

    Default 200 (msec)

    This is the period of time that the server waits between retries. If it is set too low, the server receives multiple sharing violations. If it is set too high, the Server Message Block (SMB) response to the client might be delayed, thereby reducing performance.
  • SharingViolationRetries

    Default 5

    This is the number of times that the server retries an SMB requested operation if it receives a sharing violation from the local server's file system. Operations that are affected by this include open, rename, and delete. This minimizes network traffic because if the server can resolve the sharing violation locally, the remote clientdoes not have to retry the operation.
4.00 prodnt status_sharing_violation smb and delete timeout one second delay slow performance netmon

Article ID: 150384 - Last Review: 02/21/2007 00:57:30 - Revision: 4.3

Microsoft Windows 2000 Service Pack 3, Microsoft Windows 2000 Service Pack 2, Microsoft Windows 2000 Service Pack 1, Microsoft Windows NT Workstation 4.0 Developer Edition, Microsoft Windows NT Workstation 3.51, Microsoft Windows NT Server 4.0 Standard Edition, Microsoft Windows NT Server 3.51, Microsoft Windows Server 2003, Standard Edition (32-bit x86), Microsoft Windows Server 2003, Web Edition, Microsoft Windows XP Home Edition, Microsoft Windows XP Professional

  • kbnetwork KB150384