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.

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?

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.

On a desktop machine we performed the fix on I am showing the following Under Product Information after the fix was installed: For MS Access: : Version 2112 Build 14729.20260 Under About Access it reads: Microsoft® Access® for Microsoft 365 MSO (Version 2112 Build 16.0.14729.20224) 32-bit ) On a machine we have not installed the updates on I show the following Under Product Information on a machine after the December update: For MS Access: : Version 2102 Build 13801.21086 Under About Access it reads: Microsoft® Access® for Microsoft 365 MSO (16.0.13801.21072) 32-bit )

I have two versions and different builds showing on my machine for Access after we pushed out the latest update Under Product Information after the fix was installed: For MS Access shows: Version 2108 Build 14326.20738 Under About Access it reads: Microsoft® Access® for Microsoft 365 MSO (16.0.14326.20702) 32-bit

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

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

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

2022-01-21T21:16:41+00:00

On a desktop machine we performed the fix on I am showing the following

Under Product Information after the fix was installed: For MS Access: : Version 2112 Build 14729.20260

Under About Access it reads: Microsoft® Access® for Microsoft 365 MSO (Version 2112 Build 16.0.14729.20224) 32-bit)

On a machine we have not installed the updates on I show the following

Under Product Information on a machine after the December update: For MS Access: : Version 2102 Build 13801.21086

Under About Access it reads: Microsoft® Access® for Microsoft 365 MSO (16.0.13801.21072) 32-bit)
Was this answer helpful?

0 comments No comments
Anonymous

2022-01-21T21:11:52+00:00

I have two versions and different builds showing on my machine for Access after we pushed out the latest update

Under Product Information after the fix was installed: For MS Access shows: Version 2108 Build 14326.20738

Under About Access it reads: Microsoft® Access® for Microsoft 365 MSO (16.0.14326.20702) 32-bit
Was this answer helpful?

0 comments No comments