February 24, 2012 at 5:26 am
Hey There
Coming across the below error in our reporting services log file can anyone tell me what is causing this been googling for the last few days with no luck...
An error occurred within the report server database. This may be due to a connection failure, timeout or low disk condition within the database. ---> System.Data.SqlClient.SqlException: SQLServerAgent exceeded the allowed timeout for creating the shared job list. The Jobs cannot be enumerated.
We are running SQL Server 2008 R2 SP1 x64...
these errors are also beein log in the log file
ERROR: Throwing Microsoft.ReportingServices.Diagnostics.Utilities.ReportServerStorageException: , An error occurred within the report server database. This may be due to a connection failure, timeout or low disk condition within the database.;
At a loss at to what is causing this your help would be much appreciated
Thanks
February 27, 2012 at 2:13 am
No one?.... damn
November 19, 2013 at 12:07 pm
I'm experiencing the same problem on some of my SSRS reports, and it appears to be intermittent.
We have several hundred report subscriptions, the SQL Agent Jobs report success, but I get messages in the SSRS log to this effect:
11/17/2013-02:15:31:: Error processing event 'TimedSubscription', data = fdce1441-883d-409c-8dd6-401ed2c9f331, error = Microsoft.ReportingServices.Diagnostics.Utilities.ReportServerStorageException: An error occurred within the report server database. This may be due to a connection failure, timeout or low disk condition within the database. ---> System.Data.SqlClient.SqlException: SQLServerAgent exceeded the allowed timeout for creating the shared job list. The Jobs cannot be enumerated.
I've learned that the enumeration is handled by xp_sqlagent_enum_jobs procedure, which is undocumented. However, I can run the following and I get results very quickly (sub-second):
exec master.dbo.xp_sqlagent_enum_jobs 1, ''
The 2 reports that have this issue have been running fine, and nothing has changed for these reports or the servers/etc involved in months. Also, scheduled reports before and after these ran fine. It seems like something else is causing these to hang. Both reports with the issue run outside of business hours when db usage is very low.
Any thoughts? Running on Windows 2008 R2, SQL Server 2012, VMWare esxi 5
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply