IIS7:处理应用程序池'YYYYY遇到致命的通信错误的Windows进程激活服务 [英] IIS7: A process serving application pool 'YYYYY' suffered a fatal communication error with the Windows Process Activation Service

查看:1630
本文介绍了IIS7:处理应用程序池'YYYYY遇到致命的通信错误的Windows进程激活服务的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我们正在运行的是32位的Windows Server 2008的7.我们正在尝试发布一个asp.net web应用4.0和IIS版本,到目前为止,我们的努力只取得了SERVERLOG一些警告,甚至没有停止4.0 applicationpool结果
结果
进程服务应用程序池ASP.NET v4.0的遇到致命的通信错误的Windows进程激活服务。进程ID是1904年。数据字段包含错误号。

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 applicationpool

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.

该应用程序下4.0应用程序池,默认网站下运行。我们也有一些较旧的.asp的完美运行。
甚至尝试发布一个荒芜时(读。只有1行文字)的.aspx文件无疾而终......我们已经很久以来用完就做什么,因此任何形式的输入将apritiated的想法...

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 apritiated...

推荐答案

确保每个应用程序池在IIS中,在高级设置有启用32位应用程序设置为true

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

这篇关于IIS7:处理应用程序池'YYYYY遇到致命的通信错误的Windows进程激活服务的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
相关文章
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