Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.

Dismiss

Non Zero Return Code when recycling App Pools.

471 views

Skip to first unread message

Gonzo

unread,

Dec 7, 2007, 11:44:03 AM12/7/07

Hello all. Does anyone know why I would get a Non Zero return code when an
App Pool is recycled either manually or automatically. I am doing logging
when an App Pool exits with a Non Zero Return Code and this is driving me
crazy. If you look at the output of DegugDiag below, it does not appear that
it is crashing, but that some of the threads are returning the exit code of
0xfffffffe. It appears that the main thread 8196 exits with 0, but all the
rest with 0xfffffffe which causes the process to exit with code 0xfffffffe.
I cannot find very much if any information on what the code 0xfffffffe means,
nor am I getting any kind of event log to tell me what the problem is.

Any help would be most greatly appreciated... Gonzo

Loading control script C:\Program Files\DebugDiag\scripts\CrashRule_9188.vbs
DumpPath set to C:\Program Files\DebugDiag\Logs\Crash rule for process id 9188
[12/6/2007 5:43:21 PM] Process created. BaseModule -
c:\windows\system32\inetsrv\w3wp.exeBaseThread System ID - 2164
[12/6/2007 5:43:21 PM] Thread created. New thread system id - 8196
[12/6/2007 5:43:21 PM] Thread created. New thread system id - 7372
[12/6/2007 5:43:21 PM] Thread created. New thread system id - 5792
[12/6/2007 5:43:21 PM] Thread created. New thread system id - 3280
[12/6/2007 5:43:21 PM] Thread created. New thread system id - 452
[12/6/2007 5:43:21 PM] Thread created. New thread system id - 6076
[12/6/2007 5:43:21 PM] Thread created. New thread system id - 6160
[12/6/2007 5:43:21 PM] Thread created. New thread system id - 3328
[12/6/2007 5:43:21 PM] Thread created. New thread system id - 4404
[12/6/2007 5:43:21 PM] Thread created. New thread system id - 6988
[12/6/2007 5:43:21 PM] Thread created. New thread system id - 8320
[12/6/2007 5:43:21 PM] Thread created. New thread system id - 8680
[12/6/2007 5:43:21 PM] Thread created. New thread system id - 1368
[12/6/2007 5:43:21 PM] Thread created. New thread system id - 9568
[12/6/2007 5:43:21 PM] Thread created. New thread system id - 6632
[12/6/2007 5:43:21 PM] Thread created. New thread system id - 4012
[12/6/2007 5:43:21 PM] Thread created. New thread system id - 5332
[12/6/2007 5:43:21 PM] C:\WINDOWS\system32\ntdll.dll loaded at 0x7c800000
[12/6/2007 5:43:21 PM] C:\WINDOWS\system32\kernel32.dll loaded at 0x77e40000
[12/6/2007 5:43:21 PM] C:\WINDOWS\system32\msvcrt.dll loaded at 0x77ba0000
[12/6/2007 5:43:21 PM] C:\WINDOWS\system32\ADVAPI32.dll loaded at 0x77f50000
[12/6/2007 5:43:21 PM] C:\WINDOWS\system32\RPCRT4.dll loaded at 0x77c50000
[12/6/2007 5:43:21 PM] C:\WINDOWS\system32\USER32.dll loaded at 0x77380000
[12/6/2007 5:43:21 PM] C:\WINDOWS\system32\GDI32.dll loaded at 0x77c00000
[12/6/2007 5:43:21 PM] C:\WINDOWS\system32\ole32.dll loaded at 0x77670000
[12/6/2007 5:43:21 PM] c:\windows\system32\inetsrv\IISUTIL.dll loaded at
0x64700000
[12/6/2007 5:43:21 PM] C:\WINDOWS\system32\CRYPT32.dll loaded at 0x761b0000
[12/6/2007 5:43:21 PM] C:\WINDOWS\system32\MSASN1.dll loaded at 0x76190000
[12/6/2007 5:43:21 PM] C:\Program Files\BMC Software\AppSight\Bin\MgInst.dll
loaded at 0x66840000
[12/6/2007 5:43:21 PM] C:\Program Files\BMC Software\AppSight\Bin\SDCore.dll
loaded at 0x67040000
[12/6/2007 5:43:21 PM] C:\WINDOWS\system32\PSAPI.DLL loaded at 0x76b70000
[12/6/2007 5:43:21 PM] C:\WINDOWS\system32\SHELL32.dll loaded at 0x7c8d0000
[12/6/2007 5:43:21 PM] C:\WINDOWS\system32\SHLWAPI.dll loaded at 0x77da0000
[12/6/2007 5:43:21 PM] C:\Program Files\BMC
Software\AppSight\Bin\InfrastructureStat.dll loaded at 0x661d0000
[12/6/2007 5:43:21 PM] C:\Program Files\BMC
Software\AppSight\Bin\InstrRuntime.dll loaded at 0x661f0000
[12/6/2007 5:43:21 PM]
C:\WINDOWS\WinSxS\x86_Microsoft.Windows.Common-Controls_6595b64144ccf1df_6.0.3790.2778_x-ww_A8F04F11\comctl32.dll loaded at 0x77420000
[12/6/2007 5:43:21 PM] C:\Program Files\BMC Software\AppSight\Bin\ExInst.dll
loaded at 0x65fe0000
[12/6/2007 5:43:21 PM] C:\Program Files\BMC
Software\AppSight\Bin\ClientSideTraceComponents.dll loaded at 0x65c40000
[12/6/2007 5:43:21 PM] C:\Program Files\BMC Software\AppSight\Bin\CdInst.dll
loaded at 0x65bc0000
[12/6/2007 5:43:21 PM] C:\Program Files\BMC
Software\AppSight\Bin\BbxOsDepNTS.dll loaded at 0x65950000
[12/6/2007 5:43:21 PM] C:\Program Files\BMC
Software\AppSight\Bin\DNLoader.dll loaded at 0x65fa0000
[12/6/2007 5:43:21 PM] C:\WINDOWS\system32\VERSION.dll loaded at 0x77b90000
[12/6/2007 5:43:21 PM] C:\Program Files\BMC Software\AppSight\Bin\VLInfo.dll
loaded at 0x67b50000
[12/6/2007 5:43:21 PM] C:\WINDOWS\system32\IMM32.dll loaded at 0x76290000
[12/6/2007 5:43:21 PM] C:\Program Files\BMC
Software\AppSight\Bin\IISHandler.dll loaded at 0x66130000
[12/6/2007 5:43:21 PM] C:\Program Files\BMC Software\AppSight\Bin\CdInfo.dll
loaded at 0x65aa0000
[12/6/2007 5:43:21 PM] C:\WINDOWS\system32\OLEAUT32.dll loaded at 0x77d00000
[12/6/2007 5:43:21 PM] C:\Program Files\BMC
Software\AppSight\Bin\TrigActClient.dll loaded at 0x67870000
[12/6/2007 5:43:21 PM] C:\Program Files\BMC
Software\AppSight\Bin\GlobInfo.dll loaded at 0x66050000
[12/6/2007 5:43:21 PM] C:\Program Files\BMC
Software\AppSight\Bin\AsyncInfo.dll loaded at 0x652b0000
[12/6/2007 5:43:21 PM] C:\WINDOWS\system32\xpsp2res.dll loaded at 0x10000000
[12/6/2007 5:43:21 PM] c:\windows\system32\inetsrv\w3core.dll loaded at
0x5a390000
[12/6/2007 5:43:21 PM] C:\WINDOWS\system32\IISMAP.dll loaded at 0x5a420000
[12/6/2007 5:43:21 PM] C:\WINDOWS\system32\IisRTL.DLL loaded at 0x647b0000
[12/6/2007 5:43:21 PM] C:\WINDOWS\system32\WS2_32.dll loaded at 0x71c00000
[12/6/2007 5:43:21 PM] C:\WINDOWS\system32\WS2HELP.dll loaded at 0x71bf0000
[12/6/2007 5:43:21 PM] c:\windows\system32\inetsrv\LONSINT.dll loaded at
0x62da0000
[12/6/2007 5:43:21 PM] C:\WINDOWS\system32\Secur32.dll loaded at 0x76f50000
[12/6/2007 5:43:21 PM] C:\WINDOWS\system32\NETAPI32.dll loaded at 0x71c40000
[12/6/2007 5:43:21 PM] C:\WINDOWS\system32\strmfilt.dll loaded at 0x5b640000
[12/6/2007 5:43:21 PM] C:\WINDOWS\system32\HTTPAPI.dll loaded at 0x67150000
[12/6/2007 5:43:21 PM] c:\windows\system32\inetsrv\W3CACHE.dll loaded at
0x5a400000
[12/6/2007 5:43:21 PM] c:\windows\system32\inetsrv\W3TP.dll loaded at
0x5a300000
[12/6/2007 5:43:21 PM] c:\windows\system32\inetsrv\W3COMLOG.dll loaded at
0x5a3f0000
[12/6/2007 5:43:21 PM] c:\windows\system32\inetsrv\w3dt.dll loaded at
0x5a360000
[12/6/2007 5:43:21 PM] c:\windows\system32\inetsrv\wamreg.DLL loaded at
0x60ba0000
[12/6/2007 5:43:21 PM] C:\WINDOWS\system32\WSOCK32.dll loaded at 0x71bb0000
[12/6/2007 5:43:21 PM] c:\windows\system32\inetsrv\iisres.dll loaded at
0x6d0f0000
[12/6/2007 5:43:21 PM] C:\WINDOWS\system32\CLBCatQ.DLL loaded at 0x777b0000
[12/6/2007 5:43:21 PM] C:\WINDOWS\system32\COMRes.dll loaded at 0x77010000
[12/6/2007 5:43:22 PM] C:\WINDOWS\system32\ADMWPROX.DLL loaded at 0x608f0000
[12/6/2007 5:43:22 PM] C:\WINDOWS\system32\rsaenh.dll loaded at 0x68000000
[12/6/2007 5:43:22 PM]
C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\aspnet_filter.dll loaded at
0x60060000
[12/6/2007 5:43:22 PM]
C:\WINDOWS\WinSxS\x86_Microsoft.VC80.CRT_1fc8b3b9a1e18e3b_8.0.50727.42_x-ww_0DE06ACD\MSVCR80.dll loaded at 0x78130000
[12/6/2007 5:43:22 PM] c:\windows\system32\inetsrv\w3isapi.dll loaded at
0x5a320000
[12/6/2007 5:43:22 PM] C:\WINDOWS\System32\mswsock.dll loaded at 0x71b20000
[12/6/2007 5:43:22 PM] C:\WINDOWS\system32\DNSAPI.dll loaded at 0x76ed0000
[12/6/2007 5:43:22 PM] C:\WINDOWS\System32\winrnr.dll loaded at 0x76f70000
[12/6/2007 5:43:22 PM] C:\WINDOWS\system32\WLDAP32.dll loaded at 0x76f10000
[12/6/2007 5:43:22 PM] C:\WINDOWS\system32\rasadhlp.dll loaded at 0x76f80000
[12/6/2007 5:43:22 PM] C:\WINDOWS\system32\inetsrv\gzip.dll loaded at
0x685b0000
[12/6/2007 5:43:22 PM] Thread created. New thread system id - 8212
[12/6/2007 5:43:22 PM] Thread exited. Exiting thread system id - 4012. Exit
code - 0x00000000
[12/6/2007 5:43:22 PM] Thread created. New thread system id - 404
[12/6/2007 5:43:22 PM] Initializing control script
[12/6/2007 5:43:22 PM] Clearing any existing breakpoints
[12/6/2007 5:43:22 PM]
[12/6/2007 5:43:22 PM] Current Breakpoint List(BL)
[12/6/2007 5:43:22 PM] Thread created. New thread system id - 5032
[12/6/2007 5:43:22 PM] Thread exited. Exiting thread system id - 1368. Exit
code - 0x00000000
[12/6/2007 5:43:22 PM] Thread exited. Exiting thread system id - 6632. Exit
code - 0x00000000
[12/6/2007 5:43:22 PM] Thread exited. Exiting thread system id - 8212. Exit
code - 0x00000000
[12/6/2007 5:43:22 PM] Thread exited. Exiting thread system id - 9568. Exit
code - 0x00000000
[12/6/2007 5:43:22 PM] Thread exited. Exiting thread system id - 8680. Exit
code - 0x00000000
[12/6/2007 5:43:27 PM] Thread created. New thread system id - 7112
[12/6/2007 5:43:27 PM] Thread exited. Exiting thread system id - 6988. Exit
code - 0x00000000
[12/6/2007 5:43:27 PM] C:\WINDOWS\system32\inetsrv\gzip.dll unloaded from
0x685b0000
[12/6/2007 5:43:27 PM] c:\windows\system32\inetsrv\w3isapi.dll unloaded from
0x5a320000
[12/6/2007 5:43:27 PM] First chance exception - 0xc0000005 caused by thread
with system id 2164
[12/6/2007 5:43:27 PM] First chance exception - 0xc0000005 caused by thread
with system id 2164
[12/6/2007 5:43:27 PM]
C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\aspnet_filter.dll unloaded from
0x60060000
[12/6/2007 5:43:27 PM]
C:\WINDOWS\WinSxS\x86_Microsoft.VC80.CRT_1fc8b3b9a1e18e3b_8.0.50727.42_x-ww_0DE06ACD\MSVCR80.dll unloaded from 0x78130000
[12/6/2007 5:43:27 PM] Thread exited. Exiting thread system id - 3328. Exit
code - 0x00000000
[12/6/2007 5:43:27 PM] Thread exited. Exiting thread system id - 6076. Exit
code - 0x00000000
[12/6/2007 5:43:27 PM] Thread exited. Exiting thread system id - 6160. Exit
code - 0x00000000
[12/6/2007 5:43:27 PM] Thread exited. Exiting thread system id - 452. Exit
code - 0x00000000
[12/6/2007 5:43:28 PM] C:\WINDOWS\System32\winrnr.dll unloaded from 0x76f70000
[12/6/2007 5:43:29 PM] C:\WINDOWS\system32\WLDAP32.dll unloaded from
0x76f10000
[12/6/2007 5:43:29 PM] First chance exception - 0xc0000005 caused by thread
with system id 2164
[12/6/2007 5:43:29 PM] First chance exception - 0xc0000005 caused by thread
with system id 2164

