Prev: how to hide print button in ReportViewer Toolbar
Next: NULL Parameter in Data Driven Subscription
From: Rich on 29 Jun 2006 11:40
Hi all,

We've started having problems with our SSRS 2005 reports in the last
few weeks, whereby users get the following error when they try to
access reports: "The selected report is not ready for viewing. The
report is still being rendered or a report snapshot is not available.
(rsReportNotReady)". If they click View Report again, the report
displays fine.

I've checked the logs, and the error listed is:
"e ERROR: Throwing
Microsoft.ReportingServices.Diagnostics.Utilities.ReportNotReadyException:
The selected report is not ready for viewing. The report is still being
rendered or a report snapshot is not available., ;
Info:
Microsoft.ReportingServices.Diagnostics.Utilities.ReportNotReadyException:
The selected report is not ready for viewing. The report is still being
rendered or a report snapshot is not available."

Our users normally access our reports through SharePoint, so initially
I thought the problem was with the webpart. The error does not occur
when we access the reports directly through the
http://<servername>/Reports link.

But I've been able to duplicate the issue outside of SharePoint, by
using the http://<servername>/reportserver link, so I think the problem
may be with the ReportViewer.aspx page.

The reports had been working fine for months, but only started acting
up in the last few weeks. I am able to reproduce the problem on our
production, test/qa, and development boxes. Our development box is
running SP1 currently, but not our test/qa and production boxes.

All of our reports are parameterized, adhoc style reports, so we do not
use snapshots.

I have a feeling that our Systems Engineering group may have changed a
server, proxy or network setting that could inadvertantly be causing
this problem, but I have no idea what to even point to.

Any help would be greatly appreciated.

From: Rich on 7 Jul 2006 16:28
Any ideas???

I've tried numerous workarounds, and so far, nothing is working.


Rich wrote:
> Hi all,
>
> We've started having problems with our SSRS 2005 reports in the last
> few weeks, whereby users get the following error when they try to
> access reports: "The selected report is not ready for viewing. The
> report is still being rendered or a report snapshot is not available.
> (rsReportNotReady)". If they click View Report again, the report
> displays fine.
>
> I've checked the logs, and the error listed is:
> "e ERROR: Throwing
> Microsoft.ReportingServices.Diagnostics.Utilities.ReportNotReadyException:
> The selected report is not ready for viewing. The report is still being
> rendered or a report snapshot is not available., ;
> Info:
> Microsoft.ReportingServices.Diagnostics.Utilities.ReportNotReadyException:
> The selected report is not ready for viewing. The report is still being
> rendered or a report snapshot is not available."
>
> Our users normally access our reports through SharePoint, so initially
> I thought the problem was with the webpart. The error does not occur
> when we access the reports directly through the
> http://<servername>/Reports link.
>
> But I've been able to duplicate the issue outside of SharePoint, by
> using the http://<servername>/reportserver link, so I think the problem
> may be with the ReportViewer.aspx page.
>
> The reports had been working fine for months, but only started acting
> up in the last few weeks. I am able to reproduce the problem on our
> production, test/qa, and development boxes. Our development box is
> running SP1 currently, but not our test/qa and production boxes.
>
> All of our reports are parameterized, adhoc style reports, so we do not
> use snapshots.
>
> I have a feeling that our Systems Engineering group may have changed a
> server, proxy or network setting that could inadvertantly be causing
> this problem, but I have no idea what to even point to.
>
> Any help would be greatly appreciated.

From: Rich on 21 Jul 2006 17:57
Well, it looks like I fixed our problem. It seems that there must be a
bug in SSRS, in that if you do not cache the reports, this problem
occurs with user promted parameterized reports.

To fix it, I did the following:

In SQL Server Management Studio, connect to each Reporting Services
instance, navigate to each report.

Right click each report, select the Execution page, and make sure
"Render this report with the most recent data" and "Cache the report.
Expire after (minutes)" is checked.

Rich

 | 
Pages: 1
Prev: how to hide print button in ReportViewer Toolbar
Next: NULL Parameter in Data Driven Subscription