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-15T23:14:04+00:00

    Further ... when attempting to open a database already opened by a prior user (shared or exclusive makes no difference), the second user's attempt fails, but DOES result in the second user deleting the lock file.

    Subsequently when the first user closes and reopens the database, no lock file is created (at least not in the same location as the database), yet the second user still CANNOT open the database - even though no lock file exists.

    This is unexpected.

    Greg

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments
  2. 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
  3. 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
  4. Tom van Stiphout 40,216 Reputation points MVP Volunteer Moderator
    2021-12-17T01:41:23+00:00

    From MSFT:

    New builds with the fix have started rolling out for some channels:

    Current Channel: 16.13801.21092

    Current Channel (Preview): 16.0.14729.20170

    Semi-Annual Channel (Preview): 16.0.14326.20272

    Semi-Annual Channel: 16.0.13801.21092

    Semi-Annual Channel (Extended): 16.0.13127.21846

    For anyone who has seen the issue on one of these channels, if you have the opportunity, please Update Now (it may not happen automatically) to get the updated version and validate that it addresses the issue.

    Was this answer helpful?

    0 comments
  5. Anonymous
    2021-12-17T13:23:29+00:00

    Tested Semi-Annual Channel: 16.0.13801.21092, but still problems...

    Was this answer helpful?

    0 comments