Record Lock on Database will not go away

I have a Backend Access Data Base, that has an associated Record Lock File, yet noone is logged into the database.  Every time I try to delete it it says another user has the DB. However I do not see who that person is.

How do I find out who has it locked.
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Sometimes, when you are sure that everyone is really out of the database, if you open it and close it, Access will naturally delete the lock file - assuming that the person opening/closing has delete permission to the folder holding the database.  Remember, all users require Creat, Read, Update, Delete permission to the folder because the first person to open the file causes Access to CREATE the lock file and the last person to close the app causes Access to DELETE the lock file.  In between, everyone needs to have permission to read and update so Access can properly track actions in the lock file.

If nothing else works, you may have to reboot the server where the lock file persists in order to convince DOS to let it go.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
seamus9909Author Commented:
i have rebooted the server and still it shows being locked?
John TsioumprisSoftware & Systems EngineerCommented:
Check your antivirus on both your machine and server....disable them and try again...
Active Protection takes the fight to cryptojacking

While there were several headline-grabbing ransomware attacks during in 2017, another big threat started appearing at the same time that didn’t get the same coverage – illicit cryptomining.

Did you try deleting the lock file after the reboot?  Rebooting won't delete the file but it should kill what ever process was locking it.
seamus9909Author Commented:
Hi Yes i did try and delete it after reboot
seamus9909Author Commented:
Thank you that worked
It's a little pesky and most network admins are loath to reboot a server if they don't have to.  You just have to convince them to do it but in your case, you were lucky enough to have the power to do it yourself.
seamus9909Author Commented:
Yes  now on to my bigger issues
Jim Dettman (Microsoft MVP/ EE MVE)President / OwnerCommented:
Couple other comments:

1. A LDB will also get left behind if a user abnormally disconnects from the DB.  As Pat said, all users should have delete priv's.   Check this and then if the LDB continues to get left behind, you've got other issues.

2. It is possible to release the lock on the LDB without rebooting the server.   If it's a network connection, you just have to close the session.  That's done from Computer Managernt, Files and Shares.

  If the lock is from a local logon, then you would need to use something like process Explorer that can find the handle and kill it.

It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft Access

From novice to tech pro — start learning today.