Managing Subscriptions in .NET

Creator QR Code JIS X 0510 in .NET Managing Subscriptions

In Report Manager, click the My Subscriptions link in the top right corner of the browser window. Your screen looks similar to this:

Click the Last Run column to change the sort order of the subscriptions. The first time you click a column to change the sort order, the subscriptions sort in ascending order. Click the column again to reverse the sort order. Right now, only a few subscriptions appear on this page, so the sorting feature is not particularly helpful. However, as you add more subscriptions, you ll find the ability to sort a long list of subscriptions useful. You can sort the subscriptions using any column on this page.You can also use this page to open a report to which a subscription is attached or even the folder in which the report is stored. Click the Edit link to the left of the file share delivery subscription for the Actual Vs Quota report.

13

5 6 7 8

The status for the subscription notes a failure because of the change in the report s use of credentials.

Now you will edit the subscription to execute it one more time. Before it actually executes, you ll change the credentials assigned to the data source to force an error. Click the Select Schedule button. Change the Start Time of the report to 5 minutes from now, and then click the OK button. Type NADirector as both the user name and password, and then click the OK button. Click the Actual Vs Quota report link for the same subscription, click the Properties tab, and then click the Data Sources link. Change the Connect Using option to The Credentials Supplied By The User Running The Report and then click the Apply button. Because a subscription must use stored credentials to execute, choosing this connection option will cause the subscription to fail. After waiting 5 minutes, click the My Subscriptions link. Your screen looks similar to this:

If you have permissions to access the trace log files, you can review the ReportServerService_<timestamp>.log file to get more information related to subscription processing and deliveries. For example, if a data-driven subscription is done processing but includes errors, you can use the log file to investigate the underlying errors. The subscription might have processed just fine, but the delivery extension might not have been able to connect to the mail server to forward the messages. If, for some reason, the mail server might not be available when the Report Server tries to connect, you can configure a certain number of retry attempts. By default, this value is set to three. You can edit the RSReportServer.config file to raise or lower this setting as appropriate for your environment. Many other situations can cause a subscription to fail. Usually the status message or the trace log will indicate what is causing the problem, but in some cases you ll need to peform basic troubleshooting. Here are some options to consider: On the Report Server, make sure the delivery extension has not been removed or disabled. (Always back up the configuration file before making changes!) Check that the ReportServer and the SQLServerAgent services are both running. Make sure the destination server is running either the e-mail server or the target computer with a file share, depending on the delivery extension used. If using file share delivery, confirm that the file share is configured for write access, that the subscription is using the proper credentials, and that the disk is not full. Sometimes the problem can be caused by the report itself. If a subscription uses a snapshot, which itself is based on a schedule, confirm that the snapshot schedule is still active. Changing credentials for the data source to anything other than stored credentials will also cause a subscription to fail. Any modifications to the report definition, such as a parameter name or data type, can also invalidate a subscription. Finally, if the report is too big for the recipient s mailbox, the report will be undeliverable.