My problem is with the reporting services for sql2008:
-I add a parameter to an already established report, where I get the names of certain people. RespStep, and it shows on the preview. But when I upload it to the server, it wontshow:
It pretends it´s loading for less than a second and then the report stays in blank.
NOTES:
This behavior happends only when I set the parameter to allow multiple value.
I thought it was a null problem, but the column from where the parameter values come has no nulls and still presents these problems.
I am desperate to know where the problem might be, on the server the data source and everything is well directed. Actually it shows no erros, just wont load anything and keep the page in blank.
just delete the report on server and re-depoly it.after that you can see the parameter in report
Related
I am having this problem where the data being shown in report is different when I deploy it on server. So let's say if I am viewing report by pressing F5 (to debug) or by clicking on "Preview" button on the report in BI Studio the data shown is correct. But when I deploy the same report and when I run it from server such as http://myserver/reports then data shown is incorrect/missing.
For e.g. in some cases it is not showing data for a particular field and there are some number fields which are showing wrong data. I have cleaned the solution, deleted data cache files, rebuilt and deployed like 100 times but no luck.
When I deploy it shows some warning (which I guess I can ignore) but no errors.
I have checked the database by running queries and stored procedures directly and they all return correct data.
How do I fix this issue?
I went to report server and looked at the XML of one of the data set which was creating problem and found out that the new FIELD I have added is not there. Then I tried to deploy that data set and it said Overwrite Dataset property is set to False and that's why it was not deploying and I missed it in messages when it deploys a solution. So I simply set the property to True, deployed it and viola problem is solved.
here is my problem. I had had defalut values in the parameter and displaying of the report - both locally and on webpage went great. Then I wanted to cancel default values and this time only locally I didn't have this value. On the web page the report still displayed content with default parameter values. Why is that? Any ideas? The things I ve done: delete cookies, clean browser cache, I've deleted .data files, I've matched 'always refresh' option in report parameter properties. I would be grateful for support.
Artur
Delete the report completely from Report Manager and re-deploy it, or go into report manager and update the parameters from there. Parameters have been an issue when deploying reports since the dawn of time and I believe it's on purpose actually.
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.
I have an SSRS report that's called up by a page with an ASP.Net ReportViewer object. The report takes parameters for filtering. Right now when the page is first called up, there are default values in the parameters and the viewer just takes off and renders a report with those settings. I thought this would be a nice time-saver, but my client complains that this takes several seconds, so what we want to do now is have it just wait until I hit "View Report" before it tries to render anything.
What's the best approach? Not set defaults to the param's? Set the ShowReportBody to false? Something else? Seems like this should be simple.
Removing the default should will make the report not render. I think that's your only option. And also the simplest.
If some clients like the old behavior, you could provide defaults programatically for certain users. (IE, store a browser cookie that tells your page to provide defaults if they check a "save defaults" checkbox.)
I agree with Tims answer. But in my case NULL (no default) was interpreted as an option in the value list that is beeing loaded for that field from the db. So removing the default value was not the enough. What helped me was setting the default to a value that knowingly not exists on the loaded lookup list, in my case "-1". Some random GUID should do the trick in most cases.
In order to populate a textbox in a page header I am setting up a parameter (as you cannot use Fields) and referencing this in the textbox. The parameter has the Default Value set to "From Query" and the Dataset and Value Field are set accordingly. This works a treat in developmentt in Visual Studio 2005. Once I have deployed the report and am viewing the report in the ReportViewer control I get the error:
"Parameter validation failed. It is not possible to provide valid values for all parameters. (rsParameterError)".
If I remove the parameter, the report works fine.
(Strange thing is that I thought I had this working earlier).
You've probably checked, but has the default value copied over? I've had issues in the past with reporting services where the default values were lost when I moved a report from one box to another.
Thanks for the answer - it has pointed me in the right direction...I have been using my own program to deploy multiple reports so rarely look at them via the Report Manager website. Anyway - I just deployed the report on my home PC and it worked fine....looking at the report in Report Manager on both PCs I found that "Prompt User" on the PC that wasn't working was not ticked...go figure. Ticking this resolved the problem.
I am liking the results that I am getting from SSRS, but I am quite new to it and am finding some things (like this) a little frustating...mouse and keyboard are lucky to not find themselves thrown out the window!