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

Question

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 502.5 - Process Fai

Answer 1

As VS2017 RC is shipped with the new version of .NET Core SDK (.NET Core 1.0.4 SDK 1.0.1), you need to update framework on server as well.

Answer 2

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:

Answer 3

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.

Answer 4

For .net core 2.0

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

Answer 5

For me I had to make sure I had the latest .Net Core Runtime and Windows Hosting Module installed, all of which are available from https://www.microsoft.com/net/download/windows (newest versions should always be available here).

Specifically, I installed:

• .Net Core Runtime - https://www.microsoft.com/net/download/thank-you/dotnet-runtime-2.0.5-windows-x64-installer
• Windows Server Hosting Runtime - https://www.microsoft.com/net/download/thank-you/dotnet-runtime-2.0.5-windows-windows-server-hosting-installer
• .Net Framework 4.7.1 Runtime - https://www.microsoft.com/net/download/thank-you/net471

The full .Net Framework 4.7.1 runtime might not be needed if you truly do only host .Net Core apps on your server, but I installed it to be safe.

Answer 6

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.