Can't connect to SQL Server - Could not find stored procedure

Veeam ONE
Last Modified:


Veeam Reporter can't connect to the SQL Server.  Could not find stored procedure 'ProcedureName'.  Veeam Reporter is unable to connect to the database. 


This is caused by lack of permissions during the install.  You can also find a similar error within the Reporter log "schedulingservice.log". 

ERROR 1932 5 EXCEPTION: Cannot open database "VeeamReporter" requested by the login. The login failed.
Login failed for user 'YourUserName'.
ERROR 1932 5 EXCEPTION: Access to the path is denied.
Machine Name:          'YourReporterServer'
IP Address:            'xx.xx.xx.xx'
Current User:          'YourUserName (same as above)'


Per our user guide we require the following permissions.  
Required Permissions 
 - To be able to access SQL backend data, the clients should be members of the Veeam Reporter Administrators or Veeam Reporter Viewers local groups on the Veeam Reporter Server console. To learn more about the user groups, see the Veeam Reporter User Groups section.
 - Make sure that the SQL Server account is granted administrative privileges on both the specified SQL Server instance and on the local machine, as Windows authentication for SQL Server is required.  We Require DBO access when setting up the DB. 

Our user guide can be found here:

We also encourage local admin for the installation to make sure we have the correct permissions to install on top of IIS correctly.

More Information

Once done, you may need to run through the steps from KB1019 to have SSRS working correctly.

Please be aware that we’re making changes which will restrict access to product updates for users without an active contract.


Rate the quality of this KB article: 
5 out of 5 based on 1 ratings

Couldn't find what you were looking for?

Below you can submit an idea for a new knowledge base article.

Report a typo on this page:

Please select a spelling error or a typo on this page with your mouse and press CTRL + Enter to report this mistake to us. Thank you!

Spelling error in text: