ASP.NET application encountering HTTP Error 500.19 - Internal Server Error on IIS

Mark Alfred 20 Reputation points
2023-12-13T06:41:18.3166667+00:00

Hey everyone,

I am currently developing an ASP.NET Core web application for my Fiiviq website. and I'm facing an issue with my ASP.NET application hosted on IIS. Whenever I try to access certain pages, I encounter an HTTP Error 500.19 - Internal Server Error. The error message specifically mentions a configuration issue related to the <configSections> element in my web.config file.

Here's a snippet of the section causing the problem:

<configSections>
  <sectionGroup name="myCustomGroup">
    <section name="myCustomSection" type="MyNamespace.MyCustomSection, MyAssembly" allowLocation="true" allowDefinition="Everywhere" />
  </sectionGroup>
</configSections>

The error message points to this block and highlights the <sectionGroup> tag, indicating a problem parsing this section.

I've checked the permissions, ensured that the necessary modules are installed, and validated the configuration files for any syntax errors. However, the issue persists.

Could someone please guide me on how to resolve this 500.19 error specifically related to the <configSections> setup? Any insights or suggestions would be greatly appreciated.

Thank you in advance!

Windows development Internet Information Services
Developer technologies ASP.NET ASP.NET Core
{count} votes

Accepted answer
  1. Yurong Dai-MSFT 2,846 Reputation points Microsoft External Staff
    2023-12-13T09:09:00.8033333+00:00

    Hi @Mark Alfred,
    Please provide complete error page information and be careful to hide private information. To resolve this 500.19 Internal Server Error, please refer to the following document and learn the appropriate HRESULT code information.

    HTTP Error 500.19 - internal server error when you open an IIS Webpage.

    Based on the partial snippet you provided that is causing the problem, I would suggest that you could temporarily remove or comment out the <configSections> block related to the custom section and see if the error persists. This can help determine if your error is related to that section.

    Additionally, enabling failed request tracing in IIS can get more detailed information about errors, which will generate detailed log files to help you identify the problem.

    Troubleshoot failed requests using tracing in IIS.


    If the answer is the right solution, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".

    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the email notification for this thread.

    Best regards,

    Yurong Dai

    0 comments No comments

0 additional answers

Sort by: Most helpful

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.