SQL Server Reporting Services is spewing logs - This may be due to a connection failure, timeout or low disk condition within the database.

Lori Cho 0 Reputation points
2024-04-16T21:05:48.3733333+00:00

On SQL Server Reporting Services,

all of a sudden logs are full of :

library!WindowsService_0!16e4!04/16/2024-13:52:26:: e 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.;

There's not an obvious action being taken to correlate to an error.

I will note that I was deleting subscriptions by hand the other day, and did get an error like this at one point in the UI as well. I eventually refreshed and it "cleared".

There's no disk issue (though there will be with how fast these logs are generating). Seemingly reports are generating, and subscriptions running. I did see a solution about orphaned subscriptions. I'm not finding any.

What's a likely reason for this to be constantly spewing?

yes, I've also restarted and rebooted as well. Upon restart these are the lines that exist around when the errors start:

appdomainmanager!DefaultDomain!222c!04/16/2024-13:44:37:: i INFO: SetInitialized AppDomain id '2': initialized = 1

appdomainmanager!WindowsService_0!222c!04/16/2024-13:44:37:: i INFO: Appdomain:2 WindowsService_0 initialized.

library!WindowsService_0!16e4!04/16/2024-13:44:37:: e 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.;

schedule!WindowsService_0!16e4!04/16/2024-13:44:38:: i INFO: Schedule (bfe088d7-50ed-4203-90df-2433ce80ebf3) not present, being added.

library!WindowsService_0!16e4!04/16/2024-13:44:38:: e 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.;

library!WindowsService_0!16e4!04/16/2024-13:44:38:: e 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.;

I will note that the line about the Schedule exists on every restart. INFO: Schedule (bfe088d7-50ed-4203-90df-2433ce80ebf3) not present, being added.

SQL Server Reporting Services
SQL Server Reporting Services
A SQL Server technology that supports the creation, management, and delivery of both traditional, paper-oriented reports and interactive, web-based reports.
2,801 questions
0 comments

5 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Deleted

    This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

    Comments have been turned off. Learn more

  2. ZoeHui-MSFT 33,051 Reputation points
    2024-04-17T01:50:36.12+00:00

    Hi @Lori Cho，

    Have you done any change such as migrate the database or agent job before the error occurred?

    Reporting Services uses a predefined database role called RSExecRole to grant report server permissions to the report server database.

    Timeout or low disk condition within the database

    You may also check your report server database's property to see if has been set to Auto close.

    User's image Regards，

    Zoe Hui

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

    0 comments
  3. Lori Cho 0 Reputation points
    2024-04-17T15:27:16.87+00:00

    Thanks for responding. No there was no maintenance like a migration. Only maintenance was me on the UI deleting some old subscriptions by hand. This service really hasn't been touched for months.

    I did check the RSExecRole as I saw it referenced in various forums. I see it on the ReportServer with many permissions. If there's any specific perm, I could check that.

    Checked the Database Properties and Auto Close = False.

    User's image

    What's wild is just how MUCH it's spewing. Roughly 33M every couple of minutes. It's not like it's happening for a singular report. Is there anyway to get more logs that would tell me what is being attempted that may be triggering?

    0 comments
  4. ZoeHui-MSFT 33,051 Reputation points
    2024-04-18T06:16:36.1966667+00:00

    Hi @Lori Cho，

    Could you please check the Windows Event logs and application logs to see if there are any useful information?

    And please check the jobs via agent job to see if the subscription has not been deleted.

    User's image

    0 comments
  5. Lori Cho 0 Reputation points
    2024-04-18T15:24:23.1433333+00:00

    The item does not exist in the listed jobs.

    Looked through system logs. Potentially notable:

    Not quite as frequent as the log in the description, but I do see these in System Logs

    • A fatal error occurred while creating a TLS client credential. The internal error state is 10013. (Started before this issue did)

    In the Application logs, see these Informational ones from the Windows Error Reporting Service. Also not the same frequency:

    • Fault bucket , type 0 Event Name: WindowsUpdateFailure3 Response: Not available Cab Id: 0 <shortened for brevity>
    0 comments