为应用程序池“Classic .NET AppPool”提供服务的进程与Windows进程激活服务发生致命的通信错误 [英] A process serving application pool 'Classic .NET AppPool' suffered a fatal communication error with the Windows Process Activation Service

问题描述

我在Windows Server 2008上的IIS 7上运行ASP.NET 3.5 Web应用程序。

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错误503.该服务不可用。

我查了一下事件日志并发现：

I looked in the Event logs and discovered that:

服务应用程序池'Classic .NET AppPool'的进程与Windows进程激活服务发生致命的通信错误。进程ID为'3328'。数据字段包含错误编号。

以下是该事件的完整详细信息：

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:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-WAS" Guid="{5 .. 0}" EventSourceName="WAS" />
    <EventID Qualifiers="32768">5011</EventID>
    <Version>0</Version>
    <Level>3</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2009-09-18T13:58:31.000Z" />
    <EventRecordID>23552</EventRecordID>
    <Correlation />
    <Execution ProcessID="0" ThreadID="0" />
    <Channel>System</Channel>
    <Computer>computername</Computer>
    <Security />
  </System>
  <EventData>
    <Data Name="AppPoolID">Classic .NET AppPool</Data>
    <Data Name="ProcessID">3328</Data>
    <Binary>6D000780</Binary>
  </EventData>
</Event>

这导致：

应用程序池Classic .NET AppPool由于为该应用程序池提供服务的过程中出现一系列故障而被自动禁用。

以下是该事件的完整详情：

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:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-WAS" Guid="{5 .. 0}" EventSourceName="WAS" />
    <EventID Qualifiers="49152">5002</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2009-09-18T14:03:05.000Z" />
    <EventRecordID>23557</EventRecordID>
    <Correlation />
    <Execution ProcessID="0" ThreadID="0" />
    <Channel>System</Channel>
    <Computer>computername</Computer>
    <Security />
  </System>
  <EventData>
    <Data Name="AppPoolID">Classic .NET AppPool</Data>
    <Binary>
    </Binary>
  </EventData>
</Event>

结束于：HTTP错误503.该服务不可用。

Concluding in the: HTTP Error 503. The service is unavailable.

有人请帮助我确定这是怎么发生的，以及我需要做些什么来阻止它在将来发生。

Would someone please help me to identify how this happened and what I need to do to prevent it from happening in the future.

推荐答案

这个是一个非常令人讨厌的。我建议您使用 IIS Debug Diagnostics 工具。您可以通过关闭应用程序池属性中的快速失败保护来缓解症状，但这只会掩盖问题。发生了什么事情是你的应用程序经常/如此频繁地经历异常，以至于服务自行关闭。您需要运行诊断工具来捕获进出的所有内容，以找到发生的异常。

This one is a pretty nasty one. I recommend getting the IIS Debug Diagnostics tools. You can probably alleviate the symptom by turning off "Rapid Fail Protection" in the properties of your application pool, but that will just mask the problem. What is going on is that your application is experiencing an exception so often/so repeatedly that the service shuts itself off. You'll need to run the diagnostic tool to capture everything going in and out to find the exception that's occuring.

这可能是一项非常费力的任务，因为该工具将收集筛选的千兆字节垃圾。如果你很幸运，关闭快速失败保护可能会允许异常进入浏览器，但我的猜测是服务器最终会挂起。

This can be a very laborious task because the tool will gather gigabytes of junk to sift through. If you're lucky, the turning off of the "Rapid Fail Protection" might allow the exception to proceed through to the browser, but my guess is that the server will just end up hanging.

这篇关于为应用程序池“Classic .NET AppPool”提供服务的进程与Windows进程激活服务发生致命的通信错误的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！