The line above repeated a bunch more times

[12/6/2007 5:43:29 PM] C:\WINDOWS\System32\mswsock.dll unloaded from
0x71b20000
[12/6/2007 5:43:29 PM] c:\windows\system32\inetsrv\iisres.dll unloaded from
0x6d0f0000
[12/6/2007 5:43:29 PM] C:\WINDOWS\system32\ADMWPROX.DLL unloaded from
0x608f0000
[12/6/2007 5:43:29 PM] c:\windows\system32\inetsrv\w3core.dll unloaded from
0x5a390000
[12/6/2007 5:43:29 PM] C:\WINDOWS\system32\WSOCK32.dll unloaded from
0x71bb0000
[12/6/2007 5:43:29 PM] c:\windows\system32\inetsrv\wamreg.DLL unloaded from
0x60ba0000
[12/6/2007 5:43:29 PM] c:\windows\system32\inetsrv\w3dt.dll unloaded from
0x5a360000
[12/6/2007 5:43:29 PM] c:\windows\system32\inetsrv\W3COMLOG.dll unloaded
from 0x5a3f0000
[12/6/2007 5:43:29 PM] c:\windows\system32\inetsrv\W3CACHE.dll unloaded from
0x5a400000
[12/6/2007 5:43:29 PM] c:\windows\system32\inetsrv\W3TP.dll unloaded from
0x5a300000
[12/6/2007 5:43:29 PM] C:\WINDOWS\system32\strmfilt.dll unloaded from
0x5b640000
[12/6/2007 5:43:29 PM] C:\WINDOWS\system32\HTTPAPI.dll unloaded from
0x67150000
[12/6/2007 5:43:29 PM] C:\WINDOWS\system32\NETAPI32.dll unloaded from
0x71c40000
[12/6/2007 5:43:29 PM] c:\windows\system32\inetsrv\LONSINT.dll unloaded from
0x62da0000
[12/6/2007 5:43:29 PM] C:\WINDOWS\system32\Secur32.dll unloaded from
0x76f50000
[12/6/2007 5:43:29 PM] C:\WINDOWS\system32\IISMAP.dll unloaded from 0x5a420000
[12/6/2007 5:43:29 PM] C:\WINDOWS\system32\IisRTL.DLL unloaded from 0x647b0000
[12/6/2007 5:43:29 PM] First chance exception - 0xc0000005 caused by thread
with system id 2164
[12/6/2007 5:43:29 PM] First chance exception - 0xc0000005 caused by thread
with system id 2164
[12/6/2007 5:43:29 PM] First chance exception - 0xc0000005 caused by thread
with system id 2164
[12/6/2007 5:43:29 PM] First chance exception - 0xc0000005 caused by thread
with system id 2164
[12/6/2007 5:43:29 PM] First chance exception - 0xc0000005 caused by thread
with system id 8196
[12/6/2007 5:43:29 PM] First chance exception - 0xc0000005 caused by thread
with system id 8196

