I am trying to determine where in Reporting Services I can go to find out why a report failed on a particular date. I have a particular report subscription that I was unaware had been failing sporadically. The user has given me the dates when the report has failed. I want to be able to look at the history of this particular subscription and note the errors causing the subscription not to go out. How can I go about doing that? Thank you for your help.

You can refer to report's execution log information to check the detail reason of failure, the log is available at this location C:\Program Files\Microsoft SQL Server\MSRS10_50.MSSQLSERVER\Reporting Services\LogFilesPlease remember to mark the replies as answers if they help and unmark them if they provide no help.

You can refer to report's execution log information to check the detail reason of failure, the log is available at this location C:\Program Files\Microsoft SQL Server\MSRS10_50.MSSQLSERVER\Reporting Services\LogFilesPlease remember to mark the replies as answers if they help and unmark them if they provide no help.

It's been some time and I have finally been able to track down the execution logs for our Report Server. Now, I am trying to interpret them. The problem subscription is 1 of 26 different subscriptions for the same report. The other 25 send get delivered via email without any issues. However, this report had been randomly failing about once a week and more recently been failing more. According to the Report Server table named ExecutionLogStorage, the report is never failing. So I looked up the subscription ids for 4 of the reports that do not have any issues being emailed out. I searched for the ids in the logs and found the following information for each subscription: B40913BA-A6BB-43F9-9857-0B80AD9C84AB (Good Report1): schedule!WindowsService_11!a08!11/22/2011-02:30:05:: Creating Time based subscription notification for subscription: ####### notification!WindowsService_11!2390!11/22/2011-02:30:16:: i INFO: Handling subscription ###### to report Report_Name, owner: user_name, delivery extension: Report Server Email. ######## is the subscription id Then I searched for the subscription ID of the faulty subscription and only found the following logs: 32EDEFB9-E35C-4DD4-BF01-2F83718987BB (ProblemReport): library!ReportServer_0-10!204c!11/22/2011-13:52:22:: Call to GetSubscriptionPropertiessAction(########). library!ReportServer_0-10!11f4!11/22/2011-14:43:13:: Call to GetSubscriptionPropertiessAction(########). The interesting thing is the above are logs when the report supposedly delivered ok. Here are the logs on a day that the report failed: 32EDEFB9-E35C-4DD4-BF01-2F83718987BB (ProblemReport): schedule!WindowsService_13!191c!11/23/2011-02:30:11:: Creating Time based subscription notification for subscription: ####### notification!WindowsService_13!be0!11/23/2011-02:30:21:: i INFO: Handling subscription ######## to report report_name, owner: user_name, delivery extension: Report Server Email. library!ReportServer_0-12!c88!11/23/2011-10:06:34:: Call to GetSubscriptionPropertiessAction(##########). What does the GetSubscriptionPropertiessAction() function do? I was wondering if anyone has expertise on interpreting these execution logs.