Defaultapppool Fatal Error
Contents |
Web Platform Installer Get Help: Ask a Question in our Forums More Help Resources Blogs Forums Home IIS.NET Forums IIS 7 and Above Setup "fatal communication error" "fatal communication error" RSS 22
Application Pool Suffered A Fatal Communication Error With The Windows Process Activation Service
replies Last post Nov 29, 2012 06:40 PM by Rovastar ‹ Previous Thread|Next a process serving application pool suffered a fatal communication error 5011 Thread › Print Share Twitter Facebook Email Shortcuts Active Threads Unanswered Threads Unresolved Threads Advanced Search Reply topf 5 Posts
A Process Serving Application Pool Suffered A Fatal Communication Error With The World Wide Web
"fatal communication error" Jul 28, 2007 09:21 PM|topf|LINK I am attempting to migrate stable sites from IIS6 running on Server 2003 x64 to a test platfrorm running IIS7 on Server 2008 x64 the data field contains the error number. (June 2007 CTP). Much works Okay, but specific "modules" within the site consistently generate the following event error: "A process serving application pool ['Classic .NET AppPool'] or [DefaultAppPool]*suffered a fatal communication error with the Windows Process Activation Service." * It makes no difference which type of Application Pool is selected, nor whether I "migrate" the sites or not. I would be most grateful for an advice how to use the debug diagnostics tool to troubleshoot a process that has stopped responding in iis on what this error means, and hoe I might setting about resolving it. Richard Issues IIS 7.0 Reply mvolo 647 Posts Re: "fatal communication error" Jul 29, 2007 08:22 PM|mvolo|LINK Richard, Are any of your applications pools on W2k3 configured to run as 32 bit? If so, you'll need to configure the same on IIS7. Are you able to request a simple static file/ASPX pagefrom the default web site? Thanks, Mike Volodarsky Program Manager IIS Core Server Visit mvolo.com for more inside information on IIS7, IIS and ASP.NET Mike Volodarsky CTO at LeanSentry Former IIS/ASP.NET PM Reply topf 5 Posts Re: "fatal communication error" Jul 29, 2007 10:33 PM|topf|LINK Mike No - the W2K3 live site is running 'pure' 64-bit with only x64 asp.net v2.0.50527 allowed as a service extension (and not 32-bit). Yes - There's no problem with static files, nor with various dynamic ascx modules. I don't know how to trace the specific cause of the error, but my best guess is that it relates to a call on a 3rd party, 64-bit dllwhich is works fine under W2K3/IIS6. I hope this makes sense? Apologies if not - I'm an academic rather
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about
Fatal Communication Error With The Windows Process Activation Service Iis 7
hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask 6d000780 Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 4.7 million programmers, just like you, helping each other.
8007006d
Join them; it only takes a minute: Sign up How to diagnose IIS fatal communication error problem up vote 14 down vote favorite 4 I've a a customer using IIS and an application, developed by us, in Asp.NET 1.1. http://forums.iis.net/t/1139442.aspx?+fatal+communication+error+ Monday, for 4 times in a row the error “A process serving application pool 'xxxx' suffered a fatal communication error with the World Wide Web Publishing Service. The process id was 'yyyy'. The data field contains the error number.” appeared. Any idea about how to diagnose this? The only link I've found talks about installing low level debug tools but before proceeding in this kind of low level analysis I would know if someone has a better idea http://stackoverflow.com/questions/207617/how-to-diagnose-iis-fatal-communication-error-problem or a suitable alternative. The problem (from what I can see) is something in the customer environment, because the same application it's installed at other customer sites on at least 20 or 30 different servers and the problem do not happen. Regards Massimo asp.net debugging iis share|improve this question edited Oct 16 '08 at 6:57 Mark Cidade 71.2k23181212 asked Oct 16 '08 at 6:52 massimogentilini 2,51732130 In my case, problem was an unlimited recursive loop in my application code. –Mohsen Unlimited May 19 at 13:47 add a comment| 5 Answers 5 active oldest votes up vote 3 down vote I'm getting the same error, here are some more details: running: Windows Server 2003, IIS 6.0 / ASP 3.0, 2.13 GHz, 1 GB ram My web site is in Beta, so I hardly have any visitors to the site. According to the event viewer I'm getting this warning 3 times every 3 minutes, then it stops for a few hours. Then sometimes I get the error: A process serving application pool 'DefaultAppPool' terminated unexpectedly. The process id was '3900'. The process exit code was '0x800703e9'. which follow by: Application pool 'DefaultAppPool' is being automatically disabled due to a series of failures in the process(es) serving that application pool. Which then causes a 'Service Unavailable' message when browsing to the website. after reading too many post about this issue, I did the follo
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more http://stackoverflow.com/questions/1445566/a-process-serving-application-pool-classic-net-apppool-suffered-a-fatal-commu about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 4.7 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up A process serving application pool 'Classic .NET AppPool' suffered a fatal communication error fatal communication with the Windows Process Activation Service. HTTP Error 503 up vote 29 down vote favorite 12 I am running an ASP.NET 3.5 web application on IIS 7 on Windows Server 2008. I received the following error earlier this afternoon: HTTP Error 503. The service is unavailable. I looked in the Event logs and discovered that: A process serving application pool 'Classic .NET AppPool' suffered a fatal communication error with fatal communication error the Windows Process Activation Service. The process id was '3328'. The data field contains the error number. Here is the full details of that event: Log Name: System Source: Microsoft-Windows-WAS Date: 18/09/2009 14:58:31 Event ID: 5011 Task Category: None Level: Warning Keywords: Classic User: N/A Computer: computername Description: A process serving application pool 'Classic .NET AppPool' suffered a fatal communication error with the Windows Process Activation Service. The process id was '3328'. The data field contains the error number. Event Xml: 5011 0 3 0 0 0x80000000000000 23552 System computername Classic .NET AppPool 3328 6D000780 This resulted in: Application pool 'Classic .NET AppPool' is being automatically disabled due to a series of failures in the process(es) serving that application pool. Here is the full details of that event: Log Name: System Source: Microsoft-Windows-WAS Date: 18/09/2009 15:03:05 Event ID: 5002 Task Category: None Level: Error Keywords: Classic User: N/A Computer: computername Description: Application pool 'Classic .NET AppPool' is being automatically disabled due to a series of failures in the process(es) serving that application pool. Event Xml: 5002 0 2 0 0 0x80000000000000 23557 System computername Classic .NET AppPool Concluding in the: HTTP Error 503. The service is unavailable. Would someone please help me to identify how this