blocks|key|391822|text|由于VS2017+RC随新版本的.NET+Core+(.NET核心1.0.4SDK1.0.1)一起提供，您还需要在服务器上更新框架。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|391823|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/dotnet/core/blob/master/release-notes/download-archives/1.0.4-download.md^0|R|J|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

As VS2017 RC is shipped with the new version of .NET Core SDK (<a href="https://github.com/dotnet/core/blob/master/release-notes/download-archives/1.0.4-download.md" rel="noreferrer">.NET Core 1.0.4 SDK 1.0.1</a>), you need to update framework on server as well.

blocks|key|2109060|text|错误代码：0x80004005表示文件丢失或无法访问。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|2109061|子代码：80008083似乎是一个版本冲突.|2109062|此错误意味着需要在服务器上安装不同版本的dotnet。|2109063|entityMap^0|5|A|0|4|8|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@$9|M|A|N|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|O|8|@$9|P|A|Q|B|C]]|D|@]|E|$]]|$1|H|3|I|5|6|7|R|8|@]|D|@]|E|$]]|$1|J|3|-4|5|6|7|S|8|@]|D|@]|E|$]]]|K|$]]

Error code: <code>0x80004005</code> means a file missing or can't be accessed.

Sub-code: <code>80008083</code> appears to be a version conflict.

This error means a different version of dotnet needs to be installed on the server.

blocks|key|391876|text|我也面临同样的问题，我只在我的服务器上安装了dotnet+2，所以通过安装这个链接，您可以在其他版本的dotnet中运行您的代码。不要忘记重新启动IIS。1.1.5-WindowsHosting.exe|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|391877|entityMap|0|LINK|mutability|MUTABLE|url|https://download.microsoft.com/download/6/A/2/6A21C555-B042-46EA-BBB4-368AACCB3E25/DotNetCore.1.0.8_1.1.5-WindowsHosting.exe^0|25|O|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

I faced the same issue and I only had dotnet cor 2 installed on my server, so by installing this link you are able to run your code in other versions of dot net core. dont forget to restart IIS.
<a href="https://download.microsoft.com/download/6/A/2/6A21C555-B042-46EA-BBB4-368AACCB3E25/DotNetCore.1.0.8_1.1.5-WindowsHosting.exe" rel="nofollow noreferrer">https://download.microsoft.com/download/6/A/2/6A21C555-B042-46EA-BBB4-368AACCB3E25/DotNetCore.1.0.8_1.1.5-WindowsHosting.exe</a>

blocks|key|391946|text|我已经向发布了一个新的.NET+Core2.0Web应用程序，并遇到了这个错误。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|391947|击中现场：|391948|HTTP错误502.5+-进程失败此问题的常见原因:应用程序进程启动应用程序进程失败，但随后停止应用程序进程启动，但未能侦听配置好的端口|blockquote|offset|length|style|BOLD|391949|使用Azure应用程序的调试：使用Azure+Advanced++(KUDU)查看Tools+-+Debug+Console+-浏览LogFiles文件夹有一个日志行：|391950|应用程序'MACHINE/WEBROOT/APPHOST/xxxx‘，物理根'D:\home\site\wwwroot\’未能使用命令行'dotnet。\WebApp.dll‘启动进程，ErrorCode+=+'0x80004005+:+8000808c。|391951|<Provider+Name="IIS+AspNetCore+Module"/>
<EventID>1000</EventID>
<Level>1</Level>
<Task>0</Task>
<EventData>
<Data>Application+'MACHINE/WEBROOT/APPHOST/xxxx'+with+physical+root+'D:\home\site\wwwroot\'+failed+to+start+process+with+commandline+'dotnet+.\WebApp.dll',+ErrorCode+=+'0x80004005+:+8000808c.</Data>
</EventData>
</Event>|code-block|syntax|javascript|391952|溶液|391953|这个答案:删除wwwroot文件夹在蔚蓝和再次发布从VS，为我工作，尽管没有一个遗留的核心1.1应用程序最初。|391954|在应用程序中启动Azure控制台并删除wwwroot文件夹的内容，然后重新部署。|391955|RMDIR+wwwroot+/S+/Q|CODE|391956|在此之后进一步测试对测试非常有帮助，如果遵循相同的方法，它就能工作，但是您需要找到错误。https://learn.microsoft.com/en-us/aspnet/core/tutorials/publish-to-azure-webapp-using-vs|391957|entityMap|0|LINK|mutability|MUTABLE|url|http://stackoverflow.com/a/46277882/878612|1|https://learn.microsoft.com/en-us/aspnet/core/tutorials/publish-to-azure-webapp-using-vs^0|0|0|0|H|0|C|3|N|9|15|L|1U|8|25|7|0|0|3K|0|0|0|2|0|0|1J|0|H|0|0|0|14|0|0|J|0|J|0|0|3O|18|2G|1|0^^$0|@$1|2|3|4|5|6|7|1E|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|1F|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|1G|8|@$G|1H|H|1I|I|J]]|9|@]|A|$]]|$1|K|3|L|5|6|7|1J|8|@$G|1K|H|1L|I|J]|$G|1M|H|1N|I|J]|$G|1O|H|1P|I|J]|$G|1Q|H|1R|I|J]|$G|1S|H|1T|I|J]]|9|@]|A|$]]|$1|M|3|N|5|6|7|1U|8|@$G|1V|H|1W|I|J]]|9|@]|A|$]]|$1|O|3|P|5|Q|7|1X|8|@]|9|@]|A|$R|S]]|$1|T|3|U|5|6|7|1Y|8|@$G|1Z|H|20|I|J]]|9|@]|A|$]]|$1|V|3|W|5|6|7|21|8|@$G|22|H|23|I|J]]|9|@$G|24|H|25|1|26]]|A|$]]|$1|X|3|Y|5|6|7|27|8|@$G|28|H|29|I|J]]|9|@]|A|$]]|$1|Z|3|10|5|6|7|2A|8|@$G|2B|H|2C|I|J]|$G|2D|H|2E|I|11]]|9|@]|A|$]]|$1|12|3|13|5|6|7|2F|8|@$G|2G|H|2H|I|J]]|9|@$G|2I|H|2J|1|2K]]|A|$]]|$1|14|3|-4|5|6|7|2L|8|@]|9|@]|A|$]]]|15|$16|$5|17|18|19|A|$1A|1B]]|1C|$5|17|18|19|A|$1A|1D]]]]

