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
    2021-12-17T13:55:53+00:00

    You updated all your PC to this build and confirmed it was successful? Have you rebooted (yes, grasping at straws here!)?

    Was this answer helpful?

    0 comments
  2. Anonymous
    2021-12-17T20:13:26+00:00

    When will new builds be released for Monthly Enterprise Channel (Feature Update)?

    Was this answer helpful?

    0 comments
  3. Anonymous
    2021-12-17T20:30:24+00:00

    There's a lot of "only affects databases on a network drive" going on, but it also affects databases stored on local substituted (SUBST) drives.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2021-12-18T05:39:37+00:00

    The fix is available now for MEC:

    • Monthly Enterprise Channel Version 2110, build 14527.20344

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments
  5. Anonymous
    2021-12-18T05:40:06+00:00

    You are correct, this impacts SUBST drives as well, and the fix will also address that case.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments