An error occurred within the report server database. This may be due to a connection failure, timeout or low disk condition within the database

An error occurred within the report server database. This may be due to a connection failure, timeout or low disk condition within the database

An error occurred within the report server database. This may be due to a connection failure, timeout or low disk condition within the database

This short blog post helps you troubleshoot the below error message in SQL Server Reporting Services (SSRS):

An error occurred within the report server database. This may be due to a connection failure, timeout or low disk condition within the database. (rsReportServerDatabaseError) Get Online Help For more information about this error navigate to the report server on the local server machine, or enable remote errors.

So, what you can do if you get the above message is:

1. Ensure that SQL Server Reporting Services (SSRS) are up and running.

2. Ensure that the user with which you are accessing the relevant reports has Folder/Report permissions to do so.

3. Ensure that the SSRS instance’s service account (can be found in SQL Server Configuration Manager or SQL Server Reporting Services Configuration Manager) has db_owner access to the respect ReportServer and ReportServerTempDB databases.

If all the above is OK, then you can further troubleshoot using the below steps:

In SQL Server Configuration Manager, navigate to “SQL Server Services”, then right-click on the SQL Server Reporting Service and on the “Advanced” tab, find the Dump Directory path.

Via Windows Explorer, navigate to the the Dump Directory folder (that is actually the location of the SSRS instance’s log files), try to reproduce the problem and then directly open the latest log file. Check the entries in the log file, where in addition to the above message, you will also find more details. For example you might see the additional error message: “The transaction log for database ‘ReportServer’ is full“….

If you indeed find the error about the transaction log, then it is crystal clear that you need to check the database server onto which the ReportServer database is hosted, for disk space issues. In this case, you need to check the drive that hosts the transaction log file for the “ReportServer” database. If you cannot shrink other log files and thus return space back to OS for further use by the transaction log of database “ReportServer”, then you will need to add more space to the disk.

Did you find this article useful and interesting?

Find hundreds of useful SQL Server administration and troubleshooting articles in 9 Times Microsoft Data Platform MVP, Artemakis’ Artemiou eBook: “Administering SQL Server (Second Edition)“.

Check our other related SQL Server Troubleshooting articles.

Check out our latest software releases!

Subscribe to our newsletter and stay up to date!

 

Rate this article: 1 Star2 Stars3 Stars4 Stars5 Stars (1 votes, average: 5.00 out of 5)

Loading...

Reference: SQLNetHub.com (https://www.sqlnethub.com)

© 2018 SQLNetHub

 

Artemakis Artemiou
Artemakis Artemiou is a Senior SQL Server and Software Architect, Author, and a 9 Times Microsoft Data Platform MVP (2009-2018). He has over 15 years of experience in the IT industry in various roles. Artemakis is the founder of SQLNetHub and TechHowTos.com. Artemakis is the creator of the well-known software tools Snippets Generator and DBA Security Advisor. Also, he is the author of many eBooks on SQL Server. Artemakis currently serves as the President of the Cyprus .NET User Group (CDNUG) and the International .NET Association Country Leader for Cyprus (INETA). Artemakis's official website can be found at aartemiou.com.