Manage a subscription

You can view, modify, and delete subscriptions used to deliver Reporting Services reports . You can manage any subscription that you created yourself. If you have Manage Alerts permissions, you can view, modify, or delete any subscription throughout the site. You can only manage one subscription at a time, and you can only access subscription properties through the Manage Subscriptions page of the report.

What do you want to do?

View and modify a subscription

Delete a subscription

View subscription status

View and modify a subscription

  1. If the library is not already open, click its name on the Quick Launch. If the name of your library does not appear, click View All Site Content, and then click the name of your library.

  2. Point to the report.

  3. Click the down arrow, and then click Manage Subcriptions.

  4. Each subscription is identified by the type of delivery. Click the subscription type to view and change the existing properties. For more information about how to specify the properties for different types of deliveries, see Manage a subscription.

Top of Page

Delete a subscription

  1. Point to the report.

  2. Click the down arrow, and then click Manage Subcriptions.

  3. Click the check box next to the subscription, and click Delete.

Top of Page

View subscription status

Subscription status appears on the Manage Subscriptions page. You can also look in the report server log files for more information about report delivery errors. The Manage Subscriptions page shows the event that triggers subscription processing (either a snapshot refresh or a schedule), when the subscription last ran, and whether it succeeded.

The following table provides a list of status indicators and a description of what it means.

New subscription

Appears when you first create the subscription.

Inactive

Appears when a subscription cannot be processed.

Failure sending mail: the transport failed to connect to the server.

Indicates that the report server did not connect to the e-mail server; this message is from the e-mail delivery extension.

File <filename> was written to <path>.

Indicates that the delivery to the file share location was successful; this message is from the file share delivery extension.

An unknown error occurred when writing file.

Indicates that the delivery to the file share location did not succeed; this message is from the file share delivery extension.

Failure connecting to the destination folder, <path>. Verify the destination folder or file share exists.

Indicates that the folder you specified could not be found; this message is from the file share delivery extension.

The file <filename> could not be written to <path>. Attempting to retry.

Indicates that the file could not be updated with a newer version; this message is from the file share delivery extension.

Failure writing file <filename>: <message>

Indicates that the delivery to the file share location did not succeed; this message is from the file share delivery extension.

<custom status messages>

Status messages about delivery success and failure, provided by delivery extensions. If you are using a third-party or custom delivery extension, additional status messages may be provided.

Status messages are updated when the subscription is scheduled to process. If the subscription never occurs (for example, the schedule never runs), the status message will not be updated. Report server administrators can review the reportserverservice_*.log files to determine subscription delivery status. For e-mail delivery, report server log files include a record of processing and deliveries to specific e-mail accounts. The log file does not include information about whether the report was opened, or whether the delivery actually succeeded.

If a subscription cannot be delivered (for example, if the mail server is unavailable), the delivery extension retries the delivery. A configuration setting specifies the number of attempts to make. The default value is three retries. In some cases, the report might have been processed without data (for example, if the data source is offline), in which the report might be delivered without any data.

For report server e-mail, a successful delivery means that there were no errors generated during processing and that the report server connected to the mail server. If the e-mail resulted in an undeliverable message error in the user mailbox, that information will not be included in the log file. For more information about log files, search for "Reporting Services Log Files" in SQL Server Books Online or on MSDN.

Managing inactive sessions

If a subscription becomes inactive, you should either delete it or reactivate it by resolving the underlying conditions that prevent it from being processed. Subscriptions can become inactive if conditions occur that prevent processing. These conditions include:

  • Removing or uninstalling the delivery extension specified in the subscription.

  • Changing credential settings from stored to integrated or prompted values.

  • Changing a parameter name or data type in the report definition and then republishing a report. If a subscription includes a parameter that is no longer valid, the subscription becomes inactive. For more information, see Create a data-driven subscription

  • You modified a model-driven report by adding securing individual items in the model. If a model includes model-item security, you cannot subscribe to a report that uses that model as a data source.

Top of Page

Share Facebook Facebook Twitter Twitter Email Email

Was this information helpful?

Great! Any other feedback?

How can we improve it?

Thank you for your feedback!

×