Forum Discussion

PeteHadden's avatar
PeteHadden
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
scottchester's avatar
scottchester
Copper Contributor
Dec 31, 2021

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.

  • scottchester's avatar
    scottchester
    Copper Contributor
    Jan 06, 2022

    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

    • ahmed1315's avatar
      ahmed1315
      Copper Contributor
      Jan 17, 2022

       

      The sharing issue with MS Access database is solved today after Microsoft has published the newly update (KB5009545).

      scottchester 

      • Karl_Donaubauer's avatar
        Karl_Donaubauer
        MVP
        Jan 17, 2022

        Hi,

         

        Since the discussion here has been read by many people with all kinds of versions and networks, I'd rather repeat the ~3/4 all-clear in more detail:

         

        Read the support article carefully, especially if you have reverted to an older Office build or uninstalled or disabled updates because of the bug!


        According to the article and most reactions in forums etc. Microsoft fixed the bug for most Office versions and variants last week. However, this has not yet been completely done for:

        • Office 2013
        • Office 2016 MSI
        • Microsoft 365 Apps Semi-Annual Enterprise Channel Extended

        For these versions, the bug was only fixed for direct network paths, not for DFS namespaces, short file names, mapped drives etc. If you are not sure what is used on your network, check with your system administrator.

         

        Microsoft will update the article when these versions are also completely fixed. However, there is no time forecast for this yet.

         

        Servus
        Karl
        ************
        Access News
        Access DevCon

Resources