SQL Backup Error: Cannot access resource

When trying to browse a different server’s backup folders; If you try to access a network share through the Folder Browser or File Browser through the SQL Backup GUI and you are using a Windows authenticated user account, you may encounter the following error:

Cannot access resource. Check that you have the correct permissions to view this resource.

This is caused by Windows security restrictions that prevent a "double hop" of credentials from one server to another, using an intermediate server.

There are two possible fixes for this issue. We recommend the first.

1. Browsing network shares using the SQL Backup Agent service startup account

This solution is only available if the SQL Backup Agent service startup account (the account the service logs on as) is a domain account with access to the network resources.

The SQL Backup Agent service is created for each SQL Server instance when you install the SQL Backup Pro server components. The name of the service is in the format: SQL Backup Agent-<instance name> You can change the account the service uses to log on from the Windows Services panel.

To allow a user to browse a network share using the SQL Backup Agent service startup account:

  • Open Registry Editor (regedit.exe).
  • Navigate to the following registry key:

     HKEY_LOCAL_MACHINE\SOFTWARE\Red Gate\SQLBackup\BackupSettingsGlobal\<instance>

     where <instance> is the SQL Server you are connecting to, through the SQL Backup Pro GUI

  • Create a Multi-String Value entry called BrowsingUserList.
  • In the Value data, list each Windows user that you want to allow to browse the network shares using the SQL Backup Agent service startup account. Each user should be listed on a new line in the format DOMAIN\USER.

2. Changing the Windows authentication method to Kerberos

Since the second fix can involve making changes to Active Directory authentication methods, we would recommend the first fix.

For more information on this error and the second method for a solution please visit our documentation:


Was this article helpful?

1 out of 4 found this helpful
Have more questions? Submit a request