June 24, 2008 at 4:36 pm
When I attempt to run a particular RS 2005 Service Pack 2 report that has two parameters, the report works fine through the report designer. It also works okay if I make the parameters user selected, through report manager. However, if I run the report with a default value, and not user selectable but hidden, then the report displays but it doesn't use the parameter to obtain any data. The report is blank except for labels. This is just the preliminary problem actually. The point of doing this is to then use a Url through an application call to run the report with a parameter passed to it. When we try to run the report through the Url, we get a "Parameter is missing a value." message.
Anyone else run across this problem? Any solutions?
June 24, 2008 at 5:46 pm
G'day mate,
I'm not sure of your specific problem, but one place to maybe get a more verbose error might be:
C:\Program Files\Microsoft SQL Server\MSSQL\Reporting Services\LogFiles
I am trying to work my way through a similar problem and it has given me a clue where to look next, maybe it can do the same for you 🙂
- Damien
June 25, 2008 at 7:28 am
While setting default value of parameters consider two things:
1. If its integer then use =Value (here Value means any default value)
2. If its string then use ="value" (here Value means any default value)
Try it... 😛
June 25, 2008 at 8:46 am
Hari,
It doesn't help. Actually, I just want to default to null. I am finding that the problem is having available values coming from a query. If I take out the queries data set for available values then I can pass the parameter. It's really strange because I have a different report that works nearly identically and it works.
aktikt
June 25, 2008 at 11:10 pm
Hi,
"Parameter is missing a value." message displayed only when your parameter is not having any value in deployed report.
If you will set it NULL by default, it'll create problem because it is hidden parameter and you are not able to change the value from Default to some other required value.
If its not a hidden parameter then probably you can change the parameter value manully at run time.
So always set accurate vaue By Default for any hidden value.
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply