"Could not lock file" with Access build 14701.20248

Anonymous

I had a client today who could not open their shared backend database. The system displayed the error “Could not lock file”.

I determined that Access was trying to open the file in exclusive mode, even though none of the normal methods to open the file exclusively were being applied:

• The File / Options / Client Settings / Advanced / Default open mode was set to Shared

• No command line /excl was being used

• The user had Full Control permissions for the shared folder containing the database

• Creating a new test database opened it exclusively, so that no other user could open it.

• The newly created test database could not be reopened if another user opened it,

• Several other users could simultaneously open the new test database without a problem.

The user had been using the database for normal operations for several days prior to the problem.

The user’s system has updated to build 16.0.14701.20248 today.

All other test users had build 16.0.14701.20226.

I rolled the user's Office installation back to 16.0.14701.20226 by using the Office Deployment Tool https://support.microsoft.com/en-us/topic/how-to-revert-to-an-earlier-version-of-office-2bd5c457-a917-d57e-35a1-f709e3dda841

The problem was solved.

Can anyone else confirm that this problem exists with the latest build of Access?

Neil Sargent

Smart IT Ltd

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

50 answers

Anonymous

2021-12-20T23:01:43+00:00

Note that when you initially create a database, it will be opened exclusively, so you won't be able to open it in a second instance of Access. This isn't related to the bug, it is by design.

If you still see the problem with an existing database file, can you try opening two instances of Access on the same machine that have the new build, and seeing if they can both open the file?

Also do what you can to ensure that no one else (who might not have an updated version) does not have the file open, since it is on a network share.

We have many people reporting that the new build fixes the issue for them, so we'd like to determine why it is not resolving the issue for you.

Shane
Was this answer helpful?

0 comments No comments
Anonymous

2021-12-20T19:06:45+00:00

We still have problem with our network Access files.

Being uncertain about something wrong in our setup did a reproduce the error with a new Access file:

We have two clients updated to "Current Channel Version 2111, build 14701.20262". (Both rebooted to make sure)

Created a new access file on network server and it can only be opened by one at the time.

Gives "Could not use 'xxxxxxxx.accdb>'; file already in use." on the second client. I can repeat the problem with new files and other clients.

Really problematic that it is said to be resolved. It does not seem to be the case.
Was this answer helpful?

0 comments No comments
Anonymous

2021-12-20T14:24:23+00:00

I installed the latest version of the Semi-Annual Preview Channel (Version 2108 Build 14326.20702). According to the patch notes, this should correct the issue with shared Access databases. However, I am still getting the error when I try to open one. It should be noted that we jumped directly from November's patch to the one released on 12/16, skipping Version 2108 Build 14326.20692 altogether.
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-20T00:20:03+00:00

When will the MSI version be fixed? Is only the Click2Run version fixed now?
Was this answer helpful?

1 person found this answer helpful.

0 comments No comments