How can I debug when an app pool encounters fatal communication error that did not create dump file when crashing?

0

An app pool is crashing with the error "A process serving application pool 'appPoolName' suffered a fatal communication error with the Windows Process Activation Service. The process id was 'id'. The data field contains the error number."

When other app pools crash in that machine, they create a dump file and also log another event in the event viewer that says something like - "Faulting application name: w3wp.exe, version: 10.0.XXX.0, time stamp: 0x57899b8a Faulting module name: clr.dll, version: 4.8, time stamp: 0XXXXX Exception code: 0xc00000fd"

What can crash the app pool without a dump file and without logging the faulting application name and details in the event viewer ?

.net
iis
w3wp
asked on Stack Overflow Aug 26, 2020 by ajp • edited Aug 26, 2020 by ajp

0 Answers

Nobody has answered this question yet.


User contributions licensed under CC BY-SA 3.0