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
    2022-01-21T22:21:08+00:00

    There are different channels, which use different versions.

    Current Channel is currently using Version 2112, and Build 14729.20260 is the latest build, and it has the full fix.

    Semi-Annual Channel is using Version 2108, Build 14326.20738 is the latest build, and it has the full fix.

    Prior to January update, Semi-Annual Channel was on Version 2102, and the full fix has not been released for that version.

    The build number under About Access where it says 'for Microsoft 365 MSO' is not the version number for Access, and isn't relevant here.

    If you have any machines still using Version 2102, they don't have the full fix.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2022-01-23T01:54:37+00:00

    Shane, I'm on Semi Annual Enterprise and have been using 20738 since it was released with no problems. When I check for updates tonight, I am reverting back to 21092. Is this intentional, is there anything you can tell us about the reason for the regression?

    Was 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
    2022-01-24T05:23:01+00:00

    If you are on Semi Annual Channel, you should be getting Version 2108, Build 14326.20738, that is the current build and has the full fix.

    By build 21092, I assume you mean you got Version 2102, Build 13801.21092, which is the most recent version for Version 2102, but as indicated here, Error in Access when opening a database on a network file share (microsoft.com), has only the first partial fix.

    Can you try updating again, and see if it brings you back to Version 2108, Build 14326.20738, in case there was some issue with the update process?

    Shane Groff

    Was this answer helpful?

    0 comments
  5. Anonymous
    2022-01-24T11:04:35+00:00

    Correct, I am on Semi Annual Channel. When checking for updates, prior to January 22, I was getting 14326.20738. Then when I checked for updates on January 22, I got 13801.21092. Now when I check for updates on January 24, I'm getting 14326.20738 again.

    The whole time I've been using the Office Deployment Tool with this: <Updates Enabled="TRUE" Channel="SemiAnnual" TargetVersion="" />

    So as of today, the version is back to what I expected. It's just strange that on January 22 it reverted back to 13801.21092.

    Was this answer helpful?

    0 comments