当前位置： 文江博客话题详情

“默认应用程序池”与万维网发布服务发生致命通信错误

发布于 2024-10-26 19:30:26 字数 1663 浏览 6 评论 0原文

每次访问该站点时，我都会收到事件日志条目：

Event Type: Error
Event Source:   VsJITDebugger
Event Category: None
Event ID:   4096
User:       NT AUTHORITY\NETWORK SERVICE
Computer:   COMPUTER-02
Description:
An unhandled Microsoft .NET Framework exception occurred in w3wp.exe [2908]. Just-In-Time debugging this exception failed with the following error: Debugger could not be started because no user is logged on.

Check the documentation index for 'Just-in-time debugging, errors' for more information.

Data:
0000: 02 00 5c 80               ..\

系统日志

Event Type: Error
Event Source:   W3SVC
Event Category: None
Event ID:   1002
Date:       28/03/2011
Time:       17:49:28
User:       N/A
Computer:   COMPUTER-02
Description:
Application pool 'DefaultAppPool' is being automatically disabled due to a series of failures in the process(es) serving that application pool.

应用程序日志

Event Type: Warning
Event Source:   W3SVC
Event Category: None
Event ID:   1011
Date:       28/03/2011
Time:       17:49:28
User:       N/A
Computer:   COMPUTER-02
Description:
A process serving application pool 'DefaultAppPool' suffered a fatal communication error with the World Wide Web Publishing Service. The process id was '3724'. The data field contains the error number. 

Data:
0000: 6d 00 07 80               m..

我还遵循了 Microsoft 的建议支持网站但运气不好。网络服务帐户访问注册表没有任何问题。

我需要在 IIS6（而不是 IIS Express 7.5）中运行该站点，因为该站点运行 ASP 以及 ASP.NET 我需要通配符映射以在 ASP 中进行身份验证。

我已经完全没有想法了，因为该网站在 ASP.NET 3.5 (CLR v2...) 中运行良好，但这次升级通过调试完全搞砸了。

任何帮助将不胜感激。

原文

I am getting Event Log entries every time I access the site:

Event Type: Error
Event Source:   VsJITDebugger
Event Category: None
Event ID:   4096
User:       NT AUTHORITY\NETWORK SERVICE
Computer:   COMPUTER-02
Description:
An unhandled Microsoft .NET Framework exception occurred in w3wp.exe [2908]. Just-In-Time debugging this exception failed with the following error: Debugger could not be started because no user is logged on.

Check the documentation index for 'Just-in-time debugging, errors' for more information.

Data:
0000: 02 00 5c 80               ..\

System Logs

Event Type: Error
Event Source:   W3SVC
Event Category: None
Event ID:   1002
Date:       28/03/2011
Time:       17:49:28
User:       N/A
Computer:   COMPUTER-02
Description:
Application pool 'DefaultAppPool' is being automatically disabled due to a series of failures in the process(es) serving that application pool.

Application Log

Event Type: Warning
Event Source:   W3SVC
Event Category: None
Event ID:   1011
Date:       28/03/2011
Time:       17:49:28
User:       N/A
Computer:   COMPUTER-02
Description:
A process serving application pool 'DefaultAppPool' suffered a fatal communication error with the World Wide Web Publishing Service. The process id was '3724'. The data field contains the error number. 

Data:
0000: 6d 00 07 80               m..

I have also followed the advice of Microsoft's Support site without luck. The Network Service account didn't have any problems accessing the registry.

I need to run the site in IIS6 (instead of IIS Express 7.5) as the site runs ASP as well as ASP.NET I need the wildcard mapping for authentication in ASP.

I have completely run out of ideas, as the site was fine in ASP.NET 3.5 (CLR v2...), but this upgrade has completely messed up by debugging.

Any help will be much appreciated.

如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论， 你可以免费 注册 一个本站的账号。

评论（2）

叹沉浮 2024-11-02 19:30:26

您将需要 WinDbg（Windows 调试工具）和 DebugDiag。

  1. 安装 DebugDiag 和 WinDbg
  2. 确保您已将相关框架的 SOS.dll 复制到 WinDbg 目录。
  3. 添加规则以捕获 IIS/COM+ 进程
  4. 在出现第一个异常时，创建完整的用户转储。限制为 10
  5. 打开网站并查看 DebugDiag，您应该发现它开始进行完整转储。
  6. 获得一些内存转储后，加载 WinDbg 并单击“文件”->“打开故障转储”并加载其中一个内存转储。
  7. 输入 .load sos
  8. 输入 !clrstack
  9. 您将获得错误的堆栈跟踪，如下所示：
0:016> .load sos
0:016> !clrstack
PDB symbol for clr.dll not loaded
OS Thread Id: 0xa60 (16)
Child SP IP       Call Site
01d2eb5c 7c81a251 [HelperMethodFrame: 01d2eb5c] System.Diagnostics.Debugger.LaunchInternal()
01d2ebac 7a0e0166 System.Diagnostics.Debugger.Launch()*** WARNING: Unable to verify checksum for mscorlib.ni.dll
*** ERROR: Module load completed but symbols could not be loaded for mscorlib.ni.dll

