Parameter bug in Service Pack 1

I'm just curious if Microsoft has officially recognized the bug in Service
Pack 1, where attempting to pass a hidden and a prompted variable to a
report generates a Javascript "Object expected" error.
Or is this still being researched? Anyone?
BrianWe are aware of this. It is a bug. It happens when a parameter that you
hide would normally have a null check box. If you can set the parameter to
non-nullable, that will fix the problem. Otherwise, there is no workaround.
--
This posting is provided "AS IS" with no warranties, and confers no rights
"G" <brian.grant@.si-intl-kc.com> wrote in message
news:eJaxcCMdEHA.2752@.TK2MSFTNGP12.phx.gbl...
> I'm just curious if Microsoft has officially recognized the bug in Service
> Pack 1, where attempting to pass a hidden and a prompted variable to a
> report generates a Javascript "Object expected" error.
> Or is this still being researched? Anyone?
> Brian
>|||Finally, confirmation.
Thank you Brian.
"Brian Hartman [MSFT]" <brianhartman@.hotmail.com> wrote in message
news:ub8NqxMdEHA.3988@.tk2msftngp13.phx.gbl...
> We are aware of this. It is a bug. It happens when a parameter that you
> hide would normally have a null check box. If you can set the parameter
to
> non-nullable, that will fix the problem. Otherwise, there is no
workaround.
> --
> This posting is provided "AS IS" with no warranties, and confers no rights
> "G" <brian.grant@.si-intl-kc.com> wrote in message
> news:eJaxcCMdEHA.2752@.TK2MSFTNGP12.phx.gbl...
> > I'm just curious if Microsoft has officially recognized the bug in
Service
> > Pack 1, where attempting to pass a hidden and a prompted variable to a
> > report generates a Javascript "Object expected" error.
> >
> > Or is this still being researched? Anyone?
> >
> > Brian
> >
> >
>|||I have another symptom associated with hidden parameters to report:
Reporting Services does not respond when attempting to view a report that
has both "Prompted Credentials" AND hidden parameters. The only work-around
that I have found is to make all parameters visible (i.e. prompted) when
selecting prompted credentials for the data source.
M
"G" wrote:
> Finally, confirmation.
> Thank you Brian.
> "Brian Hartman [MSFT]" <brianhartman@.hotmail.com> wrote in message
> news:ub8NqxMdEHA.3988@.tk2msftngp13.phx.gbl...
> > We are aware of this. It is a bug. It happens when a parameter that you
> > hide would normally have a null check box. If you can set the parameter
> to
> > non-nullable, that will fix the problem. Otherwise, there is no
> workaround.
> >
> > --
> > This posting is provided "AS IS" with no warranties, and confers no rights
> >
> > "G" <brian.grant@.si-intl-kc.com> wrote in message
> > news:eJaxcCMdEHA.2752@.TK2MSFTNGP12.phx.gbl...
> > > I'm just curious if Microsoft has officially recognized the bug in
> Service
> > > Pack 1, where attempting to pass a hidden and a prompted variable to a
> > > report generates a Javascript "Object expected" error.
> > >
> > > Or is this still being researched? Anyone?
> > >
> > > Brian
> > >
> > >
> >
> >
>
>

Paging

I am getting an "An unexpected error occurred in Report Processing" error
when attempting to navigate to the next page in a report. The first page of
the report comes up in the browser OK but produces the error when clicking on
the "next" arrow. The main report uses a subreport that accepts two
parameters, one of which can be null. The subreport is used to display
subtotals at the 1st and 2nd grouping level. Each report runs fine
standalone and everything works as expected in the designer. The number of
rows returned by the stored procedure is small (29). I have reviewed
recommended log files but nothing stands out. Is there more I can do to
troubleshoot this problem. TIA
DIt apprears that the subreport is the problem as paging works if the
subreport is removed. The subreport has 23 columns and is placed into a
merged cell in the main report, also 23 columns. Are there limitations on
the use of the subreport?
dp
"dp" wrote:
> I am getting an "An unexpected error occurred in Report Processing" error
> when attempting to navigate to the next page in a report. The first page of
> the report comes up in the browser OK but produces the error when clicking on
> the "next" arrow. The main report uses a subreport that accepts two
> parameters, one of which can be null. The subreport is used to display
> subtotals at the 1st and 2nd grouping level. Each report runs fine
> standalone and everything works as expected in the designer. The number of
> rows returned by the stored procedure is small (29). I have reviewed
> recommended log files but nothing stands out. Is there more I can do to
> troubleshoot this problem. TIA
> D