asked on Random Files locked for editing
We have several servers in a VMWare environment that have file shares that are deployed via mapped drives to a terminal server with about 40-50 users on it. The server os used on all is Server 2008 R2 with all latest patches.
A few months ago the servers locked up and had to be rebooted due to issues with one of our SANs. Since that has happened random files have been giving users an error message when they attempt to open them. It actually lets them open the files after a second attempt which is clearly showing something is glitched out.
"xxx.docx is locked for editing by 'another user' "
Sometimes it would actually say the users name, one time it even said the name of a user that didn't even work there anymore.
I ended up resetting ownership of all 250GB worth of files to the administrator account, and gave Domain Users read/write and modify permissions. I essentially stripped ANY custom permissions and made the files appear to Windows as if they had always belonged to the admin and reset all permissions to a blank slate and this is still happening. Any ideas? I'm posting a picture of the file below as well. Any help would be appreciated and if more info is needed please ask. Thanks!
Locked-for-Editing.JPG
A few months ago the servers locked up and had to be rebooted due to issues with one of our SANs. Since that has happened random files have been giving users an error message when they attempt to open them. It actually lets them open the files after a second attempt which is clearly showing something is glitched out.
"xxx.docx is locked for editing by 'another user' "
Sometimes it would actually say the users name, one time it even said the name of a user that didn't even work there anymore.
I ended up resetting ownership of all 250GB worth of files to the administrator account, and gave Domain Users read/write and modify permissions. I essentially stripped ANY custom permissions and made the files appear to Windows as if they had always belonged to the admin and reset all permissions to a blank slate and this is still happening. Any ideas? I'm posting a picture of the file below as well. Any help would be appreciated and if more info is needed please ask. Thanks!
Locked-for-Editing.JPG
Microsoft Server OSSecurityVMware
Last Comment
Robin CM
SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
ASKER CERTIFIED SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
ASKER
This issue occured after a server crash. There is no one opening the files at the time of the messages in fact several times it has shown as locked by users that didn't work at the company anymore. Also the fact that it is saying it to users and then allowing them to open afterwards points to some sort of glitch.
I have also opened a Microsoft ticket but all they did was recommend the hotfixes that robincm posted so I will try that first. I will also try the open files program by Btan and see if it can see the Owner temp files associated with these "open" word documents.
I have also opened a Microsoft ticket but all they did was recommend the hotfixes that robincm posted so I will try that first. I will also try the open files program by Btan and see if it can see the Owner temp files associated with these "open" word documents.
Let us know how you get on! Hopefully the hotfixes will do it.
The error message as far as I'm aware is completely separate from VMWare. It is not associated with powering the VM. All VM's could have been on for weeks and the error message is displayed at random times throughout the day.
That link you provided in the second paragraph does seem helpful however the link going to Server 2008 R2 is an update rollup so it's likely it was already installed. I will go through the update history and varify. Edit: I may be mistaken on this I think I clicked the link for Itanium and not 2008 R2 x64. Will review.
Thanks BTan:
The error message you show is different, that's a VMWare error message for deploying templates. The error message we're getting is associated with a Windows locked error message.
I have checked the backups but they are running from within the VM, not outside. There don't appear to be any errorsin the backup logs either. Backups were not occuring during the lockup and force reboot so that shouldn't be it but I can check with another tech here to see.