I faced an error "Application '/LM/W3SVC/2/ROOT' with physical root '######' failed to load coreclr." after upgrading my site to DotNet 6

Question

I faced an error "Application '/LM/W3SVC/2/ROOT' with physical root '######' failed to load coreclr." after upgrading my site to DotNet 6

Sunil Ratna Bajracharya 0

I have upgrade my site from DotNet Core 2.1 to DotNet 6. It seems to work fine for couple of days. Then it started to crash in random interval of time.

I checked in the Event Log to find out the cause of this issue and I found the following error message. "Application '/LM/W3SVC/2/ROOT' with physical root 'C:....' failed to load coreclr. Exception message: Managed server didn't initialize after 4****** ms."

It seems to be issue with ".Net Runtime" and "IIS AspNet Core Module V2".But I have not found the solution to stop from my site getting crashed.

I have changed the AspNet Hosting model from "Inprocess" to "OutOfProcess" too But it did not work. I also added the StartUptime but it did not work either.

Yurong Dai-MSFT 2,846 Reputation points Microsoft External Staff

2023-03-14T09:54:15.9133333+00:00
Hi @Sunil Ratna Bajracharya,
According to the MSDN for "500.37 ANCM Failed to Start Within Startup Time Limit"

ANCM failed to start within the provided startup time limit. By default, the timeout is 120 seconds. This error can occur when starting a large number of apps on the same machine. Check for CPU/Memory usage spikes on the server during startup. You may need to stagger the startup process of multiple apps. Your server might simply be overloaded to handle the startup of the app at that time.

I suggest that you close the application running on the system first, then try again to increase the startup time limit, there is an option in web.config element <aspNetCore>.

<system.webServer> <aspNetCore xdt:Transform="SetAttributes(startupTimeLimit)" startupTimeLimit="500"> </aspNetCore> </system.webServer>

There were similar discussions here that may provide some help depending on your application:

HTTP Error 500.37 - ANCM Failed to Start Within Startup Time Limit - Still not resolved after increasing Startup Time Limit
Azure Functions Error HTTP Error 500.37 - ANCM Failed to Start Within Startup Time Limit
IIS AspNetCore Module V2 throws failed to load coreclr

Your answer

Yurong Dai-MSFT 2,846 Reputation points Microsoft External Staff

2023-03-14T09:54:15.9133333+00:00

Hi @Sunil Ratna Bajracharya,
According to the MSDN for "500.37 ANCM Failed to Start Within Startup Time Limit"

ANCM failed to start within the provided startup time limit. By default, the timeout is 120 seconds. This error can occur when starting a large number of apps on the same machine. Check for CPU/Memory usage spikes on the server during startup. You may need to stagger the startup process of multiple apps. Your server might simply be overloaded to handle the startup of the app at that time.

I suggest that you close the application running on the system first, then try again to increase the startup time limit, there is an option in web.config element <aspNetCore>.

<system.webServer> <aspNetCore xdt:Transform="SetAttributes(startupTimeLimit)" startupTimeLimit="500"> </aspNetCore> </system.webServer>

There were similar discussions here that may provide some help depending on your application:

HTTP Error 500.37 - ANCM Failed to Start Within Startup Time Limit - Still not resolved after increasing Startup Time Limit
Azure Functions Error HTTP Error 500.37 - ANCM Failed to Start Within Startup Time Limit
IIS AspNetCore Module V2 throws failed to load coreclr

Share via

I faced an error "Application '/LM/W3SVC/2/ROOT' with physical root '######' failed to load coreclr." after upgrading my site to DotNet 6

Your answer