The line above repeated a bunch more times

[12/6/2007 5:43:30 PM] C:\Program Files\BMC Software\AppSight\Bin\CdInst.dll
unloaded from 0x65bc0000
[12/6/2007 5:43:30 PM] First chance exception - 0xc0000005 caused by thread
with system id 8196
[12/6/2007 5:43:30 PM] C:\Program Files\BMC Software\AppSight\Bin\ExInst.dll
unloaded from 0x65fe0000
[12/6/2007 5:43:30 PM] First chance exception - 0xc0000005 caused by thread
with system id 8196
[12/6/2007 5:43:30 PM] C:\Program Files\BMC
Software\AppSight\Bin\TrigActClient.dll unloaded from 0x67870000
[12/6/2007 5:43:30 PM] First chance exception - 0xc0000005 caused by thread
with system id 8196
[12/6/2007 5:43:30 PM] C:\Program Files\BMC Software\AppSight\Bin\CdInfo.dll
unloaded from 0x65aa0000
[12/6/2007 5:43:30 PM] First chance exception - 0xc0000005 caused by thread
with system id 8196
[12/6/2007 5:43:30 PM] C:\Program Files\BMC
Software\AppSight\Bin\IISHandler.dll unloaded from 0x66130000
[12/6/2007 5:43:30 PM] First chance exception - 0xc0000005 caused by thread
with system id 8196
[12/6/2007 5:43:30 PM] C:\Program Files\BMC Software\AppSight\Bin\VLInfo.dll
unloaded from 0x67b50000
[12/6/2007 5:43:30 PM] First chance exception - 0xc0000005 caused by thread
with system id 8196
[12/6/2007 5:43:30 PM] C:\Program Files\BMC
Software\AppSight\Bin\AsyncInfo.dll unloaded from 0x652b0000
[12/6/2007 5:43:30 PM] First chance exception - 0xc0000005 caused by thread
with system id 8196
[12/6/2007 5:43:30 PM] C:\Program Files\BMC
Software\AppSight\Bin\BbxOsDepNTS.dll unloaded from 0x65950000
[12/6/2007 5:43:30 PM] First chance exception - 0xc0000005 caused by thread
with system id 8196
[12/6/2007 5:43:30 PM] C:\Program Files\BMC
Software\AppSight\Bin\ClientSideTraceComponents.dll unloaded from 0x65c40000
[12/6/2007 5:43:30 PM] First chance exception - 0xc0000005 caused by thread
with system id 8196
[12/6/2007 5:43:30 PM] C:\Program Files\BMC
Software\AppSight\Bin\DNLoader.dll unloaded from 0x65fa0000
[12/6/2007 5:43:30 PM] First chance exception - 0xc0000005 caused by thread
with system id 8196
[12/6/2007 5:43:30 PM] C:\Program Files\BMC
Software\AppSight\Bin\GlobInfo.dll unloaded from 0x66050000
[12/6/2007 5:43:30 PM] First chance exception - 0xc0000005 caused by thread
with system id 8196
[12/6/2007 5:43:30 PM] First chance exception - 0xc0000005 caused by thread
with system id 8196
[12/6/2007 5:43:30 PM] First chance exception - 0xc0000005 caused by thread
with system id 8196
[12/6/2007 5:43:30 PM] First chance exception - 0xc0000005 caused by thread
with system id 8196
[12/6/2007 5:43:30 PM] First chance exception - 0xc0000005 caused by thread
with system id 8196
[12/6/2007 5:43:30 PM] C:\Program Files\BMC Software\AppSight\Bin\MgInst.dll
unloaded from 0x66840000
[12/6/2007 5:43:30 PM] C:\Program Files\BMC
Software\AppSight\Bin\InfrastructureStat.dll unloaded from 0x661d0000
[12/6/2007 5:43:30 PM] C:\Program Files\BMC
Software\AppSight\Bin\InstrRuntime.dll unloaded from 0x661f0000
[12/6/2007 5:43:30 PM] C:\Program Files\BMC Software\AppSight\Bin\SDCore.dll
unloaded from 0x67040000
[12/6/2007 5:43:30 PM] C:\WINDOWS\system32\SHELL32.dll unloaded from
0x7c8d0000
[12/6/2007 5:43:30 PM] Thread exited. Exiting thread system id - 8196. Exit
code - 0x00000000
[12/6/2007 5:43:30 PM] Thread exited. Exiting thread system id - 3280. Exit
code - 0xfffffffe
[12/6/2007 5:43:30 PM] Thread exited. Exiting thread system id - 7372. Exit
code - 0xfffffffe
[12/6/2007 5:43:30 PM] Thread exited. Exiting thread system id - 5792. Exit
code - 0xfffffffe
[12/6/2007 5:43:30 PM] Thread exited. Exiting thread system id - 4404. Exit
code - 0xfffffffe
[12/6/2007 5:43:30 PM] Thread exited. Exiting thread system id - 8320. Exit
code - 0xfffffffe
[12/6/2007 5:43:30 PM] Thread exited. Exiting thread system id - 5032. Exit
code - 0xfffffffe
[12/6/2007 5:43:30 PM] Thread exited. Exiting thread system id - 5332. Exit
code - 0xfffffffe
[12/6/2007 5:43:30 PM] Thread exited. Exiting thread system id - 404. Exit
code - 0xfffffffe
[12/6/2007 5:43:30 PM] Thread exited. Exiting thread system id - 7112. Exit
code - 0xfffffffe
[12/6/2007 5:43:30 PM] Process exited. Exit code - 0xfffffffe

