The monitor checks if the number of failed report executions per minute does not exceed the threshold expressed as an absolute value. The monitor will raise an alert and change its state only when several consecutive checks have failed. Note: This monitor is disabled by default. Please use overrides to enable it when necessary.
The monitor checks if the number of failed report executions per minute does not exceed the threshold expressed as an absolute value. The monitor will raise an alert and change its state only when several consecutive checks have failed.
Report executions can fail for variety of reasons, some of them can be
Specific design issues with the report
Permissions issues that is prohibiting the report from rendering
SSRS has not been configured correctly
Resource issues like memory, CPU utilization in the server
Connectivity loss between the SSRS server and Catalog database
Connectivity loss between the SSRS server and server from where the data for the report is being pulled
The following technet article walks through various troubleshooting steps that can be taken to identify why a report rendering is failing and how to fix the same
http://technet.microsoft.com/en-us/library/ms156290(v=sql.105).aspx
http://technet.microsoft.com/en-us/library/cc879329(v=sql.105).aspx
http://technet.microsoft.com/en-us/library/cc879330(v=sql.105).aspx
http://technet.microsoft.com/en-us/library/cc879331(v=sql.105).aspx
http://technet.microsoft.com/en-us/library/cc879328(v=sql.105).aspx
http://technet.microsoft.com/en-us/library/cc879334(v=sql.105).aspx
Name | Description | Default Value |
Enabled |
| 0 |
Generates Alerts |
| Yes |
Interval (seconds) | The recurring interval of time in seconds in which to run the workflow. | 300 |
Number of samples | Indicates how many times a measured value should breach a threshold before the state is changed. | 6 |
Synchronization Time |
|
|
Threshold | The monitor checks if the number of failed report executions per minute doesn’t exceed the threshold expressed as an absolute value. | 100 |
Time out for database connection | The workflow will fail and register an event if it cannot access the database during specified time interval. | 200 |
Target | Microsoft.SQLServer.2014.ReportingServices.Instance | ||
Parent Monitor | System.Health.PerformanceState | ||
Category | PerformanceHealth | ||
Enabled | False | ||
Alert Generate | True | ||
Alert Severity | Warning | ||
Alert Priority | Normal | ||
Alert Auto Resolve | True | ||
Monitor Type | Microsoft.SQLServer.2014.ReportingServices.MonitorType.Instance.ReportsExecutionFailure | ||
Remotable | True | ||
Accessibility | Public | ||
Alert Message |
| ||
RunAs | Default |
<UnitMonitor ID="Microsoft.SQLServer.2014.ReportingServices.UnitMonitor.Instance.ReportsExecutionFailure" Accessibility="Public" Enabled="false" Target="SQLRS!Microsoft.SQLServer.2014.ReportingServices.Instance" ParentMonitorID="SystemHealth!System.Health.PerformanceState" Remotable="true" Priority="Normal" TypeID="Microsoft.SQLServer.2014.ReportingServices.MonitorType.Instance.ReportsExecutionFailure" ConfirmDelivery="false">
<Category>PerformanceHealth</Category>
<AlertSettings AlertMessage="Microsoft.SQLServer.2014.ReportingServices.UnitMonitor.Instance.ReportsExecutionFailure.AlertMessage">
<AlertOnState>Warning</AlertOnState>
<AutoResolve>true</AutoResolve>
<AlertPriority>Normal</AlertPriority>
<AlertSeverity>Warning</AlertSeverity>
<AlertParameters>
<AlertParameter1>$Data/Context/Property[@Name='ExecutionFailures']$</AlertParameter1>
</AlertParameters>
</AlertSettings>
<OperationalStates>
<OperationalState ID="Warning" MonitorTypeStateID="Error" HealthState="Warning"/>
<OperationalState ID="Success" MonitorTypeStateID="Success" HealthState="Success"/>
</OperationalStates>
<Configuration>
<Threshold>100</Threshold>
<SampleCount>6</SampleCount>
<IntervalSeconds>300</IntervalSeconds>
<TimeOut>200</TimeOut>
<SyncTime/>
</Configuration>
</UnitMonitor>