The report server can’t connect to its database

Question

I'm trying to configure an instance of SSRS, but with little success.

I've installed SSRS on the server DWHFRONT. It runs under the Network Service credentials. On the Database tab of the Reporting Services Configuration Manager, I've set it up to use a database on DWHBACK, which it created succesfully. The connection uses a domain account DOM\SA_DWH. I've added a Login to the server DWHBACK for DOM\SA_DWH, and I can see that the Reporting Services Manager added the authorisations to the SSRS-databases. The Configuration Manager accepts these connection parameters.

However (after setting up the URLs, Virtual Directories etc) if I visit the URL of DWHFRONT/Reports/, I get an error saying:

The service is not available.

The report server isn’t configured properly. Contact your system administrator to resolve the issue. System administrators: The report server can’t connect to its database because it doesn’t have permission to do so. Use Reporting Services Configuration Manager to update the report server database credentials.

At first I thought it might be an issue because there is noting deployed to the SSRS instance yet. When I try to deploy something however, I get this error in BIDS:

The report server cannot open a connection to the report server database. A connection to the database is required for all requests and processing. ---> Microsoft.ReportingServices.Library.ReportServerDatabaseUnavailableException: The report server cannot open a connection to the report server database. A connection to the database is required for all requests and processing. (Microsoft.ReportingServices.Designer)

Answer 1

1. Check SQL Logs for any error
2. Run SQL Profile on SQL Server to catch any connection/permissions errors
3. Try to re-enter permissions for a domain account
4. Check a domain account is not disabled / locked / password expired
5. Try to run SSRS Service under same AD account that connects Report Server DB.
6. Try to enable also Named Pipes on both servers (protocols and client protocols)
7. Try to delete encryption keys and to re-create them.
8. Try another domain user and check granted permissions in all DBs (ReportServer, ReportServer Temp, msdb), check if DB user in each DB maps to the valid SID)
9. Try to grant SQL server sysadmin permissions for that AD account (temporary).
10. Check SSRS Logs for any errors (it's good if you attach them).
11. Check Event Viewer --> Security --> Failed Audit on SQL Server