IIS 5 & IIS 6
Last post May 20, 2007 03:11 AM by steve schofield
May 19, 2007 10:10 AM|webservermatrix|LINK
I have having Hosting Server with 800 domains, web Service crashes once a day, I did lots of research but still don’t get any thing useful.
Every time Server Crashes, Rest of the Services remaining unaffected Just IIS goes down,
Even IIS’s own services are also remain started but it becomes Unresponsive, nothing works, I checked event logs and everything but no hints of
this issue. I Just get following Error
I think this has something to do with Server’s memory, I found following KB , Do we need to use /3GB Switch on the server, as server’s specification
is Dual Xeon with 4GB Ram.
This server is purely used for web Hosting and we are just running IIS only on this server, we have already done Memory tests for Memory leakage
and all but didn’t find any useful results.
May 19, 2007 12:19 PM|steve schofield|LINK
The /3GB switch will be ok, that might help in the short-term. The KB article I've not done personally. I would work on isolating the problem and resolving that. If this happens once a day, I would review your event logs, look at the scheduled tasks,
look at process monitor or use a tool called 'pmon' to see if there is a memory leak.
Windows Server MVP - IIS
Log archival solution
Install, Configure, Forget
May 19, 2007 04:19 PM|webservermatrix|LINK
We have tried that, There is no indication in Eventlogs, we have also tired stopping all the scheduled tasks for 48hrs. also for IIS we have done Application Pool Isolation. but that also didnt helped.
May 20, 2007 03:11 AM|steve schofield|LINK
The next time this happens, open task manager and add the Virtual Memory option in the 'processes' tab. See if there is any processes that have a lot of virtual memory and very little physical memory. If the process is say 5 MB or (5000) and the Virtual
memory is say (500,000) or a large number for example, inspect that for a memory leak. I would look at firmware versions on the box, agents running as I've seen Dell agents have memory leaks, turn off other 3rd party agents and see. You might want to also
track your higher memory usage application pools. For memory and process management, ensure you look at periodic recycles on your application pools.. It might be also your applications are using too much memory, one last thing to check is make sure the paging
file is 1 1/2 times the amount of RAM. I've seen a misconfigured paging file call strange issues.
To really solve the issue, you need to track down the memory leak, if you are unsure and can't find anything, call Microsoft PSS, they can help you track it down