HTTP Error 500.30 - ANCM In-Process Start Failure

[Plasma]

Describe the bug

When trying to launch an ASP.NET Core 2.2 web app locally (Windows 10) I receive HTTP Error 500.30 - ANCM In-Process Start Failure error message when the browser opens.

To Reproduce

Steps to reproduce the behavior:

1. Using this version of ASP.NET Core 2.2
2. Configure to use IIS in-process model

Expected behavior

It to work without error.

Screenshots

More information

None of the other bug reports appear to have a resolution.

Is this an Azure only feature, and wont ever work locally? How is it supposed to work locally?

Assuming its the most performant option, can I make it so local development continues to use Kestrel and only production/Release-mode uses IIS in-proc?

Thanks

[Plasma]

This also breaks with the same exact message on Azure App Service sometimes when restarting the website. Is it meant to be this broken? :(

[tonyatl]

i have the same problem on windows data center 2016 iis 10. i created vs 2017.9 asp.net .net core mvc application - no changes. it runs successfully on windows 10 iis but not on server. i am using asp.net core 2.2.3 runtime. i am running DotNetCore.2.0.8-WindowsHosting and httpPlatformHandler_amd64 and dotnet-hosting-2.2.3-win. the application starts as a kestrel process - ie i run the exe of my application or dotnet myapp.dll.

an empty log is created - no messages no nothing to help further isolate/identify issue.

ps - after more poking around i found a similar - perhaps same - issue
HRESULT returned: 0x800700b7

Cannot create a file that already exists?

https://github.com/aspnet/IISIntegration/blob/master/src/AspNetCoreModuleV2/InProcessRequestHandler/inprocessapplication.cpp#L415

in fact that hresult is the same one i got.

pps - so has this bug been fixed? if so where do i get the fix?

ppps - is the work around to use out of process?

[analogrelay]

Have you looked at the troubleshooting guidance in our documentation? https://docs.microsoft.com/en-us/aspnet/core/host-and-deploy/iis/troubleshoot?view=aspnetcore-2.2#50030-in-process-startup-failure

If you still have failures after going through those steps, let us know.

[Plasma]

I think I may have a lead on this, at least for local development.

I started my project with using the legacy out of process hosting system, and then later switch to the InProcess system. This seemed to have broken things with this obtuse error.

I then changed the port number and it started to work. Does it have something to do with the applicationHost.config file perhaps?

[analogrelay]

Have you looked at the Event log or standard output logs as described in the doc I linked?

[analogrelay]

Closing this as we haven't heard from you and generally close issues with no response after ~7 days. Please feel free to comment if you're able to get the information we're looking for and we can reopen the issue to investigate further!

[deanilvincent]

This error appears to me after I accidentally registered the same interface in my ConfigureServices

`services.AddScope<IMyInterface, IMyInterface>();`

Make sure to double check your Startup.cs ConfigureServices

[worldspawn]

I can confirm I also had some dynamic registrations registering an interface as both service type and implementation type. What an astonishingly awful job aspnetcore does of communicating this. We're like one or two steps away from the bad old days of Error 0x80001000.

[KooshkakiH]

I get this error and problem was mistake connection string.

[analogrelay]

Just a heads-up that since this is a closed issue we don't track it in our regular issue management processes. If you are still seeing this error and need assistance, please file a new issue so it gets right in our face :).

@worldspawn these kinds of errors should definitely be reported (in detail) on the error page when in Development mode (in ASP.NET Core 3.0 previews and the coming RTM version). We can't report them in production environments because it's a security risk, but there they should land in the Windows Event Log (in detail). If you have a situation where you aren't seeing the detailed error page in development mode (when dotnet runing or launching from VS) please feel free to file a new issue.w

[robinwilson16]

I got this error and realised I had missed a comma out of the appsettings.json file.
May be worth a try for anyone still getting this issue.

It would be good if it did give a less generic error though to speed up troubleshooting.