I've been experiencing a frustrating issue with our file server since around February. It seems to occur randomly, and I need help figuring out what's going on. Here are a few scenarios that illustrate the problem:
1. Bob edited a file a week ago, saved it, and closed it. Now, when he tries to reopen it, he gets a message saying it's open for editing by 'Bob', even though he has it closed.
2. Bob tries to access another file and receives a notice that 'Jane' has it open, yet when he checks, Jane hasn't accessed that file in days.
3. Bob created a new project folder but cannot rename it after a while.
4. Today, Bob faced the same issue as in the first scenario—the file shows as open by him when he knows it's not.
I checked 'Computer Management\Shared Folders\Open Files' and found that the file was actually opened by Jane, not Bob.
This issue affects various file types. Rebooting either Jane or Bob's computers doesn't help, and even I rebooted the file server one evening, but the problem continued the next day. Checking 'Open Files' doesn't provide much insight either, as it rarely lists the right information. I've already disabled "Offline files" and the "Preview Pane" on workstations in case these were causing the issue. I'm really at my wit's end and am hoping to tap into some collective wisdom here. Thanks!
4 Answers
Are the files in question Office files? Microsoft Office often creates hidden lock files (they start with a ~) to indicate that a file is in use. If that file is left behind—especially after a crash—it could cause the file to appear open when it’s not. You could try deleting these if you're sure no one has the file open. Also, if you've set up DFSR recently, it might be causing some sync issues with your server.
You might want to try enabling the option to view hidden system files in the folder where your documents are stored. Sometimes, those pesky .tmp files can cause confusion. It might be worth moving them somewhere safe just in case they're causing the issue!
Absolutely! Those tmp files can really go haywire.
Make sure to show hidden files in your file storage directory and check for any hidden lock files. They usually start with a ~ as well. This can happen if the server restarts while someone’s still editing a file, leaving that lock behind. Try removing it when no one is using the file.
You can check the shared files in computer management to see if there are active sessions. This might help identify if someone is genuinely accessing the files.
No DFSR here. Most files are Office ones, but I’m also seeing issues with folder renaming, so I’ll look into those hidden files.