rsreportnotready
-
Tuesday, March 20, 2007 8:59 PM
Had this problem for a week now. Unable to find a solution. I have tried almost all suggestions.
1. In the Report Properties, under execution tab, selected the option "Render this Report with the Most Recent Data" and also checked "Cache Report.. Expire after (minutes)".
2. Tried ALTER DATABASE ReportServerTempDB
SET ALLOW_SNAPSHOT_ISOLATION OFF;and
ALTER DATABASE ReportServer
SET ALLOW_SNAPSHOT_ISOLATION OFF;3. Applied Service Pack 1.
4. Applied Hot Fix for Service Pack 1.
5. Applied Service Pack 2.
Still having the same issue.
The selected report is not ready for viewing. The report is still being rendered or a report snapshot is not available. (rsReportNotReady)
I am able to run the report from VISUAL STUDIO but not from the localhost/reports . Any help will be greately appreciated.
Thank You
Senthil
All Replies
-
Wednesday, March 21, 2007 1:11 AM
Hello Senthil,
In the report properties execution tab, check the box for 'Create snapshot when the apply button is pressed', then press Apply.
Hope this helps.
Jarret
-
Thursday, March 22, 2007 2:20 PM
Jarret
Thank You. Though we are not using Snapshot for the reports, I applied the change as per your suggestion. Now, I don't get that error but, I am getting a error message box with the following error:
Unable to locate Control: oReportCell
Do you have any information on it. I tried searching through the forums and couldn't get any hit on it.
Thank You
Senthil
-
Monday, April 30, 2007 9:36 AMHye Friends,
I'm also getting the same error, thou' the report is viewable from "http://localhost/reportserver/pages/reportviewer.aspx?/<report>" , but it is not available from "http://localhost/reports....." or from ReportControl that i have inserted in a .ASPX page using VS.net 2005.
Each time i get the message box stating "Unable to locate control: oReportCell".
Any solutions ?????
Thanz ! -
Tuesday, November 13, 2007 6:24 PM
Hi Senthilrd,
I am getting this same error as you had with SRS. Did you manage to find a solution? I would appreciate if you could post the solution.
-
Thursday, November 15, 2007 12:15 PMHi.
I 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)
I hope this helps
Sigtryggur S -
Friday, November 16, 2007 9:51 AM
Hello all,
You might want to try this:
http://blogs.msdn.com/jgalla/archive/2006/08/30/live-reports-and-rsreportnotready-error.aspx
Some customers had configured their RS catalog databases to use Snapshot Isolation, which is incompatible with our session locking mechanisms and may sometimes lead to this issue.
I hope this helps.
Thanks.
-
Tuesday, September 30, 2008 8:46 PMWe had the same error returned to the web browser, but after examining the log files, the error was caused by an access denied error. The report server was not able to access the temp directory. This was a result of a group policy that was pushed onto our servers to make them more secure (which revoked write access in the temp directory for the user the report server was running under).
System.UnauthorizedAccessException: Access to the path 'C:\Program Files\Microsoft SQL Server\MSSQL.1\Reporting Services\RSTempFiles\RSFile_b6d63f4e-cc89-4e55-a8fd-25078bf2bea9' is denied. -
Tuesday, January 12, 2010 10:05 AMThere is one more possibility that causes this error. If the server that is running Reporting Services has low disk space, this error would appear. I solved this issue by deleting some Reporting log files from the server, and the Report started working.
Thanks. -
Thursday, August 19, 2010 1:27 PM
Hi shahs,
Your solution helped me, thanks alot for rocking now...................

