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: 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). Use DAO to OpenDatabase for shared (non-exclusive) access. Error 3050 (“Could not lock file.”) is thrown and the database is not opened. 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.

Hi Shane. This is my last update. Release notes for Office for Windows Desktop (Current Channel (Preview) builds) Last updated: January 12th, 2022 January 12, 2022 Version 2201 (Build 14827.20088 ) I have tried to find the option to force an update, but I do not have the option. I am an individual person. Please help as this is causing problem with my workflow!

Version 2108, Build 14326.20702 does have the partial fix, and if that makes things work for you, then you should be OK staying there for now. However, the current build for Semi-Annual Enterprise Channel (Preview), should be Version 2108, Build 14326.20738. If you update, or your organization updates, that is the build that you should get, so I'm not sure why they would have updated to the older build.

So, it looks like my organization upgraded to the following over the weekend: Version 2108, Build 14326.20702 Semi-Annual Enterprise Channel (Preview) Before, it was just the Semi-Annual Enterprise Channel. Not sure why the change to Preview and what it means. Looking at that chart on this page , it looks like that is one of the fixes for the Preview Channel, but not the full fix. However, I've tested Access this morning and this seems to have fixed the problem! It allows multiple users and locking file acts normally. Maybe they'll eventually upgrade to the build with the full fix (14326.20738), but either way, Version 2108 seems to work. Shane ... is it safe to stick to this build since it seems to work? Or should I ask my IT department to move to build 20738 ?

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.

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

Lock File Problems with Access 16.0.13801.21086

Anonymous

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:

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).
Use DAO to OpenDatabase for shared (non-exclusive) access. Error 3050 (“Could not lock file.”) is thrown and the database is not opened.
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.

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

Anonymous

2022-01-25T08:03:20+00:00

Hi Shane.

This is my last update.

Release notes for Office for Windows Desktop (Current Channel (Preview) builds)

Last updated: January 12th, 2022

January 12, 2022

Version 2201 (Build 14827.20088 )

I have tried to find the option to force an update, but I do not have the option. I am an individual person.

Please help as this is causing problem with my workflow!
Was this answer helpful?

0 comments No comments
Anonymous

2022-01-24T15:09:39+00:00

Version 2108, Build 14326.20702 does have the partial fix, and if that makes things work for you, then you should be OK staying there for now.

However, the current build for Semi-Annual Enterprise Channel (Preview), should be Version 2108, Build 14326.20738. If you update, or your organization updates, that is the build that you should get, so I'm not sure why they would have updated to the older build.
Was this answer helpful?

0 comments No comments
Anonymous

2022-01-24T14:25:03+00:00

So, it looks like my organization upgraded to the following over the weekend:

Version 2108, Build 14326.20702 Semi-Annual Enterprise Channel (Preview)

Before, it was just the Semi-Annual Enterprise Channel. Not sure why the change to Preview and what it means. Looking at that chart on this page, it looks like that is one of the fixes for the Preview Channel, but not the full fix.

However, I've tested Access this morning and this seems to have fixed the problem! It allows multiple users and locking file acts normally.

Maybe they'll eventually upgrade to the build with the full fix (14326.20738), but either way, Version 2108 seems to work.

Shane ... is it safe to stick to this build since it seems to work? Or should I ask my IT department to move to build 20738 ?
Was this answer helpful?

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