On the File menu, click Exit Task Manager. Repeat steps d and e for each occurrence of Winword.exe.ħ. Receive a message that states that the program is not responding,Ħ. In the Task Manager Warning dialog box, click Yes. Click Winword.exe, and then click End Process.ĥ. Click Task Manager, and then click the Processes tab.Ĥ. Press CTRL+ALT+DELETE to open the Windows Security dialog box.ģ. Save all your work, and then quit all programs.Ģ. Your product documentation to complete these steps. NOTE: Because there are several versions of Microsoft Windows, theįollowing steps may be different on your computer. If it is not in use, quit all instances of If the document is in use, open theĭocument as read-only. To resolve this issue, first confirm that another user on the networkĭoes not have the document open. If the file is large, she copy-pastes a LOT or it is open all day) are Temp files, left next to the original file on the network (especially
Third point above can recreate this error quite constantly From my personal experience, I've found a combination of the first The document is shared over a network, and another user has it Word previously quit improperly and, therefore, did not delete the owner file.Ī second instance of Word is running in the background with the document already open. This behaviour may occur if Word determines that the owner file for I was late posting but I've seen this before: We are currently running Office 20 (圆4 and x86) on mostly Win 7 Enterprise with very limited Win 8.1 machines. It does appear to be limited to Microsoft Office products, Word and Excel mainly. It's happened to others on other projects. This wouldn't be a huge problem except that when a project is getting ready to go out, this individual is getting angry phone calls, emails and Lync messages saying, "Get out of the project so we can print this!" and he's not in it. I have tested this by opening it on my machine (obviously I'm not him) and having my colleague (also not UserX) attempt to open the document. He's not the author and he doesn't have it open. Now, UserX is an employee here, but he has nothing to do with this document. If anyone opens the document and another person attempts to open the document it says the document is locked by UserX.
Basically, it's a table that a group of people are using as a running list of issues that a client has on a project and the teams responses on those issues. There are a few pasted items in the document, but that's it. There are no macros or any other distinguishing features that I can see. The document is a "Normal" word document. The current one is a Word document, but this has happened before. We are having issues with some Office documents on our servers.
0 kommentar(er)
