"Deepak" <Deepak@discussions.microsoft.com> wrote in message
news:696B6FCF-BE89-46A0-A7C8-8588D4F4C9B9@microsoft.com...
>I have a Report with 2 Date Parameters using Calendar Controls, followed by
>2
> multi-valued (cascading) parameters. This worked fine with the June CTP15.
> After upgrading to the Sept CTP16, if I change the default date
> (yesterday)
> on either calendar control, an error page is generated, with this message:
> "Value cannot be null. Parameter name: value". Of course, this is only
> after
> deploying the report; it still previews fine in Report Designer.
>
> Pressing the "Back" button on the browser returns to the report page, with
> the date selection intact. After selecting the second date, the same thing
> happens, and I have to press "Back" in the browser. However, no errors are
> generated when I now set the multi-select parameters themselves.
>
> I've been able to repro this problem with a trivial report having 2 date
> parameters and 1 multi-select parameter. The behavior isn't identical,
> because the error page is generated only when changing the first date from
> its default. There is also no error when no default dates are configured
> for
> the 2 calendar controls.
>
> Wondering if anyone else has encountered similar quirks?

"Robert Bruckner [MSFT]" wrote:

> Thanks for reporting this. It has been fixed in builds after CTP 16 and will
> work e.g. in the final SQL Server 2005 RTM build.
>
> -- Robert
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
> "Deepak" <Deepak@discussions.microsoft.com> wrote in message
> news:696B6FCF-BE89-46A0-A7C8-8588D4F4C9B9@microsoft.com...
> >I have a Report with 2 Date Parameters using Calendar Controls, followed by
> >2
> > multi-valued (cascading) parameters. This worked fine with the June CTP15.
> > After upgrading to the Sept CTP16, if I change the default date
> > (yesterday)
> > on either calendar control, an error page is generated, with this message:
> > "Value cannot be null. Parameter name: value". Of course, this is only
> > after
> > deploying the report; it still previews fine in Report Designer.
> >
> > Pressing the "Back" button on the browser returns to the report page, with
> > the date selection intact. After selecting the second date, the same thing
> > happens, and I have to press "Back" in the browser. However, no errors are
> > generated when I now set the multi-select parameters themselves.
> >
> > I've been able to repro this problem with a trivial report having 2 date
> > parameters and 1 multi-select parameter. The behavior isn't identical,
> > because the error page is generated only when changing the first date from
> > its default. There is also no error when no default dates are configured
> > for
> > the 2 calendar controls.
> >
> > Wondering if anyone else has encountered similar quirks?
>
>