Could not use ‘path to database.accdb’; file already in use.

[virgilio]

Good Morning,

One of my split databases is throwing this error for all users:

Could not use ‘path to database.accdb’; file already in use.

I see that there is a recent article for a similar issue here: https://support.microsoft.com/en-us/...0-d079a46f5acc


I doubt that my issue is related to an update because I have another split database that I built from the same template, and it is not having issues....although the second unaffected db does not get daily use, and it only has a handful of users.

I have tried so far:

• Using the update feature from within Access to see if there are any updates pending, I got the message that Access is up to date.
• Pulling a fresh Access install image from my internal corporate site
• Tried compact and repair database from a new window. I still get 'file in use' error.

The problem still persists. I am trying now:

• to import the locked database, and if successful I'll redirect the front end files to the new database.

These are really just progress notes, and I'll update this while I troubleshoot this issue. If anyone has any insight I would love to hear it!

Thank you,

Paul

My version is:
MS 365 Semi-Annual Enterprise Channel Version 2102, build 13801.21086

[virgilio]

Update: I can't import the accdb because I get a similar, 'file already in use' message. There was a lock file present when I started working on this, but I deleted it to see if it would unlock like an excel lock file would. Its unfortunate because I could have gotten the users name that created it and gone from there.


Update2: Not sure what changed, but I was able to import the backend file into a new blank database. I'm working on redirecting the split database to a new location now.

[virgilio]

I have server admin access, and I changed the folder permissions from rwx to full access for the users that use this db. The problem went away, not sure if that solved it, or if a user had it locked due to an improper shutdown or whatever, but it is working now.

Thanks for reading.

Paul

[Minty]

It sounds exactly like the bug reported after a office update in the link.
Once a db is opened by a rogue version it stays broken until reopened by a updated version.

Get all the users to update to the latest office version, and the problem should disappear.

[virgilio]

It sounds exactly like the bug reported after a office update in the link.
Once a db is opened by a rogue version it stays broken until reopened by a updated version.

Get all the users to update to the latest office version, and the problem should disappear.

Thanks Minty, I found that changing the folder permissions was not enough, and I issued a message for all users to update their machines.