Re: IIS 6.0 issue

From: David Wang [Msft] (someone_at_online.microsoft.com)
Date: 06/30/04


Date: Tue, 29 Jun 2004 17:05:18 -0700

How about making the applications that run on the server more stable? IIS6
tries its best to recover from user problems, but sometimes, it may not be
possible nor make sense, so IIS will disable the application pool to prevent
further server damage.

Seriously, you should not need to re-install IIS6 to fix the issue you
describe. Can you give the event log entry that says WHY the DefaultAppPool
is being disabled? Then, can you fix your application such that it doesn't
cause the Application Pool to be disabled?

A disabled application pool can be re-enabled by simply going to the UI,
selecting the stopped application pool, and changing it to "start". Now,
that says nothing about whether you could be running junk in the application
pool that makes it disabled again.

All IIS is doing is trying to run your application. If your application
misbehaves and triggers the many health-monitoring checks of IIS6, the
Application Pool gets recycled. When this recycle happens too many times
and too frequently, IIS stops the Application Pool to prevent any more abuse
of system resources. This is also a sign for you to fix your application or
maybe IIS configuration (perhaps your health-monitoring is too aggressive
for the application).

In other words, IIS6 is simply notifying you of potential problems and tries
to buy you some more time by proactively recycling the application to keep
it running. You should try to fix the problems, not shoot the messenger.
Fundamentally, it is impossible for IIS6 to keep a buggy application running
all the time, so the only real way to make the application more stable is to
remove the bugs in it.

-- 
//David
IIS
This posting is provided "AS IS" with no warranties, and confers no rights.
//
"JG" <anonymous@discussions.microsoft.com> wrote in message
news:233d201c45e27$45e15fb0$a501280a@phx.gbl...
Hi all,
I got an error message this morning from my IIS 6.0 server.
It seems the Default AppPool was disabled because it had
something to do with the http.sys.
To resolve this issue, I had to re-install IIS since it
would not start the websites.
I also configured an app pool for each website running on
the server. I also disabled Rapid Failover and Pinging.
Is there anything else I can do to make the server more
stable ?
thanks


Relevant Pages

  • Re: IIS 6 features
    ... of your web *server*. ... In the case where a web application pool is failing ... You can configure how and when Rapid Fail Protection kicks in. ... interested in getting to know IIS 6, then I suggest reading the IIS Res Kit: ...
    (Focus-Microsoft)
  • RE: OWA HTTP 500 Error for some users
    ... Known issues that cause the "HTTP 500 internal server error" error message ... Right-click Application Pools, point to New and select Application Pool. ... Outlook Web Access to Connect to Your Microsoft Exchange Server 2003 Mailbox ... Open "Internet Information Service (IIS) Manager" console, ...
    (microsoft.public.windows.server.sbs)
  • Re: iis - cannot find page (cannot find server or dns error)
    ... the problem is unlikely to be related to IIS6. ... IP address of the web server directly from a client machine that is EXTERNAL ... with IIS and is likely DNS related. ... If using IP does not work, then it has nothing to do with IIS and is ...
    (microsoft.public.inetserver.iis)
  • Re: IIS 6.0 and Permissions?
    ... Read the F1-help in IIS Manager UI on how to configure Application Pool ... I do not think you've configured the server properly yet. ... I suspect it has to do with permissions. ...
    (microsoft.public.inetserver.iis.security)
  • Re: Automatic Password Reset
    ... Create a new application pool on the IIS Server ... Assign the newly create application pool to the virtual website. ... Smart Cards Company confidential and proprietary information ...
    (Security-Basics)