The rule collects the number of scheduled execution failures per minute for entire SSRS Deployment. The rule queries SSRS Catalog database to get the information.
The rule collects the number of scheduled execution failures per minute for entire SSRS Deployment. The rule queries SSRS Catalog database to get the information.
Scheduled executions are logged into RS Catalog Database under ExecutionLogStorage table.
Subscription failures can occur due to variety of causes. Some of the common causes for a subscription failure can be as follows:
SQL Server Agent job is not firing
RS is not processing the subscription events
SMTP is not delivering the emails
File share location is not accessible
The report (or subscription) is invalid
You can find details on troubleshooting a subscription failure in this article: Troubleshoot Reporting Services Subscriptions and Delivery
Name | Description | Default Value |
Enabled | Enables or disables the workflow. | Yes |
Interval (seconds) | The recurring interval of time in seconds in which to run the workflow. | 900 |
Synchronization Time | The synchronization time specified by using a 24-hour format. May be omitted. |
|
Time out for database connection | The workflow will fail and register an event, if it cannot access the database during the specified period. | 200 |
Timeout (seconds) | Specifies the time the workflow is allowed to run before being closed and marked as failed. | 300 |
Target | Microsoft.SQLServer.ReportingServices.Core.DeploymentWatcher |
Category | PerformanceCollection |
Enabled | True |
Alert Generate | False |
Remotable | True |
ID | Module Type | TypeId | RunAs |
---|---|---|---|
DS | DataSource | Microsoft.SQLServer.ReportingServices.Core.DataSource.RsSqlDeploymentMetrics | Microsoft.SQLServer.Core.RunAs.Monitoring |
Mapper | ConditionDetection | System.Performance.DataGenericMapper | Default |
WriteToDB | WriteAction | Microsoft.SystemCenter.CollectPerformanceData | Default |
WriteToDW | WriteAction | Microsoft.SystemCenter.DataWarehouse.PublishPerformanceData | Default |
<Rule ID="Microsoft.SQLServer.ReportingServices.Core.CollectionRule.DeploymentWatcher.ScheduledExecutionFailures" Enabled="true" Target="Microsoft.SQLServer.ReportingServices.Core.DeploymentWatcher" ConfirmDelivery="false" Remotable="true" Priority="Normal" DiscardLevel="100">
<Category>PerformanceCollection</Category>
<DataSources>
<DataSource ID="DS" TypeID="Microsoft.SQLServer.ReportingServices.Core.DataSource.RsSqlDeploymentMetrics" RunAs="SqlCoreLib!Microsoft.SQLServer.Core.RunAs.Monitoring">
<DBMachineName>$Target/Property[Type='Microsoft.SQLServer.ReportingServices.Core.DeploymentWatcher']/DBServerName$</DBMachineName>
<DBInstanceName>$Target/Property[Type='Microsoft.SQLServer.ReportingServices.Core.DeploymentWatcher']/DBInstanceName$</DBInstanceName>
<DBConnectionString>$Target/Property[Type='Microsoft.SQLServer.ReportingServices.Core.DeploymentWatcher']/DBConnectionString$</DBConnectionString>
<DBName>$Target/Property[Type='Microsoft.SQLServer.ReportingServices.Core.DeploymentWatcher']/DBName$</DBName>
<SQLCounterClassName>PerformanceStatisticsBatch</SQLCounterClassName>
<SQLCounterName/>
<SqlTimeoutSeconds>15</SqlTimeoutSeconds>
<TimeoutSeconds>300</TimeoutSeconds>
<IntervalSeconds>900</IntervalSeconds>
<SyncTime/>
</DataSource>
</DataSources>
<ConditionDetection ID="Mapper" TypeID="SystemPerf!System.Performance.DataGenericMapper">
<ObjectName>SQL RS Deployment Watcher</ObjectName>
<CounterName>Scheduled execution failures/min</CounterName>
<InstanceName/>
<Value>$Data/Property[@Name='ScheduledExecutionFailures']$</Value>
</ConditionDetection>
<WriteActions>
<WriteAction ID="WriteToDB" TypeID="SC!Microsoft.SystemCenter.CollectPerformanceData"/>
<WriteAction ID="WriteToDW" TypeID="SCDW!Microsoft.SystemCenter.DataWarehouse.PublishPerformanceData"/>
</WriteActions>
</Rule>