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 No comments

98 answers

Sort by: Oldest
  1. Anonymous
    2022-02-03T23:27:27+00:00

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2022-02-04T14:47:21+00:00

    Hi,

    In our case, we are using Microsoft Office Access 2016 (MSI) not the C2R version.

    We have applied latest updates in last weeks and many people using an Access Database on a network shared path inform us they got the same problem where the file is locked out.

    Does someone have a solution ? I searched inside all Office updates for December 2021 and January 2022, but no one seem to talk about something specific with Access. I just see something about security for Excel, ACE, MSO and VBE. Nothing about "Know problems" also.

    I see a very new patch KB5002138 released on Febuary 1st talk about a fix for this issue. Do you tried it ? Someone can confirm this new patch fix this issue ?

    February 1, 2022, update for Office 2016 (KB5002138) (microsoft.com)

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2022-02-04T14:59:22+00:00

    Yes, the February 1st patch for Office 2016 (and Office 2013) should resolve the issue.

    Shane Groff

    Access Engineering

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  4. Anonymous
    2022-02-04T19:48:31+00:00

    Thank you, thank you, thank you. This solved the problems. Tried various things all day to eliminate the problems. KB5002138 would not install. Kept telling me there were no affected products installed. Nothing else I tried worked.

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2022-02-06T04:46:27+00:00

    Note that for Office Click-to-Run installations (all subscription versions are click-to-run, for 2016 perpetual license, you can have either click-to-run or 'MSI' install), Office updates will never be done by a KB, or show up in 'Installed Updates'.

    Installed Updates only shows updates for Windows and MSI-installed applications.

    Was this answer helpful?

    0 comments No comments