IIS 7 and Above
A process serving application pool 'XXXX' suffered a fatal communicat...
Last post Feb 07, 2019 06:17 AM by Jalpa Panchal
Feb 06, 2019 09:35 AM|Luck Besozzi|LINK
recently, checking the event viewer of our web server Windows 2012 R2, I realized this warning generated by one of our site:
Event ID: 5011 A process serving application pool 'XXXX' suffered a fatal communication error with the Windows Process Activation Service. The process id was 'YYYYY'. The data field contains the error number.
We are currently investigating, we have also tried some solutions that we read online, without success.
However, my question is, does this warning cause a recycle or an AppPool crash?
Our WS is based on Windows 2012 R2 build 9600 with the latest update installed, .Net CLR Version v4.0.30319.
Thank in advanced.
Feb 06, 2019 03:31 PM|lextm|LINK
Feb 07, 2019 06:17 AM|Jalpa Panchal|LINK
A worker process that fails to respond may exhibit one of the following symptoms:
Communication failure with WAS.
Worker process startup time-out.
Worker process shutdown time-out.
Worker process orphan action failure.
To diagnose a worker process that is failing to respond, refer to one or more of the following resources:
How to use the Debug Diagnostics tool to troubleshoot a process that has stopped responding in IIS
How to use the IIS Debug Diagnostics tool to troubleshoot a memory leak in an IIS process
How to use the Debug Diagnostics Tool to troubleshoot high CPU usage by a process in IIS
To perform this procedure, you must have membership in Administrators , or you must have been delegated the appropriate authority.
To verify that an application pool has started:
1.Click Start , click Control Panel , and then click Administrative Tools
2.Right-click Internet Information Services (IIS) Manager and select Run as administrator
3.In the Connections pane, expand the server node and select Application Pools
4.In Features View , the Status column for the application pool will indicate
Started if the application pool has started.
You could also see the below article related to the issue: