aspnetcore: HTTP Error 500.30 - ANCM In-Process Start Failure
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:
- Using this version of ASP.NET Core 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
About this issue
- Original URL
- State: closed
- Created 5 years ago
- Comments: 39 (4 by maintainers)
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.
This error appears to me after I accidentally registered the same interface in my
ConfigureServicesMake sure to double check your
Startup.csConfigureServicesI 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.
I get this error and problem was mistake connection string.
This work for me
In the file MyProject.csproj
I Change this line
<AspNetCoreHostingModel>InProcess</AspNetCoreHostingModel>For this
<AspNetCoreHostingModel>OutOfProcess</AspNetCoreHostingModel>I’m looking for a better solution…
This also breaks with the same exact message on Azure App Service sometimes when restarting the website. Is it meant to be this broken? 😦
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