"short circuit"/stop auto generating report after clicking report

In Report Manager, using a parameterless report or a report with parameters
that have default values, if one clicks on the report link in a folder, the
report automatically begins generating and then the data is viewable.
Is there any way to prevent the report from being (automatically) generated
so as to require the user to have to click the standard "View Report" button?
A solution might be in the "code"/RDL or perhaps the
"web.config"/RSWebApplication.config. Either is OK. Or anything else.On Jun 27, 1:28 pm, John <J...@.discussions.microsoft.com> wrote:
> In Report Manager, using a parameterless report or a report with parameters
> that have default values, if one clicks on the report link in a folder, the
> report automatically begins generating and then the data is viewable.
> Is there any way to prevent the report from being (automatically) generated
> so as to require the user to have to click the standard "View Report" button?
> A solution might be in the "code"/RDL or perhaps the
> "web.config"/RSWebApplication.config. Either is OK. Or anything else.
The easiest way to accomplish this is, in cases where report
parameters are used, to not have a default set for at least one of the
parameters. Sorry that I could not be of greater assistance.
Regards,
Enrique Martinez
Sr. Software Consultant

"Server Application Unavailable" error on generating PDF reports

Hi,
I'm using ASP.NET with SQL Reporting Service to generate PDF reports.
Most of the time it works well.
But sometimes PDF doesn't come out (esp. if the report is complicated),
with the error message at below.
I use 2 separate servers for Web Server / Reporting Service.
And i suspect a cause is not enough memory?
Thanks,
Azul
-- error message --
Server Application Unavailable
The web application you are attempting to access on this web server is
currently unavailable. Please hit the "Refresh" button in your web browser
to retry your request.
Administrator Note: An error message detailing the cause of this specific
request failure can be found in the application event log of the web server.
Please review this log entry to discover what caused this error to occur.
--.: at
System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(...)
at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(...)
at LYNX.ReportServices.ReportingService.Render(...) in ...
at LYNX.BLL.reportServices.getCustomReport(...) in ...
at LYNX.BLL.reportServices.getPDFReport(...) in ...
at LYNX.Components.Report.RunningAverage.PreviewGraph() in ...
-- end of error message --I found the solution from another post in this newsgroup!
Just downloaded and installed Reporting Services SP1, everything works fine
Although the earlier post talked about long long table,
the solution also applies in my case of generating complicated graphs.
"Azul" <a@.b.c> wrote in message
news:ebcX1F1qEHA.3324@.TK2MSFTNGP15.phx.gbl...
> Hi,
> I'm using ASP.NET with SQL Reporting Service to generate PDF reports.
> Most of the time it works well.
> But sometimes PDF doesn't come out (esp. if the report is complicated),
> with the error message at below.
> I use 2 separate servers for Web Server / Reporting Service.
> And i suspect a cause is not enough memory?
> Thanks,
> Azul
>
> -- error message --
> Server Application Unavailable
> The web application you are attempting to access on this web server is
> currently unavailable. Please hit the "Refresh" button in your web
> browser to retry your request.
> Administrator Note: An error message detailing the cause of this specific
> request failure can be found in the application event log of the web
> server. Please review this log entry to discover what caused this error to
> occur.
> --.: at
> System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(...)
> at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(...)
> at LYNX.ReportServices.ReportingService.Render(...) in ...
> at LYNX.BLL.reportServices.getCustomReport(...) in ...
> at LYNX.BLL.reportServices.getPDFReport(...) in ...
> at LYNX.Components.Report.RunningAverage.PreviewGraph() in ...
> -- end of error message --
>