I had published a new .NET Core 2.0 web app to Azure App Service and hit this error.

Hitting the site:

<blockquote>
 HTTP Error 502.5 - Process Failure 
 Common causes of this issue: The application process failed to start 
 The application process started but then stopped The application
 process started but failed to listen on the configured port
</blockquote>

Debugging:
Using Azure Application Insights &amp; the App Service - Advanced Tools (KUDU) looking at the Tools - Debug Console - Browsing the LogFiles folder eventlog.xml had a log row:

Application 'MACHINE/WEBROOT/APPHOST/xxxx' with physical root 'D:\home\site\wwwroot\' failed to start process with commandline 'dotnet .\WebApp.dll', ErrorCode = '0x80004005 : 8000808c.

<pre><code>&lt;Provider Name="IIS AspNetCore Module"/&gt;
&lt;EventID&gt;1000&lt;/EventID&gt;
&lt;Level&gt;1&lt;/Level&gt;
&lt;Task&gt;0&lt;/Task&gt;
&lt;EventData&gt;
&lt;Data&gt;Application 'MACHINE/WEBROOT/APPHOST/xxxx' with physical root 'D:\home\site\wwwroot\' failed to start process with commandline 'dotnet .\WebApp.dll', ErrorCode = '0x80004005 : 8000808c.&lt;/Data&gt;
&lt;/EventData&gt;
&lt;/Event&gt;
</code></pre>

Solution

<a href="http://stackoverflow.com/a/46277882/878612">This answer: Deleting the wwwroot folder</a> in azure and publish again from VS, worked for me despite not having a legacy Core 1.1 app initially. 

Launch Azure Console within the app and delete the contents of the wwwroot folder then redeploy.

<code>RMDIR wwwroot /S /Q</code>

Further testing
Following this was very helpful for testing and it works when followed identically, then deviate however you need to find errors.
<a href="https://learn.microsoft.com/en-us/aspnet/core/tutorials/publish-to-azure-webapp-using-vs" rel="noreferrer">https://learn.microsoft.com/en-us/aspnet/core/tutorials/publish-to-azure-webapp-using-vs</a>

blocks|key|392028|text|目前，有一种简单的方法可以查看实际错误是什么。打开app服务中的Console部分，然后尝试运行dotnet应用程序。从那里我们可以得到完整的错误消息和跟踪信息：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|392029|📷|atomic|offset|length|392030|​|392031|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://developer.qcloudimg.com/http-save/yehe-900000/916f6b58285f343a06bd6f899e427107.png|imageAlt^0|0|0|1|0|0|0^^$0|@$1|2|3|4|5|6|7|R|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|S|8|@]|9|@$E|T|F|U|1|V]]|A|$]]|$1|G|3|H|5|6|7|W|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|X|8|@]|9|@]|A|$]]]|J|$K|$5|L|M|N|A|$O|P|Q|-4]]]]

For now, there is a simple way to see what the actual error is.
Open Console section from the App service, then try to run the dotnet app. From there we may get the full error message and trace info:
<a href="https://i.stack.imgur.com/eHXbQ.png" rel="noreferrer"><img src="https://i.stack.imgur.com/eHXbQ.png" alt="enter image description here"></a>

