如何诊断IIS致命的通信错误的问题 [英] How to diagnose IIS fatal communication error problem

问题描述

我有一个使用IIS和应用，我们开发，在Asp.NET 1.1客户。周一，在连续4次错误服务应用程序池的方法，XXXX遇到致命的通信错误与万维网发布服务。进程ID是'YYYY。数据字段包含错误号。出现了。

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. The process id was 'yyyy'. The data field contains the error number." appeared.

有关如何诊断这个你知道吗？在<一个href=\"http://blogs.msdn.com/david.wang/archive/2005/08/29/HOWTO_Understand_and_Diagnose_an_AppPool_Crash.aspx\">only链接我发现有关安装水平低调试工具会谈，但在这种低水平的分析，然后再继续，如果有人有更好的主意或合适的替代我会知道的。

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.

问题（从我所看到的）东西在客户环境，因为相同的应用程序它安装在至少20个或30个不同的服务器和问题不会发生在其他客户的网站。

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.

问候

马西莫

推荐答案

我得到了同样的错误，这里有一些更多的细节：

I'm getting the same error, here are some more details:

运行：在Windows Server 2003，IIS 6.0 / ASP 3.0，
2.13 GHz的，1 GB RAM

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.

根据事件查看器中我得到这个警告，每3分钟3次，
然后它停止了几个小时。

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:

进程服务应用程序池DefaultAppPool意外终止。进程ID是'3900'。进程退出code是0x800703e9。

它通过如下：

应用程序池DefaultAppPool'被自动由于服务于该应用程序池的过程（ES）一系列的失败禁用。

在浏览该网站时，然后会导致服务不可用的消息。

Which then causes a 'Service Unavailable' message when browsing to the website.

阅读关于这个问题太多帖子之后，我做了以下步骤：

after reading too many post about this issue, I did the following steps:

1. 我看，这可能是注册表的访问权，所以我安装了一个监控和跟踪所有W3SVC拒绝访问错误，并授予permition

1. I read that it might be registry access right, so I installed a monitor and trace all the W3SVC Access Denied errors and grant permition

我读到了0x800703e9错误意味着在流动堆栈这会导致w3wp.exe的崩溃，我应该安装调试工具，并尝试获取内存转储。
我这样做，但我没有得到任何转储，所以我安装了一个新的调试工具，但没有得到一个崩溃呢。

I read that the 0x800703e9 error means stack over flow which causes a w3wp.exe crash and I should install a Debug tool and try to get a memory dump. I did that but I didn't get any dump, so I installed a new debugging tool, but didn't got a crash yet.

我的网站是做一些数据挖掘这使服务器忙。

My web site is doing some data mining which keeps the server busy.

结论：

1. 我不知道什么是对那里发生的......但我知道，我的服务器计算机的方式来对资源放缓，所以我要升级并重新安装它，我敢肯定，它会解决这个问题...

1. I don't know what is going on there... but I do know that my server machine is way to slow on resource, so I'm going to upgrade and reinstall it, I'm certain that it will solve the problem...

问题发生的时间，甚至当我的.NET code是空闲的，因此它在服务器出了问题，而不是在我的code。

The problem happens all the time, even when my .net code is idle, therefore it is a problem in the server, and not in my code.

我认为，第一WARNNING 进程服务应用程序池......发生的每一段时间，和每一个现在，然后它会导致应用程序池重新启动，因此一个附着调试器并不能帮助 - 进程不断重新启动和调试器不能有效再...
我认为0x800703e9错误（这将导致服务不可用），当应用程序池重新启动，我想，它需要很多，因为我的机器太慢它得到0x800703e9资源和可能发生......因为之前所说，这是一个堆放超过流量，但我认为这是低的资源，而不是由一个无限递归造成的。

I think that the first warnning "A process serving application pool ..." happens every some time, and every now and then it causes the Application Pool to restart, therefore a attaching a debugger doesn't help - the process keeps restarting and the debugger is not effective any longer... I think that the 0x800703e9 error (which causes the Service Unavailable) maybe happens when the app pool restart, I guess that it needs a lot of resource and since my machine is too slow it gets the 0x800703e9 ... as said before this is a stack over flow, but I think that it is caused by low resource and not by an endless recursion.

我认为，这是由微软宣称的注册表访问权成为问题，是废话，但我并没有得到服务不可用，因为所以它可能帮助（以为我仍然得到WARNNING 进程服务应用程序池......）。

I think that the 'registry access right' which is claimed by Microsoft to be the issue, is nonsense, but I didn't got 'Service Unavailable' since so it might helped (thought I still get the warnning "A process serving application pool ..." ).

希望这有助于有人...

Hope this help someone...

这篇关于如何诊断IIS致命的通信错误的问题的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！