I took over report creation/maintenance at a new job. We are using SQL Server 2012 and SSRS 2012. When I try to edit one of the older reports using Report Builder I find I can't even add a comment to some of the code in a dataset without breaking the report. This particular report has 14 parameters and all I have to do is try to add a comment line (never mind change the code) to a dataset and click OK to close the dataset edit it presents this DEFINE QUERY PARAMETERS prompt to verify the parameters. If you click OK then all the fields disappear from under the dataset in the Report Data window and the report doesn't work.
Running the report itself without trying to apply any edits still works fine, it's the editing that breaks it. I can edit other previous reports, it's just this particular report that's showing this behavior.
Finally figured it out after all this time. The SQL for this dataset has at least a dozen IF-THEN statements spread throughout the code, that keep checking for a certain input parameter that was selected. I finally simplified the previous report writer's code into one big IF-THEN-ELSE statement and now the dataset can be edited in Report Builder and Visual Studio with no problem. I'm guessing something changed in Microsoft's SSRS parsing routine between when this report was written in 2018 (where it had no problem with all those IF-THEN statements) and 2020, when the parsing failed but with no helpful error message.
Related
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.
This is a very strange and perplexing problem I have never run across. I am working on an SSRS report that feeds off a database. I use an SSIS extraction package to append data to a table in said database. Everything seemed to work fine until the first time I updated the table. I can see the new data in SSMS, but the report looks like it is only seeing the data I had in there prior to the update. I've restarted Visual Studio, checked the connection string, and checked my dataset queries and I have no clue why the report is doing what it's doing.
If you are editing the report in Visual Studio, yes, it can be overly aggressive about caching the results of queries.
Look in the Solution folder (in file explorer, not Visual Studio) and look for a file with the name of the report, but .data appended, such as Report1.rdl.data.
Delete that file, which you can do while VS is running. Then preview the report again.
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.
Good morning, All.
First let me start off by saying that I'm extremely new at CRM and even after reading umpteen million articles, whitepapers, and blog entries, I still feel completely lost.
I have an instance of Dynamics CRM 2013 On Premise that I'm trying to write custom reports for. Before I realized that all reports had to be done inside of BIDS, I wrote out a beautiful custom Quote inside of SSRS itself. I made sure to use the Filtered Views in my query to the database, and the structure of the query seems sound, but I can't seem to upload the .rdl file into CRM.
I get the error:
Reporting Error
Error occurred while setting the data source for the report
I have two questions:
How do I move this report into CRM without having to fully recreate it in BIDS?
How do I pass the Quote ID from CRM to this report query?
Thanks in advance for all of your help.
Edit: Added Error Message
You Should be able to upload the RDL directly to CRM...
Try creating a really basic report with the same data source and something along the lines of "select top 10 from filteredincident" and upload it.
If it works then you know it's something with your query.
CRM is notorious for giving error messages that don't have enough information, or are at worst misleading. I've seen this error when I accidentally used non filtered tables and a autofilter parameter that was incorrect.
Also take a look at the SSRS server that CRM talks to, if it's misconfigured that may cause an issue as well. You may want to try uploading your report to SSRS and run it from there to ensure that SSRS is working correctly.
I'm pretty new to Reporting Services though I have a lot of experience with Crystal Reports and databases (and MS Access reports if that counts ;-). Anyway, I created simple reporting project in VS2008 using wizard, with simple stored procedure that has 2 options parameters - and since they're optional I do not assign their values. There's data in the dataset's "Preview data" window, but when I run the report it's empty - there're headers/etc but no data.
What can be wrong here? Can it be because I do not assign SP parameters - and if so, how do I do it? And how do I debug such cases "in general"? There's no even "preview" in report designer in VS2008.
Hm, I created report with tables inside, and manually added SP - it worked. But it shows data incorrectly in matrix. When I do the same thing using wizard in Report Builder 2.0 - it works like a charm - report is created, there's a preview, and data is correct in the resulting page. Looks like either VS2008 is broken or I don't understand something in there.