May 5, 2009 at 8:43 am
Apologies, as this is likely a repeat posting of a common issue. We have a reporting server that goes to sleep after usage in the evening. Subsequently, people in the morning become impatient for the services to start, and report Helpdesk tickets that the server is down.
Once the server is up, it responds quickly. So, what settings do I have wrong on the server to keep it running at all times? What is the reason that the service would sleep anyway?
OS NameMicrosoft(R) Windows(R) Server 2003 Standard x64 Edition
Version5.2.3790 Service Pack 2 Build 3790
System ManufacturerDell Inc.
System ModelPowerEdge 2950
System Typex64-based PC
Total Physical Memory16,378.64 MB
Available Physical Memory13.73 GB
Total Virtual Memory17.40 GB
Available Virtual Memory15.45 GB
Page File Space2.00 GB
Thank you.
July 17, 2009 at 2:37 pm
As a follow-up, I did find a posting that describes a change in IIS for the Application Pools.
Instruction was to simply uncheck the "idle timeout" which by default is checked with a 20 min threshold. However, the issue persists.
As it turns out, it was the Recycling setting, which was 20 minutes. We removed this to recycle the worker process. It is super quick now, but I am worried about unintended side-effects. We have a little over 300 reports/day, so it is fairly light compared to most environments.
Anyone know if this will cause issues?
Viewing 2 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply