Troubleshooting HTTP Error 500.30 in Azure App Service Webapp

Azure App Service troubleshooting | Azure App service Console debugging | Azure app service app start failures | dotnet core web app failures in start

Troubleshooting HTTP Error 500.30 in Azure App Service Webapp
Sanjeevi Subramani's photo
Sanjeevi Subramani

Published on Sep 25, 2020

2 min read

Subscribe to my newsletter and never miss my upcoming articles

In .NET Core 3.1 created a simple api and published in Azure App Service which was giving the following error: HTTP Error 500.30 — ANCM In-Process Start Failure.

Enabled logging using Azure Application Insights but still I didn't get any logs in Application Insights for this failure.

The reason is the Api is not started itself as per below description in Microsoft portal:

The worker process fails. The app doesn’t start.

The ASP.NET Core Module attempts to start the .NET Core CLR in-process, but it fails to start. The cause of a process startup failure can usually be determined from entries in the Application Event Log and the ASP.NET Core Module stdout log.

Common failure conditions:

  • The app is misconfigured due to targeting a version of the ASP.NET Core shared framework that isn’t present. Check which versions of the ASP.NET Core shared framework are installed on the target machine.

  • Using Azure Key Vault, lack of permissions to the Key Vault. Check the access policies in the targeted Key Vault to ensure that the correct permissions are granted.

We are not getting the configured Application insights logging because the app itself is not started and the configuration of app insights is not initiated.

To see what's failing on the startup on the app service we don't need to write or integrate any other logging components just the Console log using console.writeline is sufficient for logging the error on the startup.cs or program.cs like below: Program.cs

public class Program
 {
 public static void Main(string[] args)
 {
 try
 {
 CreateHostBuilder(args).Build().Run();
 }
 catch (Exception ex)
 {
 Console.WriteLine(ex.Message + ex.StackTrace);
 }
 }

Startup.cs

public Startup(IConfiguration configuration)
 {
 try
 {
 this.Configuration = configuration;
 }
 catch (Exception ex)
 {
 Console.WriteLine(ex.Message + ex.StackTrace);
 }
 }

Now we have a question where to see this log after deploying to the Azure App Service — In Azure App service there is an Console under where you have to initiate your application as an exe like below:

yourapplicationName.exe

sample image shown below:

You will get the logs in the above console, so that you can see it and fix it.

Refer this article for writing log using Serilog at app start into a file or console or both.

Happy Coding :)

Thanks,

Sanjeevi Subramani

 
Share this