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.

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 ?

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.

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!

Look at https://www.devhut.net/microsoft-office-uninstall-an-update/ although the title says Uninstall, the same process is used to update to a specific build. Short version: Open a Command Prompt (as an administrator) and then change into the folder that houses the officec2rclient.exe. So, in the Command Prompt, a concrete example might be: cd C:\Program Files\Common Files\Microsoft Shared\ClickToRun officec2rclient.exe /update user updatetoversion=16.0.14827.20088

I am running Access in Office365 - in Access it says: Version 2201 Build 14827.20158 Since this morning, I have issues with Access backend files being left in a locked state. The two most recent Windows Updates are from January 13 (KB5009543 and KB5008876)- and my Access application worked yesterday. It appears to be related to OneDrive. All my files are on OneDrive. Any clue on what exactly to do? Like - where exactly to find a patch - or which update to uninstall?

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-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-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-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-25T09:23:41+00:00
Look at https://www.devhut.net/microsoft-office-uninstall-an-update/ although the title says Uninstall, the same process is used to update to a specific build.

Short version:

Open a Command Prompt (as an administrator) and then change into the folder that houses the officec2rclient.exe. So, in the Command Prompt, a concrete example might be:
```
cd C:\Program Files\Common Files\Microsoft Shared\ClickToRun
officec2rclient.exe /update user updatetoversion=16.0.14827.20088
```
Was this answer helpful?

0 comments No comments
Anonymous

2022-02-03T15:03:26+00:00

I am running Access in Office365 - in Access it says: Version 2201 Build 14827.20158

Since this morning, I have issues with Access backend files being left in a locked state.

The two most recent Windows Updates are from January 13 (KB5009543 and KB5008876)- and my Access application worked yesterday. It appears to be related to OneDrive. All my files are on OneDrive.

Any clue on what exactly to do?

Like - where exactly to find a patch - or which update to uninstall?
Was this answer helpful?

0 comments No comments