SQL Server Error 5120: Unable to Open Physical File - A Complete Guide to Causes, Fixes, and Prevention

Facing SQL Server Error 5120 – Unable to Open Physical File? Learn causes, proven fixes, and expert solutions to resolve access denied and file issues quickly.

SQL Server environments often encounter file access issues, and one of the most common among them is Error 5120 – Unable to Open Physical File. This error typically occurs when SQL Server fails to access database files such as MDF, NDF, or LDF due to permission issues, incorrect file paths, or system-level restrictions.

If not addressed promptly, this error can lead to database inaccessibility, downtime, and potential data loss. In this guide, we’ll break down the causes, troubleshooting methods, and best practices for resolving and preventing SQL Server Error 5120.

What is SQL Server Error 5120?

SQL Server Error 5120 appears when the database engine cannot open a specified physical file. The error message usually looks like:

“Unable to open the physical file ‘file_path’. Operating system error 5: Access is denied.”

This error commonly occurs during:

1. Database attach operations
2. Database restore processes
3. Startup or recovery of a database
4. Accessing database files stored on external drives or network locations

Common Causes of SQL Server Error 5120

Understanding the root cause is critical for applying the right fix. Below are the most common triggers:

1. Insufficient File Permissions

SQL Server service account lacks required access to database files.

2. Incorrect File Path

The file path specified during attach or restore is invalid or inaccessible.

3. File Locked by Another Process

Another application or process is currently using the database file.

4. Corrupted Database Files

Damaged MDF or LDF files may prevent SQL Server from accessing them.

5. SQL Server Service Account Issues

The service account running SQL Server does not have sufficient privileges.

6. Antivirus or Security Restrictions

Security tools may block SQL Server from accessing certain directories.

7. Disk or Storage Issues

Bad sectors, drive failures, or disconnected storage devices can trigger the error.

How to Fix SQL Server Error 5120?

Method 1: Grant Proper File Permissions

Ensure the SQL Server service account has full control over database files.

Steps:

1. Right-click the MDF/LDF file
2. Go to Properties, then Security
3. Add SQL Server service account
4. Grant Full Control

Method 2: Verify File Path

Double-check the file location used in your query.

CREATE DATABASE database_name

ON (FILENAME = 'C:\CorrectPath\file.mdf')

FOR ATTACH;

Ensure:

1. File exists at the location
2. Path is correctly typed
3. No network restrictions

In Case Manual Method Fails

Manual fixes work well for permission or path issues. However, in cases of severe corruption or inaccessible files, these methods may not be sufficient.

Professional Solution Suggestion

A complete repair toolkit like SysTools SQL Server Recovery Manager can help in:

1. Repairing corrupted MDF/NDF files
2. Recovering inaccessible databases
3. Restoring data from SQL backup files without altering original files
4. Handling severe logical and physical corruption in transaction Log files
5. Resetting lost or forgotten SQL Server passwords

Method 3: Run SQL Server as Administrator

Temporarily run SQL Server Management Studio with elevated privileges.

Method 4: Check for File Locks

Use Task Manager or Resource Monitor to identify processes using the file and terminate them if necessary.

Method 5: Move Database Files

Move files to a different directory with proper permissions and retry the operation.

Method 6: Disable Antivirus Temporarily

Some antivirus tools restrict file access. Disable temporarily and test again.

Method 7: Repair Corrupt Database Files

If corruption is suspected, use DBCC CHECKDB:

DBCC CHECKDB ('database_name') WITH NO_INFOMSGS, ALL_ERRORMSGS;

Best Practices to Prevent Error 5120

To avoid encountering this error in the future:

1. Always assign proper permissions to SQL Server service accounts
2. Store database files in secure and accessible locations
3. Regularly monitor disk health and storage systems
4. Avoid abrupt system shutdowns
5. Keep antivirus exclusions for SQL Server directories
6. Maintain regular database backups

Conclusion

SQL Server Error 5120 – Unable to Open Physical File is primarily caused by permission issues, incorrect paths, or file corruption. While many cases can be resolved with simple configuration fixes, complex scenarios may require advanced recovery solutions.

By understanding the root causes and implementing preventive measures, you can ensure smoother database operations and avoid unexpected downtime.