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-23T05:36:31+00:00

    Even with the updated build, using DFS paths will prevent multi-user access. Fow now, you will have to use a direct network path to the database if you want to have multiple instances accessing the same database.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  2. Anonymous
    2021-12-23T13:51:12+00:00

    Even with the updated build, using DFS paths will prevent multi-user access. Fow now, you will have to use a direct network path to the database if you want to have multiple instances accessing the same database.

    Thanks for the clarification Shane. Is there a time frame you're aware of within which this might be sorted? How long is "for now"? I will let them know about this and we'll work something out.

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments
  3. 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

  4. Anonymous
    2021-12-23T17:30:43+00:00

    Even with the updated build, using DFS paths will prevent multi-user access. Fow now, you will have to use a direct network path to the database if you want to have multiple instances accessing the same database.

    Our organization has multiple MS Access databases shared via DFS. DFS being deployed as an enterprise solution to presenting file shares. This patch has been extremely disruptive with the 2nd patch not resolving the issue. How soon can we expect a full resolution?

    Was this answer helpful?

    5 people found this answer helpful.
    0 comments
  5. Anonymous
    2022-01-01T16:13:05+00:00

    This problem seemed to be fixed, but yesterday MS updated my office and again, I am having it.

    Was this answer helpful?

    0 comments