My reporting server seems to go to sleep after some time of non-use. This is affecting the users who create reports at the start of the day. A report that takes 1 second to generate takes 11 seconds on first hit in the morning. After the initial "wake up" call, the report server generates the reports normally without any delay. Can I keep it awake the whole time? Is there a setting somewhere?
Is there an error generated? What tells you that the report has gone to "sleep"?|||No error. Just the delay. It's not the report that goes to sleep, its the reporting service. As I said, a report that takes 1 second to generate takes 11 seconds on first hit if the reporting server hasn't been used for a while.
I searched this forum and found other posts similar to mine. It seems that you need to change the shutdown timeout of the App Pool of the reporting service and/or create a snapshot of a dummy report each hour or so.
Any other suggestions beside these?
|||>> any other suggestions
Those *are* the right answers, usually. ( examples: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1056458&SiteID=1 or http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=703914&SiteID=1)
Are you saying you already tried this advice and it did not work for you, or that you don't want to follow those instructions for some reason <s>?
>L<
|||I tried both and they aren't working. When I run a report in the morning, it still takes a long time to "wake up". I then look at Event Log of the reporting server to discover that an entry has just been made saying that reporting services has been activated. It should already be activated according to those other posts.
I've got reporting services creating a snapshot of a dummy report every hour and I've set the background thread in IIS to shutdown after 2 days, so I'm doing everything those other posts suggest. Still no go.
|||OK. This might be a stupid question but... could overnight patching or maintenance procedures of any type that might require a reboot, or even just a shut down of ASP.NET, be involved here?
>L<
|||I don't think the web server / reporting server shuts down each night. I believe it is constantly turned on.
I had a look at how the snapshot works. It seems to create an SQL job, which runs on a schedule. This would mean the snapshot has nothing to do with ASP.NET and the IIS worker process, which I think it is the culprit. Maybe I need something to constantly download a dummy report on the web server to keep the web service alive? How could I do that?
|||To tell you the truth, I didn't even understand why you were creating a snapshot on the hour (did you find that part in the instructions somewhere? ) I ws sure the worker thread thing was what you needed to do. (I know you said you set the background thread -- are you sure you did the right thing for the application pool that reporting services is using?)
As far as how you can download a dummy report, sure you can do that various kludgey ways with a bunch of work -- but that seems like a depressing idea, doesn't it <s>?
Can you describe exactly what you did re " I've set the background thread in IIS to shutdown after 2 days" and under what OS/version of IIS ?
>L<
|||One of the forum posts suggested to create a snapshot.
Reporting Services is running on Windows Server 2003 on IIS 6.
There are two virtual directories under "Default Website": Reports and ReportServer. The application pool for each is "ReportServer". But the application pool for "Default Website" is "DefaultAppPool". Maybe that's a problem?
Going to the properties window of the "ReportServer" app pool, in the Performance tab, there is an option "Shut down worker process after being idle for (time in minutes)". This was 20 minutes and I changed it to 2880 minutes (2 days).
In the "Recycling" tab (the first tab) there is a "Recycle worker process (in minutes)" option which is set to 1740 (if that helps).
Everytime the report server wakes up, an entry in the Event Log is created with the text:
The ReportServer service has been activated.
The report server seems to deactivate a lot during the day, not just in the mornings. Maybe it's something to do with the fact that Default Web Site has a different app pool than the two reporting services virtual directories that sit under it?
|||I suppose you could change the values for the default web site/app pool also but you shouldn't need to.
Try unchecking the Recycle worker process option altogether. **
Are you absolutely sure that the event log says "has been activated" rather than "started" or "started successfully" each time? Are you *sure* <g>? because this message shouldn't be happening multiple times... and doesn't mean what you are interpreting it to mean...
** Look: I'm pretty sure that, in spite of the fact that you think it's the "reportserver service" and are seeing that message, that what you are seeing is due to recompiling of the app instance for the web application.
... but, just in case, if it is really the service, I assume you have also checked to make sure that the service startup type is Automatic?
>L<
|||I had copied and pasted the Event Log message into my post, and it happens multiple times a day. I checked the Service and it's set to "Automatic".
Before I set it to 2 days, I had originally tried unchecking the Recycle worker process altogether, but the same thing.
In the meantime, I've set up a little console application that runs on the server via Windows Scheduler every 15 minutes. It uses the Reporting Services Web Service to download one of the AdventureWorks sample reports before closing. This seems to be a good interim solution, albeit not ideal.
We are eventually going to upgrade to Reporting Services 2005, so maybe that will help.
|||Oh!!! I am terribly sorry for having wasted your time on the event log message. I had no idea that you were in RS 2000. I am sure that the messages might be different there.
>L<
|||I'm going to refer the problem to Microsoft Support and see if I can get any further with this
|||I think that's a good idea. I hope you get further than this...
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=203521&SiteID=1
... I believe the solution posted there is specific to RS 2005 but at least it is a cogent explanation of the IIS component of the issue <s>.
Good luck,
>L<
No comments:
Post a Comment