Reporting Service's 2005 upgrade issue

We have completed the Reporting Service's 2005 upgrade (sept ctp) and have
been testing some of the reports. We are finding reports that work just find
on 2000 (our prod. box) are not working properly in 2005. Is anyone else
having any issues? I will try to explain one of the scenarios in which we
have encountered issues:
Ok. The report has two date dropdowns and three other string dropdowns. The
dates are defaulted but the others are not. One of the three other dropdowns
are greyed out until the other two are selected first. The problem is when we
select either of the first two dropdowns, it displays an error page stating
"Value cannot be null. Parameter name: value ". The 2000 version works
correctly.
Any help is appreciated!It sounds like you run into a known issue with datatime parameters in
combination with multi-value parameters when running them in report manager.
The error happens with CTP September. It is fixed in the final RTM release
of SQL Server 2005.
You should basically just take again a backup of your RS 2000 production
server, and then run the upgrade with the SQL Server 2005 RTM release once
it is available.
-- Robert
This posting is provided "AS IS" with no warranties, and confers no rights.
"clutch" <clutch@.discussions.microsoft.com> wrote in message
news:0A495BC3-1FAE-403B-BF93-156B89C8913F@.microsoft.com...
> We have completed the Reporting Service's 2005 upgrade (sept ctp) and
> have
> been testing some of the reports. We are finding reports that work just
> find
> on 2000 (our prod. box) are not working properly in 2005. Is anyone else
> having any issues? I will try to explain one of the scenarios in which we
> have encountered issues:
> Ok. The report has two date dropdowns and three other string dropdowns.
> The
> dates are defaulted but the others are not. One of the three other
> dropdowns
> are greyed out until the other two are selected first. The problem is when
> we
> select either of the first two dropdowns, it displays an error page
> stating
> "Value cannot be null. Parameter name: value ". The 2000 version works
> correctly.
> Any help is appreciated!|||Thank you Robert!
"Robert Bruckner [MSFT]" wrote:
> It sounds like you run into a known issue with datatime parameters in
> combination with multi-value parameters when running them in report manager.
> The error happens with CTP September. It is fixed in the final RTM release
> of SQL Server 2005.
> You should basically just take again a backup of your RS 2000 production
> server, and then run the upgrade with the SQL Server 2005 RTM release once
> it is available.
> -- Robert
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
> "clutch" <clutch@.discussions.microsoft.com> wrote in message
> news:0A495BC3-1FAE-403B-BF93-156B89C8913F@.microsoft.com...
> > We have completed the Reporting Service's 2005 upgrade (sept ctp) and
> > have
> > been testing some of the reports. We are finding reports that work just
> > find
> > on 2000 (our prod. box) are not working properly in 2005. Is anyone else
> > having any issues? I will try to explain one of the scenarios in which we
> > have encountered issues:
> >
> > Ok. The report has two date dropdowns and three other string dropdowns.
> > The
> > dates are defaulted but the others are not. One of the three other
> > dropdowns
> > are greyed out until the other two are selected first. The problem is when
> > we
> > select either of the first two dropdowns, it displays an error page
> > stating
> > "Value cannot be null. Parameter name: value ". The 2000 version works
> > correctly.
> >
> > Any help is appreciated!
>
>