Are you getting this error after posting or publishing a .Net Core application to a web directory?

 HTTP Error 500.30 - ANCM In-Process Start Failure
Common solutions to this issue:
 
    The application failed to start
    The application started but then stopped
    The application started but threw an exception during startup
 
Troubleshooting steps:
 
    Check the system event log for error messages
    Enable logging the application process' stdout messages
    Attach a debugger to the application process and inspect
 
For more information visit: https://go.microsoft.com/fwlink/?LinkID=2028265 

It's basically a generic error and the best place to check for the reason is the Application Event Log. I've run into this error when my database connection string was incorrect or an auto-detection server version variable wasn't working. Those were obvious clues given in the Application Event Log.

However, if you don't see a reason in the Application Event Log or a less than obvious reason, one thing you can try is to:

  1. Go to IIS Manager > Application Pools and find the application pool that the website you just published to is using.
  2. Right click the application pool and choose Advanced Settings.
  3. One of the very first options is Enable 32-Bit Applications and it is set to true by default. Set it to False. Choose Ok to exit.

Refresh the page and see if your website is working now. 

Comments


Comments are closed