The monitor raises an alert if the monitoring workflow cannot access the Reporting Services Database Note: This monitor is disabled by default. Please use overrides to enable it when necessary.
The monitor raises an alert if the monitoring workflow cannot access the Reporting Services Database.
This issue may be caused by various factors:
Database server is unreachable due to networking issues in the environment
Physical server hosting the database is running low in resources
Permissions required to connect to the database is missing
Please check if the report server database has been configured properly from within reporting services - http://msdn.microsoft.com/en-us/library/ms159133.aspx
Please proceed with troubleshooting steps to find out why connectivity to a database fails using the following technet articles
http://technet.microsoft.com/en-us/library/ms156468(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. | 900 |
Synchronization Time |
|
|
Time out for database connection | The workflow will fail and register an event if it cannot access the database during specified time interval. | 300 |
Target | Microsoft.SQLServer.2014.ReportingServices.Instance | ||
Parent Monitor | System.Health.AvailabilityState | ||
Category | PerformanceHealth | ||
Enabled | False | ||
Alert Generate | True | ||
Alert Severity | Error | ||
Alert Priority | Normal | ||
Alert Auto Resolve | True | ||
Monitor Type | Microsoft.SQLServer.2014.ReportingServices.MonitorType.Instance.DBConnectionMonitor | ||
Remotable | True | ||
Accessibility | Public | ||
Alert Message |
| ||
RunAs | Default |
<UnitMonitor ID="Microsoft.SQLServer.2014.ReportingServices.UnitMonitor.Instance.DBConnection" Accessibility="Public" Enabled="false" Target="SQLRS!Microsoft.SQLServer.2014.ReportingServices.Instance" ParentMonitorID="SystemHealth!System.Health.AvailabilityState" Remotable="true" Priority="Normal" TypeID="Microsoft.SQLServer.2014.ReportingServices.MonitorType.Instance.DBConnectionMonitor" ConfirmDelivery="false">
<Category>PerformanceHealth</Category>
<AlertSettings AlertMessage="Microsoft.SQLServer.2014.ReportingServices.UnitMonitor.Instance.DBConnection.AlertMessage">
<AlertOnState>Error</AlertOnState>
<AutoResolve>true</AutoResolve>
<AlertPriority>Normal</AlertPriority>
<AlertSeverity>Error</AlertSeverity>
<AlertParameters>
<AlertParameter1>$Data/Context/Property[@Name='Errors']$</AlertParameter1>
</AlertParameters>
</AlertSettings>
<OperationalStates>
<OperationalState ID="Error" MonitorTypeStateID="Error" HealthState="Error"/>
<OperationalState ID="Success" MonitorTypeStateID="Success" HealthState="Success"/>
</OperationalStates>
<Configuration>
<DatabaseServerName>$Target/Property[Type="SQLRS!Microsoft.SQLServer.2014.ReportingServices.Instance"]/DatabaseServerFQDN$</DatabaseServerName>
<DatabaseInstanceName>$Target/Property[Type="SQLRS!Microsoft.SQLServer.2014.ReportingServices.Instance"]/DatabaseServerInstanceName$</DatabaseInstanceName>
<DatabaseName>$Target/Property[Type="SQLRS!Microsoft.SQLServer.2014.ReportingServices.Instance"]/DatabaseName$</DatabaseName>
<TimeOut>300</TimeOut>
<IntervalSeconds>900</IntervalSeconds>
<SyncTime/>
</Configuration>
</UnitMonitor>