• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1038
  • Last Modified:

Files are repeatedly "Locked for editing by 'another user' "

Users in our HR department keep complaining that they receive an error almost every time they try to open an MS Office file (xls, xlsx, doc, docx, etc...).

I have verified the problem and I checked the usual suspects: no orphaned owner files, no open files are listed on the file server. I even reset user permissions for the file share (forced reinherit).

This occurs regardless of which file is opened, but only seems to happen on this one mapped share. Here's a sample screenshot of the error.  Locked for editing by 'another user' error
0
Stuart_Page
Asked:
Stuart_Page
1 Solution
 
Stuart_PageAuthor Commented:
Number-1,

Thanks for the reply but that article refers to orphaned owner files, which I already mentioned that I checked for.

Thanks.
0
 
MaximumIQCommented:
And you already made sure the files are not actually being used?

You can check from the file server's console in computer management > Shared Folders > open files
0
Ultimate Tool Kit for Technology Solution Provider

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy now.

 
Randy DownsOWNERCommented:
OK, these are not Sharepoint are they?
http://support.microsoft.com/kb/899709
0
 
Stuart_PageAuthor Commented:
Nope, not sharepoint. Users are just accessing files from a mapped file share (SMB).
0
 
Randy DownsOWNERCommented:
0
 
Stuart_PageAuthor Commented:
This last KB doesn't seem to refer to the same problem.
0
 
Randy DownsOWNERCommented:
It's similar but doesn't apply unless there is a Microsoft Windows 2000-based network share involved.-
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.
0
 
Stuart_PageAuthor Commented:
My file server is 2008 R2 x64
0
 
Stuart_PageAuthor Commented:
No luck with any of these suggestions.
0
 
toookaCommented:
I have the same problem and have yet to find solution
0
 
Stuart_PageAuthor Commented:
I ended up upgrading the affected user's workstations to Win7 Pro x32. The problem hasn't come back since.
0
 
Stuart_PageAuthor Commented:
This was a very frustrating issue. I wasn't able to adequately troubleshoot the cause of the issue. Eventually, it became more important to come up with a resolution. Upgrading the workstations was the only option.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Ultimate Tool Kit for Technology Solution Provider

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy now.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now