SSRS report subscription ended with an error

Question

I hate to cross post, but I wasn't getting any progress with this on serverfault and there appears to be a lot more activity with regard to reporting services here.

I've created a simple report in SSRS, and then tried my hand out with a data driven subscription. I can verify that the subscription runs on the 'My Subscriptions' page. Under Status it says Done: 1 processed of 1 total; 1 errors.

How do I find out what this error is?

I've looked in the Windows Event Logs and haven't found anything. I also checked the SQL Server Logs and nothing is there either.

Answer 1

You need to look in the "Report Server Execution Log" which is a particular SQL Reporting Services log file.

See Reporting Services Log Files for details.

Answer 2

A bit late to the party, however: Here is where I find my logs when DD subscription fails:

C:\Program Files\Microsoft SQL Server\MSSQL.2\Reporting Services\LogFiles look for filename: ReportServerService*.log with relevant Date Modified

Answer 3

You also can check the Report History, to get this option, put the mouse on top of your report and select manage option from drop-down list of your report, look for the "Report History" on the left options, create a "New Snapshot"

It will show you, the last error know:

Parameter validation failed. It is not possible to provide valid values for all parameters (rsParameterError) 

for this case you need to check the definition of the report, I had an issue with the drop-down list I used to send parameters to the report.

Answer 4

The path under which you can find Report Server Service logs could be different, such as: C:\Program Files\Microsoft SQL Server\MSRS12.MSSQLSERVER\Reporting Services\LogFiles

In this logs you can find errors that happened after generating the report itself. For instance, if the Reporting Services user needs to write the report as a CSV file after a subscription and it lacks the necessary authorization, the only place where you can find the description of the error is in these logs, while the history of the Job connected with the subscription and the Execution Log will tell you that the Report was correctly generated (nothing about saving the report).