※ Download: Windows process activation service
Regards, Ivy Ivy Hi, Could you please paste the contents in the error event logs? A system error has occurred System error 6801 has occur Transaction support within the specified resources manager is not started or was shut down due to an error. To resolve this issue, please ensure that the applicationhost.
After I run the capture, I scroll around looking for suspicious stuff. Performance Counters All IIS performance counters get funneled through WAS.
- This can be beneficial to other community members reading the thread.
Introduction If you observe either of the following events under the system logs in Event Viewer, then this article is meant for you. A process serving application pool '%1' suffered a fatal communication error with the Windows Process Activation Service. The process id was '%2'. The data field contains the error number. A process serving application pool '%1' terminated unexpectedly. The process id was '%2'. The process exit code was '%3'. This is a clear indication of an application pool crash issue wherein something went wrong within the application and the application pool had to be terminated. Once the application pool is terminated, its corresponding w3wp process is also terminated. Ideally, when an application pool crashes, in order to honor the incoming requests, a new w3wp process gets spawned up automatically. However, if the application pool crashes more than 5 times within a period of 5 minutes, then the application pool goes into a stopped state. You will have to restart the application pool manually to get it up and running. You will observe the following event under system logs in Event Viewer if something similar happens. Application pool '%1' is being automatically disabled due to a series of failures in the process es serving that application pool. Capture Dumps Now that we know that our application pool has crashed, the next step is to determine why exactly it crashed. In order to determine this, we will have to capture a dump of the w3wp process just before it terminates. There are multiple ways to do this. You can set up WER, procdump and Debug Diag to capture a crash dump. In this article, I will discuss only the Debug Diag way of capturing data. Debug Diag This is by far the easiest and the most sophisticated tool to capture a crash dump of an application pool. This is how we set it up. You can download it from. You might also receive a pop up indicating that the IIS management compatibility feature is not installed and that the application pools will not be listed. Just click on OK and type in the application name manually in the above window. Action Type indicates the type of dump that would be captured. A mini user dump will not provide complete information of the issue as it captures very minimal data of the w3wp process. Action Limit indicates the number of dumps that this rule will capture. The size of each dump file will be the same as that consumed by w3wp process in the memory. So, keeping that in mind, place the dumps in a drive that has enough free disk space. As soon as the issue occurs, the dump count will increase and a corresponding dump file will be generated. PS: A normal recycle of the application pool will also trigger a dump. This is because when the application pool recycles, its corresponding w3wp process's PID changes and hence a dump gets generated. This is a false positive dump and will not help in the analysis of the application pool crash issue. So whenever you see an increment in the userdump count, check the event logs to see if the above mentioned crash events have occurred. If yes, then the dump that has been captured is correct. Dump Analysis Once the dump is captured, you can use the Debug Diag Analysis executable to analyse the captured crash dump. Make sure you have the symbol path set right. Once the report is generated, you can open it in IE and understand the call stack of the thread that triggered the Breakpoint Expression.
The questions still remain unanswered. Then when the server comes back up go ahead and add back the IIS components, you will not have to recheck Windows Process Activation Service, it will automatically get added when you reinstall IIS. Wow, I Googled all over and I KNOW I'm good at Googling and I couldn't find a darn thing. Provides helper functions for the process host. Windows process activation service Pool State Management Application Pools can be stopped, recycled or started via publicly available API's, e. After all, we have two app pools recycling at 3:05 and at 3:10 which spawn the error, yet Nagios reports a socket time-out on a third application, one which has never reported this warning. The Windows Process Activation Service WAS will not start on my Windows 10 PC anymore.
