ASP.NET CORE 3.1 IIS Worker在启动时崩溃

发布于 2025-02-07 02:55:27 字数 2378 浏览 1 评论 0原文

ASP.NET Core 3.1 Web API在启动时崩溃,并在事件日志中具有以下错误:

错误应用程序名称:W3WP.EXE,版本:10.0.14393.0,时间戳记:0x57899135 故障模块名称:ucrtbase.dll,版本:10.0.14393.3659,时间戳:0x5E914092

工人甚至都不会启动。该应用程序通过安装程序发布,因此所有内容都是自动设置的。它经过测试并在Windows Server 2012,2016年和2019年的20多个服务器环境中工作。故障环境在Windows Server 2016上运行,并安装了所有最新更新以及.NET Core Runtime库的最新版本。

我的问题是如何跟踪此错误。

Update

使用调试诊断工具从应用程序池收集转储文件后,我遵循了堆栈跟踪,似乎ASP Core正在尝试启动失败的重定向。这是完整的堆栈跟踪:

[0x0]   ucrtbase!_invoke_watson + 0x12   
[0x1]   ucrtbase!_invalid_parameter + 0x75   
[0x2]   ucrtbase!_invalid_parameter_noinfo + 0xb   
[0x3]   ucrtbase!_fileno + 0x308a1   
[0x4]   aspnetcorev2!StdWrapper::StartRedirection + 0x39   
[0x5]   aspnetcorev2!StandardStreamRedirection::Start + 0x13e   
[0x6]   aspnetcorev2!StandardStreamRedirection::TryStartRedirection + 0x35   
[0x7]   aspnetcorev2!StandardStreamRedirection::{ctor} + 0x46   
[0x8]   aspnetcorev2!HandlerResolver::FindNativeAssemblyFromHostfxr + 0x233   
[0x9]   aspnetcorev2!HandlerResolver::LoadRequestHandlerAssembly + 0x369   
[0xa]   aspnetcorev2!HandlerResolver::GetApplicationFactory + 0x3d6   
[0xb]   aspnetcorev2!APPLICATION_INFO::TryCreateApplication + 0x2e8   
[0xc]   aspnetcorev2!APPLICATION_INFO::CreateApplication + 0x25a   
[0xd]   aspnetcorev2!APPLICATION_INFO::CreateHandler + 0x1b3   
[0xe]   aspnetcorev2!ASPNET_CORE_PROXY_MODULE::OnExecuteRequestHandler + 0x108   
[0xf]   iiscore!NOTIFICATION_CONTEXT::RequestDoWork + 0x2e3   
[0x10]   iiscore!NOTIFICATION_CONTEXT::CallModulesInternal + 0x4af   
[0x11]   iiscore!NOTIFICATION_CONTEXT::CallModules + 0x2b   
[0x12]   iiscore!NOTIFICATION_MAIN::DoStateRequestExecuteHandler + 0x40   
[0x13]   iiscore!NOTIFICATION_MAIN::DoWork + 0x116   
[0x14]   iiscore!W3_CONTEXT_BASE::StartNotificationLoop + 0x93   
[0x15]   iiscore!W3_MAIN_CONTEXT::OnNewRequest + 0xbf   
[0x16]   w3dt!UL_NATIVE_REQUEST::DoWork + 0xb0   
[0x17]   w3dt!UL_RECEIVE_CONTEXT::DoWork + 0x1b   
[0x18]   w3dt!WP_CONTEXT::OnCompletion + 0x3a   
[0x19]   w3tp!THREAD_POOL_DATA::ThreadPoolThread + 0xb0   
[0x1a]   w3tp!THREAD_POOL_DATA::ThreadPoolThread + 0x2b   
[0x1b]   w3tp!THREAD_MANAGER::ThreadManagerThread + 0x67   
[0x1c]   kernel32!BaseThreadInitThunk + 0x24   
[0x1d]   ntdll!__RtlUserThreadStart + 0x2f   
[0x1e]   ntdll!_RtlUserThreadStart + 0x1b  

