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.
How to Resolve the Issue
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 respective 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.
Learn more tips like this! Get the Online Course!
Check our online course titled “Essential SQL Server Administration Tips” (special limited-time discount included in link).
Learn essential hands-on SQL Server Administration tips on SQL Server maintenance, security, performance, integration, error handling and more. Many live demonstrations and downloadable resources included!
Related Error Messages and ways to Resolve them:
- The Database Engine system data directory in the registry is not valid
- .Operating System Error 170 (Requested Resource is in use)
- Rule “Setup account privileges” failed – How to Resolve
- An error occurred in a SQL Server Service Broker/Database Mirroring transport connection endpoint (9642) – How to Resolve
- There is no SQL Server Failover Cluster Available to Join
- Setup failed to start on the remote machine. Check the Task scheduler event log on the remote machine.
- SQL Server 2008 R2 Service Pack Installation Fails – Element not found. (Exception from HRESULT: 0x80070490)
- Could not load file or assembly ‘Microsoft.SqlServer.Smo, Version=10.0.0.0, …
- The operation failed because either the specified cluster node is not the owner of the group, or the node is not a possible owner of the group
- There is not enough space on the disk. (mscorlib)
- A network-related or instance-specific error occurred while establishing a connection to SQL Server
- The conversion of a char data type to a datetime data type resulted in an out-of-range datetime value
- Fix: VS Shell Installation has Failed with Exit Code 1638
- Issue Adding Node to a SQL Server Failover Cluster – Greyed Out Service Account – How to Resolve
- initerrlog: could not open error log file. Operating system error=3 … – How to Resolve It
- Resolve SQL Server CTE Error – Incorrect syntax near ‘)’.
- SQL Server is Terminating Because of Fatal Exception 80000003 – How to Troubleshoot
- An existing History Table cannot be specified with LEDGER=ON – How to Resolve
- … more SQL Server troubleshooting articles
Featured Online Courses:
- AI Essentials: A Beginner’s Guide to Artificial Intelligence
- SQL Server 2022: What’s New – New and Enhanced Features
- Data Management for Beginners – Main Principles
- Introduction to Azure Database for MySQL
- Working with Python on Windows and SQL Server Databases
- Boost SQL Server Database Performance with In-Memory OLTP
- Introduction to Azure SQL Database for Beginners
- Essential SQL Server Administration Tips
- SQL Server Fundamentals – SQL Database for Beginners
- Essential SQL Server Development Tips for SQL Developers
- Introduction to Computer Programming for Beginners
- .NET Programming for Beginners – Windows Forms with C#
- SQL Server 2019: What’s New – New and Enhanced Features
- Entity Framework: Getting Started – Complete Beginners Guide
- A Guide on How to Start and Monetize a Successful Blog
- Data Management for Beginners – Main Principles
Did you find this article useful and interesting?
Subscribe to our newsletter and stay up to date!
Check our other related SQL Server Troubleshooting articles.
Check out our latest software releases!
Rate this article:
Reference: SQLNetHub.com (https://www.sqlnethub.com)
Artemakis Artemiou is a Senior Database and Software Architect, Certified Database, Cloud and AI professional, Author, a 9 Times Microsoft Data Platform MVP (2009-2018). He has over 20 years of experience in the IT industry in various roles. Artemakis is the founder of SQLNetHub. 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. Moreover, Artemakis teaches on Udemy, you can check his courses here.