Struggling with HTTP Error 502.5 – Process Failure error on your website?

ASP.NET platform helps to create and develop web applications effectively.

However, process failure error happens when the ASP.NET application fails to run on the server.

At Bobcares, we get requests on ASP.NET errors for our customers, as a part of our Server Management Services.

Today, let’s see how our Support Engineers fix the error for our customers.

Causes for HTTP Error 502.5 – Process Failure

In general, the 502.5 error occurs when the ASP.NET application is not running. However, from our expertise in managing server, our Windows Experts identify the common causes for the error as:

• Incorrect deployment and architecture
• Missing .NET framework installation in the server.
• The application pool has no access to the .NET files.
• Incorrect path in web.config

Further, we check the Event log to find more information regarding the error. The sample error looks like:

How to fix HTTP Error 502.5 – Process Failure

Recently one of our customers contacted as his website was showing HTTP Error 502.5 – Process Failure error. Let us discuss how our Support Engineers resolved the error.

1. Wrong Deployment mode and architecture

The common reason for the error is the incorrect architecture or the deployment mode. On analyzing the server we found that the 64-bit .NET core was installed.

On checking the .net files, the files were present in 32-bit architecture. So our Support Engineers resolved the error by changing the architecture to the correct version.

We opened the .NET exe file and changed the Deployment mode to Self-Contained.

Next, we changed the Target Runtime to win-x6. Finally, saved the changes.

Changing the deployment will change the runtime to the application directory. So we always analyze the whole system and the impact it will create before changing the option.

Thus changing the option resolved the error.

2.The .NET framework not installed

Another reason for the error is that the .NET framework is not installed on the server. A few application requires framework libraries to run the application. The .NET Core doesn’t support the desktop applications with a user interface.

Thus we install the .NET framework for our customers in the server to resolve the error.

3. Incorrect path in web.config

The web.config contains variables LAUNCHER_PATH and LAUNCHER_ARGS. When IIS tries to run the application, it uses these variables to connect.

So our Support Engineers add the below code on the web.config file to publish the contains from the output folder.

<aspNetCore processPath="dotnet" arguments=".\MyApplication.dll" stdoutLogEnabled="true"
stdoutLogFile=".\logs\stdout" forwardWindowsAuthToken="false" />

Adding the lines will replace the variables with the exact path.

[Looking for fixing ASP.net errors? Come to us, we’ll help you.]

Conclusion

In short, we have discussed the causes for the error HTTP Error 502.5 – Process Failure. Also, we have discussed how our Support Engineers resolve the error.