How to fix Microsoft.ReportingServices.Diagnostics.Utilities.ReportServerStorageException

Question

Issue: ERROR: Throwing Microsoft.ReportingServices.Diagnostics.Utilities.ReportServerStorageException: , An error occurred within the report server database. This may be due to a connection failure, timeout or low disk condition within the database.;

upon restoring from backup the SSRS seems to be working fine except the error above is generating a lot of log files that causes SQL drive to be full within one day.

I'm using SQL Server 2016 standard edition

SCCM custom report was backup using SQL native backup and encryption keys was back up using RSConfig tool.

Service account is a dbo owner and rsexecrole is properly configured.

Answer 1

Hello

Please refer to this link. seems to have reported the same issue you mentioned here

https://social.msdn.microsoft.com/Forums/sqlserver/en-US/37934c15-7128-4130-bb33-509dea58cfea/an-error-occurred-within-the-report-server-database-this-may-be-due-to-a-connection-failure?forum=sqlreportingservices#:~:text=To%20fix%20this%20issue%2C%20I%20suggest%20that%20you,Manager%20to%20recreate%20the%20Report%20Server%20catalog%20databases.

Regards

Javier

Answer 2

Hi,

Thanks very much for your feedback and sharing. We're glad that the issue is gone now. It's appreciated that you could click "Accept Answer" to the helpful reply, this will help other users to search for useful information more quickly. Here's a short summary for the problem.

Problem/Symptom:

The error below is generating a lot of log files that causes SQL drive to be full within one day.

ERROR: Throwing Microsoft.ReportingServices.Diagnostics.Utilities.ReportServerStorageException: , An error occurred within the report server database. This may be due to a connection failure, timeout or low disk condition within the database.;

Solution/Workaround:

It turns out the errors were caused by orphaned subscriptions. After deleting the entries in the [dbo].[subscriptions] and restarted the Report service the error stop.

Thanks again for your time. Have a nice day!

Best regards,

Simon

---

If the response is helpful, please click "Accept Answer" and upvote it.

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Answer 3

Hi,

Thank you very much for your feedback and sharing.

We're glad that the question is solved now. It's appreciated that you could click "Accept Answer" to the helpful answer. It may help others who have similar issue. If you have any questions in future, we warmly welcome you to post in Microsoft Q&A forum again.

Have a nice day!

Best Regards,

Simon

Answer 4

In my case I looked at all the tables in the ReportServer and ReportServerTempDB database. The SessionData table in the ReportServerTempDB database had a problem (Unable to find index entry in index ID 1, of table 933578364, in database 'ReportServerTempDB'). I put the database in single-user mode and ran DBCC CHECKTABLE with repair allow data loss (it's a SessionData table anyway so no problem with data loss) and deleted the existing rows and everything was fine afterward.

Answer 5

In my case I looked at all the tables in the ReportServer and ReportServerTempDB database. The SessionData table in the ReportServerTempDB database had a problem (Unable to find index entry in index ID 1, of table 933578364, in database 'ReportServerTempDB'). I put the database in single-user mode and ran DBCC CHECKTABLE with repair allow data loss (it's a SessionData table anyway so no problem with data loss) and deleted the existing rows and everything was fine afterward.