1)Give Permission to All user for Files:

File authorization problems may impede an ASP.NET Core program from reaching the necessary files for operation, leading to the occurrence of the “HTTP Error 500.30 – ASP.NET Core app failed to start.” It is vital to guarantee that your program possesses the suitable permissions to access its files and folders.

Steps to Verify and Correct File Permission Issues:

  1. place project folder in C:\inetpub\wwwroot\your project folder
  2. Go to the “Security” tab.
image 5

Give Full access IIS _IUSRS and restart the APPPOOL of the project

Solution 2:

: Examining Application Configuration Incorrect application settings may result in startup malfunction. Examine your “appsettings.json” document for inconsistencies.

Access the “appsettings.json” file within your project. Confirm the accuracy of all configurations. Particular focus should be placed on connection strings, file pathways, and web addresses. Rectify any inconsistencies and preserve the modifications.

Solution 3:

Installing or changing Version of .NET Core Hosting Bundle

The .NET Core Hosting Bundle comprises the .NET Core Runtime and the ASP.NET Core Module, enabling the execution of ASP.NET Core applications within IIS.

If the Hosting Bundle is installed prior to IIS, it needs to be repaired. After installing IIS, rerun the Hosting Bundle installer for the necessary configuration.

Solution 4:

Leveraging ASP.NET Core Logging Activation of logging within ASP.NET Core proves immensely beneficial in pinpointing application issues. Error logs are integrated into Microsoft.Extensions.Logging. We advise consulting the Logging segment in the .NET official documentation for further guidance.

Solution 5: Checking Event Logs in Windows

Guide on Checking Event Logs in Windows:

  1. Press the “Windows” key on your keyboard or click on the Windows icon in the taskbar to open the Start menu.
  2. In the search bar, type “Event Viewer” and press Enter.
  3. The Event Viewer window will open. Here, you’ll find a tree structure on the left-hand side with various categories of event logs, such as Application, Security, Setup, System, and more.
  4. Click on the category that corresponds to the type of event log you want to check. For example, if you’re looking for application-related events, click on “Application.”
  5. Once you’ve selected the desired category, the corresponding events will appear in the middle pane. You can scroll through these events to view details such as the date and time of occurrence, event ID, and description.
  6. If you want to filter the events based on specific criteria, you can use the “Filter Current Log” option in the Actions pane on the right-hand side.
  7. To view detailed information about a specific event, double-click on it. This will open a new window with additional details, including event properties and error codes.
  8. You can also use the search feature in Event Viewer to quickly find specific events. Simply type keywords related to the event you’re looking for in the search box at the top-right corner of the window.
  9. Once you’ve finished reviewing the event logs, you can close the Event Viewer window by clicking on the “X” button in the top-right corner.
  10. It’s important to note that accessing event logs may require administrative privileges on your Windows system. If prompted, provide the necessary permissions to view the logs.


Need Professional Software click here to contact us