KB Patch Stopped .Net Core API from Starting

George Belletty 0

We have a .Net Core 6 API running in IIS 10.

Since Sunday 26th February the API has been failing by timeout with the following error:

HTTP Error 500.37 - ASP.NET Core app failed to start within startup time limit

The environment is AWS - Windows Server 2016 Datacenter.

We suspect the issue started when a windows update patch was applied.

Our server team started uninstalling patches, and the API started to work again. But, the patch will be installed again automatically, so this is not a long term solution.

Unfortunately, we don't have the name of the windows update patch.

I'm not seeing any reports of this online from other dev teams.

Is this a known issue or does anyone have any more information about this?

Sam Wu-MSFT 7,286 Reputation points Microsoft Vendor

2023-03-03T09:20:49.2733333+00:00

@George Belletty

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.

You can also try increasing the startupTimeLimit to 300 to solve this issue, more information you can refer to this link: https://stackoverflow.com/a/62810710/13336642

Share via

KB Patch Stopped .Net Core API from Starting