The application pool serving process "{0}" has experienced a fatal communication error with Windows Activation Service. How to get a landfill?

I have a standalone standalone server running Windows Server 2008 with Service Pack 2 (64 bit) and IIS7. It runs an ASP.NET website created against .NET 3.5 in its own application pool. Accidentally at different times of the day I get the above error. This may occur once a day or more. Often, when this happens, it happens two or three times in a relatively quick sequence.

Examining the processes and logs leading to the failure does not seem to cause a real template or a specific script that causes it.

Of the searches, most of the recommendations seem to be to get a crash dump and analyze it, however I am trying my best to get it.

I have Debug Diagnostics 1.2 installed and tried various settings for the failure rules, but they do not create userdump. Currently, I have a Failure rule for all processes related to IIS / COM + with an extended default configuration.

Can anyone suggest why this does not create a crash when a problem occurs? Is there any other way to get a crash dump?

EDIT: I installed the Debugging Tools according to this useful link and start ADPlus with this command:

ADPlus -crash -pn w3wp.exe -oc:\ADplusCrashDump 

I hope I get an emergency dump when it happens again.,.

EDIT. 2: a recursive method call was found that caused a stack overflow in rare cases. I hope the problem is resolved. However, I found another useful link, see This Blog Post .

+3
source share

Source: https://habr.com/ru/post/952628/


All Articles