IIS hosted .net core application showing 500.0

Question

when hosted .net core 8.0 version application in IIS version 10.0, it showing Error 500.30 - ASP.NET Core app failed to start

this application is connected to database. but i have same version of application hosted without database. This application is working fine.

i have checked .net version installed in my computer. They listed below

NewQueue is the application that i have issue

Jayraj Chhaya · Answer

Hi @Bineesh Viswanath, The error "CLR worker thread exited prematurely" indicates a problem with the .NET Core runtime. To troubleshoot this issue: Ensure that the correct .NET Core Hosting Bundle is installed on the server. Check the application pool settings in IIS to match the .NET Core version. Verify that the application's web.config or appsettings.json files are correctly configured. Review the permissions and ensure the application pool identity has the necessary access rights. Check for any missing dependencies or runtime components required by the application.

Bineesh Viswanath · Answer

Below is the error details showing in event Viewer Application '/LM/W3SVC/4/ROOT' with physical root 'C:\inetpub\wwwroot\NewQueue\' failed to load coreclr. Exception message: CLR worker thread exited prematurely

Jayraj Chhaya · Answer

When encountering Error 500.30 in IIS for a .NET Core application, it typically indicates a problem with the application startup process. To troubleshoot this issue, consider the following steps: Check Event Viewer : Look for detailed error logs in the Windows Event Viewer under "Windows Logs" > "Application" to identify specific error messages related to the application startup. Verify Application Pool Settings : Ensure that the application pool running the .NET Core application is configured correctly, especially regarding the .NET CLR version and pipeline mode. Review Web.config : Check the Web.config file for any misconfigurations, especially related to database connections or environment-specific settings. Update Dependencies : Ensure that all required dependencies for database connectivity are correctly installed and configured. Restart IIS : Sometimes, a simple restart of the IIS server can resolve temporary configuration issues. By following these steps and analyzing the error logs, you can pinpoint the root cause of the Error 500.30 and take appropriate actions to resolve the startup failure of the "NewQueue" application in IIS.