--
Gonzo

David Wang

unread,

Dec 8, 2007, 7:39:01 PM12/8/07

What are you trying to do?

IIS never defined an extension point for w3wp.exe termination code
since it executes user-code, not to be trusted. So, this "lack of
information" is by-design.

Manually or Automatically recycling Application Pool is considered
expected and not logged by default.

IIS logs events for *unexpected* process termination by default. These
events take into account internal IIS state that you never have access
to (since there's no extensibility point). You can base your logging
based on presence of those events, instead of process exit code. You
can also configure IIS to log events for all process recycling on a
per-AppPool basis (LogEventOnRecycle - not exposed in the UI). You can
also configure IIS to execute commands when an Application Pool
unexpectedly terminates (OrphanActionExe and OrphanActionParams - not
exposed in the UI). These are some of the advanced/esoteric things not
exposed in the UI because it would be confusing for most people.

Basically, there are lots of better ways to do what you want,
depending on what you want to do.

//David
http://w3-4u.blogspot.com
http://blogs.msdn.com/David.Wang
//

> C:\WINDOWS\WinSxS\x86_Microsoft.Windows.Common-Controls_6595b64144ccf1df_6.-0.3790.2778_x-ww_A8F04F11\comctl32.dll loaded at 0x77420000

> C:\WINDOWS\WinSxS\x86_Microsoft.VC80.CRT_1fc8b3b9a1e18e3b_8.0.50727.42_x-ww-_0DE06ACD\MSVCR80.dll loaded at 0x78130000

> C:\WINDOWS\WinSxS\x86_Microsoft.VC80.CRT_1fc8b3b9a1e18e3b_8.0.50727.42_x-ww-_0DE06ACD\MSVCR80.dll unloaded from 0x78130000

Gonzo

unread,

Dec 10, 2007, 4:14:06 PM12/10/07

Hello David. We have a third party vendor software that monitors our
servers. One of the things it does is create a log file when ever a process
exits with a non zero return code. The software considers a non zero return
to be an error. Most of our AppPools are set to the default of "Shutdown
worker processes after being idle for 20 minutes". I am being overran at the
moment by log files because we are getting 20 exits over an 8 to 10 day. It
will be a lot more when we run it 24 x 7. Since it is a non zero return and
appears on the surface to be some kind of an error, I am trying to track down
why and what is happening. I also get the same return if I manually recycle
one of the pools. Someone on the net has said that 0xfffffffe means a
graceful exit to a worker process. Do you know why the exiting process would
return 0xfffffffe instead of zero for a successful exit? I am just trying to
figure out if we have a problem with our applications.

Thanks for your feedback and any insight you can give me.

Ken
--
Gonzo

David Wang

unread,

Dec 10, 2007, 4:33:39 PM12/10/07

Can you configure the third party software to not monitor w3wp.exe for
this shutdown code check. It does not make sense for w3wp.exe.

You care about the status of w3wp only when you get an event log entry
when IIS recycles the worker process, indicating non-expected issue.
This is the default behavior.

This third party software is also pretty broken/useless if it only
considers non-zero error code as error. I can think of many useful
tools which use non-zero error code to indicate forms of success. It
should be configurable to choose which error codes are ok for what
process name as well as which process names to exclude.

//David
http://w3-4u.blogspot.com
http://blogs.msdn.com/David.Wang
//

> > > C:\WINDOWS\WinSxS\x86_Microsoft.Windows.Common-Controls_6595b64144ccf1df_6.--0.3790.2778_x-ww_A8F04F11\comctl32.dll loaded at 0x77420000

> > > C:\WINDOWS\WinSxS\x86_Microsoft.VC80.CRT_1fc8b3b9a1e18e3b_8.0.50727.42_x-ww--_0DE06ACD\MSVCR80.dll loaded at 0x78130000

> > > [12/6/2007 5:43:22 PM] c:\windows\system32\inetsrv\w3isapi.dll
>

> ...
>
> read more >>- Hide quoted text -
>
> - Show quoted text -

0 new messages