blocks|key|392090|text|对我有用的一个可能的解决方案是在Visual中将其添加到发布配置文件中：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|392091|<PublishWithAspNetCoreTargetManifest>False</PublishWithAspNetCoreTargetManifest>|code-block|syntax|javascript|392092|我相信这将使主机使用所需的文件来运行应用程序，而不是依赖目标清单中设置的可能错误的规范(无论是服务器上的运行时/sdk还是您的本地版本都与这些规范相冲突)。|392093|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|L|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|M|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

A possible solution that worked for me is that I added this to my publish profile in Visual Studio:

<pre><code>&lt;PublishWithAspNetCoreTargetManifest&gt;False&lt;/PublishWithAspNetCoreTargetManifest&gt;
</code></pre>

I believe this will make the host use the required files to run the app instead of relying on specifications set in a target manifest which could be wrong (either the runtime/sdk on server or your local is in conflict with these specifications).

blocks|key|817438|text|对于.net核心2.0|type|unstyled|depth|inlineStyleRanges|entityRanges|data|817439|检查适当的DotNetCore.2.0.Y-WindowsHosting是否已安装。如果您的项目是2.1，那么安装2.1。因此)|ordered-list-item|817440|安装windows主机后，“需要”重新启动计算机。|817441|打开powershell；cd+installation_directory；dotnet+abcd.dll+--这是一个可以在安装WindowsHosting后检查的预控件。|offset|length|style|CODE|817442|entityMap^0|0|0|0|13|F|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|P|8|@]|9|@]|A|$]]|$1|E|3|F|5|D|7|Q|8|@]|9|@]|A|$]]|$1|G|3|H|5|D|7|R|8|@$I|S|J|T|K|L]]|9|@]|A|$]]|$1|M|3|-4|5|6|7|U|8|@]|9|@]|A|$]]]|N|$]]

For .net core 2.0 

<ol>
<li>Check the appropriate DotNetCore.2.0.Y-WindowsHosting is installed. If your project is 2.1 then install 2.1. accordingly)</li>
<li>A computer restart is "required" after windows hosting is installed. </li>
<li>Open powershell; cd installation_directory; 
<code>dotnet abcd.dll</code> This is a pre control you can check after you install WindowsHosting...</li>
</ol>

blocks|key|2109346|text|要修复这个错误，我所要做的就是重新启动我的开发计算机，并重新编译和重新发布站点。VS的反应不正常。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2109347|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

All I had to do to fix this error was reboot my development computer and recompile &amp; re-publish the site. VS was not responding properly.

blocks|key|2109391|text|我也有这个问题，我想我应该张贴我的解决方案。我不确定这是否有意，但我认为dotnet核心2不支持项目名称中的空格字符。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2109392|我创建并发布了一个名为"Mikes“的项目，当我试图使用IIS运行站点时，我会得到这个错误(.NET核心应用程序由于ErrorCode+=‘0x80004005’而无法在IIS中启动)。当我通过stdoutLogs文件启用web.config时，发现了以下错误：|2109393|没有可执行文件找到匹配命令"dotnet-.\Mikes“|blockquote|2109394|这一点很奇怪，因为web.config文件确实正确地显示了参数下的dll路径，即".\Mikes+App.dll“。|2109395|<aspNetCore+processPath="dotnet"+arguments=".\Mikes+App.dll"+stdoutLogEnabled="true"+stdoutLogFile=".\logs\stdout"+/>|code-block|syntax|javascript|2109396|我在Visual中创建了一个新的dotnet+2项目，并将其命名为"Mikes-App“，然后重新发布它，并更新了IIS站点上的目录。|2109397|然后这个网站运作得很好！|2109398|entityMap^0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|T|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|U|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|V|8|@]|9|@]|A|$]]|$1|G|3|H|5|6|7|W|8|@]|9|@]|A|$]]|$1|I|3|J|5|K|7|X|8|@]|9|@]|A|$L|M]]|$1|N|3|O|5|6|7|Y|8|@]|9|@]|A|$]]|$1|P|3|Q|5|6|7|Z|8|@]|9|@]|A|$]]|$1|R|3|-4|5|6|7|10|8|@]|9|@]|A|$]]]|S|$]]

I had this problem as well and thought I'd post my solution.
I'm not sure if this is intended or not, but I don't think dotnet core 2 supports Space characters in your Project Name.

I created and published a Project called "Mikes App" and when trying to run the site with IIS I would get this error (.NET Core app unable to start in IIS due to ErrorCode = '0x80004005'). When I enabled stdoutLogs through the web.config file I found the error:

<blockquote>
 No executable found matching command "dotnet-.\Mikes" 
</blockquote>

Which I found strange because the web.config file did correctly show the dll path under arguments which was ".\Mikes App.dll"

