Menu
I can't seem to get any ASP.NET sites to run under IIS8 on Windows 8. Under IIS Express they are fine, but I've:
But I get: HTTP Error 500.19 - Internal Server Error The requested page cannot be accessed because the related configuration data for the page is invalid.
Config Source: -1: 0:
Any ideas?
657
When running an ASP.NET Core website in IIS, you may experience the following error: "HTTP Error 500.19 – Internal Server Error" (Code: 0x8007000d)
When running an ASP.NET Core website in IIS, you may experience the following error: "HTTP Error 500.19 – Internal Server Error" (Code: 0x8007000d) The following article describes the error as being "This problem occurs because the ApplicationHost.config file or the Web.config file contains a malformed XML element.":
At Bobcares, we often receive requests to fix IIS related errors as part of our Server Management Services. Today, let’s analyze IIS error 500.19 and see how our Support Engineers fix it for our customers. The IIS error 500.19 causes due to a number of reasons.
There’s one intermittent 500.19 error we’ve observed while using Shared Configuration with multiple web servers in a load balanced environment and the configuration files stored on a common UNC file share. In this scenario, if the file share content goes offline, the web server will stop responding.
ASP.Net applications come pre-wired with a handlers section in the web.config.
By default, this is set to readonly within feature delegation within IIS.
Take a look in IIS Manager, under the Server name → Feature delegation. If Handler Mappings is set to readonly and your site web.configs have a handlers section, flip the value to read/write and see what happens.
Worked for me when moving to Windows 8 / IIS 8 / ASP.Net MVC 4.
71
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
