I'm getting the error: "An attempt was made to set a report parameter 'ABC_PrintCopyOriginal_TH"' that is not defined in this report. when I try to view my reports in a web browser. I'm executing this reports through a menu with button code. When the page comes up I get the error.
I have added manually ABC_PrintCopyOriginal_TH in parameter level report design. this ABC_PrintCopyOriginal_TH was enum which I used to print filter expression based on menu item button. eg: when click on original menu button it needs to print original on report design if etc copy button wise versa....
Can you please help me how to resolve this?
Are you using an SSRS Reporting server to host your reports? If so, have you deployed the report and tried restarting the Reporting server after the changes?
What editor are you using to edit the .rdl files?
If deploying and restarting the server doesn't help there is probably a typo in your .rdl file somewhere since you manually add stuff. Try using Report Builder and check if that gives you more info about the issue.
I'm currently working on a Java Project to generate the XML of an SSRS Report, without using Report Builder (this project writes the XML of a report to an .rdl file).
I'm stuck on the Datasets part of my project. I provide a query to my Dataset and when I open my report, my Dataset is created but the fields are not displayed.
And When I execute my report, I have an error that tells me a problem with my DataSet.
This error means "An error occured during local report processing".
The solution I found is to go to "properties of the dataset" and click on "Refresh fields".
"Actualiser les champs" means "Refresh Fields".
The list of fields is displayed and I can run my report without any problem.
So I wanted to know if it was possible to have the fields update automatically without going through the properties of the DataSet and without the action of the user ?
I have already tried to edit the "AutoRefresh" value of the report, without success.
Is there an option to make this happen or some way to run the script behind the button ?
P.S : I need to generate a hundred of Dataset, so my click on "refresh fields" of each Dataset is not viable.
Thank you for any help you can give me.
I added a new report to my SSRS project by right-clicking the Reports folder and selecting "Add New Report"
After selecting a sahred data source, the Report Wizard dialog displayed. I clicked through to the query page and added my custom SQL. The next page allowed me to determine where the fields returned from the query would be located in the report.
However, whether I put all of the fields in the "Displayed Fields" box or all but one, putting that one in the "Group" box, I cannot proceed - the "Finish" button is not active.
What must I do to be able to move on and proceed with the wizardification of the report?
I can reproduce this by attempting to create a matrix report. Matrix reports require at least 1 column,1 row and 1 detail line. Tabular reports don't have this requirement.
I have changed the SSRS report names in my reporting server projects. I have four reports and four linked reports in this projects. The linked reports are being called by an action setup on a column value where the parameters are being passed to the linked reports. After renaming all the report names I have made similar changes in the Action property in order direct the parameters to the changed report name. I have also saved the changes and re-built the project and have not got any errors. All the four main reports are working fine but the linked reports are trowing the following error while running the reports using preview options in MS Visual Studio 2010
An error occurred during local report processing. Object reference not set to an instance of an object.
I have deployed this to my local report server and on browser I getting the following error
The item '/Unit Reports/OLDREPORTNAME' cannot be found. (rsItemNotFound)
Here you can see that it is still trying to locate it to the old report name not the new changed one.
I have clean, built and deployed the project several times but still getting these errors
Please let me know if I need to make changes in any other files to avoid this error.
Thanks
Within the .rdl search for "OLDREPORTNAME" and replace with "NEWREPORTNAME"...
Take a backup first :-)
I have noticed that when I implement the Action property on the report field, it automatically set-up the same Action property of that text box where the field was defined.
I have found that the text box Action property was still pointing to the old report. I have changed text box Action property to point it to the new report and now my linked reports are working absolutely fine.
Thanks
Yogesh
Full error from Preview window in Visual Studio '08 (BIDS): "An error occurred during local report processing. Object reference not set to an instance of an object."
There are no further errors/warnings detailed in the Error List or Output windows.
Background: On this report I am using a table to display a sub-report [x] number of times, dependant on the number of related objects that exist in the SQL database. That is to say that the sub-report is set within one of the cells (the only cell) of the table, in a row that repeats for each item returned in a dataset.
Removing the sub-report allows the master report to compile and run, so I feel the issue is related to the arrangement of the sub-report. If the sub-report only displays once, then the master report compiles and runs fine, it is only when a second instance is required that the issue arises.
When testing the sub-report separately, it compiles and runs when given the parameters for each instance it is being asked to render from the master report. So I can rule out the idea that the data for the second instance is causing it to fail (in some div-by-0 type way).
Given the lack of detail from the error and that the sub-report works on it's own, I do not understand why this is happening.
Does anyone have any ideas for debugging or suggested solutions?
Thanks
Brian
tldr: Master report fails when a sub-report repeats more than once.
I figured out a solution. The sub-report is being passed 4 parameters, one of these had a value referring to the value a table-cell on the master report. Changing this parameter to be the value of the expression that was setting that table-cell fixed the issue. I have no idea why this is a solution, but it is.
In more detail: [table_cell_a] had an expression computing it's value.
[parameter_a] for the sub report was set as "=ReportItems("[table_cell_a]").Value", when I changed the expression for [parameter_a] to mirror the expression for [table_cell_a], everything worked again.
This is messed up, and I can't even begin to understand why it behaves like this. If [table_cell_a] was not being computed before the calls were made to the sub-reports, I could understand. But if that was the case, how come the report worked when there was only one sub-report?
If anyone can provide an explanation, I would be most grateful.
Brian
Brian,
I'm having a similar issue with charts imbedded in a Tablix. I found this article that seems to address the issue, although I have not gotten the server upgraded yet to actually test it:
http://support.microsoft.com/kb/2639301
Hope that helps.
G
I was getting the similar error after changing the names of reports in my project even though I changed all the updated report names in the Action property.
An error occurred during local report processing. Object reference not set to an instance of an object.
I found a solution by running the dataset of linked report providing the parameter values manually.
I am not sure what difference it made by running the dataset of linked report manually but it solved my problem and I am no longer getting this error.
Thanks
Yogi
Just sharing. In my case, it was not a sub-report. I had the same message when I was accessing a drill-through-report. Apparently, at the "Action: Go to report" > "Specify a report:", I have wrongly pasted the full name of the report with the extension. Removing the ".rdl" extension solved my problem.
Addendum: If the drill-through report name is part of an expression then the .rdl extension is necessary for it to work when hosted in SharePoint. That prevents it working in preview mode, as you've found. Solution is to code to avoid having to use an expression for the report name.
Copy the Dataset and Queries.
Create new report or copy paste Tablix to new report. You will not get the error again.
I had to remove the SubReport and add it again. Then it worked.
I had the same error when I changed the name of the report I drilled to. I did change the name in the action expression to the new name via the properties > Action > Go to Report > (...) > Expression, but that apparently didn't take. When I opened the text box > Properties dialog window instead of using the Properties pane, and changed the drilled to report name within that window, it solved my issue.