Lock File Problems with Access 16.0.13801.21086

Anonymous
2021-12-14T12:18:17+00:00

On 12/14/2021, SemiAnnual Enterprise channel updated to version 16.0.13801.21086. This is causing several strange behaviors in Microsoft Access. For example:

  1. Create a new Access database on a network drive or open an existing database from a network drive. Close it. The .laccdb file is not automatically deleted (even though no other users are in it).
  2. Use DAO to OpenDatabase for shared (non-exclusive) access. Error 3050 (“Could not lock file.”) is thrown and the database is not opened.
  3. Databases opened on a network drive appear to always be opened for exclusive access. Once one person has opened a database, others can't--even when opening for shared access.

Reverting to the prior version 16.0.13801.21050 fixes the problem.

This problem seems specific to databases located on a network share. For databases on a local machine, there is no issue.

Microsoft 365 and Office | Access | For business | Windows

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

98 answers

Sort by: Newest
Most helpful Newest Oldest
  1. Anonymous
    2022-01-21T00:11:40+00:00

    You have build 13801.21092, which has the fix for UNC paths. (the 13801.21072 is specifically the build number on specific component, which wasn't updated in this case so it has an older build number.) However, there are some issues that the fix may still not address (e.g. if you have 8.3 file names), so it is possible there is another issue you are hitting.

    Semi-Annual channel has updated to Version 2108, build 14326.20738, and that does have the full fix, so the recommendation is to move to that build.

    Shane Groff

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  2. Anonymous
    2022-01-21T00:05:47+00:00

    Do you know if it works on build 16.0.14701.20226

    It will work with build 16.0.14701.20226, because for Version 2111, the problem was not introduced until build 16.0.14701.20248.

    However, if you are on version 2111, build 14701.20290 has the full fix. If you are using Current Channel, though, an update should take you to Version 2112, build 14729.20248, which also has the full fix.

    This page: Error in Access when opening a database on a network file share (microsoft.com)

    Has this information.

    Shane Groff

    Was this answer helpful?

    0 comments
  3. Anonymous
    2022-01-20T23:57:36+00:00

    Unfortunately, no, Version 2102, Build 13801.21106 does not have the fix for this issue.

    However, the current release for Semi-Annual Channel as of January 11 is now Version 2108, Build 14326.20738, and that build does have the fix.

    Shane Groff

    Was this answer helpful?

    0 comments
  4. Anonymous
    2022-01-20T18:57:51+00:00

    Thank you ExcelApostle. So, you're saying I need to talk to our IT people and ask them to upgrade to Version 2108? Looking at this link again:
    https://support.microsoft.com/en-us/office/error-in-access-when-opening-a-database-on-a-network-file-share-6cbc1560-62c2-46e7-9980-d079a46f5acc

    Looking at that large update table they have, I assume you mean: Version 2108, build 14326.20738

    Please confirm the exact build number you have. Thanks.

    P.S. Doing some more digging, I see MS has this latest build for Version 2102, just released Jan 11:
    Semi-Annual Enterprise Channel: Version 2102 (Build 13801.21106)

    Would this build (21106) solve my problem? Or is it just a security update?

    Was this answer helpful?

    0 comments
  5. Anonymous
    2022-01-20T16:54:44+00:00

    We have the same issue on build 13801.21086, is there a true fix for this build

    Was this answer helpful?

    0 comments