Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
HTTP Error 500.30 - ANCM In-Process Start Failure
See original GitHub issueDescribe 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
Issue Analytics
- State:
- Created 4 years ago
- Comments:39 (4 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
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.csConfigureServices