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.

Are you using a DFS Namespace, or other means of redirecting from the actual database location to an aliased path/filename?

The fix is available now for MEC: Monthly Enterprise Channel Version 2110, build 14527.20344 Updated two clients to this build, tested on two access files, one older mdb and a newer accdb, both on a shared network drive. At this time, the second user trying to open the database file gets the same error, cannot open. However, now, the lock file is not being deleted. But I still cannot get more than one user to open a database. Access is configured to open in shared mode.

just in case somebody is using on-prem (for Access 2016)... I created the following shutdown script which successfully uninstalled the KB on all my machines in the domain (shutdown script applied by Group Policy). Maybe it's for some help for some other users. If you use Access 2019, you may have to check and edit the reg values *** :: check architecture if %PROCESSOR_ARCHITECTURE%==x86 ( set reg\_root=HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall ) else ( set reg\_root=HKLM\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall ) REM uninstall KB500209 because of laccdb issues rem check if kb is installed reg query "%reg_root%{90160000-0011-0000-0000-0000000FF1CE}_Office16.PROPLUS_{BA36399C-CF0F-4368-8327-7D35302BF0BB}" /v UninstallString if ERRORLEVEL 1 goto EndKB500209 call start /wait msiexec.exe /package {90160000-0011-0000-0000-0000000FF1CE} /uninstall "{BA36399C-CF0F-4368-8327-7D35302BF0BB}" /qb

It is intentional that you cannot use the .laccdb file in a symbolic link directory, because it introduces a potential security risk. This is by design.

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

2021-12-21T19:44:41+00:00

Are you using a DFS Namespace, or other means of redirecting from the actual database location to an aliased path/filename?
Was this answer helpful?

0 comments No comments
Anonymous

2021-12-21T19:30:50+00:00
The fix is available now for MEC:

Monthly Enterprise Channel Version 2110, build 14527.20344
Updated two clients to this build, tested on two access files, one older mdb and a newer accdb, both on a shared network drive. At this time, the second user trying to open the database file gets the same error, cannot open. However, now, the lock file is not being deleted. But I still cannot get more than one user to open a database. Access is configured to open in shared mode.
Was this answer helpful?

1 person found this answer helpful.

0 comments No comments
Anonymous

2021-12-21T16:17:46+00:00
just in case somebody is using on-prem (for Access 2016)...

I created the following shutdown script which successfully uninstalled the KB on all my machines in the domain (shutdown script applied by Group Policy). Maybe it's for some help for some other users. If you use Access 2019, you may have to check and edit the reg values

***

:: check architecture

if %PROCESSOR_ARCHITECTURE%==x86 (
```
set reg\_root=HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall 
```
) else (
```
set reg\_root=HKLM\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall 
```
)

REM uninstall KB500209 because of laccdb issues

rem check if kb is installed

reg query "%reg_root%{90160000-0011-0000-0000-0000000FF1CE}_Office16.PROPLUS_{BA36399C-CF0F-4368-8327-7D35302BF0BB}" /v UninstallString

if ERRORLEVEL 1 goto EndKB500209

call start /wait msiexec.exe /package {90160000-0011-0000-0000-0000000FF1CE} /uninstall "{BA36399C-CF0F-4368-8327-7D35302BF0BB}" /qb
Was this answer helpful?

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

2021-12-21T00:48:19+00:00

It is intentional that you cannot use the .laccdb file in a symbolic link directory, because it introduces a potential security risk. This is by design.
Was this answer helpful?

0 comments No comments