Microsoft KB Archive/814112

From BetaArchive Wiki
Knowledge Base


Article ID: 814112

Article Last Modified on 12/1/2007



APPLIES TO

  • Microsoft Windows XP Professional x64 Edition
  • Microsoft Windows XP Professional
  • Microsoft Windows XP Professional
  • Microsoft Windows XP Tablet PC Edition
  • Microsoft Windows 2000 Server
  • Microsoft Windows 2000 Service Pack 1
  • Microsoft Windows 2000 Service Pack 2
  • Microsoft Windows 2000 Service Pack 3
  • Microsoft Windows 2000 Professional Edition
  • Microsoft Windows 2000 Service Pack 1
  • Microsoft Windows 2000 Service Pack 2
  • Microsoft Windows 2000 Service Pack 3
  • Microsoft Windows 2000 Advanced Server
  • Microsoft Windows 2000 Advanced Server
  • Microsoft Windows 2000 Advanced Server
  • Microsoft Windows 2000 Advanced Server
  • Microsoft Excel 2000 Standard Edition
  • Microsoft Excel 2002 Standard Edition
  • Microsoft FrontPage 2000 Standard Edition
  • Microsoft FrontPage 2002 Standard Edition
  • Microsoft PowerPoint 2000 Standard Edition
  • Microsoft PowerPoint 2002 Standard Edition
  • Microsoft Word 2000 Standard Edition
  • Microsoft Word 2002 Standard Edition
  • Microsoft Access 2000 Standard Edition
  • Microsoft Access 2002 Standard Edition



Important This article contains information that shows you how to help lower security settings or how to turn off security features on a computer. You can make these changes to work around a specific problem. Before you make these changes, we recommend that you evaluate the risks that are associated with implementing this workaround in your particular environment. If you implement this workaround, take any appropriate additional steps to help protect your system.

SYMPTOMS

You may experience any one of the following symptoms:

  • When you copy a file over a network in Microsoft Windows XP, if the source file is located on a Microsoft Windows 2000-based network share, you may receive either of the following error messages:

    File or network path no longer exists.

    No network provider accepted the given network path.

  • When you try to open a file from a network share, the file may take longer than expected to open.
  • You may receive various error messages or experience other issues when you use a program that opens and closes files or that creates temporary files on the server if the Windows 2000-based server has Server Message Block (SMB) signing turned on.
  • A file that you opened over the network is opened as read-only, or a sharing violation occurs and you must save the file locally to make changes.

    This issue may occur even if your permissions are set to Full Control for both the share and the volume that uses the NTFS file system, and no other user has the file open. In this case, you may receive one of the following error messages:

    File in use: Filename is locked for editing by username. Click 'Notify' to open a read-only copy of the document and receive notification when the document is no longer in use.

    This command is not available because the document is locked for editing.

    The document Filename is locked for editing by another user. To open a read-only copy of his document, click...

    File is locked for editing, do you want to open a read-only version of the file.

    Cannot open Filename on network share. Make sure a disk is in the drive you specified.

    Access is denied. The file may be in use by another application.

  • When you open files, programs such as Microsoft Excel or Microsoft PowerPoint may open two files successfully but display a "Read-Only" error message when you open a third file.
  • When you open or when you close files, network programs that rely on heavy network file input/output (I/O) may seem to stop responding, or delays may occur.
  • You may experience issues when Windows XP applies group policies or runs logon scripts.
  • You can save a Microsoft Office file by using the same file name only after you have the file open for at least 30 minutes.
  • You may also receive other error messages, depending on the program that you are using. For example, you may receive error messages that indicate that a file is already in use or that a file can be opened only as read-only.


CAUSE

This issue may occur if any one of the following conditions is true:

  • There is an issue with negotiating SMB signing from a client that is running Microsoft Windows XP Service Pack 1 (SP1) to a Windows 2000-based server that requires SMB signing.
  • Another process has the file open and locked. For example, this issue may be caused by either of the following items:
    • The network folder is open in Microsoft Windows Explorer and you are using Details view to display additional details (such as the author or title) for files in the folder. Windows Explorer reads the contents of the files in the folder to obtain the additional details. If a program tries to open a file exclusively and Windows Explorer has the network file open to extract this additional file information, a sharing violation occurs.
    • Another program or process, such as an antivirus program (either on the client computer or on the server), may have the file locked.


