IIS7: A process serving application pool 'YYYYY' suffered a fatal communication error with the Windows Process Activation Service

asp.netIis 7Windows Server-2008Http Status-Code-503

asp.net Problem Overview

We're running a 32-bit Windows server 2008 with an IIS version of 7.
We're attempting to publish an asp.net 4.0 webapp and so far our attempts have only yielded a few warnings in the serverlog without even stopping the 4.0 application pool

>A process serving application pool 'ASP.NET v4.0' suffered a fatal communication error with the Windows Process Activation Service. The process id was '1904'. The data field contains the error number.

The application is running under a 4.0 app-pool and under the default website.
We've also got some older .asp's running flawlessly.
Even when attempting to publish a barren (read. only 1 line of text) .aspx-file it failed miserably... We've since long run out of ideas on what to do so any form of input would be appreciated...

asp.net Solutions

Solution 1 - asp.net

Make sure that each Application Pool in IIS, under Advanced Settings has Enable 32 bit Applications set to True

IIS screenshot

Solution 2 - asp.net

I was debugging the problem for the better part of the day and when I was close to burning the building I discovered the Process Monitor tool from Sysinternals.

Set it to monitor w3wp.exe and check last events before it exits after you fire a request in the browser. Hope that helps further readers.

Solution 3 - asp.net

Debug Diagnostics Tool (DebugDiag) can be a lifesaver. It creates and analyze IIS crash dumps. I figured out my crash in minutes once I saw the call stack. https://support.microsoft.com/en-us/kb/919789

Solution 4 - asp.net

When I had this problem, I installed 'Remote Tools for Visual Studio 2015' from MSDN. I attached my local VS to the server to debug.

I appreciate that some folks may not have the ability to either install on or access other servers, but I thought I'd throw it out there as an option.

Solution 5 - asp.net

I ran into this recently. Our organization restricts the accounts that run application pools to a select list of servers in Active Directory. I found that I had not added one of the machines hosting the application to the "Log On To" list for the account in AD.

Solution 6 - asp.net

For me the problem was a configuration file that was missing an Element.

Categories
Recommended asp.net Solutions
Recommended Iis 7 Solutions
Recommended Windows Server-2008 Solutions
Recommended Http Status-Code-503 Solutions

Previous Solution:

How to move (and overwrite) all files from one directory to another?

LinuxUnix

Next Solution:

e.printStackTrace(); in string

JavaAndroidStack Trace

Attributions

All content for this solution is sourced from the original question on Stackoverflow.

The content on this page is licensed under the Attribution-ShareAlike 4.0 International (CC BY-SA 4.0) license.

Content TypeOriginal AuthorOriginal Content on Stackoverflow
QuestionEnrorView Question on Stackoverflow
Solution 1 - asp.netPeter BrombergView Answer on Stackoverflow
Solution 2 - asp.netGrozzView Answer on Stackoverflow
Solution 3 - asp.netmhenry1384View Answer on Stackoverflow
Solution 4 - asp.netDan AtkinsonView Answer on Stackoverflow
Solution 5 - asp.netJMMView Answer on Stackoverflow
Solution 6 - asp.netJonView Answer on Stackoverflow