Greetings!
I am using SSRS with MS SQL Server 2008 R2, which has the new feature of supporting shared datasets.
First, I created my shared dataset, and made sure that it worked correctly and had a good connection. That worked great.
Second, I created a new report (Let's call it "ReportSub"), and I had it use my shared dataset. The report works great.
Third, I created another report (Let's call is "ReportMain"), and I put a subreport object into the report and associated it with "ReportSub". Doesn't work. Instead, I get this error:
Data retrieval failed for the subreport, 'ReportSub', located at: /ReportSub. Please check the log files for more information.
Any ideas of what the problem may be? It will work if I use an embedded dataset, but I really need to use a shared dataset.
Thanks,
Currently, there is no way to Preview the subreport with shared datasource/dataset in BIDS.
Link: http://social.msdn.microsoft.com/Forums/en/sqlreportingservices/thread/74e51434-1d14-4fb1-9b1c-1a394c187b2f
I had this problem for "preview" only. As soon as I deploy this to Reporting Service server it starts working fine.
I had the same problem when previewing my MainReport. The SubReport preview works fine, but the MainReport preview produces the error "Data retrieval failed for the subreport".
The solution is not use shared dataset in the SubReport but an embedded daaset!
I have also observed that some changes in the SubReport are not taken over by the MainReport. So I had to close and repoen the project again.
I was experiencing this problem even after deploying. I discovered that I was prompting for datasource credentials in the subreport, but not in the main report.
After I made them both the same (prompt for credentials or set them both to use the provided credentials), the problem went away and I was able to preview.
Related
I have a really bizarre one here...I have developed and deployed to my back end system a launchpad application that currently works OK. Part of this application is a report that, based on certain filters, returns a table and a chart (see snapshot below).
After finishing deployment next step is configuring the app so it runs from the launchpad within the SAP portal. Not familiar with the portal, another colleague undertook the task, application is now running from within the portal as well. With one exception - the chart above is not visible (see 2nd snapshot below).
Noticing the "No Data" message and NO exception in the Chrome debugger, thought as a good idea to debug the OData methods in the back end. To my big surprise, found out that while filters pass to the method just fine both for table and chart (two different entities but almost identical and accepting exactly the same parameters) when running outside portal, when running from within (the portal) parameters "get lost" on their way to the chart entity - no parameters for the chart method. See snapshots below and pay attention to the IT_FILTER_SELECT_OPTIONS at the bottom right.
Outside portal (parameter table filled)
Within Portal (parameter table empty)
Furthermore, the filter table passed to both OData tables is common, you can see the code underneath - just two lines: one for table and one for chart binding.
Closing with a clarification. Mentioned above that there are no errors in the debugger when calling the back end methods. There are actually a couple of them but they take place during the initialization of the app and do not seem to affect anything else in the app, which aside a set of reports has a lot of data operations (dialogs, tables etc), everything else works fine. These errors can be seen below.
Does this situation ring any bells to anyone?
Thanks in advance
Issue solved, it was a deployment issue...
I have a legacy system that has a CMS server set up to generate Crystal Reports all from the same database. Users will input the required parameters in a front end application, which then passes it to the CMS to generate the report in a CrystalReportViewer.jsp page. The report titles as shown in both the CMC console and InfoView is as follows:
PersonnelDetailsA
PersonnelDetailsB
PersonnelDetailsC
After a recent update to the application (which did not touch on the Crystal Report functionality at all), users reported that they were unable to generate a report for PersonnelDetailsB (A and C were both working fine). The stated error message that they got was
Report source could not be retrieved from the state object
After some googling and trial and error on our development setup, I figured out that the error was caused by the CMS not being able to find the report requested, so my immediate, and actually only, hypothesis was that the report name my application passed to the CMS was wrong (the only way I've managed to reproduce the error). So I went and verified it in the production InfoView.
Turns out I was dead wrong. All the report names are correct.
As far as I know, nothing has changed with the set up of the CMS in production. The reports worked fine prior to our application update and I've verified that we did not make any changes in our application that would affect the Crystal Report functionality. In fact all the reports work perfectly in our development setup. Yet something clearly went wrong when we deployed to production. All 3 reports are in the same folder, and yet one of them cannot be found even when the correct report name is provided.
What am I missing here? What other way would cause the CMS to throw that specific error beside not being able to find the report in question?
I have a main report that runs multiple sub-reports. One of my sub reports runs perfectly fine in Preview, but when I deploy the report and run it from the browser, i simply get:
Error: Subreport could not be shown.
I've done some research and I am still not sure what the issue is. I've tried it in different browsers, my data sources for both the main report and sub report use the same shared data sources. And the main report and the parameters seem to pass fine (since it works in preview, I am assuming).
The error doesn't tell me much - has anyone else had this issue? Or any ideas how to debug? Many thanks!
Issue resolved. I needed to deploy my subreport as well, not just build.
Check the parameters of the Sub Report. Correcting them appropriately will make it working.
If you are working with multiples servers, be careful of where the datasets for all the sub reports are pointing to.
I have a report that is taking about 10 minutes to load when opened through the application, but only 2 seconds when opened through VS 2008. There are many other reports which all work fine and I don't know what could be different about this one.
In the application, all of the code to load and setup the report runs fine but when I launch the form that has the viewer on it it displays the form, but hangs for several minutes before the report comes up. It's clear that it's not the query itself that is the problem since it only takes a second to run in VS, and all that is on the form is just the viewer.
After setting up my report into a variable named rDoc, I run the following code:
CrystalReportViewerForm frm = new CrystalReportViewerForm();
frm.CrystalReportViewer.ReportSource = rDoc;
Application.Run(frm);
CrystalReportViewerForm has the viewer control on it, and a public property called CrystalReportViewer that exposes the viewer so the calling code can set the ReportSource before opening the form, as you can see in the code. That is literally all the form consists of. When Application.Run(frm); is run it shows the form and viewer, but the report doesn't load for about 10 minutes.
If anyone else has run into this and solved it please let me know what you did!!
Thanks!
I'll go ahead and post the way I fixed it here in case it helps anyone, but I'd still like to hear if anyone else knows what the problem actually is...
My report was using the built in features of CR to select tables with data expert. I got rid of all the tables and added a command with the sql needed to get the data. This solution would obviously be faster because it doesn't return as much data and the processing is all done in SQL. However, it worked fine the way it was when run through VS so I know that's not the whole of the problem. At least it works now though.
I have a report set up on our test environment which uses a datasource called DEFAULT, which is also the name of the datasource on the client's production server. (Both are ODBC)
The databases in our test environment are called systemname_clientname but on site they are simply systemname.
I modified a report for the client and put it onsite then changed the datasource to the client version (DEFAULT.systemname) but the report keeps throwing errors saying that the object systemname_clientname.dbo.table does not exist.
I can't seem to make it realise that it is no longer pointing at the systemname_clientname database.
This is using Crystal Reports 9 and the reports are launched using an ASP page written in VBScript.
Google has been most unhelpful and my co-workers are equally stumped, can anybody offer some help here?
Database->Set Datasource Location has a bug in Crystal XI at least, maybe other versions.
Select the database and then updating doesn't update the source of every table.
If you expand the properties of each table you will see that it's still pointing at the old data source.
Try updating the data source for each table one by one.
Yes, it is tedious, sorry.