Forum Discussion
Database no longer shareable
- Dec 15, 2021
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.
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?
- George_HepworthDec 15, 2021Silver Contributor
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.
- PeteHaddenDec 16, 2021Copper Contributor
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!
- George_HepworthDec 16, 2021Silver Contributor
PeteHadden MS now has a discussion up on this site. It notes that they'll update it when they get a fix ready. We'll all be keeping an eye on that page, I think.
- NerdyGuy86Dec 16, 2021Copper Contributor
Here's a detailed rundown and fixes for the following issue. Thank me later 🙂
Symptoms:
- You receive the following error when opening access "Could not use ‘path to database.accdb’; file already in use"
- Your database backend is stored on a network location.
- The laccdb lock file does not automatically disappear when all users have disconnected from the shared accdb file.Affected Versions:
- Office 2019 Version 1808, build 10381.20020
- Office LTSC 2021 Version 2108, build 14332.20204
- Current Channel Version 2111, build 14701.20248
- Monthly Enterprise Channel Version 2110, build 14527.20340
- Monthly Enterprise Channel Version 2109, build 14430.20380
- Semi-Annual Enterprise Channel (Preview) Version 2108, build 14326.20692
- Semi-Annual Enterprise Channel Version 2102, build 13801.21086
- Semi-Annual Enterprise Channel Version 2008, build 13127.21842Caused by:
Microsoft Jet Red Database Engine and Access Connectivity Engine Elevation of Privilege Vulnerability update.Resolution:
This issue can be resolved one of 3 ways (See below);1.) Removing the following updates;
- KB5002099
- KB5002104
[Note] This will only temporarily fix the problem until the next time office updates. You can disable the updates in File > Account > Office Updates > Disable Updates2.) Reverting back to an older version of office by running the following command (elevated)
- Version 2013 – “C:\Program Files\Common Files\microsoft shared\ClickToRun\OfficeC2RClient.exe” /update USER displaylevel=True forceappshutdown=true updatetoversion=15.0.5397.1002"
- Version 2016 – “C:\Program Files\Common Files\microsoft shared\ClickToRun\OfficeC2RClient.exe” /update USER displaylevel=True forceappshutdown=true updatetoversion=16.0.14701.20226"
[Note] This will only temporarily fix the problem until the next time office updates. You can disable the updates in File > Account > Office Updates > Disable Updates3.) Combination permanent build fix until next build change.
a. Revert back to last update (as seen above).
b. make a copy of the acecore.dll files. You can find these by searching your program files directories.
c. Update Microsoft office as normal using the File > Account > Office Updates > Update Now
d. Once updated, copy the acecore.dll files back into the original locations.- ShakerDBDec 20, 2021Copper Contributor
Thank you for the information. I have been working hard over the weekend trying to solve the problem with no luck.
The fact that it is not my database or the network folder configuration made me happy even before solving the problem.
I will go ahead and try the fix and get back to the group.
Again thank you to everyone in this post.
Update:
By uninstalling the update of KB5002104, I could get 5 computer back in business, all computers have Office 2013 Pro. One thing I couldn't understand, one of the computers didn't have this update installed but was not able to link to the back end as well, is that because the other computers already locked the BE out. Does that mean if I still have a computer with this update installed, it can infect the BE if it try to connect to it?