"Could not lock file" with Access build 14701.20248

Thanks for your reply.
Ok. No need other then to make sure that 14701.20262 is installed. Which it is.

I have already examined that the process is running 16.0.14701.20262 (C:\Program Files\Microsoft Office\root\Office16\MSACCESS.EXE) and it's from 19th dec.

I have now examined acecore.dll (C:\Program Files\Microsoft Office\root\vfs\ProgramFilesCommonX64\Microsoft Shared\OFFICE16)

and it's also 16.0.14701.20262.

In that folder are the following also files updated on 19th dec:
csi.dll, (acecore.dll), mso.dll, fltldr.exe, Mso50win32client.dll, Mso40UIwin32client.dll, Mso30win32client.dll, Mso20win32client.dll, OLicenseHeartbeat.exe, msowercrash.dll, msoshext.dll and Mso98win32client.dll.

I have asked the IT department to roll back over christmas atleast, but they said it is updating automatically. I asked them if it is not possible to pause the updates. So I have put the immediate problem in their hands and I focus on to get it to work with 14701.20262.

Unfortunatly do I not have any more ideas to try/test. (Other than ask IT to roll back, which I prefer to avoid for me to make sure 14701.20262 works)

You should not have to do anything other than get the latest updated, which for Current Channel is 14701.20262. You do have to ensure that all instances of Access have been updated, but if you were using multiple instances on the same machine and still see the problem that must not be the problem for you.

Can you confirm that the File version on your copy of acecore.dll is 16.0.14701.20262, just to make sure the update applied properly? (The path to this file should be C:\Program Files\Microsoft Office\root\vfs\ProgramFilesCommonX64\Microsoft Shared\OFFICE16, for 64-bit Office, or C:\Program Files (x86)\Microsoft Office\root\vfs\ProgramFilesCommonX86\Microsoft Shared\OFFICE16 for 32-bit Office)

If this is urgent for you, you should be able to roll back to the previous version (Version 2110), temporarily.

Hi All

We had the same problem with our system . . 20 + PCs with several that were updated causing a lockout.

On Monday AUS time . . i did a windows update and everything went back to normal.

So - if you still having an issue - maybe look for latest updates rather than doing any roll-backs.

cheers for now

Hope everyone has a great Xmas . . :-)

PaulG

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

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.