David
Wed Jun 30 04:25:33 CDT 2004
Well, IIS5 also does not have application pools, health monitoring, is
vulnerable to CodeRed/Nimda, runs as LocalSystem, etc -- so trying to draw
any operational comparison is like comparing apples and oranges.
Disabled Application Pools is simply a sign that you have something
troubling the application that should be investigated. IIS6 tried to
address the issue in the ways that it can (and that you configured), but it
wasn't sufficient. A human will have to intervene and figure out what's
going on.
Whether the issue is within your application (just because it runs on IIS5
says nothing about whether it is written correctly) or is due to OS changes
(IIS6 is a lot more secure and more restrictive than IIS5, both as a
platform and from the underlying OS perspective), that is to be
investigated. You can start by reading documentation on how to
troubleshoot -- we have an entire section dedicated to it:
http://www.microsoft.com/downloads/details.aspx?FamilyID=80a1b6e6-829e-49b7-8c02-333d9c148e69&DisplayLang=en
As well as useful tools for IIS:
http://www.microsoft.com/downloads/details.aspx?FamilyID=56fc92ee-a71a-4c73-b628-ade629c89499&DisplayLang=en
Usually, when an application fails due to Rapid Fail protection, something
is horribly incompatible with your application that requires immediate
attention. For example, you may have code that requires running as
LocalSystem, and that doesn't work on IIS6 by default... so it may have
legitimate problems. Of course, for security reasons, we changed the
process identity on IIS6, and we knew that it can break people -- but we're
just going to call your attention to it by failing, and you can figure out
why and make the security assessment yourself. We'd rather you be broken
(and secure) than working (and insecure).
--
//David
IIS
This posting is provided "AS IS" with no warranties, and confers no rights.
//
"Jeff" <anonymous@discussions.microsoft.com> wrote in message
news:234cc01c45e3c$2b6f2710$a501280a@phx.gbl...
David
thanks for the reply.
However, one thing that concerns me is that i never had
these problems in IIS 5.0 in win2k.
Oh well.
I have disabled some monitoring of the worker processes
and we will see if that helps..
thanks
>-----Original Message-----
>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
>
>
>.
>