Each failed subscription lists a reason in the Status column. The most common reasons are grouped below, with how to handle each one.
Server or database errors
These are usually caused by a server or database problem at the time. Rerun the subscription to see if it goes through. If it fails again with the same error, assign the ticket to DBA/NOC to investigate.
- Error: An error occurred within the report server database. This may be due to a connection failure, timeout, or low disk condition within the database.
- Failure sending mail: An error has occurred during report processing.
- Failure sending mail: An error has occurred during report processing. Mail will not be resent.
Selection criteria too large, or invalid/missing values
Reduce the report's selection criteria to a manageable size and rerun the subscription. If the subscription has invalid or missing values, edit it to specify the missing values or fix the invalid ones, then rerun it.
- The thread was being aborted.
- The setting 'Subject' requires a value.
- The subscription contains parameter values that are not valid.
User-cancelled reports
This happens when the user cancels the report while it's processing.
- Failure sending mail: Report processing has been cancelled by the user. Mail will not be resent.
Automatically disabled subscriptions
Subscriptions are disabled automatically to protect the system and prevent one subscription from affecting other users. Maintenance jobs disable a subscription automatically if it runs longer than the maximum allowed time (the timeout threshold), to save system resources.
You receive an email notification when a subscription fails to process. To resolve it, reconfigure the subscription to run as a "Bulk Export" report if applicable, or recreate it as separate, smaller reports.
Also read Disabled report subscriptions - date range changes