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: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2021-12-21T19:30:50+00:00

    The fix is available now for MEC:

    • Monthly Enterprise Channel Version 2110, build 14527.20344

    Updated two clients to this build, tested on two access files, one older mdb and a newer accdb, both on a shared network drive. At this time, the second user trying to open the database file gets the same error, cannot open. However, now, the lock file is not being deleted. But I still cannot get more than one user to open a database. Access is configured to open in shared mode.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  2. Anonymous
    2021-12-20T21:25:45+00:00

    16.0.13801.21086 is known to be the buggy update released on Patch Tuesday. This also explains why the earlier build, 16.0.13801.21050, doesn't experience any issues.

    You should simply update to 16.0.13801.21092 and the problem should be resolved.

    If you want to read all the details, check out

    https://www.devhut.net/access-lock-file-issues/

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  3. 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
  4. Anonymous
    2021-12-15T23:58:39+00:00

    Yes, thanks Daniel - reverted and disabled until an update.

    Thanks for all your efforts - greatly appreciated.

    Greg

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  5. Anonymous
    2021-12-15T23:26:13+00:00

    Did you review the supplied link? Did you uninstall the updates, rollback the build no? That solve the issue while we wait for a fix from Microsoft.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments