If you are still getting the error and are unable to access the database and data, try the following solutions. If any other process uses the database, use the KILL command to kill that process. This command shows more details than sp_who, including all the running system and user processes.Īnother option is to check the activity using SQL Profiler, but consider that SQL Profiler will be deprecated in future versions. This command returns session id (spid) of active connection in an instance of SQL Server. Use the officially documented sp_who or undocumented sp_who2 stored procedure to find any currently running processes or sessions. You can do so by using any of these options:

If it is set to SINGLE_USER mode, you must find and kill any processes using the database. Right-click on the database, click on Options, then navigate to the State section to check your database state. For this, launch SQL Server Management Studio (SSMS) and connect to a server instance. Since the 924 error is associated with a single user connection problem, you must first check if the database you’re trying to access is in SINGLE_USER mode or not.

Alldup file errors