Share via

“The database has been placed in a state by user ‘Admin’ on machine ‘LOCALHOST’ that prevents it from being opened or locked.”

Wright Kenia 40 Reputation points
2026-01-24T05:55:07.24+00:00

Hi, I’m experiencing an issue with Microsoft Access and would appreciate some guidance. I’m using Microsoft Access 365 (Microsoft 365 Apps for enterprise) on Windows 11 Pro, working with an .accdb database stored on my local machine.

The issue occurs when I try to open a form that is bound to a query, but Access freezes for several seconds and then displays an error. The exact error message is: “The database has been placed in a state by user ‘Admin’ on machine ‘LOCALHOST’ that prevents it from being opened or locked.”

Microsoft 365 and Office | Access | For business | Other
0 comments

Answer accepted by question author

Dora-T 13,745 Reputation points Microsoft External Staff Moderator
2026-01-24T07:50:32.2833333+00:00

Hi @Wright Kenia

Thank you for reaching out to the Microsoft Q&A Forum and sharing your issue. 

Based on my research, this error usually indicates that Access believes the database is already in use or has been left in a locked state, even though it is stored locally. This can happen if a lock file remains, or if the database was not closed properly. 

Here are some steps you can try: 

1.Close Access completely 

-Make sure all Access windows are closed. 

-Open Task Manager and check whether MSACCESS.EXE is still running. 

-If it is, select it and choose End Task. 

2.Delete the lock file (.laccdb) 

-Go to the folder where the database is stored. 

-Look for a file with the same name as your database but ending in .laccdb. 

-Delete it, then try opening the database again. 

3.Restart your computer  

If you do not see MSACCESS.EXE running but the lock persists, restarting Windows can clear any remaining background sessions. 

After rebooting, try deleting the lock file again and opening the database. 

4.Compact and Repair the database 

-Open Access > Database Tools > Compact and Repair Database 

This can fix corruption or leftover locking issues. 

5.Check if the form/query is causing the freeze 

-Try opening the query directly in Datasheet View 

-If it also freezes, the query may be too complex or referencing a missing table/link. 

6.Test in a new blank database 

-Import the affected form/query into a new database file 

This helps confirm whether the issue is file-level corruption. 

7.Ensure the database is not opened in Exclusive mode 

File > Options > Client Settings > Advanced > Default Open Mode should normally be Shared 

I hope this helps. 

If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment". 

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Was this answer helpful?

0 comments

2 additional answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Carl Walker 0 Reputation points
    2026-02-10T10:36:50.97+00:00

    Usually it happens after a crash, someone opening the DB in Design View, or bad multi-user setup. Make sure everyone closes the database, then delete the leftover .laccdb / .ldb lock file if it’s still there. Also double-check that the database is split (front end / back end) and that all users have full read/write permissions on the backend folder, that setup prevents this lock-state issue most of the time.

    Was this answer helpful?

    0 comments
  2. George Hepworth 22,855 Reputation points Volunteer Moderator
    2026-01-24T15:04:10.0933333+00:00

    We need additional information.

    Is this a database you created, or is it a database created by someone else for your use?

    Is the database shared with anyone else? From the description, it appears that you do have an accdb on your computer.

    However, that doesn't preclude the possibility that this accdb is the "Front End" accdb in which the interface objects (forms and reports) are located and that the data is located on a shared network location in a "Back End" accdb to be shared with other users.

    I raise this question because the error might suggest that the problem resides in such a Back End accdb which others have opened exclusively.

    Also, please confirm that the name reported "LOCALHOST" refers to the computer you use. It may just be a coincidence that the name "LOCALHOST" refers to the local computer that a program is running on, typically associated with the IP address 127.0.0.1. It is used to access network services running on the same machine without needing an external network connection. That raises the possibility that some additional network activity is involved. And that, in turn, raises the question above about a second, Back End accdb.

    It's more likely that you could get this kind of error in that scenario.

    Thanks for providing additional context to help us offer you suggestions.

    Was this answer helpful?

    0 comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.