Hello all: I have a main report with subreports. I set everything up correctly (parameters, data sources, etc). The sub report renders just fine in BIDS environment and on the Report Server. But when I try to Preview the main report in BIDS, I get the "Error: Subreport could not be shown." Funny thing is that the whole set WILL in fact render just fine when run from any of three Report Server environments (DEV, QA, and PROD), but generate errors when Previewed in BIDS. The fact that it renders fine on the server tells me that the Parameters are specified correctly, and that the name is specifiec correctly. I have tried everything I could from various posts: sub report width needs to be smaller than the main report - did not fix it sub report parameters should be designed with NO default values - did not fix it copy and past the subreport as an rdlc file - did not fix it Any ideas out there? Thanks in advanceTodd C - MSCTS SQL Server 2005 - Please mark posts as answered where appropriate.

Hi Todd C, Are there any warnings received when you run the main report in Business Intelligence Development Studio (BIDS)? If so, please post the complete warning message for further analysis. Additionally, are you using a remote report server? If so, are there any date/time type parameters? If the report server and your computer use different date/time format, such an error may occur when passing the date/time parameters to the subreport. Meanwhile, I also suggest that you try to update the SQL Server Reporting Services in your test environment. For the SQL Server versions information, please see: http://sqlserverbuilds.blogspot.com/ If you have any questions, please feel free to ask. Regards, Mike Yin TechNet Subscriber Support If you are TechNet Subscription user and have any feedback on our support quality, please send your feedback here.

I was able to figure out what was happening and get it resolved. Both main and sub-reports are based off MDX queries, and have a Date parameter that comes from a Shared Dataset (aslo an MDX query that gets Dimension members from the Date dimension). So in the Sub report, its Date parameter had Available Values coming from a dataset, and a Default Value of something like "[Date].[Year-Qtr-Month Hierarchy].&[2012].&[May]" The solution was to remove the Shared dataset from the subs, and to NOT use Available Values section of the Parameter dialog box. Todd C - MSCTS SQL Server 2005 - Please mark posts as answered where appropriate.

I was able to figure out what was happening and get it resolved. Both main and sub-reports are based off MDX queries, and have a Date parameter that comes from a Shared Dataset (aslo an MDX query that gets Dimension members from the Date dimension). So in the Sub report, its Date parameter had Available Values coming from a dataset, and a Default Value of something like "[Date].[Year-Qtr-Month Hierarchy].&[2012].&[May]" The solution was to remove the Shared dataset from the subs, and to NOT use Available Values section of the Parameter dialog box. Todd C - MSCTS SQL Server 2005 - Please mark posts as answered where appropriate.

Hi Todd C, Thanks for posting and sharing your answer. I am glad to hear that you have resolved the issue by removing the parameter available values that are obtained from a shared dataset. Please mark your answer so that this thread can help more people who face the same issue. Regards, Mike Yin TechNet Subscriber Support If you are TechNet Subscription user and have any feedback on our support quality, please send your feedback here.

Mike: As a former frequent responder in the SSIS forum, I never really liked to see people mark their OWN posts as an answer. But I see your point, that if someone is searching on a topic, they can see related posts and if it have been answered or not.Todd C - MSCTS SQL Server 2005 - Please mark posts as answered where appropriate.