Is The Data Field Contains The Error Number

here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and a process serving application pool suffered a fatal communication error 5011 policies of this site About Us Learn more about Stack Overflow the

Suffered A Fatal Communication Error With The Windows Process Activation Service 5011

company Business Learn more about hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users

A Process Serving Application Pool Suffered A Fatal Communication Error With The World Wide Web

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

6d000780

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. 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. 8007006d 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 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.5k23181212 asked Oct 16 '08 at 6:52 massimogentilini 2,53732130 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 B

Microsoft Tech Companion App Microsoft Technical Communities Microsoft Virtual Academy Script Center Server and Tools Blogs TechNet Blogs   TechNet Flash Newsletter TechNet Gallery TechNet Library TechNet Magazine TechNet Subscriptions TechNet Video TechNet Wiki Windows Sysinternals Virtual Labs Solutions how to use the debug diagnostics tool to troubleshoot a process that has stopped responding in iis Networking Cloud and Datacenter Security Virtualization Downloads Updates Service Packs Security Bulletins Windows Update a process serving application pool 'defaultapppool' suffered a fatal communication error Trials Windows Server 2012 R2 System Center 2012 R2 Microsoft SQL Server 2014 SP1 Windows 8.1 Enterprise See all trials » Related 0x800703e9 iis Sites Microsoft Download Center TechNet Evaluation Center Drivers Windows Sysinternals TechNet Gallery Training Training Expert-led, virtual classes Training Catalog Class Locator Microsoft Virtual Academy Free Windows Server 2012 courses Free Windows 8 courses SQL Server training http://stackoverflow.com/questions/207617/how-to-diagnose-iis-fatal-communication-error-problem Microsoft Official Courses On-Demand Certifications Certification overview MCSA: Windows 10 Windows Server Certification (MCSE) Private Cloud Certification (MCSE) SQL Server Certification (MCSE) Other resources TechNet Events Second shot for certification Born To Learn blog Find technical communities in your area Support Support options For business For developers For IT professionals For technical support Support offerings More support Microsoft Premier Online TechNet Forums MSDN Forums Security Bulletins & Advisories Not an IT pro? https://technet.microsoft.com/en-us/library/cc735151(v=ws.10).aspx Microsoft Customer Support Microsoft Community Forums United States (English) Sign in Home Windows Server 2012 R2 Windows Server 2008 R2 Library Forums We’re sorry. The content you requested has been removed. You’ll be auto redirected in 1 second. Internet Information Services (IIS) 7.0 IIS Windows Process Activation Service (WAS) IIS Application Pool IIS Application Pool IIS Application Pool Availability IIS Application Pool Availability IIS Application Pool Availability IIS Worker Process IIS Application Pool Availability Event ID 1026 Event ID 1027 Event ID 1084 Event ID 1089 Event ID 2297 Event ID 2299 Event ID 5002 Event ID 5009 Event ID 5010 Event ID 5011 Event ID 5012 Event ID 5013 Event ID 5014 Event ID 5015 Event ID 5021 Event ID 5025 Event ID 5039 Event ID 5054 Event ID 5057 Event ID 5059 Event ID 5082 Event ID 5091 Event ID 5101 Event ID 5104 Event ID 5107 Event ID 5127 Event ID 5144 Event ID 5145 Event ID 5146 Event ID 5160 Event ID 5163 Event ID 5164 Event ID 5184 Event ID 5190 IIS Application Pool Configuration IIS Application Pool Recycling TOC Collapse the table of content Expand the table of content This documentation is archived and is not being maintained. This documentation is archived and is not being maintained. IIS

