连接到IISExpress的灾难性故障 [英] Catastrophic Failure attaching to IISExpress

问题描述

我遇到了一个问题，当我尝试将调试程序附加到IIS Express时，它失败并显示无法附加到进程。灾难性故障。然后它会杀死我的IIS Express会话。我不知道从哪里开始调试此问题。

I'm having an issue where when I attempt to attach my debugger to IIS express, it fails with a "Unable to attach to the process. Catastrophic failure". It then kills my IIS Express session. I have no clue where to begin debugging this issue.

导致此问题的步骤：

1. 我的应用程序存在于我的本地计算机上


2. Documents\IISExpress\config\applicationhost.config已设置站点


3. 我通过管理控制台模式运行IIS express到C：\Program Files \ IIS Express \ iisexpress.exe


4. 我在VS中加载我的解决方案。


5. 我附加了尝试将我的调试器附加到IISexpress。


6. 我遇到了灾难性的失败错误。


7. IIS被终止并停止。

1. My application exists on my local machine
2. Documents\IISExpress\config\applicationhost.config has the Site set up
3. I run IIS express via an administrative console mode by going to C:\Program Files\IIS Express\iisexpress.exe
4. I load up my solution in VS.
5. I attach attempt to attach my debugger to IISexpress.
6. I get the catastrophic failure error.
7. IIS is killed and stopped.

想知道Visual Studio日志在哪里可以看到可能发生的事情？我尝试使用/ log选项运行devenv.exe但它没有帮助解决任何错误。

Any idea of where to go for Visual studio logs to see what might have happened? I tried running devenv.exe with the /log option but it did not help with any errors.

我也查了一下IIS日志，但没有什么不同寻常的点灾难性的失败。

I also looked up IIS logs, but nothing out of the ordinary that points to the catastrophic failure.

推荐答案

您是否在同一个应用程序池中运行多个站点？
我遇到了同样的问题，并认为将应用程序站点分成不同的应用程序池解决了这个问题。

Are you running more than one site within the same application pool? I was having the same problem and believe that separating the app sites into different application pools fixed the issue.

此外，我在Visual Studio中选择了错误的启动项目时遇到了问题。确保在连接之前选择了正确的启动项目，但我不明白为什么这应该重要。

Additionally I had issue when the wrong start-up project was selected in Visual studio. Make sure the correct start-up project is selected before attaching, though I can't see why this should matter.

此外，我还为应用程序启动调试器创建了一个控制器，这不仅使其更容易，而且似乎也没有问题。

Also I created a controller for the debugger to be launched from the application, which no only makes it much easier, also appears to have less issues.

    #if DEBUG
    public virtual ActionResult Attach()
    {
        System.Diagnostics.Debugger.Launch();
        return new EmptyResult();
    }
    #endif 

这篇关于连接到IISExpress的灾难性故障的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！