Link to home
Start Free TrialLog in
Avatar of TopCat-007
TopCat-007Flag for United Kingdom of Great Britain and Northern Ireland

asked on

File Locks - 2008 Server

I've a problem with Files being locked the network and server are several years old and this has only just started to happen.

The file shows as "File Locked by network user", I've Win 10 Pro clients with 2008 R1 file server, the file is not shown as being locked on the server.  This particular .DOCX file was used by one user who has restarted but the lock remains.

Is there a tool to better show file locks other than Comp Man\Shared Folders\Open Files?

Thanks in advance.
Avatar of N8iveIT
N8iveIT
Flag of United States of America image

See https://support.microsoft.com/en-us/help/313472/the-document-is-locked-for-editing-by-another-user-error-message-when for a possible resolution, particularly:
  • Word previously quit improperly and, therefore, did not delete the owner file.
  • The owner file is located in the same folder as the document that you tried to open. The owner file name uses the following convention: It begins with a tilde (~), followed by a dollar sign ($), followed by the remainder of the document file name. The file name extension is .doc. For example, the owner file for Document.doc is named ~$cument.doc.
There is a tool for Windows desktop called LockHunter.  However, I am unsure if it will work with servers and network file lock.

https://lockhunter.com

For network admin I only use  Comp Man\Shared Folders\Open Files as you mentioned.
Avatar of TopCat-007

ASKER

yes, I've seen that article. there's no owner file.

it looks like it might be the client machine causing this because its happened again on another file, same user/PC.  

What I don't understand is I cant see the lock on the server and therefore I can't release it.  I'm sure a server reboot will fix it but that shouldn't be needed.

thanks for your msg
I have seen this problem before but not with Server 2008.  It's with server 2003.  Just trying to recall what we did to fix it.
Just curious; if you make a copy of the file, does the copy show as open?
yes, open the file as a copy and save as a new file works as you'd expect.  tks
(This is *not* a final answer but a work-around from having to prevent a reboot until the actual solution is found) At this point, would a work-around be:
1. Copy the original file
2. Delete the original file
3. Rename the copy to the original file name

... or ...

Does the server prevent the original file from being deleted (i.e. does it show it as open or does Word "think" it is open)?
David, I couldn't rename/delete it before but I've just tried again and its worked.  I'm in the UK so this office has shut down and gone home so I'm thinking someone must have had an active lock on it (or there's a timeout for locked files?)  but again, how come I couldn't see it from the server that was sharing the file..
Hi TopCat-007, which office version is it and is this problem specific only to DOCX files?  How about Excel files,etc?
SOLUTION
Avatar of N8iveIT
N8iveIT
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
One additional note about the Owner file (from https://serverfault.com/questions/691593/file-lock-on-windows-server?utm_medium=organic&utm_source=google_rich_qa&utm_campaign=google_rich_qa), "The owner file is hidden, so you will need to enable 'view hidden files and folders' to view it. If the owner file is present then you can simply delete it to 'unlock' the file."

Interestingly enough, this post discusses Word but refers to the above Blog link at the end.
ASKER CERTIFIED SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
No final answer was given as to if or what resolved the issue.

Awarding points because I think Wayne88 is correct in thinking it is Word and it most likely ties into some of the locking issues discussed in the referenced Excel post.