RESOLUTION

Warning This workaround may make your computer or your network more vulnerable to attack by malicious users or by malicious software such as viruses. We do not recommend this workaround but are providing this information so that you can implement this workaround at your own discretion. Use this workaround at your own risk.

Note An antivirus program is designed to help protect your computer from viruses. You must not download or open files from sources that you do not trust, visit Web sites that you do not trust, or open e-mail attachments when your antivirus program is disabled.

For additional information about computer viruses, click the following article number to view the article in the Microsoft Knowledge Base:

129972Computer viruses: description, prevention, and recovery


To resolve this issue, follow these steps:

  1. Download and install the MS02-070 security update that is described in Microsoft Knowledge Base article 329170 on all Windows 2000-based and Windows XP-based file servers and client computers.

    For additional information about this update, click the following article number to view the article in the Microsoft Knowledge Base:

    329170 MS02-070: Flaw in SMB signing may permit Group Policy to be modified

  2. Upgrade any Windows XP-based client computers to Windows XP Service Pack 1 (SP1), and then obtain and install the hotfixes that are described in Microsoft Knowledge Base articles 328170 and 812937.

    For additional information about how to obtain Windows XP SP1, click the following article number to view the article in the Microsoft Knowledge Base:

    322389 How to obtain the latest Windows XP service pack

    For additional information about how to obtain the hotfixes, click the following article numbers to view the articles in the Microsoft Knowledge Base:

    812937 File Lock or Access Denied error message when you save files over the network

    328170 Program opens a file as read-only or returns a sharing violation or "Access Denied" message when opening from or saving to a network folder

  3. If you have not resolved the issue, disable network drive scanning in your antivirus program. To turn off your antivirus program, see the antivirus program documentation or online help for steps and information about how to do this.

    If the issue is still not resolved, temporarily turn off your antivirus program. Sometimes, you may have to remove antivirus software on both the client and the server to troubleshoot this issue. If removing or disabling your antivirus program does not resolve the issue, contact the manufacturer of your antivirus program for additional information about this issue and the steps that you must take to resolve the issue. For example, visit the following third-party Web sites for information about how to resolve this issue with specific antivirus products: Microsoft provides third-party contact information to help you find technical support. This contact information may change without notice. Microsoft does not guarantee the accuracy of this third-party contact information.


MORE INFORMATION

Network Monitor traces may show "DOS Error, (5) ACCESS_DENIED" or "DOS Error, (32) SHARING_VIOLATION" error messages after 35 seconds (between "SMB: C NT create & X" commands for the same file name). The time that the server waits for an Oplock Break response is controlled by the LanmanServer parameter OplockBreakWait. By default, this parameter is set to 35 seconds.

For more information about how to work around logon delays, click the following article number to view the article in the Microsoft Knowledge Base:

319440 Logon delays occur over a slow connection if opportunistic locking is not granted for the policy file in Windows


REFERENCES

For additional information, click the following article numbers to view the articles in the Microsoft Knowledge Base:

306981 Level II oplocks are not granted after a file is locked


324002 Searching files across a network may leave open files


296264 Configuring opportunistic locking in Windows


812513 File takes an unexpectedly long time to open through server message block protocol


829700 Slow network performance when you open a file that is located in a shared folder on a remote network computer


826722 Cannot delete shortcut on a network share: "It is being used by another person or program"


822227 Program may raise a sharing violation when a file is opened from Windows Explorer


811005 User authentication to services such as Microsoft Exchange Server may time out on a member server



Additional query words: enableoplocks oplocksdisabled level ii file locking offline files slow performance anti-virus locking non-shared files blocked for 30 minutes 3rd file or 4th file smb signing Office 2002 Office XP Outlook Visio terminal server columnhandlers Shell32.dll 6.0.2800.1157 Mrxsmb.sys Srv.sys 331519 q331519

Keywords: kbnetwork kberrmsg kbprb KB814112