Error: Subreport could not be shown.

I have a problem with a report containing a number of subreports not running successfully when deployed to the Report Server.

The report runs successfully every time in the VS Development environment, so parameters are all setup correctly and the result is as expected accross the whole report.

No errors or warnings are listed when building or deploying.

All subreports are in the same project as the main report and deployed to the same folder in Report Manager. All the individual subreports run successfully both in VS Studio (Preview Tab) and in the Report Manager portal.

About 50% of the time, the main report runs but shows the error "Subreport could not be shown" for some or all of the subreports.

Running SQL 2005 SP1

Please advise.

Are any of the reports/subreports set to execute on a schedule or are cached?

and do they all have credentials stored?

|||

Thanks for the reply.

None of the reports are cached.|||

Hi,

Can you be experiencing a parameter passing problem? Dates are always a little bit problemetic.

For one of my reports which I use date parameters and the date picker control of the SSRS 2005, the case is just the opposite. It fails on the VS2005 IDE, but runs successfully on the deployed Report Server.

Eralper

http://www.kodyaz.com

|||

Hi,

I don't think this is the issue, because all the subreports are driven by the same 3 parameters from the parent report, 2 of which are using the date picker control and it always works fine in VS. All of the subreports when run individually using the same parameters work fine.

Also, when it returns an error, which is only around half the time, generally the first 1 or 2 of 6 subreports is rendered correctly with the rest showing the error. I have reconciled the data results which are filtered by the parameters (Start & End dates) and the parameters are being correctly applied.

FYI, each subreport takes around 5 minutes to run individually, with the parent report averaging around 15-25 mins.

As a test, I deleted all the reports from the portal, rebuilt the solution and redeployed and everything was working as expected for several runs of the report including a snapshot via a linked report. Unfortunately, the problem has now re-occurred for no apparent reason.

I am begging to suspect resource related / timeout issues or some deloyment related issues but don't really understand why the report would be reliable in VS and not in the portal.

Any help appreciated.

PS: Re your experience, if you haven't already done so, refresh the datasets in VS then try previewing the report.