Office Software Thread, "File Locked for Editing By..." has Wrong Name - how?! in Technical; You know the "This file is locked for editing by..." message in Office? Well, we've got a weird one here ...
11th February 2013, 03:47 PM #1
"File Locked for Editing By..." has Wrong Name - how?!
You know the "This file is locked for editing by..." message in Office? Well, we've got a weird one here whereby whoever opens a specific file, it says "This file is locked for editing by Mr A" even though Mr B has the file open. If Mr B opens a different file, then it reports correctly that Mr B has it open, so it isn't anything to do with Mr B's settings.
This isn't a major problem, but is bugging me! Plus, it can be annoying if you desperately need that file, so got to Mr A and ask him to close it, then find he doesn't have it open.
IDG Tech News
11th February 2013, 03:49 PM #2
I have noticed that if you have the file selected in the directory it will not permit deleting or moving, we have had this before too and it is a pain although not quite sure what the exact cause is.
11th February 2013, 03:58 PM #3
So, let me get this straight. You're suggesting that Mr A has My Computer open and has highlighted the file, Mr B opens the file quite happily, but when Mr C comes to open it, they're told Mr A has it locked because he has it highlighted. Yes?
Originally Posted by NikChillin
11th February 2013, 05:06 PM #4
Sorry, that sounded a bit critical and I didn't mean it to. I just want to clarify the scenario you're proposing so that I know what to replicate here so that I can test it.
11th February 2013, 06:56 PM #5
When Word opens a file it generally creates a hidden temp version of the file, that files owner is usually the person shown as locking the file and I think if Mr A opens the file originally, he creates the temp file which is *ownered* to him so when Mr B's word see's the file it displays the message with Mr A the current owner. I think though if Mr A closes the word document while Mr B has it open the temp file is not cleaned up and Mr A keeps ownership of the temp file which means Mr C will see Mr A as locking the file although its actually Mr B in control.
Word cant directly query the FS/Kernel to find out who is locking if its on a share so it has to use this owner based scanning of a hidden temp file.
Thanks to ZeroHour from:
enjay (12th February 2013)
12th February 2013, 09:42 AM #6
I suspect that Mr A had the file open at some point in the past, then experienced a crash of Word/Windows which meant the lock file was not deleted as Word never officially closed the file. Now it is stuck there in limbo. Turn on hidden files and look for the associated lock file, and delete it. For example, for a document named Ducking Word Document.docx, the lock file will be named ~$cking Word Document.docx
Thanks to AngryTechnician from:
enjay (12th February 2013)
12th February 2013, 10:17 AM #7
I think it might have been that hidden file - there was a ~$filename.docx dating back to November created by Mr A, which was evidently preventing another one getting by Mr B when he opened it.
Last edited by enjay; 12th February 2013 at 10:25 AM.
By glennda in forum Windows 7
Last Post: 9th September 2011, 10:37 AM
By elsiegee40 in forum Hardware
Last Post: 10th January 2010, 10:16 PM
By FN-GM in forum Our Advertisers
Last Post: 20th October 2009, 10:22 AM
By pete in forum Our Advertisers
Last Post: 7th July 2009, 03:19 PM
By Little-Miss in forum Office Software
Last Post: 22nd April 2009, 11:51 AM
Users Browsing this Thread
There are currently 1 users browsing this thread. (0 members and 1 guests)