HELP! Parameter default or provided value not valid???

Default value or value provided for the report parameter 'ParamaterName' is
not a valid value. (rsInvalidReportParameter)
I am getting this error when I am trying to run a deployed report. However,
this is driving me mad because in the report preview within VS.Net the report
works fine and i can choose the same parameter settings from within the dev
environment with no problems. I am populating this parameter with a dropdown
with valid values from a sproc (and this I've done a thousand times before).
I can not figure out why it is throwing this error, particularly since it
works perfectly fine in the preview pane. How could it be crappin out when I
deploy it?!?! I am going insane!
-isamuAre you sure it is exactly in the valid values list? The list is case
sensitive. Also, if you are using date / time functions you have to be
careful as they will need to be exact matches.
--
Brian Welcker
Group Program Manager
Microsoft SQL Server Reporting Services
This posting is provided "AS IS" with no warranties, and confers no rights.
"isamu" <isamu@.discussions.microsoft.com> wrote in message
news:D6B6D595-8748-4308-8EF2-2B7F846EB9B5@.microsoft.com...
> Default value or value provided for the report parameter 'ParamaterName'
> is
> not a valid value. (rsInvalidReportParameter)
> I am getting this error when I am trying to run a deployed report.
> However,
> this is driving me mad because in the report preview within VS.Net the
> report
> works fine and i can choose the same parameter settings from within the
> dev
> environment with no problems. I am populating this parameter with a
> dropdown
> with valid values from a sproc (and this I've done a thousand times
> before).
> I can not figure out why it is throwing this error, particularly since it
> works perfectly fine in the preview pane. How could it be crappin out
> when I
> deploy it?!?! I am going insane!
> -isamu|||Hi Brian,
I believe there must've been some buggy stuff going on. What I did to fix
it, on a whim, was change all my variable names in my stored procedure and in
my report, and voila, guess what? it worked. I don't know what could've
been causing it to act so strangely, but I'm just happy it got fixed. Wasted
a good 3 hours of time though.
"Brian Welcker [MSFT]" wrote:
> Are you sure it is exactly in the valid values list? The list is case
> sensitive. Also, if you are using date / time functions you have to be
> careful as they will need to be exact matches.
> --
> Brian Welcker
> Group Program Manager
> Microsoft SQL Server Reporting Services
> This posting is provided "AS IS" with no warranties, and confers no rights.
> "isamu" <isamu@.discussions.microsoft.com> wrote in message
> news:D6B6D595-8748-4308-8EF2-2B7F846EB9B5@.microsoft.com...
> > Default value or value provided for the report parameter 'ParamaterName'
> > is
> > not a valid value. (rsInvalidReportParameter)
> >
> > I am getting this error when I am trying to run a deployed report.
> > However,
> > this is driving me mad because in the report preview within VS.Net the
> > report
> > works fine and i can choose the same parameter settings from within the
> > dev
> > environment with no problems. I am populating this parameter with a
> > dropdown
> > with valid values from a sproc (and this I've done a thousand times
> > before).
> > I can not figure out why it is throwing this error, particularly since it
> > works perfectly fine in the preview pane. How could it be crappin out
> > when I
> > deploy it?!?! I am going insane!
> >
> > -isamu
>
>

Help! 120day Eval to Full version

Ok, several months ago we had an independant contractor install some
financial software on a server I provided. I gave the guy a fully licenced
version of SQL Server and let him do his work.
Unfortunately, it appears he didn't use my copy of SQL, he downloaded and
used the 120 day evaluation version of SQL which has now expired.
Does anyone know if I can simply uninstall the 120 day eval version of SQL,
install the Full version and the copy over the raw data and log files? I am
unable to do a normal backup and restore since the Eval services won't
start.
Please help!
http://support.microsoft.com/default...b;en-us;281574
Take a filesystem backup that includes the database files before you start.
David Portas
SQL Server MVP

Help! 120day Eval to Full version

Ok, several months ago we had an independant contractor install some
financial software on a server I provided. I gave the guy a fully licenced
version of SQL Server and let him do his work.
Unfortunately, it appears he didn't use my copy of SQL, he downloaded and
used the 120 day evaluation version of SQL which has now expired.
Does anyone know if I can simply uninstall the 120 day eval version of SQL,
install the Full version and the copy over the raw data and log files? I am
unable to do a normal backup and restore since the Eval services won't
start.
Please help!http://support.microsoft.com/default.aspx?scid=kb;en-us;281574
Take a filesystem backup that includes the database files before you start.
--
David Portas
SQL Server MVP
--

Help! 120day Eval to Full version

Ok, several months ago we had an independant contractor install some
financial software on a server I provided. I gave the guy a fully licenced
version of SQL Server and let him do his work.
Unfortunately, it appears he didn't use my copy of SQL, he downloaded and
used the 120 day evaluation version of SQL which has now expired.
Does anyone know if I can simply uninstall the 120 day eval version of SQL,
install the Full version and the copy over the raw data and log files? I am
unable to do a normal backup and restore since the Eval services won't
start.
Please help!http://support.microsoft.com/defaul...kb;en-us;281574
Take a filesystem backup that includes the database files before you start.
David Portas
SQL Server MVP
--