Hi, I have started getting this error since a week now when I try to schedule a report or change a schedule of a report. An error occurred within the report server database. This may be due to a connection failure, timeout or low disk condition within the database. (rsReportServerDatabaseError) Get Online Help For more information about this error navigate to the report server on the local server machine, or enable remote errors We have SQL Server 2008 installed along with SSRS running on the server. I have never seen this happening before for almost a year now but suddenly it appeared. Along with this, report subscription is also messed up and some report are not been emailed as they have a error like: Failure sending mail: An error occurred within the report server database. This may be due to a connection failure, timeout or low disk condition within the database.Mail will not be resent. I am not sure what caused this but if anyone has any idea of what is going on it will be great. Thanks you for your help. Please reply soooon !!!

Hello, These threads could help: SSRS 2008 crashing when running a report with huge amount of data long running report can not be rendered in Report Manager or through Subscription Sergei

Hi Sergei, Thank you for the links, but none of them helps. I have already increased the session timeout to 3600. When i moved this database to a different server with a different instance of SSRS it works fine. So it means suddenly something happened to my current instance of SSRS or Reporting Database and i am not able to figure out how to solve this issue. Thanks.

I have run into some issues similar to this. I have sharepoint 2010 integration, so your issue is not the same, but you should start by looking closely at your logs.... Enable Verbose logging from Reporting services. You need to restart service after this change - then you should look at the traces. http://support.microsoft.com/kb/2146315 If this doesn't give you enough information, you should trace the sql as well. good luck, Luis

The closest I have to come to solving this issue is by taking a backup of current reporting DB and Temp DB and then restoring them in a New Reporting DB on the same server. Later performing the activity of pointing the SSRS service to the new db. I know this is the not the correct to do but it solved the issue. If any one has a better idea then it will be helpful to me or others in future. Thank you for your inputs.

I just encountered the first problem. I was modifying a schedule to run twice a week from once a week. The report website was somewhat sluggish at the time but not sure if that really matters. After that failed anytime visiting the Schedules page under Site Settings it would fail with the first error you listed. Anyway what I noticed was that 2 Jobs were added the SQLAgent with the same identifier that matched the identifier in [ReportServer].[dbo].[Schedule] for my schedule in the report server. Both the old job and the new job were now corrupt and had no steps or schedules. I deleted the second job via SSMS and then the Schedules web page worked again. I edited the schedule again and it had my changes but I reapplied them and that fixed the SQLAgent Job so it had proper a schedule and steps.

I just encountered the first problem. I was modifying a schedule to run twice a week from once a week. The report website was somewhat sluggish at the time but not sure if that really matters. After that failed anytime visiting the Schedules page under Site Settings it would fail with the first error you listed. Anyway what I noticed was that 2 Jobs were added the SQLAgent with the same identifier that matched the identifier in [ReportServer].[dbo].[Schedule] for my schedule in the report server. Both the old job and the new job were now corrupt and had no steps or schedules. I deleted the second job via SSMS and then the Schedules web page worked again. I edited the schedule again and it had my changes but I reapplied them and that fixed the SQLAgent Job so it had proper a schedule and steps.