Dynamics Community Forum Thread Details

Hi,

I added nine subscriptions to the SSRS manager in order to generate 9 Reports based on CRM data. These reports will be trigggered every monday night by using an interval of 10 minutes. E.g. 1.00 am, 1.10 am, 1.20 am etc.

Previous monday all reports have been generated. This monday only eight reports have been generated. One failed. The failed report was started at 1.40 am. An exception was written to the log at 1.47 pm:

library!WindowsService_8!c68!04/18/2016-01:47:33:: 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.;
dbcleanup!WindowsService_8!c68!04/18/2016-01:47:33:: e ERROR: Error in CleanOrphanedSnapshots: 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. ---> System.Data.SqlClient.SqlException: Timeout expired.  The timeout period elapsed prior to completion of the operation or the server is not responding.

This is the complete log:

schedule!WindowsService_8!8fc!04/18/2016-01:40:01:: i INFO: Handling Event TimedSubscription with data 3de97bc5-9948-4019-a3cd-39096c5421b3.
library!WindowsService_8!8fc!04/18/2016-01:40:01:: i INFO: Schedule 9f32ae5b-127d-4672-ad8e-c606222d7505 executed at 04/18/2016 01:40:01.
schedule!WindowsService_8!8fc!04/18/2016-01:40:01:: i INFO: Creating Time based subscription notification for subscription: 3de97bc5-9948-4019-a3cd-39096c5421b3
library!WindowsService_8!8fc!04/18/2016-01:40:01:: i INFO: Schedule 9f32ae5b-127d-4672-ad8e-c606222d7505 execution completed at 04/18/2016 01:40:01.
schedule!WindowsService_8!1bd0!04/18/2016-01:40:01:: i INFO: Handling Event DataDrivenSubscription with data 3DE97BC5-9948-4019-A3CD-39096C5421B3.
library!WindowsService_8!23c4!04/18/2016-01:40:01:: i INFO: Handling data-driven subscription 3de97bc5-9948-4019-a3cd-39096c5421b3 to report /CRMLIVE_MSCRM/CustomReports/{3f2c29c2-0cc1-e511-bcb9-005056a1000f}, owner: MOP\CrmAdmin, delivery extension: Report Server FileShare.
library!WindowsService_8!23c4!04/18/2016-01:40:01:: i INFO: Initializing EnableExecutionLogging to 'True'  as specified in Server system properties.
library!WindowsService_8!984!04/18/2016-01:40:01:: i INFO: Initializing EnableExecutionLogging to 'True'  as specified in Server system properties.
notification!WindowsService_8!984!04/18/2016-01:40:01:: i INFO: Handling subscription 3de97bc5-9948-4019-a3cd-39096c5421b3 to report {3f2c29c2-0cc1-e511-bcb9-005056a1000f}, owner: MOP\CrmAdmin, delivery extension: Report Server FileShare.
library!WindowsService_8!984!04/18/2016-01:40:01:: i INFO: RenderForNewSession('/CRMLIVE_MSCRM/CustomReports/{3f2c29c2-0cc1-e511-bcb9-005056a1000f}')
library!WindowsService_8!c68!04/18/2016-01:40:33:: i INFO: Call to CleanBatch()
processing!WindowsService_8!19a4!04/18/2016-01:41:18:: w WARN: Processing Scalability -- Memory Shrink Request Received
processing!WindowsService_8!19a4!04/18/2016-01:41:18:: w WARN: Processing Scalability -- Memory Shrink Request Received
reportrendering!WindowsService_8!19a4!04/18/2016-01:43:54:: w WARN: Pagination Scalability -- Memory Shrink Request Received
excelrenderer!WindowsService_8!19a4!04/18/2016-01:43:54:: w WARN: Rendering Scalability -- Memory Shrink Request Received
library!WindowsService_8!c68!04/18/2016-01:47:33:: 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.;
dbcleanup!WindowsService_8!c68!04/18/2016-01:47:33:: e ERROR: Error in CleanOrphanedSnapshots: 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. ---> System.Data.SqlClient.SqlException: Timeout expired.  The timeout period elapsed prior to completion of the operation or the server is not responding.
library!WindowsService_8!c68!04/18/2016-01:47:33:: i INFO: Cleaned 0 batch records, 0 policies, 1 sessions, 0 cache entries, 0 snapshots, 0 chunks, 0 running jobs, 0 persisted streams, 0 segments, 0 segment mappings, 0 edit sessions.
library!WindowsService_8!c68!04/18/2016-01:47:33:: i INFO: Call to CleanBatch() ends

If I trigger the reports manually in a row, no problems occur.

Does anybody know the reason for this issue? I checked thet imeout settings of the report server, they seemed to be ok. Is it possible that the subscriptions "steal" resources from each other? The exceptions are not very meaningful.

Best regards