<pre><code>&lt;aspNetCore processPath="dotnet" arguments=".\Mikes App.dll" stdoutLogEnabled="true" stdoutLogFile=".\logs\stdout" /&gt;
</code></pre>

I created a new dotnet core 2 project in Visual Studio and named it "Mikes-App" instead, re-published it and updated the directory on my IIS site. 

Then the site worked fine!

blocks|key|817465|text|我正在IIS上运行，我在事件查看器->应用程序日志中发现了0x80004005+:+0错误。造成这种情况是因为我的应用程序池无法访问网站文件夹位置。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|817466|我通过将应用程序池标识更改为具有文件夹访问权限的标识来解决这个问题。|817467|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

I'm running on IIS, and I had error 0x80004005 : 0, which I found in the Event Viewer -> Application Logs. It was being caused because my application pool did not have access to the website folder location. 

I resolved it by changing the application pool identity to one with access to the folder.

blocks|key|392202|text|我发现您必须安装与您在VS2017中编译的版本完全相同的宿主版本。后来的版本并不是向后兼容的(至少我没有尝试过)。因此，2.2.8不会运行2.2.1版本，即使您希望有一个较小的修订来这样做。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|392203|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I've found you have to install the hosting version that is exactly the same as what you have compiled in VS2017. Later versions aren't backwards compatible (at least none I've tried are). So 2.2.8 won't run a 2.2.1 version, for example, even though you would expect a minor revision to do so.

blocks|key|817477|text|如果你|type|unstyled|depth|inlineStyleRanges|entityRanges|data|817478|Failed+to+start+application+'/LM/W3SVC/2/ROOT/{ControllerName}',+ErrorCode+'0x80004005'.+Process+Id:+29720.+File+Version:+16.0.21269.0.+Description:+IIS+ASP.NET+Core+Module+V2.|code-block|syntax|javascript|817479|在Visual+2019或其他版本中运行应用程序时出错。|817480|溶液|offset|length|style|BOLD|817481|您需要关闭VS项目并删除位于项目文件夹中的.vs隐藏文件夹，并重新启动VS项目。|CODE|817482|您必须从Windows中启用隐藏项选项，以便可以查看隐藏的.vs文件夹。|817483|entityMap^0|0|0|0|0|2|0|L|3|0|E|3|T|3|0^^$0|@$1|2|3|4|5|6|7|V|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|W|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|X|8|@]|9|@]|A|$]]|$1|I|3|J|5|6|7|Y|8|@$K|Z|L|10|M|N]]|9|@]|A|$]]|$1|O|3|P|5|6|7|11|8|@$K|12|L|13|M|Q]]|9|@]|A|$]]|$1|R|3|S|5|6|7|14|8|@$K|15|L|16|M|N]|$K|17|L|18|M|N]]|9|@]|A|$]]|$1|T|3|-4|5|6|7|19|8|@]|9|@]|A|$]]]|U|$]]

If you're getting
<pre><code>Failed to start application '/LM/W3SVC/2/ROOT/{ControllerName}', ErrorCode '0x80004005'. Process Id: 29720. File Version: 16.0.21269.0. Description: IIS ASP.NET Core Module V2.
</code></pre>
error when running the app in Visual Studio 2019 or another version.
Solution
You need to close the VS Project and delete <code>.vs</code> hidden folder located in your project folder and restart your VS Project.
You have to Enable Hidden Items option from Windows Explorer so that you can view the hidden .vs folder.

I have a .NET Core application. It runs locally with VS2017 and Kestrel. It runs locally under IIS. However, on the server it fails to start with a <code>502.5 - Process Failure</code> message.

In the event logs I get more detail:

<blockquote>
 Application '...' with physical root 'C:...\my-app-folder\' failed to start process with commandline '"dotnet" .\MyApp.dll', ErrorCode = '0x80004005 : 80008083.
</blockquote>

Previous builds of the application work fine on the same server, the only difference being that they were published with VS2017RC (2&amp;3) and this is the first build with the fully released VS2017.

What does <code>ErrorCode = '0x80004005 : 80008083.</code> mean?

How do I fix it?

.NET Core app unable to start in IIS due to ErrorCode = '0x80004005 : 80008083

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

我有一个.NET核心应用程序。它使用VS2017和Kestrel在本地运行。它在IIS下本地运行。但是，在服务器上，它不能从502.5 - Process Failure消息开始。在事件日志中，我得到了更多细节：申请“.”使用物理根‘C：\my文件夹’无法使用命令行“”dotnet“启动进程。\MyApp.dll‘，E...

问由于.NET = '0x80004005 : 80008083，无法在IIS中启动ErrorCode核心应用程序
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问由于.NET = '0x80004005 : 80008083，无法在IIS中启动ErrorCode核心应用程序EN