California Consumer Privacy Act (CCPA) Opt-Out Icon

introduction

ASP.NET Core applications hosted on IIS are designed to deliver powerful performance. However, in some cases, you may encounter issues where the app does not start properly within the expected time. One common problem is HTTP Error 500.37, which indicates that the application failed to start within the startup time limit. This article will guide you through what causes this error and how to fix it.

problem

HTTP Error 500.37 occurs when an ASP.NET Core application hosted on IIS does not start within the allotted startup time. The default timeout is 120 seconds. This can be caused by a variety of reasons, such as limited resources (CPU and memory), long initialization operations, or improper startup time configuration in IIS. The error message usually looks like this:

This issue can be particularly problematic for large or resource-intensive applications that may require longer startup times to complete initialization operations.

way out

The good news is that you can easily fix this problem by increasing the startup time limit for your application in the web.config file. Here’s a step-by-step guide to apply the fix:

Find your application web.config The file must be located in the root directory of your ASP.NET Core application. and update Start time limit to a value higher than the default 120 within seconds part time job.

In this example, startTimeLimit is set to 360 seconds (6 minutes). You can adjust this value depending on the needs of your application. This configuration allows your application to have a longer period of time to properly initialize, preventing 500.37 errors from occurring.

Although this fix may resolve the issue and keep your application running smoothly, it is important to review the following: Startup.cs or Program.cs A file to identify if there are any modules or dependencies that are taking longer than expected to initialize.

conclusion

HTTP Error 500.37 indicates a failure to start an ASP.NET Core application on IIS that requires more time to initialize. by adjusting Start time limit In the web.config file, you can provide the time needed to start the application and avoid startup errors. This simple yet effective solution ensures that your applications run smoothly even under complex startup conditions.