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-20T21:04:34+00:00

    I have the same problem of locking every Access database that I open using version 16.0.13801.21086 . However, I notice that if I log into a remote desktop (VDI with earlier version 16.0.13801.21050 ) I can reopen the locked database (on network drive), then close it, and the lock goes away.

    Was 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-21T00:00:39+00:00

    FYI. Same problem exists now on symbolic link directories. How to report it to MS?

    Was this answer helpful?

    0 comments
  4. Anonymous
    2021-12-21T00:48:19+00:00

    It is intentional that you cannot use the .laccdb file in a symbolic link directory, because it introduces a potential security risk. This is by design.

    Was this answer helpful?

    0 comments
  5. Deleted

    This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

    Comments have been turned off. Learn more