Skip to main content

How to Troubleshoot an IIS 500.19 Configuration Error

An IIS 500.19 error indicates that the web server cannot process a request because of a configuration error in the web.config file. This error typically occurs when a section of the configuration is locked at the server level or when the configuration...

An IIS 500.19 error indicates that the web server cannot process a request because of a configuration error in the web.config file. This error typically occurs when a section of the configuration is locked at the server level or when the configuration contains invalid syntax.

Before you begin

You will need:

  • Administrator access to the Windows Server

  • Access to the specific website's root directory

  • The ability to use the IIS Manager console

Check the web.config file for syntax errors

The most common cause of a 500.19 error is a malformed web.config file.

  1. Navigate to the website's root directory.

  2. Open the web.config file using a text editor such as Notepad++ or the IIS Manager editor.

  3. Check for common syntax errors, including:

    • Unclosed tags or attributes.

    • Typos in attribute names.

    • Special characters that are not properly escaped.

  4. Save the file and refresh the website in a browser.

Check for locked configuration sections

IIS often "locks" certain sections of the configuration (such as <modules>, <handlers>, or <requestFiltering>) to prevent them from being modified by individual websites. If an application requires a change to a locked section, it will trigger a 500.19 error.

  1. Open Internet Information Services (IIS) Manager.

  2. Select the Server Name in the left pane.

  3. Double-click Feature Delegation in the center pane.

  4. Locate the section mentioned in the error (e.g., Handler Mappings or Modules).

  5. If the status is Read Only, the section is locked.

  6. Right-click the section and select Read/Write.

  7. Restart the IIS service or the specific Application Pool.

Identify the specific locked section via the error message

The 500.19 error page often provides a specific "Config Error" message that identifies which section is causing the failure.

  1. Load the page showing the 500.19 error in a browser.

  2. Look for a line stating: The section 'X' cannot be extended.

  3. Note the name of the section (e.g., modules, handlers, or requestFiltering).

  4. Open the IIS Manager.

  5. Select the Server Name and open the Feature Delegation tool.

  6. Locate the specific section identified in the error message.

  7. Change the setting from Read Only to Read/Write.

  8. Restart the IIS service.

Verify the .NET Framework version and hosting bundle

If you are running an ASP.NET Core application, a 500.19 error can occur if the required hosting bundle is missing or if the web.config is attempting to use features not supported by the installed version.

  1. Open Control Panel > Programs and Features.

  2. Verify that the Microsoft .NET Core [Version] Hosting Bundle is installed.

  3. If the application requires a specific version (e.g., .NET 6.0 or .NET 8.0), ensure the corresponding bundle is present.

  4. If you recently updated the application, ensure the web.config reflects the correct environment settings.

Confirm the configuration is valid in IIS Manager

You can use the IIS Manager to validate the configuration of a specific site.

  1. Open Internet Information Services (IIS) Manager.

  2. Select the specific Site in the left pane.

  3. In the right-hand Actions pane, click Test Settings.

  4. Review the results for any errors regarding the web.config or specific configuration sections.

Confirm the result

  • The website loads successfully without the 500.19 error page.

  • The browser displays the expected content or application home page.

Limitations

This procedure addresses configuration-level errors. It does not resolve application-level bugs, database connection failures, or permission issues that do not involve the web.config structure.

Did this answer your question?