I'm not yet clear what I did, but I'm blogging it so it can be found if someone else has this issue. For whatever reason, last week both of my Vista 64-bit machines suddenly stopped being able to start IIS (Internet Information http://www.hanselman.com/blog/FixedWindowsProcessActivationServiceWASIsStoppingBecauseItEncounteredAnError.aspx Server). The service just wouldn't start. I started getting this error instead "Cannot start service https://sysadminspot.com/server-administration/isapi-filter-cwindowsmicrosoft-netframeworkv4-0-30319aspnet_filter-dll-could-not-be-loaded-due-to-a-configuration-problem/ W3SVC on Computer '.'" which wasn't too helpful. A visit to the System Event Log via the Event Viewer in Computer Management told me these four errors: "The World Wide Web Publishing Service service depends on the Windows Process Activation Service service which failed to start because of the following error: The system cannot find the file specified." and "The Windows a process Process Activation Service service terminated with the following error: The system cannot find the file specified." and "Windows Process Activation Service (WAS) is stopping because it encountered an error. The data field contains the error number." and "The directory specified for the temporary application pool config files is either missing or is not accessible by the Windows Process Activation Service. Please specify an existing directory and/or ensure that it has proper access flags. The data field suffered a fatal contains the error number." Unfortunately there's little information to go on in any of these error messages. However, it's clear (as mud) from the last error that there's a directory missing or not accessible. I'll add "anymore" to that because it worked before. That means that something changed. If IIS won't start because Windows Process Activation Service won't start, then I need to get WAS started up first. However, I don't know what directory it doesn't have access to. I can see from the Services application that WAS isn't its own executable, but rather lives inside of an instance of svchost.exe, where a lot of services live. So I'll fire up Process Monitor and set the filters (filters are VERY important if you want to avoid being overwhelmed quickly in procmon) to show only svchost.exe processes. Even still, there's a lot of svchost.exe processes out there and they will quickly fill the monitor up. I'll need to setup some strategic (read: guessed) highlighting as well. The hotkey to stop capturing in procmon.exe is Ctrl-E. Basically I'll clear the screen, hit Ctrl-E to capture, try to start WAS (pronounced WAAZ), watch it fail, the stop capture with Ctrl-E. Based on the vague message about application pools temporary files and a directory I'll make a guess and configure highlighting to find paths that contain "temp," "log," "config" or "a

‘C:\Windows\Microsoft.NET\Framework\v4.0.30319\\aspnet_filter.dll' could not be loaded due to a configuration problem Posted on November 18, 2012 by Brendan in Server Administration, WindowsProblemAfter monthly server patching, I also made some security enhancements to the web.config files in the C:\Windows\Microsoft.NET\FrameworkXX\vXXX\CONFIG\ directories. It was therefore important that I test both 32bit and 64bit application pool modes. I found that tests running 64bit mode were suddenly failing with the following error message:ISAPI Filter ‘C:\Windows\Microsoft.NET\Framework\v4.0.30319\\aspnet_filter.dll' could not be loaded due to a configuration problem. The current configuration only supports loading images built for a AMD64 processor architecture. The data field contains the error number. To learn more about this issue, including how to troubleshooting this kind of processor architecture mismatch error, see http://go.microsoft.com/fwlink/?LinkId=29349.It was of no surprise what so ever that the link included in the error message was 100% useless (thanks again Microsoft). One article I found suggested I uninstall .NET 4 - that's like turning a monitor off to fix a dead pixel.SolutionUpon closer inspection of the error message I noticed the problem:v4.0.30319\\aspnet_filter.dllWindows doesn't handle double slashes very well as opposed to Linux. What is strange is none of these settings are manually changed which suggests it was perhaps a Windows update that caused this, however I have no evidence beyond change control logs.I fixed with the following process:Opened IIS Manager and selected the IIS web server node:In the middle pane, browse to the IIS section and select ISAPI Filters:Expand the columns as required, looking for an Executable path with \\ in it, then click Edit:From the above screenshot, change the \\ to \ so the path reads:C:\Windows\Microsoft.NET\Framework\v4.0.30319\aspnet_filter.dllJust keep in mind that the folders Framework and Framework64 or the .NET version may change depending on your implementation.After clicking OK, all my testing started to work again and the 500 Internal Server errors went away.ConclusionA possible Microsoft update (exact cause unknown) made an error updating an existing or installing a new ISAPI handler to IIS. By mishandling the path, it inserted \\ instead of \ into the executable path causing IIS to be unable to load the filter.This caused 500 Internal Server error