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 No comments

98 answers

Sort by: Newest
  1. Anonymous
    2022-01-12T07:41:59+00:00

    Seriously? I have made the tests and I can confirm, it's fixed it only for 2108 (14326.20738) and not for 2102 (13801.21106)! This is outrageous, 2102 supposed to be stable channel, still supported, we have procedures on the production, we can't change Office version for thousands of users without testing the AddIns and any other Office dependent software. Why fixing only for one build and not the others?

    And why there are still no 2008 version? This version supposed to be supported until 8th of March 2022, is there a plan to release it? What is going on there?

    Was this answer helpful?

    5 people found this answer helpful.
    0 comments No comments
  2. Anonymous
    2022-01-11T22:27:24+00:00

    Version 2102 is Semi-Annual Enterprise Channel Extended and has not been updated yet.

    You can move to Version 2108, which is the current Semi-Annual Enterprise Channel version, and has been updated (build 14326.20738), so if you can move to that channel, it will address the issue for you.

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2022-01-11T18:03:43+00:00

    Can anyone provide the version number for Semi-Annual Enterprise Channel 2102? I could only update to 2108 but it's hard to guess 2102 :(

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2022-01-11T17:57:23+00:00

    My issue might be that I had only updated on 1 PC to test and the database was being used by someone with the December version. There are many others in my environment that are still on that version. I will update all in the coming days and see if this issue is resolved.

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2022-01-11T17:49:30+00:00

    Ah, that may be my problem. that is good news then that this fixes it.

    Was this answer helpful?

    0 comments No comments