Failed Subscriptions

Microsoft.SQLServer.ReportingServices.Core.Monitor.DeploymentWatcher.FailedSubscriptions (UnitMonitor)

The monitor alerts if there are any failed or unknown statuses of report subscriptions or scheduled refresh plans.

Knowledge Base article:

Summary

The monitor raises a Critical alert if the SQL Server Reporting Services or Power BI Report Server has subscriptions or scheduled refresh plans with failed statuses, otherwise, it raises a Warning alert if the statuses are unknown (other than successful and failed). The failed subscription status defines from the 'Subscriptions' table in the 'ReportServer' database based on the following list:

<number> error
Done: <number> errors.
Failure sending mail: the transport failed to connect to the server.
An unknown error occurred when writing file.
Failure connecting to the destination folder, <path>. Verify the destination folder or file share exists.
The file <filename> could not be written to <path>. Attempting to retry.
Failure writing file <filename>: <message>

Causes

Report subscriptions and scheduled refresh plans may fail due to various reasons. For more information on what caused the failure, refer to "My subscriptions" on the reporting portal and "Scheduled refresh" on the Power BI reporting portal, respectively.

Possible reasons:

SMTP server failure for e-mail subscriptions
Windows file share is no longer available
Permissions required to connect to the windows file share are missing
Errors during generating report with data driven subscription
Driver related problems
Memory pressure
Kerberos configuration

Resolutions

Resolve all subscription issues on the portal
Delete not used failing subscriptions

External

Monitor Reporting Services Subscriptions

Troubleshoot scheduled refresh in Power BI Report Server

Overridable Parameters

Name	Description	Default Value
Alert Priority	Defines Alert Priority.	Normal
Alert Severity	Defines Alert Severity.	Match monitor’s health
Enabled	Enables or disables the workflow.	No
Generates Alerts	Defines whether the workflow generates an Alert.	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.
Timeout for database connection (seconds)	The workflow will fail and register an event, if it cannot access the database during the specified period.	15
Timeout (seconds)	Specifies the time the workflow is allowed to run before being closed and marked as failed.	300

Element properties:

Target

Microsoft.SQLServer.ReportingServices.Core.DeploymentWatcher

Parent Monitor

System.Health.PerformanceState

Category

PerformanceHealth

Enabled

False

Alert Generate

True

Alert Severity

MatchMonitorHealth

Alert Priority

Normal

Alert Auto Resolve

True

Monitor Type

Microsoft.SQLServer.ReportingServices.Core.MonitorType.DeploymentWatcher.FailedSubscriptions

Remotable

True

Accessibility

Public

Alert Message

SSRS: Failed Subscriptions

There are {0} failed report subscription(s) and {1} subscription(s) with unknown statuses. For more information on what caused the failure, refer to "My subscriptions" on the reporting portal and "Scheduled refresh" on the Power BI reporting portal, respectively.

RunAs

Default

Source Code:

<UnitMonitor ID="Microsoft.SQLServer.ReportingServices.Core.Monitor.DeploymentWatcher.FailedSubscriptions" Accessibility="Public" Enabled="false" Target="Microsoft.SQLServer.ReportingServices.Core.DeploymentWatcher" ParentMonitorID="Health!System.Health.PerformanceState" Remotable="true" Priority="Normal" TypeID="Microsoft.SQLServer.ReportingServices.Core.MonitorType.DeploymentWatcher.FailedSubscriptions" ConfirmDelivery="false">

  <Category>PerformanceHealth</Category>

  <AlertSettings AlertMessage="Microsoft.SQLServer.ReportingServices.Core.Monitor.DeploymentWatcher.FailedSubscriptions.AlertMessage">

    <AlertOnState>Warning</AlertOnState>

    <AutoResolve>true</AutoResolve>

    <AlertPriority>Normal</AlertPriority>

    <AlertSeverity>MatchMonitorHealth</AlertSeverity>

    <AlertParameters>

      <AlertParameter1>$Data/Context/Property[@Name='SubscriptionsFailed']$</AlertParameter1>

      <AlertParameter2>$Data/Context/Property[@Name='SubscriptionsQuestionable']$</AlertParameter2>

    </AlertParameters>

  </AlertSettings>

  <OperationalStates>

    <OperationalState ID="Critical" MonitorTypeStateID="Critical" HealthState="Error"/>

    <OperationalState ID="Warning" MonitorTypeStateID="Warning" HealthState="Warning"/>

    <OperationalState ID="Healthy" MonitorTypeStateID="Healthy" HealthState="Success"/>

  </OperationalStates>

  <Configuration>

    <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>

    <SqlTimeoutSeconds>15</SqlTimeoutSeconds>

    <TimeoutSeconds>300</TimeoutSeconds>

    <IntervalSeconds>900</IntervalSeconds>

    <SyncTime/>

  </Configuration>

</UnitMonitor>