进程服务应用程序池“经典.net程序池遇到致命的通信错误的Windows进程激活服务。 HTTP错误503 [英] A process serving application pool 'Classic .NET AppPool' suffered a fatal communication error with the Windows Process Activation Service. HTTP Error 503
问题描述
我在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服务不可用。
HTTP Error 503. The service is unavailable.
我看着在事件日志中，发现：
I looked in the Event logs and discovered that:
进程服务应用程序池经典.net程序池遇到致命的通信错误的Windows进程激活服务。进程ID是'3328'。数据字段包含错误号。
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.
下面是该事件的全部细节：
Here is the full details of that event:
登录名称：系统
来源：Microsoft-Windows的WAS
日期：18/09/2009 14点58分31秒
事件ID：5011
任务类别：无
级别：警告
关键字：经典
用户：N / A
计算机：计算机名
描述：
进程服务应用程序池经典.net程序池遇到致命的通信错误的Windows进程激活服务。进程ID是'3328'。数据字段包含错误号。
事件XML：
5011
0
3
0
0
0x80000000000000
23552
系统
计算机名
经典.net程序池
3328
6D000780
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
这导致：
应用程序池经典.net程序池'被自动由于服务于该应用程序池的过程（ES）一系列的失败禁用。
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:
登录名称：系统
来源：Microsoft-Windows的WAS
日期：18/09/2009 15时03分05秒
事件ID：5002
任务类别：无
级别：错误
关键字：经典
用户：N / A
计算机：计算机名
描述：
应用程序池经典.net程序池'被自动由于服务于该应用程序池的过程（ES）一系列的失败禁用。
事件XML：
5002
0
2
0
0
0x80000000000000
23557
系统
计算机名
经典.net程序池
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
结论的：HTTP错误503服务不可用
Concluding in the: HTTP Error 503. The service is unavailable.
会有人请帮我找出如何发生的，以及我需要在将来发生的事情做，以prevent它。
Would someone please help me to identify how this happened and what I need to do to prevent it from happening in the future.
感谢。
亲切的问候
沃尔特
推荐答案
这一个是pretty讨厌之一。我建议得到了 IIS调试诊断工具。您可以在您的应用程序池的属性关闭快速失败保护可能缓解症状，但只是掩盖了问题。这是怎么回事是您的应用程序正在经历一个异常所以经常/如此反复，该服务自行关闭。你需要运行诊断工具来捕捉一切进进出出发现的存在的除外。
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.
这篇关于进程服务应用程序池“经典.net程序池遇到致命的通信错误的Windows进程激活服务。 HTTP错误503的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
