Re: Application pool terminated unexpectedly

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


Date: Wed, 3 Nov 2004 00:45:26 -0800

The event log message states that something responding to the requests made
by Nessus crashed that Application Pool.

Things that can be responding to the request include:
1. Configured ISAPI Filters
2. Configured ISAPI Extensions
3. The URL itself (whatever page it is)

You should be able to see in the HTTPERR log file
(%SYSTEMROOT%\System32\LogFiles\HTTPErr\*.log) as to what request caused the
crash (it will be right before all the 503s are returned), which should help
narrow down which URL and page you need to look at. If it happens for
arbitrary pages, then you need to look at #1 and #2 that are applicable.

So, actually, you are not experiencing the same problem as anyone else.
Your symptoms look similar on the surface, but the cause is likely
different. There are many, many ways to cause the worker process to crash
and return 503s.

-- 
//David
IIS
This posting is provided "AS IS" with no warranties, and confers no rights.
//
"Brian L." <699df88b-2059788708@news.postalias> wrote in message
news:uVjjvyNwEHA.2540@TK2MSFTNGP09.phx.gbl...
Hello,
I'm experiencing what appears to be the same problem as other people. That
is, IIS stops serving pages with the message "A process serving application
pool 'DefaultAppPool' terminated unexpectedly. The process id was '1908'.
The process exit code was '0x80'". Now the cause and background for my case
are likely different from others, so I'll explain.
We are currently rebuilding from scratch a NLB, Application center clustered
(2 members) web server environment due to an irreparable configuration
mistake on the initial 2 servers. Without going into unnecessary detail, the
initial 2 servers both got built with their partitions completely out of
whack. This presents a problem for disaster recovery, and needed to be
fixed.
So in rebuilding the boxes, part of the standard procedure is to run
vulnerability scans against the machine to make sure there are no
'surprises'. We have always used Nessus for this. As it stands now I have a
condition where almost every scan I run against the rebuilt web server
causes the message below to show up in the event log. Along with this, the
web server reports Service Unavailable when you try to access any page after
the message below is generated.
I have tried to narrow down specific problem areas of the otherwise standard
practice scan I'm running, but have only succeeded in frustrating myself.
Whenever I think I have the problem isolated to a specific function, it
happens again. I'm not asking for help related to Nessus, since this is
obviously not the place for that. I'm convinced there is either some
misconfiguration or other problem that exists and is causing the crash.
I've tried to follow several other threads that I've seen with the same exit
code and error messages, but there never seems to be a solution in the
thread. I've tried using the debugging tools (IISdump, windbg) but it is not
very easy for me to comprehend :) I'll attach what I had below. Any help
would be appreciated! Thanks
-------------------------
Event:
Event Type: Warning
Event Source: W3SVC
Event Category: None
Event ID: 1009
Date:  10/20/2004
Time:  9:58:51 AM
User:  N/A
Computer: WEBSERVER01
Description:
A process serving application pool 'DefaultAppPool' terminated unexpectedly.
The process id was '1908'. The process exit code was '0x80'.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
-------------------------
Dump info from windbg:
Microsoft (R) Windows Debugger Version 6.3.0017.0
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File
[C:\IISDebugTools\logs\20041025-105506\Process_Shut_Down--2636_dllhost_AC_Lo
g_Consumer.dmp]
User Mini Dump File with Full Memory: Only application data is available
Comment: 'Generated by IISDBG'
Windows Server 2003 Version 3790 MP (2 procs) Free x86 compatible
Product: Server, suite: TerminalServer SingleUserTS Blade
Debug session time: Mon Oct 25 11:05:16 2004
System Uptime: 26 days 19:24:26.062
Process Uptime: 0 days 0:21:30.000
Symbol search path is: SRV*downstream
store*http://msdl.microsoft.com/download/symbols
Executable search path is:
...............................................................
eax=000000c0 ebx=00000000 ecx=00000000 edx=00000000 esi=00000000
edi=00000000
eip=7ffe0304 esp=0067ffa0 ebp=0067ffb8 iopl=0 nv up ei pl zr na po nc
cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000 efl=00000246
SharedUserData!SystemCallStub+0x4:
7ffe0304 c3 ret


Relevant Pages

  • Re: The server committed a protocol violation
    ... Response -> ... instead sending a new request right away. ... One potential gotcha here is that the web server does one sendfor ... application can access the web service without any problems. ...
    (microsoft.public.windowsce.embedded)
  • Re: proxy server in lisp
    ... ??>> almost all garbage collectors do full GC from time to time, ... if we'd like to test web server workloads, let's do a benchmarking of UCW. ... 100% 11754 (longest request) ... ??>> pauses) implemented for Common Lisp. ...
    (comp.lang.lisp)
  • Re: Web hits, graphics vs non-graphics
    ... AW> Every webserver I have management experience with (OSU, WASD, ... the last being the most popular Linux web server) ... AW> HTTP request and a separate hit. ... possible that someone using NetZero would issue a request for the page ...
    (rec.arts.sf.fandom)
  • Re: Difference in authentication between using IP address and DNS name
    ... The host name may resolve to a different address. ... The other thing that could be happening is if the web server uses HTTP ... The web server at the time of the request examines the requested ...
    (microsoft.public.security)
  • Re: Converting Program for Use on the Web?
    ... On a desktop, your program runs, and users interact with it, and the ... request, and you have to serve up a page that makes sense. ... playing a game of Tic-Tac-Toe: the data in the game object records ... now the web server has to determine what constitutes a "connection". ...
    (comp.lang.pascal.delphi.misc)