We have been working on a new project at work that requires the SQL 2005 Reporting Service. It is a little clunky to get installed, but eventually it works fairly well. My question is, what could cause it to bomb out the next morning after a period of inactivity? We are thinking that a service restart may be in order every morning or a job may need to be scheduled to run periodically to keep the service up. Any ideas of what could be causing this?
asked May 03 '11 at 05:51 AM in Default
Are you experiencing the problem on the application server? I mean you receive timeouts on the application server?
If it is related to the daily periodics timeouts, then it could be related to the application pool shut downs which are done after some time of inactivity on SSRS 2005. Check the MS SQL Tips for How to Speed up MS SQL Server Reporting Services SSRS on First Run. There is tip how to keep the application pool to keep running without recycling.
SSRS2008 has similar problems witht the Application Domain Restarts. I have some info related to it here: [First report and report after specific time interval starts a long time on MS SQL 2008 Reporting Services] (It was ispired by the MS SQL Tip for SSRS 2005 :-)): http://www.pawlowski.cz/2011/01/report-report-specific-time-interval-starts-long-time-ms-sql-2008-reporting-services/
answered May 03 '11 at 11:42 AM
You may wish to start with @Raj More suggestion..
Then you can look at the dbo.ExecutionLog it will give you an history of things like "TimeDataRetrieval", "TimeProcessing", "TimeRendering" and Status. You can join this table to dbo.Catalog to filter the exact report. [MS link]
Another place to look is within the LogFiles for the actual report instance. Microsoft SQL Server/MSSQL.3/Reporting Services/LogFiles
This in my location, yours maybe a little different.
Other basic quesitons would be, how many users did it affect? Is it still happening? At what time did it crash and was there anything else running at that time?: http://msdn.microsoft.com/en-us/library/ms159110%28v=SQL.90%29.aspx
My first line of investigation here would be network related - is there something dropping out of DNS or maybe a authentication issue somewhere? If the service is being reported as stopped is something causing it to stop overnight?
answered May 03 '11 at 08:33 AM