Msg 3201, Level 16 Cannot open backup device. Operating system error 5(Access is denied.)

Below you can find the solution of the following SQL Server error message:

Msg 3201, Level 16 Cannot open backup device. Operating system error 5(Access is denied.)

Probably you face this error when you try to make SQL Server database backup. It has to be admitted that this error message belongs to the permissions issue on the local disk and user account which is running SQL Server.

Msg 3201, Level 16 Cannot open backup device. Operating system error 5(Access is denied.) – Solution

Here we are going to cover two ways how you can resolve SQL Server error – Msg 3201, Level 16 Cannot open backup device. Operating system error 5(Access is denied.)

Solution 1

To solve this issue, first of all, you need to check under which user accounts your SQL Server services are running.

 

Now it is necessary to give this account full permission

If it doesn’t help or all settings are set correctly check the following solution.

Solution 2
Msg 3201, Level 16 Cannot open backup device. Operating system error 5(Access is denied.)

This issue also can happen if the file is read-only. To fix it open the folder where all SQL Server database backup is stored, and select the one that you need, right-click on it and select “Properties”, uncheck “Read-Only”. Press “OK” to save all new settings.

After you have made all necessary settings configuration, you will be able to make SQL Server database backup.

Msg 3201, Level 16 Cannot open backup device. Operating system error 5(Access is denied.)

9 thoughts on “Msg 3201, Level 16 Cannot open backup device. Operating system error 5(Access is denied.)

  1. This happened to me and the entire issue was that SSMS didn’t have permission to where I had the .bak file stored. Very frustrating.

  2. If this servers to anyone – I tried everything and nothing worked until I found out that somehow in a very mysterious way, the MDF and LDF files were changed to READ ONLY. Changing it back to read and write and setting the database back online with the script ALTER DATABASE DatabaseName SET ONLY fixed my nightmare.

Leave a Reply

Your email address will not be published. Required fields are marked *