如何确定64位服务器上IIS崩溃的原因

I have a .net 2.0 web application that is running on Windows server 2003 Standard x64, using IIS 6.

我有一个使用IIS 6在Windows Server 2003 Standard x64上运行的.net 2.0 Web应用程序。

The application pool for our website started crashing recently and I can't determine why. It started happening on a weekend, and the latest release of the website was several days earlier. I have determined that no other changes were made to the server recently, including code and Microsoft updates.

我们网站的应用程序池最近崩溃了,我无法确定原因。它开始发生在一个周末,该网站的最新版本是几天前发布的。我已经确定最近没有对服务器进行任何其他更改,包括代码和Microsoft更新。

The event log shows the following whenever a crash occurs with no additional information in the data block:

每当发生崩溃而数据块中没有其他信息时,事件日志会显示以下内容:

Faulting application w3wp.exe, version 6.0.3790.3959, stamp 45d691cc, faulting module kernel32.dll, version 5.2.3790.4062, stamp 462643a7, debug? 0, fault address 0x0000000000027d8d.

错误应用程序w3wp.exe,版本6.0.3790.3959,邮票45d691cc,错误模块kernel32.dll,版本5.2.3790.4062,邮票462643a7,调试? 0,故障地址0x0000000000027d8d。

This is running on a x64 server so I can't use any of the standard Debug Diagnostic Tools because even though there is a 64 bit version of it, it only attaches to IIS running in 32 bit mode.

这是在x64服务器上运行,因此我不能使用任何标准的调试诊断工具,因为即使它有64位版本,它也只能连接到以32位模式运行的IIS。

I have tried using the Debugging Tools for Windows (x64) and was able to attach to the w3wp process, and waited for another crash. However, this slowed the server down so much that it was unusable, so I had to stop it.

我尝试使用Windows调试工具(x64),并能够连接到w3wp进程,并等待另一次崩溃。但是,这会使服务器放慢速度以至于无法使用,所以我不得不停下来。

What other methods can I use to try to determine the cause of an IIS crash?

我可以使用哪些其他方法来确定IIS崩溃的原因?

3 个解决方案

#1

Read about ASP.NET 2.0 Crash case study: Unhandled exceptions.

阅读有关ASP.NET 2.0崩溃案例研究:未处理的异常。

Strategy #1 – logging the exception
The first way, and this is the way I would probably recommend, is to create an UnhandledExceptionHandler to log the exception along with its stack trace in the event log as shown in this article http://support.microsoft.com/?id=911816 You add the handler like this to the web.config:

策略#1 - 记录异常第一种方法,也就是我可能建议的方法,就是创建一个UnhandledExceptionHandler来记录事件日志中的异常及其堆栈跟踪,如本文http:// support所示。 microsoft.com/?id=911816您将这样的处理程序添加到web.config:
<system.web>
  <httpModules>
    <add type="WebMonitor.UnhandledExceptionModule, <strong name>"
       name="UnhandledExceptionModule"/>
  </httpModules>
      …
</system.web>   
And it hooks an eventhandler up to the UnhandledException event of the current app domain. You don’t actually need to strong name it and add it to the GAC, however if you plan it in multiple applications you should to avoid for the dll being loaded multiple times. Now the next time you get one of these unhandled exceptions, the process will still exit (unless you change the unhandled exception policy), but you have a very good chance of fixing the issue.

它将事件处理程序挂钩到当前应用程序域的UnhandledException事件。您实际上并不需要对其进行强名称并将其添加到GAC,但是如果您在多个应用程序中进行规划,则应该避免多次加载dll。现在,当您下次获得其中一个未处理的异常时,该过程仍将退出(除非您更改未处理的异常策略),但您很有可能解决该问题。

#2

You can set up performance counters to monitor things like CPU, memory and .NET specific counters. There are a lot of details, but this TechNet article might help:

您可以设置性能计数器来监视CPU,内存和.NET特定计数器等内容。有很多细节,但这篇TechNet文章可能有所帮助:

Monitoring ASP.NET Performance (IIS 6.0)

监视ASP.NET性能(IIS 6.0)

ASP.NET itself has a whole namespace for monitoring application health. You can create your own events or, most commonly, configure your application for the default events. This MSDN article has more:

ASP.NET本身有一个用于监视应用程序运行状况的完整命您可以创建自己的事件,或者最常见的是,为默认事件配置应用程序。这篇MSDN文章有更多:

ASP.NET Health Monitoring Overview

ASP.NET运行状况监视概述

If the problem is the application code such as an unhandled exception (although if this were your problem I'd expect to see more details in the Windows Event Log), you can use tools to trap and report on them. ELMAH is a great tool that I've used in the past for this. It's been described as Tivo for web applications and has a variety of ways to deliver details of exceptions and help track down what's wrong.

如果问题是应用程序代码,例如未处理的异常(尽管如果这是您的问题,我希望在Windows事件日志中看到更多详细信息),您可以使用工具来捕获和报告它们。 ELMAH是我过去用过的一个很棒的工具。它被描述为Web应用程序的Tivo,并提供了多种方式来提供异常的详细信息并帮助追踪错误。

#3

Microsoft's Debug Diagnostic Tool (DebugDiag) will do the trick. It will provide an IIS memory dump and analysis.

微软的调试诊断工具(DebugDiag)可以解决问题。它将提供IIS内存转储和分析。

#1