CODEWITHSUNDEEP
sql-serverreporting-servicesssrs-2014
Neil P
Neil P

Reputation: 3190

SSRS data driven subscriptions - Error: Subreport could not be shown

Using SSRS 2014 enterprise.

I have a data driven subscription that should be generating about 500 reports as PDF files.

These reports are made up of a master report and two sub reports. If I view the report through the web portal, it works perfectly. The master report takes one parameter that is also passed to the sub reports, this parameter is data driven from a database query.

When I run the report through the subscription, all the expected PDF reports are generaeted on the file share, however they all only contain the below error, once for every sub report.

Error: Subreport could not be shown

The SSRS execution log doesnt contain anything helpful, only the below:

ERROR: Throwing Microsoft.ReportingServices.ReportProcessing.ReportProcessingException: , Microsoft.ReportingServices.ReportProcessing.ReportProcessingException: Exception of type 'Microsoft.ReportingServices.ReportProcessing.ReportProcessingException' was thrown.;

Upvotes: 0

Views: 1471

Answers (1)

Neil P
Neil P

Reputation: 3190

This was caused by an error in the subreport. It appears that these errors are not passed up through to the logs, they are caught and then rethrown as an error that happened in the subreport, destroying any chance of identifying the error!

Running just the content of the subreport through a data driven subscription, I discovered the following:

When ran from a subscription, the job would hang, but log the following to the SSRS ReportServerService log (in the SSRS program files folder)

ERROR: Throwing Microsoft.ReportingServices.Diagnostics.Utilities.HasUserProfileDependenciesException: , Microsoft.ReportingServices.Diagnostics.Utilities.HasUserProfileDependenciesException: The '/REPORTNAME' report or shared dataset has user profile dependencies and cannot be run unattended.;

This error means that there was something in the report that had a dependency on the user.

The subreport was using the following parameter to log to a trace table:

[&UserID]

Replacing this with a value that is not user dependant value allowed the subscription to run.

Upvotes: 0

Related Questions