Can't see subreport in the Report Manager

Question

I've been following this tutorial (lesson 6) in order to build and deploy a sample report with an embedded subreport which reads its parameters' values from the parent report. This subreport is embedded in one of the group rows of the report's table, and both share the same datasource. Additionally, detail rows appear collapsed until the user presses the (+) button for each group of data in the table.

The report works great when I preview it at the Business Intelligence Development Studio (by the way, SQL 2005 Express edition) but when I deploy it and try to see in the Report Manager, the subreport is not shown. And, if I press the (+) button, the following message appears:

Some parameters or credentials have not been specified

Does anybody has the slightest idea of what I am doing wrong? Why does it works perfectly in the Report Viewer embedded in Visual Studio but not in the Report Manager web app?

Thanks in advance.

Answer 1

Does the subreport use the same Data Source as the parent report? If not, be sure to check the data source of the subreport to make sure it is correct. Check in Report Manager, not your local copy.

Answer 2

Does the subreport use the same Data Source as the parent report? If not, be sure to check the data source of the subreport to make sure it is correct. Check in Report Manager, not your local copy.

Yes, both report and subreport use the same shared datasource.

Answer 3

I'm beginning to think this could be an issue with the browser. I'm currently using Internet Explorer 8 Beta and I'm also experiencing weird behavior from the Report Manager. I've tried with Google Chrome and Firefox 3 and, although the navigation is not as smooth as I like, the problem seems fixed.

Answer 4

This may or may not be related, but I had a similar problem some time ago (except that in my case the reports were accessed through a custom web page) and it turned out we had an older version of the report viewer control (the version that came with Sql 2005 RTM). After upgrading to the latest version the issue went away.