ASP.NET Core 3.0 - InProcess vs. OutOfProcess (HTTP Error 500.30 - ANCM In-Process Start Failure)

user_414803 0
Viewed 7034

We migrated one of many ASP.Net Core 2.2 Apps to .NET Core 3.0. The application runs fine on the developer machine.

When I run it on the production server (IIS) I am keep getting HTTP Error 500.30. I tried to turn on stdout Log for more information but it only creates an empty folder without any logfiles. Also in the event log are no useful information about any errors.

However the application runs fine on the IIS when I run it OutOfProcess. Since our application is rather big and hard to track down any errors I created a default MVC web application without authentication. I deployed this application on the same IIS server and I am getting the exact same behaviour - it runs OutOfProcess but failes with InProcess.

Has anyone a suggestion to resolve this issue? I also found several entries on github but didn't help.

Edit - Additional information

I created a folder publish profile in VS2019 with Release configuration, target framework netcoreapp3.0, deploymentMode: Framework-Dependent and TargetRuntime: win-x86.

On the IIS I've installed the ASP.NET Core/.NET Core: Runtime & Hosting Bundle.

asp.net-core-3.0 c#
4 Answers

I have faced a similar kind of issue. Below is the step which I follow to resolve the issue.

  1. In the server run the below command in the command prompt after going to the deployed folder

    dotnet project_name.dll

  2. It shows the actual error.

In my case, I forgot to create the folder which was mentioned in appsettings.json.

Hope it will help you to find the actual issue.

user_14514800
user_4148030

I got this going from ASP.Net Core 2.1 to 3.0. For me, the problem was the specification of 

 hostingModel="InProcess"

in the web.config file. I removed that and it was all good. BTW: I couldn't get anything in the stdout log for some still unknown reason.

user_21360260

I have encountered the same problem error after deployment to Azure. After successful deployment, the web app was not started.

Then I have checked deployed files for more detailed error message via Kudu (you can use App Service > Advanced Tools>DebugConsole Menu or https://.scm.azurewebsites.net/DebugConsole )

For more information you can read from this article.

After checking, I had only Response status code does not indicate success: 401 (Unauthorized) error message which is not clear enough.

In my case, I was using the App registry in order to use Azure AD Auth. The missing part was related to missing access rights to my app registry on app service plan.

After giving contributor access and then restarting the app, it was solved.

user_129923760
Related