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.
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.
Hi,
Today Microsoft has updated the bug article with this caveat:
Note: If you are using Distributed File System Namespaces (DFS Namespaces overview | Microsoft Docs) to redirect a folder that contains an Access database, you will still see the issue that you cannot open the database for shared use, even with the fixed update.
You should use the direct path to the database to allow shared usage.
Servus
Karl
- caseyg1760Dec 22, 2021Copper ContributorWe use dfsr but not dfsn so I don't know if this applies to us or not. We just map all our drives via GPO. So it's just UNC path to the servers/shares.
- GustavBrockDec 23, 2021MVP
It doesn't matter wether you use an UNC path or a mapped drive. What matters is, if the UNC path used (for the mapped drive) is a virtual DFS path. If so, change the path used from the DFS path to a path having one of the member servers of the DFS name space.
If you prefer to roll back to a previous version not hit by this issue, I've found it to be this (or earlier):
Version 2102 (Build 13801.21050 Click and run) semi-annual enterprise
- ShakerDBDec 23, 2021Copper Contributor
As I'm not familiar with the server structure and all this terminology, I won't update office for the time being until this bug is completely gone. It safer that way (at least for myself).
Happy holidays guys and thank you for all your help.
- caseyg1760Dec 22, 2021Copper ContributorHi Karl, so don't use the share name but the full 'UNC' path?
Thanks
Casey