(rsReportNotReady)The selected report is not ready for viewing. The report is still being rendered or a report snapshot is not available. (rsReportNotReady)
RSS
Beside turing off the snapshot isolation, you may also try the following thread that shares a workaround which may be helpful to you.
had exactly the same problem but have found a solution that works for me.
In IIS Services Manager make sure the page Default.aspx is in the list of default content pages (under documents).
In my case the error was that the Report Manager was trying to render the reports at the reportserver url http://localhost/ReportServer but since the Default.aspx
was not configured as an application serving under that url then one of two errors would be displayed.
If I was rendering a snapshot then I would get the error:
Unable to locate control: oReportCell
and if I was not rendering a snapshot but directly the error was:
The selected report is not ready for viewing. The report is still being rendered or a report snapshot is not available. (rsReportNotReady)
mohanish
Member
11 Points
20 Posts
(rsReportNotReady)The selected report is not ready for viewing. The report is still being render...
May 26, 2008 10:04 AM|LINK
i am getting the error whwn i will access the report through .net report viiewer
through my search on web
i already done the following issues but none works
ALTER DATABASE ReportServer
SET ALLOW_SNAPSHOT_ISOLATION OFF
ALTER DATABASE ReportServer
SET READ_COMMITTED_SNAPSHOT OFF
ALTER DATABASE ReportServerTempDB
SET ALLOW_SNAPSHOT_ISOLATION OFF
ALTER DATABASE ReportServerTempDB
SET READ_COMMITTED_SNAPSHOT OFF
Mohanish Mahajan.
Microsoft Online Community Support
“Please remember to click “Mark as Answer” on the post that helps you. This can be beneficial to other community members reading the thread. ”
Nai-Dong Jin...
All-Star
41630 Points
3558 Posts
Re: (rsReportNotReady)The selected report is not ready for viewing. The report is still being ren...
May 28, 2008 05:10 AM|LINK
Hi,
Beside turing off the snapshot isolation, you may also try the following thread that shares a workaround which may be helpful to you.
Original post:
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1372400&SiteID=1
Thanks.