HTTP Error 500.19 when publish .net core project into iis with 0x80070005

error

I want to publish a sample .net core web application on my pc's IIS manager but I failed. I am using Microsoft guidance but it doesn't work for me, if you have reasonable experience to fix this problem I would be grateful to see your suggestions.

100396 次浏览
小开
最佳答案

The identity under which your web application runs in IIS doesn't have full access to the folder in which the web.config file is found. Which version of IIS are you using? Assuming 7, you can view/change the identity through the 'Advanced Settings' of the application pool that hosts your application. Folder permissions can be granted via Windows Explorer in the usual way.

小开

I was missing the AspNetCoreModule from IIS->Modules. After I installed that I no longer had the 500.19 error.

To find out more this blog was great: https://weblog.west-wind.com/posts/2016/Jun/06/Publishing-and-Running-ASPNET-Core-Applications-with-IIS

Here is the page from Microsoft to find the download: https://learn.microsoft.com/en-us/aspnet/core/publishing/iis?tabs=aspnetcore2x

小开

Sure, you have to follow this tutorial to deploy to IIS:

https://learn.microsoft.com/en-us/aspnet/core/publishing/iis

I would suggest you to do this:

  1. Publish your web application to desktop.

  2. Copy the folder to the server.

  3. Open cmd and run cd

  1. In cmd run dotnet webapplication.dll

  2. You should see that application is run and waiting for responses on localhost:port.

  3. Open browser and navigate there. It should work.

Otherwise, you will be able to see all the errors in the cmd window. OR Go to microsoft site "https://www.microsoft.com/net/download/dotnet-core/runtime-2.1.0-rc1" and install "Hosting Bundle Installer":

小开

You have to install the "Hosting Bundle Installer". Without this, IIS doesn't understand routing and cannot host your application.

Go to microsoft site "https://www.microsoft.com/net/download/dotnet-core/runtime-2.1.0-rc1" and install "Hosting Bundle Installer":

enter image description here

Before installing this you have to install the right version of runtime: https://www.microsoft.com/net/download/dotnet-core/runtime-2.1.0-rc1 Than install the right version of "Hosting Bundle Installer".

"Hosting Bundle Installer" is: .NET Core Windows Server Hosting bundle installs the .NET Core Runtime, .NET Core Library, and the ASP.NET Core Module. The module creates a reverse proxy between IIS and the Kestrel server on Windows platforms.

小开

In my case I was getting the same error.

It was nothing to do with the permissions.

I had to install the followings 1- Microsoft .NET Core Runtime 2- Microsoft ASP.NET Core Runtime 3- Microsoft ASP.NET Core Hosting Bundle

from the below location. (Please chose the relevant version) https://dotnet.microsoft.com/download/archives

Then I had to execute the following commands as well. net stop was /y net start w3svc

You can either restart the machine.

That fixed for me.

小开

Try to edit/open any configuration for the site.

If you can't access the configuration options for the site under IIS Manager, check commenting the tag < aspNetCore >, if problem solve, uncomment it and install.

ASP.NET Core Hosting Bundle.

ASP.NET Core 3.1 Runtime (v3.1.3) - Windows Hosting Bundle Installer.

小开

Very good, in my case a module called "urlrewrite" was missing.

You install it with the "Microsoft Web Platform Installer" application.

小开

Write dotnet --info in your command prompt to see your SDK versions. (after words .NET SDKs installed:)

Find your equal Hosting Bundle version and install it.

For example : SDK 3.1.408 needs Hosting Bundle 3.1.14.

https://karthiktechblog.com/aspnetcore/how-to-solve-http-error-500-19-internal-server-error-in-windows-server-iis-for-dotnet-core-application

小开

I also had this problem and the problem was solved by installing the Hosting Bundle Installer. You can install from url: https://dotnet.microsoft.com/download/dotnet

小开

We've observed this problem on our server even though Hosting Bundle was already installed. The problem was, the hosting bundle was installed BEFORE IIS feature was enabled. The fix was to Repair hosting bundle install by running the installer again.


提交答案