01d2ebd8 04470176 ebiz.Global.Application_Start(System.Object, System.EventArgs)
01d2f1f8 791421bb [DebuggerU2MCatchHandlerFrame: 01d2f1f8] 
01d2f1c4 791421bb [CustomGCFrame: 01d2f1c4] 
01d2f198 791421bb [GCFrame: 01d2f198] 
01d2f17c 791421bb [GCFrame: 01d2f17c] 
01d2f3a0 791421bb [HelperMethodFrame_PROTECTOBJ: 01d2f3a0] System.RuntimeMethodHandle._InvokeMethodFast(System.IRuntimeMethodInfo, System.Object, System.Object[], System.SignatureStruct ByRef, System.Reflection.MethodAttributes, System.RuntimeType)
01d2f41c 79b3d689 System.RuntimeMethodHandle.InvokeMethodFast(System.IRuntimeMethodInfo, System.Object, System.Object[], System.Signature, System.Reflection.MethodAttributes, System.RuntimeType)
01d2f470 79b3d37c System.Reflection.RuntimeMethodInfo.Invoke(System.Object, System.Reflection.BindingFlags, System.Reflection.Binder, System.Object[], System.Globalization.CultureInfo, Boolean)
01d2f4ac 79b3bfed System.Reflection.RuntimeMethodInfo.Invoke(System.Object, System.Reflection.BindingFlags, System.Reflection.Binder, System.Object[], System.Globalization.CultureInfo)
01d2f4d0 79b43284 System.Reflection.MethodBase.Invoke(System.Object, System.Object[])
01d2f4dc 67894f4d System.Web.HttpApplication.InvokeMethodWithAssert(System.Reflection.MethodInfo, Int32, System.Object, System.EventArgs)*** WARNING: Unable to verify checksum for System.Web.ni.dll
*** ERROR: Module load completed but symbols could not be loaded for System.Web.ni.dll

01d2f500 678951cb System.Web.HttpApplication.ProcessSpecialRequest(System.Web.HttpContext, System.Reflection.MethodInfo, Int32, System.Object, System.EventArgs, System.Web.SessionState.HttpSessionState)
01d2f550 67b34175 System.Web.HttpApplicationFactory.FireApplicationOnStart(System.Web.HttpContext)
01d2f564 672bfe1c System.Web.HttpApplicationFactory.EnsureAppStartCalled(System.Web.HttpContext)
01d2f59c 672bfd3d System.Web.HttpApplicationFactory.GetApplicationInstance(System.Web.HttpContext)
01d2f5ac 672fbf28 System.Web.HttpRuntime.ProcessRequestInternal(System.Web.HttpWorkerRequest)
01d2f5e0 672fbccd System.Web.HttpRuntime.ProcessRequestNoDemand(System.Web.HttpWorkerRequest)
01d2f5f0 672fb2cd System.Web.Hosting.ISAPIRuntime.ProcessRequest(IntPtr, Int32)
01d2f5f4 6791c30c [InlinedCallFrame: 01d2f5f4] 
01d2f668 6791c30c DomainNeutralILStubClass.IL_STUB_COMtoCLR(Int32, Int32, IntPtr)
01d2f7fc 791425a1 [GCFrame: 01d2f7fc] 
01d2f86c 791425a1 [ContextTransitionFrame: 01d2f86c] 
01d2f8a0 791425a1 [GCFrame: 01d2f8a0] 
01d2f9f8 791425a1 [ComMethodFrame: 01d2f9f8]

无论如何，对我来说，您可以看到 Debugger.Launch()< /code> 就在顶部，你瞧，我的代码里有它。如果它是你的第一行代码，似乎 IIS 根本不喜欢这样！

You will need WinDbg (Debugging Tools for Windows) and DebugDiag.

  1. Install DebugDiag and WinDbg
  2. Ensure you have copied the related framework's SOS.dll to the WinDbg directory.
  3. Add a rule to catch IIS/COM+ processes
  4. On first exceptions, create a full user dump. Limit of 10
  5. Open the website and look at look at DebugDiag, you should find it starting to take full dumps.
  6. Once you have a few memory dumps, load WinDbg and click File->Open Crash Dump and load one of the memory dump.
  7. Type .load sos
  8. Type !clrstack
  9. You will get a stack trace of the error like:
0:016> .load sos
0:016> !clrstack
PDB symbol for clr.dll not loaded
OS Thread Id: 0xa60 (16)
Child SP IP       Call Site
01d2eb5c 7c81a251 [HelperMethodFrame: 01d2eb5c] System.Diagnostics.Debugger.LaunchInternal()
01d2ebac 7a0e0166 System.Diagnostics.Debugger.Launch()*** WARNING: Unable to verify checksum for mscorlib.ni.dll
*** ERROR: Module load completed but symbols could not be loaded for mscorlib.ni.dll