转储文件中还有其他信息要查找吗? 仍然陷入困境。

an asp.net core 3.1 web api crashes on startup with the following error in the event log:

Faulting application name: w3wp.exe, version: 10.0.14393.0, time stamp: 0x57899135
Faulting module name: ucrtbase.dll, version: 10.0.14393.3659, time stamp: 0x5e914092

The worker won't even start. This app is published through an installer, so everything is set up automatically. It is tested and works on more than 20 server environments of Windows Server 2012, 2016, and 2019. The faulty environment runs on Windows Server 2016 with all the latest updates installed and the latest release of .net core runtime libraries.

My question is how to trace this error on is.

Update

After using the Debug Diagnostic Tool to collect a dump file from the application pool I followed the stack trace and it seems that asp core is trying to start a redirection that fails. Here is the full stack trace:

[0x0]   ucrtbase!_invoke_watson + 0x12   
[0x1]   ucrtbase!_invalid_parameter + 0x75   
[0x2]   ucrtbase!_invalid_parameter_noinfo + 0xb   
[0x3]   ucrtbase!_fileno + 0x308a1   
[0x4]   aspnetcorev2!StdWrapper::StartRedirection + 0x39   
[0x5]   aspnetcorev2!StandardStreamRedirection::Start + 0x13e   
[0x6]   aspnetcorev2!StandardStreamRedirection::TryStartRedirection + 0x35   
[0x7]   aspnetcorev2!StandardStreamRedirection::{ctor} + 0x46   
[0x8]   aspnetcorev2!HandlerResolver::FindNativeAssemblyFromHostfxr + 0x233   
[0x9]   aspnetcorev2!HandlerResolver::LoadRequestHandlerAssembly + 0x369   
[0xa]   aspnetcorev2!HandlerResolver::GetApplicationFactory + 0x3d6   
[0xb]   aspnetcorev2!APPLICATION_INFO::TryCreateApplication + 0x2e8   
[0xc]   aspnetcorev2!APPLICATION_INFO::CreateApplication + 0x25a   
[0xd]   aspnetcorev2!APPLICATION_INFO::CreateHandler + 0x1b3   
[0xe]   aspnetcorev2!ASPNET_CORE_PROXY_MODULE::OnExecuteRequestHandler + 0x108   
[0xf]   iiscore!NOTIFICATION_CONTEXT::RequestDoWork + 0x2e3   
[0x10]   iiscore!NOTIFICATION_CONTEXT::CallModulesInternal + 0x4af   
[0x11]   iiscore!NOTIFICATION_CONTEXT::CallModules + 0x2b   
[0x12]   iiscore!NOTIFICATION_MAIN::DoStateRequestExecuteHandler + 0x40   
[0x13]   iiscore!NOTIFICATION_MAIN::DoWork + 0x116   
[0x14]   iiscore!W3_CONTEXT_BASE::StartNotificationLoop + 0x93   
[0x15]   iiscore!W3_MAIN_CONTEXT::OnNewRequest + 0xbf   
[0x16]   w3dt!UL_NATIVE_REQUEST::DoWork + 0xb0   
[0x17]   w3dt!UL_RECEIVE_CONTEXT::DoWork + 0x1b   
[0x18]   w3dt!WP_CONTEXT::OnCompletion + 0x3a   
[0x19]   w3tp!THREAD_POOL_DATA::ThreadPoolThread + 0xb0   
[0x1a]   w3tp!THREAD_POOL_DATA::ThreadPoolThread + 0x2b   
[0x1b]   w3tp!THREAD_MANAGER::ThreadManagerThread + 0x67   
[0x1c]   kernel32!BaseThreadInitThunk + 0x24   
[0x1d]   ntdll!__RtlUserThreadStart + 0x2f   
[0x1e]   ntdll!_RtlUserThreadStart + 0x1b  

Is there any other information in the dump file to look for?
Still stuck with this one.

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

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

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。
列表为空,暂无数据
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文