Forum Discussion

Copper Contributor

Dec 15, 2021

Solved

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

Access Lock Share laccdb

George_Hepworth
Dec 15, 2021
Billspark1970
@PeteHadden

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

Copper Contributor

Dec 20, 2021

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

caseyg1760
Copper Contributor
Dec 22, 2021
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.
- Karl_Donaubauer
  MVP
  Dec 22, 2021
  
  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
  
  Access News
  - caseyg1760
    Copper Contributor
    Dec 22, 2021
    We 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.