I have a SSRS Report with six sub-reports. The sub-reports are using the same shared data source which the main report is using.
When I deploy the report and execute, the sub-report place holder shows error: Report cannot be shown.
I thought it could be due to shared data source. Therefore, I created separate shared data source for each sub-report. This works. The report starts showing all the results.
Please let me know what is this issue. Even though it works, I don't want to create separate shared data source for each sub report.
This is a known defect in SSRS 2008. I'm not sure if it has been patched yet, but it has been fixed in SSRS 2012.
As you have found, the workaround is to use separate datasets.
https://connect.microsoft.com/SQLServer/feedback/details/648560/subreport-with-shared-dataset-throws-error
Related
Ok, I have an SSRS report that has 2 subreports in it. One works just fine and the other works in testing but when I publish the report to my AMS platform under their instructions, the subreport comes up saying it can't be found. I can run the report through Visual Studio and it works just fine without a problem and I have rebuilt the entire project a few times and republished but I still keep getting the same error. I know that the publishing is working because I made a change to the main report to expand the subreport area and allow me to see the full error and that published fine. Any reason this would work through Visual Studio but not when published? The report along with the 2 subreports all are in the same directory as well.
Additional note to this. I just went to the master report in Visual Studio and deleted the subreport from it. I then re-added it and gave it a different name. Rebuilt the report and re-uploaded it including the already uploaded sub report and I am getting the same error but the error is referring to the new name I gave the subreport so it picked up the name change but not the actual sub report for some reason
Sometimes SSRS website caches your old report and doesn't get overridden by your new reports. On the SSRS website, try removing all of your reports including the main report. Then re-deploy.
I have around 10 SSRS reports (i.e. 10 .rdl files) and those needs to be exported to one PDF. How can I do this? Do I need to write custom C#.Net code or SSDT 2017 provides any simple feature to export that?
Please note that, all the RDL files has different header and footer, The 1st page has image in it,few pages has both tabular as well as matrix report.
As suggested, I have one main report and I'm adding sub-report one after another (just maintain the sequence)
I searched on MSDN, however, it looks like Microsoft does not have such feature till now OR may be I'm missing something? Or any special setting or .Net code needs to be written?
Note: I have two version of SSDT (2016 and 2017)
You could just create a master report and then put your 10 reports in that as subreports.
If you reports take a parameters then all the parameters will have to be setup in the master report and then passed to the sub report.
Then, just run the master report and export to PDF...
I have a report that consists of two graphs, with two separate datasets. They are overlapped and displayed or hidden based on a parameter on the report.
When tested in Visual Studio the report displays and runs fine (although a warning about overlapping report items is thrown), but when deployed to to our production setting, the report fails and throws an error that the Query failed for the Dataset that is hidden.
For example, datasets are WOs and WOsByAsset. When WOs is selected for display the error is Query Execution Failed for dataset WOsByAsset. When WOsByAsset is selected for display the error is Query Execution Failed for dataset WOs.
I have confirmed that both datasets work in SSMS, no actual errors are presented.
Could the fact that the graphs are overlapping cause this issue? The pattern of the errors appears to indicate that but I'd like any confirmation, or better yet, explanation that anyone may be able to give.
Thanks all for the suggestions.
Problem was of my own making. I had not taken into account that the report runs for each dataset even when the datasets related table was hidden. The report used a multivalue parameter, and by default passed all possible choices within the parameter into the report.
This was causing that dataset to fail, but when I tested the query in ssms I was only passing a single value for which the query ran just fine.
All good here.
I have a SSRS report deployed ina a server. I have to see how the report is collecting data. The datasets and datasources are shared in this case. How do i have to check the query in the shared datasets?
I'm able to locate the shared data source and dataset location in report server but have no options to see what is inside that. Please help
There are two ways i can think of achieving this, First is to Edit in report builder from the drop down, the second is to download and then add it to a projects and open it up there.
This is the scenario.
A report was working fine in SSRS 2005. It has 4 subreports, one of which has two subreports.
The server got upgraded to 2008 (not R2). Now the reports returns
>An error occurred during client rendering.
>An error has occurred during report processing.
>Object reference not set to an instance of an object
After some debugging and playing around, I found that the report works if I remove the subreports. All of them use just one parameter, which is being sent from one of the main dataset fields (userID).
Weird thing is that, testing this same report in another report Server which is 2008 R2, the report works perfectly...
Any hint?
Thanks
I'm in 2015, but same problem. Turned out my report had a space as the last character of its name. Removed that and it worked.
Try changing from a shared Dataset to an embedded Dataset. I say this because after struggling the whole day with this error and resolving it by redoing my drillthrough report which took me about 45 minutes. I just inadvertently recreated this error. This happened when I changed one of my main reports from referencing an embedded dataset to a shared dataset because I did not want to have embedded code if the code was used by multiple reports. Note, this shared dataset is not a stored procedure, the code is inside Visual Studio, I am not sure if this has anything to do with it. Just thought I should mention that. Anyways I resolved this issue by copying the code and reverting back to an embedded dataset and the error was gone.