The "ultimate Solution" process for application pool "XXX" has a critical error communicating with Windows process Activation service. The process ID is "XXXX". The data field contains the error number.

The mistake that bothered me for half a year, was solved by accident today, hereby share to the friend who is tangled by the same problem!

Previous help posts, no answer:

Http://www.cnblogs.com/freeton/archive/2012/08/28/2660585.html

http://bbs.csdn.net/topics/391988642

Symptoms

A large number of errors in the log, IIS critical error, such errors by default 5 minutes consecutive 5 times will cause the IIS application pool to hang up, after the application is basically discarded, the higher the traffic, the faster the hang!

One way to temporarily remediate this error is to adjust the application pool Service Unavailable response type to Tcplevel so that the application pool does not hang, but the problem persists.

Analyze Symptoms

0, search, basically is this solution http://www.cnblogs.com/freeton/archive/2012/08/28/2660585.html, fart use not in

1, according to the direct thinking, the feeling should be the server configuration where the problem, should be the local debugging environment, has never encountered this problem, and then replace the server, winserver08=>winserver2012 R2 helpless problem still

2, obediently Analysis of the above log errors, in the system log and w3p logs are not seen in the description of the exception. The above event exception hint, the exception code is 0XC00000FD , interpreted as a stack overflow, the basic assertion is that the program is a certain location out of the problem, it is likely that the dead loop caused, but the specific problem, it is impossible to find

3, understand that you can also directly track the cause of IIS crash through the DMP file

Locate the DMP file

What is a DMP file? Own Baidu. Simply say that the black box, recording the operation before the crash, then how to find this black box?

1. Start Windows Error Reporting Service

2, execute the following registry script, set W3wp.exe crash automatically grab DMP files, saved in the D:\dumps folder

Windows Registry Editor Version 5.00

[Hkey_local_machine\software\microsoft\windows\windows Error Reporting\localdumps\w3wp.exe]
"Dumpfolder" =hex (2): 64,00,3a,00,5c,00,64,00,75,00,6d,00,70,00,73,00,00,00
"Dumpcount" =dword:00000002
"Dumptype" =dword:00000002

3. View DMP Files

After IIS crashes, you can see the DMP file in the D:\dumps folder, which you can use to analyze the DMP file to find out why IIS crashed.

Debugging DMP Files

How to debug DMP file, this will have to please out of the universe first Ide,vs, I use the vs2013 to debug, you can directly open the DMP file

1, double-click DMP file will go directly to VS, you can see summary information

2. Optional step: Set Symbol Path

3, set the associated source code path (can be ignored)

4. All ready, click "Debug Managed Memory"

5, check the specific cause of the exception, locate the exception code location

Open local variables and stack debugging, exception code location inside! Then just find this big bug kill it! The event record is finally refreshing!

Grateful for the first ide! of the universe

The "ultimate Solution" process for application pool "XXX" has a critical error communicating with Windows process Activation service. The process ID is "XXXX". The data field contains the error number.