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

问题描述

我有一个客户使用IIS和由我们开发的Asp.NET 1.1中的应用程序。星期一，连续4次出现错误服务应用程序池xxxx'与万维网发布服务发生了致命的通信错误。进程ID为'yyyy'。数据字段包含错误编号。出现。

有关如何诊断这个的任何想法？ 只有我发现的链接会谈到安装低级别的调试工具，但在进行这种低级别分析之前，我会知道有人有更好的想法或合适的选择。

问题（从什么我可以看到）是客户环境中的一些东西，因为在至少20或30个不同服务器上的其他客户站点上安装了相同的应用程序，并且不会发生问题。

请问

Massimo

解决方案

这里有一些更多的细节：

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

我的网站是测试版，所以我几乎没有任何访问者的网站。

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

然后有时我会收到错误：

提供应用程序池DefaultAppPool的进程意外终止。进程ID为'3900'。过程退出代码为0x800703e9。

其后跟：

应用程序池DefaultAppPool由于在该应用程序池中运行的一系列故障而被自动禁用。

浏览网站时，服务不可用消息。

在阅读了关于此问题的太多帖子后，我执行了以下步骤：

1. 我读到这可能是注册表访问权限，所以我安装了一个监视器并跟踪所有的W3SVC访问被拒绝的错误并授予权限




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

我的网站正在进行一些数据挖掘，以保持服务器繁忙。

结论：

1. 我不知道那里发生了什么...但是我知道我的服务器机器是资源缓慢的方式，所以我要去升级并重新安装，我确定它会解决问题...




2. 问题一直发生，即使我的.net代码是空闲的，所以这是一个问题在服务器，而不是在我的代码。




3. 我认为第一个警告 ...每隔一段时间发生一次，然后它会导致应用程序池重新启动，因此附加调试器无助于此过程不断重新启动，调试器不再有效。 。
   我认为0x800703e9的错误（哪个导致服务不可用）可能发生在应用程序池重新启动，我想它需要大量的资源，因为我的机器太慢，它得到的0x800703e9 ...如前所述，这是一个堆栈流，但我认为这是由低资源而不是无休止的递归引起的。




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

解决方案

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 Beta, so I hardly have any visitors to the site.

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:

A process serving application pool 'DefaultAppPool' terminated unexpectedly. The process id was '3900'. The process exit code was '0x800703e9'.

which follow by:

Application pool 'DefaultAppPool' is being automatically disabled due to a series of failures in the process(es) serving that application pool.

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

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

Conclusion:

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

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

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

4. 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屋！