Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

XP runs slow and locks word docs.

Status
Not open for further replies.

j3w3ll

Technical User
Apr 10, 2003
19
GB
I have a problem with to XP machines, they run very slowly when opening a document from a double click(a word doc on desktop).. 6 - 10 seconds. also get a problem that xp crashes while in word2000 and then when you go to open file it says some one is in it. i go to the server and computer management open files and close the doc. the spec of the clients are p4 1.8 512mb 40 gb hdd c: 10gb d: 20 swap file is on drive d. server is a win2k server.

any help most appricated
 
Hello if anyone out there has any info, I am also having this same problem with 3 windows xp professionals with office xp. The major concern is that the computers will not release the files and i get a message that the file is opened by some one else.
 
spot on rich, this is exactly the same as i am getting, im looking all over the internet for a fix for this, i will post it here if i get one.
 
When Word crashes make sure to check that the winword.exe process is not still running. You can check by pressing CTRL-ALT-DEL and then clicking the process tab. Look for "winword.exe". If it is running and you have no instances of Word opened, kill the process. That should eliminate any error about documents being in use. I don't know what would be causing it to crash in the first place though. All I can recommend that you do is go to the Windows Update web page and click the Office Update link at the top of the page. Run the scan and it will check if you need any updates done to your Office installation, such as Service Pack updates. These updates might fix your problems. Good luck!

Niall
 
You could try downloading the freeware Handle.exe and see what process is using the files.


A File Cannot Be Deleted or Accessed on an NTFS Volume (Q159199)

Write-protect lies!
thread779-478243

176313 - WD: Troubleshooting Guide: File Locking in Master Documents

255908 - WD2000: Part 1: General Information About Master Documents

WD2000: Part 2: General Information About Master Documents
 
Are you using Diskeeper defragger?
My 2G4 pentium 4 Dell took up to 30 seconds to open folders, start button, apps, etc for months but only some times.
Short story:
-Diskeeper was defragging at those times.
-An update to build Diskeeper 428 and using the defrag-on-on-screen-saver option cleared the whole thing up.
 
Hello:
99% of the time this problem is cause by a corrupt Normal.dot file. Search on your hardrive for "normal.dot" rename it to normal.old. Word will then rebuild the template. Most of the time this problem is caused by Word not closing down right or virus's. You might check for virus's
Icon58
 
have serviced packed office 2000 to sp3 but still same probs - when word opens some times it is in read only, no one is in the files, if you close word the open the file again it is not in read only. this is strange
 
Has anyone solved the initial problem with windows xp locking files open????
 
Remove Windows update 811493, ignore warnings. This is a known MS problem.
 
so which one do i do.. i did a search in the registry and none of them have the enableoplocks key.

They all have that update 811493 installed.. are you sure i need to uninstall that.
 
The following fixed the original post error, it is to be applied on your windows 2000 server, it is an issue with xp and 2000, (ummm why?, i know!) Go to a win2k domain controller, open up Active Directory Users and Groups, Go to the DC OU and right clcik on it, select properties, select group policy tab. Select default domain controller policy, and click edit. navigate through until you get to Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options. Disable the following;
Digitally Sign Client Communications (allways)
Digitally Sign Client Communications (when possible)
Digitally Sign Client Communications (Always)
Digitally Sign Client Communications (when possible)

close GP Editior and click ok close Active Directory and do the following;

from the run command

SECEDIT /refreshpolicy machine_policy /enforce, this will force a DC Refresh.

I got this information from the following website, i wouldn't try and pass it off as my own knowledge!! ive applied it to three sites now and it has worked excellant, i advise reading the page as it makes interesting reading.


GOOD LUCK
 
chrisazzi,


The change in the registry is made on the File Server. If the key does not exist (odd that it would not) add it:

Click Start, and then click Run.
In the Open box, type regedit, and then press ENTER.
In Registry Editor, locate the following subkey in the registry:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet \Services\LanmanServer\Parameters

In the right pane, click EnableOplocks, and then press ENTER.
In the Value data box, type 0, and then press ENTER.
Quit Registry Editor.
 
boydo,

There are two versions of 811493. There is absolutely nothing wrong with the latter version.

Besides, it has nothing to do with this issue.
 
enableoplocks was set to zero already.. could it be because i disabled the security entries in the OU.

enableoplockforseclose has a value 1 is that correct?
 
A good checklist for this problem:



Files on Network Shares Open Slowly or Read-Only or You Receive an Error Message

The information in this article applies to:

Microsoft Windows XP 64-Bit Edition
Microsoft Windows XP Professional SP1
Microsoft Windows XP Professional
Microsoft Windows XP Tablet PC Edition
Microsoft Windows 2000 Server
Microsoft Windows 2000 Server SP1
Microsoft Windows 2000 Server SP2
Microsoft Windows 2000 Server SP3
Microsoft Windows 2000 Professional
Microsoft Windows 2000 Professional SP1
Microsoft Windows 2000 Professional SP2
Microsoft Windows 2000 Professional SP3
Microsoft Windows 2000 Advanced Server
Microsoft Windows 2000 Advanced Server SP1
Microsoft Windows 2000 Advanced Server SP2
Microsoft Windows 2000 Advanced Server SP3
Microsoft Excel 2000
Micosoft Excel 2002
Microsoft FrontPage 2000
Microsoft FrontPage 2002
Microsoft PowerPoint 2000
Microsoft PowerPoint 2002
Microsoft Word 2000
Microsoft Word 2002
Microsoft Access 2000
Microsoft Access 2002


·SYMPTOMS

You may experience any of the following symptoms:

When you copy a file over the network in Windows XP, if the source file is located on a 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 a long time to open.

You may receive various error messages, or other problems may occur, when you use a program that opens and closes files, or creates temporary files, on a Windows 2000-based server with Server Message Block (SMB) signing enabled.

A file that you open over the network is opened as read-only, or a sharing violation occurs, and you must save the file locally to make changes. This 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.

Programs such as Excel or PowerPoint may open two files successfully but display a "Read-Only" error message when you open a third file.

Network programs that rely on heavy network file input/output (I/O) may seem to stop responding (hang), or delays may occur when you open or close files (because "Oplock Break" requests are ignored).

Problems may occur when Windows 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 can be opened only as read-only.

CAUSE

This issue may be caused by any of the following items:

There is a problem in negotiating SMB signing from a client that is running 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 problem may be caused by any of the following items:

The network folder is open in 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

To resolve this issue, follow these steps:

Download and install the MS02-070 security patch 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 patch, 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

Upgrade any Windows XP-based client computers to 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


If the issue is not yet resolved, disable network drive scanning in your antivirus program. If the problem is still not resolved, temporarily disable your antivirus program. In some cases, 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 resolves the issue, contact the manufacturer of your antivirus program for additional information about this issue and how to resolve it. For example, visit the following third-party Web sites for information about how to resolve this problem with specific antivirus products:

Trend Micro OfficeScan Corporate Edition 5.0
Norton AntiVirus Corporate Edition 7.6
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" errors 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 additional 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 Over Slow Links if Oplock Is Not Granted for the Policy File


REFERENCES

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

306981 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

Last Reviewed: 6/4/2003

Keywords: kbprb KB814112
 
Can i ask an exchange 2000 question...

HOW do I migrate my mailboxes from SBS 2000 to my new Windows 2000 server.

I can not create a trust because of sbs 2000..

any help would be appreciated.

chris
 
Guys i applied all those patches to my windows xp machines.. and still every morning i have to log off the user and back on to establish a connection to the windows 2000 server..



its driving me insane.. please help.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top