IIS needs to be restarted Constantly

[mchatz13]

I have an IIS 6.0 server running internally for a couple of sites. Just about 3 times a week (average and random times) I have to restart IIS services because the "Server is Unavaialble". Odd thing is only one site may be getting this error (random) while the others are having no problems at all. If I do an iireset the problem gets fixed. Nothing in the event viewer, no errors on the server. On thursday, I plan on un-installing, re-installing, then re-creating all the VD's, but was curious if anyone had any ideas.

Please let me know. My next step is to re-build the server.

mc

 

[richw1234]

I have the same problem with IIS5, I have several servers that are constantly having to be reset, I was hoping IIS6 was going to fix this problem, if anyone has any ideas on how to fix this then it would be much appreciated.

 

[shatch]

Has anything been put into the event log? I once had a similar problem and it was down to the pooling, so maybe its worth looking in that direction.

 

[Micron1090]

check out the application pools before you run iisresest. Recycle the pool you have set for that website, right click on the pool, click recycle. If that fixes the problem, you can setup inside the pool to bounce itelf at intervals. set it up so it bounces itself before it crashes.

If you only have one pool, make one for each site, then go into the site properties to change the pool it uses.

As to why it's happening, no idea there are a ton of things that are in play. Best place to start would be looking at your code and trying to optimize.

 

[F1lby]

WHat sort of code is being executed on the server? Basic html or ASP? Or maybe Perl or PHP?
If code is executing on the server, then have you tried creating a new site and stopping the one that is suspected of causing these problems? Give this new temporary site a bit of basic html to run with and check regularly. If the server remains up, then you may well be looking at some bad coding. A bad bit of code that doesn't run cleanly can cause all sorts of havoc.

 

[mchatz13]

In the event log I found a lot of Dcom and WCF32 errors. I did some research, and found that there could be a problem with the IWAM user. What MS suggested is to reduce my application processes to low (not High (Isoltated) in IIS). and see if the problem continued. If it does not, then run some scripts to re-align the IWAM passwords.

mc