Programming has become a lot easier than it used to be; however, that’s not to say that it still doesn’t require effort. While the entire process may be simplified now, random bugs and errors are still relatively common.
In this article, we’re talking about the HTTP error 502.5 – ANCM Out-of-process startup failure error, its causes and what you can do to fix the problem.
What causes this error?
Either of these situations usually causes the error:
- The application process failed to start.
- The application process started but crashed.
- The application process started but failed to listen on the configured port.
How to fix this?
Here are two fixes you can try out.
Install the required .NET Core version
If the app you’re running is targeting a .NET Core version that’s not installed on the machine, it can cause a crash leading to this error at runtime. This is a common failure condition when the app targets a version of the ASP.NET Core shared framework that isn’t present on the machine.
The first thing you should do is find out the specific version of .NET Core that the app you’re running targets and install the required runtime version.
Use self-contained deployment
If you use the self-contained deployment method when publishing or deploying your app, you’ll be packaging all the dependencies your app requires into one deployment package. These dependencies, otherwise called deployment artefacts, keep your app from running into basic runtime issues when launched on a different system or deployed in the field.