01d2ebd8 04470176 ebiz.Global.Application_Start(System.Object, System.EventArgs)
01d2f1f8 791421bb [DebuggerU2MCatchHandlerFrame: 01d2f1f8] 
01d2f1c4 791421bb [CustomGCFrame: 01d2f1c4] 
01d2f198 791421bb [GCFrame: 01d2f198] 
01d2f17c 791421bb [GCFrame: 01d2f17c] 
01d2f3a0 791421bb [HelperMethodFrame_PROTECTOBJ: 01d2f3a0] System.RuntimeMethodHandle._InvokeMethodFast(System.IRuntimeMethodInfo, System.Object, System.Object[], System.SignatureStruct ByRef, System.Reflection.MethodAttributes, System.RuntimeType)
01d2f41c 79b3d689 System.RuntimeMethodHandle.InvokeMethodFast(System.IRuntimeMethodInfo, System.Object, System.Object[], System.Signature, System.Reflection.MethodAttributes, System.RuntimeType)
01d2f470 79b3d37c System.Reflection.RuntimeMethodInfo.Invoke(System.Object, System.Reflection.BindingFlags, System.Reflection.Binder, System.Object[], System.Globalization.CultureInfo, Boolean)
01d2f4ac 79b3bfed System.Reflection.RuntimeMethodInfo.Invoke(System.Object, System.Reflection.BindingFlags, System.Reflection.Binder, System.Object[], System.Globalization.CultureInfo)
01d2f4d0 79b43284 System.Reflection.MethodBase.Invoke(System.Object, System.Object[])
01d2f4dc 67894f4d System.Web.HttpApplication.InvokeMethodWithAssert(System.Reflection.MethodInfo, Int32, System.Object, System.EventArgs)*** WARNING: Unable to verify checksum for System.Web.ni.dll
*** ERROR: Module load completed but symbols could not be loaded for System.Web.ni.dll

01d2f500 678951cb System.Web.HttpApplication.ProcessSpecialRequest(System.Web.HttpContext, System.Reflection.MethodInfo, Int32, System.Object, System.EventArgs, System.Web.SessionState.HttpSessionState)
01d2f550 67b34175 System.Web.HttpApplicationFactory.FireApplicationOnStart(System.Web.HttpContext)
01d2f564 672bfe1c System.Web.HttpApplicationFactory.EnsureAppStartCalled(System.Web.HttpContext)
01d2f59c 672bfd3d System.Web.HttpApplicationFactory.GetApplicationInstance(System.Web.HttpContext)
01d2f5ac 672fbf28 System.Web.HttpRuntime.ProcessRequestInternal(System.Web.HttpWorkerRequest)
01d2f5e0 672fbccd System.Web.HttpRuntime.ProcessRequestNoDemand(System.Web.HttpWorkerRequest)
01d2f5f0 672fb2cd System.Web.Hosting.ISAPIRuntime.ProcessRequest(IntPtr, Int32)
01d2f5f4 6791c30c [InlinedCallFrame: 01d2f5f4] 
01d2f668 6791c30c DomainNeutralILStubClass.IL_STUB_COMtoCLR(Int32, Int32, IntPtr)
01d2f7fc 791425a1 [GCFrame: 01d2f7fc] 
01d2f86c 791425a1 [ContextTransitionFrame: 01d2f86c] 
01d2f8a0 791425a1 [GCFrame: 01d2f8a0] 
01d2f9f8 791425a1 [ComMethodFrame: 01d2f9f8]

For me anyway, you can see that the Debugger.Launch() is right at the top, and low and behold, my code had it in. It seems that IIS doesn't like that at all if it is your first line of code!

回复 原文
我偏爱纯白色 2024-11-02 19:30:26

如果您不熟悉 WinDbg，您仍然可以从转储中提取大量信息。您已经拥有 DebugDiag 创建的转储。启动 VS，文件 ->打开->文件 (Ctrl + O)，选择 .dmp 文件。 VS2010 将显示几个调试选项——混合模式或仅本机模式。选择混合模式，打开线程窗口，识别抛出异常的线程，查看调用堆栈。有时您会获取线程的局部变量，但不要过于依赖它，因为数据可能不正确。

If you are not familiar with WinDbg, you can still extract a lot of information from the dumps. You already have dumps created by DebugDiag. Launch VS, File -> Open -> File (Ctrl + O), select the .dmp file. VS2010 will than display couple of options to debug -- Mixed mode or Native Only. Choose Mixed mode, open threads window, identify thread that threw exception, look at the call stack. Sometimes you get to local variables for the thread, but don't count on that too much, as data might not be correct.

回复 原文
~没有更多了~

关于作者

韵柒

暂无简介

0 文章
0 评论
24 人气
发私信

相关话题

更多

热门标签

操作系统 程序设计 IT运维 Linux系统管理 JavaScript 服务器应用 solaris C/C++ PHP Shell BSD Vue.js aix Oracle Python HTML 系统管理 HTML5 CSS 前端
更多

推荐作者

苍风燃霜

文章 0 评论 0

我的黑色迷你裙

文章 0 评论 0

悸初

文章 0 评论 0

撧情箌佬

文章 0 评论 0

森罗

文章 0 评论 0

lyn1245

文章 0 评论 0

更多

友情链接

文江博客
    我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站，即表示您同意使用 Cookies 和您的相关数据。
    原文