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: Oldest
Most helpful Newest Oldest
  1. Anonymous
    2022-01-20T16:47:10+00:00

    Hi Traci, we had the same versions, the newer update on our channel (version 2108) solved issues.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  2. Anonymous
    2022-01-20T16:53:14+00:00

    Do you know if it works on build 16.0.14701.20226

    Was this answer helpful?

    0 comments
  3. Anonymous
    2022-01-20T16:53:35+00:00

    It fixed it for my environment as well.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  4. 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
  5. 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