querstring problem

hi all,
i have a report that i call like this:
http://servername/ReportServer/Pages/ReportViewer.aspx?/Reports/ApplicationsOverviewByTheme&rs:Command=Render&rc:Parameters=false&organ_pkey=2
this works fine.
as soon as i add another parameter to the end, like so:
http://servername/ReportServer/Pages/ReportViewer.aspx?/Reports/ApplicationsOverviewByTheme&rs:Command=Render&rc:Parameters=false&organ_pkey=2&wuser_uid=IHJ8907X1A
it blows up and gives me errors:
Reporting Services Erro
----
For more information about this error navigate to the report server on the
local server machine, or enable remote error
----
SQL Server Reporting Services
the organ_pkey parameter IS used as a report parameter, the wuser_uid is NOT
used currently in the report at all - but we want to keep it for
futureproofability though.
furthermore, how actually do i "enable remote errors" ?
thanks.
t.Seems like you can't just add a parameter name that doesn't exist in the
report. You could create a parameter in the report, called wuser, make it
not prompt the user and allow it to be null and blank. You make it not
prompt the user by just leaving the "Prompt" field blank.
Kaisa M. Lindahl Lervik
"taz" <taz@.discussions.microsoft.com> wrote in message
news:14BA863F-331C-42A3-8260-8C061E268AC8@.microsoft.com...
> hi all,
> i have a report that i call like this:
> http://servername/ReportServer/Pages/ReportViewer.aspx?/Reports/ApplicationsOverviewByTheme&rs:Command=Render&rc:Parameters=false&organ_pkey=2
> this works fine.
> as soon as i add another parameter to the end, like so:
> http://servername/ReportServer/Pages/ReportViewer.aspx?/Reports/ApplicationsOverviewByTheme&rs:Command=Render&rc:Parameters=false&organ_pkey=2&wuser_uid=IHJ8907X1A
> it blows up and gives me errors:
> Reporting Services Error
> ----
> For more information about this error navigate to the report server on the
> local server machine, or enable remote errors
> ----
> SQL Server Reporting Services
>
> the organ_pkey parameter IS used as a report parameter, the wuser_uid is
> NOT
> used currently in the report at all - but we want to keep it for
> futureproofability though.
> furthermore, how actually do i "enable remote errors" ?
> thanks.
> t.
>sql