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.
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.