Forum Discussion
Database no longer shareable
For years we've used a split front-end / back-end Access DB. Each PC has a copy of the client and the backend data lives on a NAS drive. For some reason recently, once one user opens their client, no other user can access theirs with the message "count not use \\nameofthebackendDB.accdb; file already in use"
I've checked the users have read/write/create privileges (nothings changed anyway) - the first user causes a lock file .laccdb to get created with 0 bytes, and when they close Access the file remains in the backend folder.
I even tried creating a new database with just a single table and a couple of clients to connect to it and the same thing happens. It also happens when I store the backend on different devices such as a shared folder on a PC. Has something happened to Access or Windows that would cause this behaviour?
This appears to be the newest bug released by Microsoft. Information here
Rolling back this update should resolve it until MS gets a fix out.
17 Replies
It seems that Microsoft believes this was fixed in version Version 2102 (Build 13801.21092), but we continue to experience the problem and have had to roll back to Version 2102 (Build 13801.21050). Is anyone else still having this issue?
I'm trying group policy to deny the 21092 version and force the 21050 version and have manually rolled the workstations back.
Microsoft has updated https://support.microsoft.com/en-us/office/error-in-access-when-opening-a-database-on-a-network-file-share-6cbc1560-62c2-46e7-9980-d079a46f5acc and now says:
Important: Currently, the applied fix only addresses standard UNC paths. Our team is currently working on a fix for the following network paths:
DFS-N
Short file names
Mapped drives
Hard links, Junctions and Symbolic links
The sharing issue with MS Access database is solved today after Microsoft has published the newly update (KB5009545).
PeteHadden - My users just started getting this message as well.
They are on Build - Microsoft® Access® for Microsoft 365 MSO (Version 2111 Build 16.0.14701.20240) 32-bit & Microsoft® Access® for Microsoft 365 MSO (Version 2111 Build 16.0.14701.20254) 64-bit
Both builds are affected., It was not a split database. When I try to SPlit it, I get could not lock the file.
I am asking the client if they want to Hotseat the database until a fix that actually works is issued by Microsoft, or if they want us to roll back the updates.
According to this "it is fixed (yeah, right) - https://support.microsoft.com/en-us/office/error-in-access-when-opening-a-database-on-a-network-file-share-6cbc1560-62c2-46e7-9980-d079a46f5acc
Thanks for your guys's insight, I will update what we find as soon as the client lets me know
cv_Frank - We are on the exact 64 bit build and the issue is persistent on our end. Fix it MS! I may be rolling back tomorrow morning.
PeteHadden I have exactly the same issue just since this morning. No changes to my setup either. Just stopped working for everyone. Only 1 user can use it at a time.
This is our major customer service admin database and 5 users have been getting the benefit of the system for years. Now a MAJOR problem!
I spent over an hour on to tech support at microsoft and they passed me around until they just directed me here.
Help anyone?
This appears to be the newest bug released by Microsoft. Information here
Rolling back this update should resolve it until MS gets a fix out.
Thank you George - I spent a good few hours chasing my tail trying to get to the bottom of that one. It was so recent that there wasn't really anything on the general internet that helped. I followed the instructions from MS on rolling back to an earlier version of office:
https://support.microsoft.com/en-us/topic/how-to-revert-to-an-earlier-version-of-office-2bd5c457-a917-d57e-35a1-f709e3dda841
I settled on version 2111, build 1407.20226 and this works fine. I'm so glad I've only got about 6 PCs to do and not 60! How will we know when MS have released a fix I wonder?
Thanks again - I'm buying you a virtual beer!
