500.19 error on accessing Activate Web on a new install
Summary
A HTTP 500.19 error can occur when IIS is installed after the ASP.NET Core Hosting Bundle.
In this scenario, the ASP.NET Core module is not correctly registered with IIS, which prevents the web application from loading.
The issue is resolved by repairing the ASP.NET Core Hosting Bundle installation.
Symptoms
When browsing to the Activate Web Portal, IIS returns:
- HTTP Error 500.19 – Internal Server Error
- The page cannot be displayed because the related configuration data for the page is invalid.
In many cases, the detailed error will reference:
- AspNetCoreModuleV2
- aspNetCore configuration section
- An invalid module configuration
Cause
The ASP.NET Core Hosting Bundle installs the required IIS modules (including AspNetCoreModuleV2) and registers them with IIS.
If IIS is not installed at the time the Hosting Bundle is installed:
- The IIS integration components are not correctly registered.
- The aspNetCore handler and module mappings are missing.
- IIS cannot process ASP.NET Core applications.
Installing IIS afterwards does not automatically repair or register these components.
Resolution
Repair the ASP.NET Core Hosting Bundle installation.
Steps
- Log on to the Activate web server.
- Open Control Panel → Programs and Features.
- Locate Microsoft ASP.NET Core Hosting Bundle.
- Select Change.
- Choose Repair and complete the wizard.
- Restart IIS: iisreset
- Re-test the Activate Web Portal.
Alternative Method (Reinstall)
If repair does not resolve the issue:
- Uninstall the ASP.NET Core Hosting Bundle.
- Reboot the server.
- Reinstall the Hosting Bundle.
- Run iisreset.
Verification
After repair:
- Confirm the AspNetCoreModuleV2 module is visible in IIS Manager under:
- Server → Modules
- Confirm the Activate site loads without a 500.19 error.
Prevention
When building new Activate web servers:
- Install IIS first.
- Install required IIS features.
- Install the ASP.NET Core Hosting Bundle.
- Deploy Activate.
Installing components in this order ensures IIS integration is registered correctly.