IIS 7.5 and ASP .NET 2.0

▲
16
▼

Are there any known issues with IIS 7.5? I'm getting the following error when I try to browse/start/view any page on the site.

HTTP Error 500.19 - Internal Server Error
The requested page cannot be accessed because the related configuration
 data for the page is invalid.

Module  IIS Web Core
Notification    BeginRequest
Handler Not yet determined
Error Code  0x80070021
Config Error    This configuration section cannot be used at this path. 
 This happens when the section is locked at a parent level. Locking is either by
default (overrideModeDefault="Deny"), or set explicitly by a location tag with 
  overrideMode="Deny" or the legacy allowOverride="false". 

Config Source
97:         </modules>
98:         <handlers>
99:             <remove name="WebServiceHandlerFactory-Integrated"/>
asp.net
asp.net-2.0
iis-7.5
asked on Stack Overflow Aug 1, 2009 by abjbhat • edited Jul 14, 2011 by gideon

9 Answers

▲
18
▼

Had a similar issue, ended up finding this article of use: http://support.microsoft.com/kb/942055

basically the applicationHost.config had the handler section locked: was 

<section name="handlers" overrideModeDefault="Deny" />

i changed it to 

<section name="handlers" overrideModeDefault="Allow" />

and it worked.

also worth checking that ALL the asp.net roles have been installed, see link text.

answered on Stack Overflow Sep 1, 2009 by TheRealQuagmire • edited Sep 1, 2009 by TheRealQuagmire
▲
5
▼

This has solved my issue on Windows 7 64bit IIS 7.

answered on Stack Overflow Nov 17, 2009 by Aboo
▲
2
▼

Using a text editor such as Notepad, open the applicationHost.config file in the following location:

%windir%\system32\inetsrv\config\applicationHost.config

Basically, the applicationHost.config had the handler section locked. It was

<section name="handlers" overrideModeDefault="Deny" />

changed it to

<section name="handlers" overrideModeDefault="Allow" />

and it works.

answered on Stack Overflow Dec 19, 2011 by Sai Ram • edited Dec 19, 2011 by eeerahul
▲
2
▼

I suspect that the majority of people receiving this error did not select enough check boxes in the iis feature selection in "Programs and Features" in the control panel's install.

Terrible error reporting IMO.

answered on Stack Overflow Feb 22, 2012 by David • edited Feb 22, 2012 by David
▲
1
▼

The last answer gave me the answer, then it gave me another error, so you should check this one too

answered on Stack Overflow Apr 15, 2010 by Sanchitos • edited Nov 2, 2011 by Shadow The Vaccinated Wizard
▲
1
▼

This is comming due to asp.net not install in IIS for this, Turn on Windows features on or off, iis feature selection in "Programs and Features" in the control panel's. Select IIS then "world wide web services" then "Application Devlopment Features" then "ASP" and "ASP.NET"

answered on Stack Overflow Jun 13, 2013 by user2482222
▲
0
▼

After fixing as above said We will get the following error

Error message when you visit a Web site that is hosted on IIS 7.0:
HTTP Error 403.14 - Forbidden.

To resolve this problem, use one of the following methods.

Method 1:To resolve this problem, follow these steps:

  • Start IIS Manager. To do this, click Start, click Run, type inetmgr.exe, and then click OK.
  • In IIS Manager, expand server name, expand Web sites, and then click the Web site that you want to modify.
  • In Features view, double-click Directory Browsing.
  • In the Actions pane, click Enable.

Method 2: To resolve this problem, follow these steps:

  • Start IIS Manager. To do this, click Start, click Run, type inetmgr.exe, and then click OK.
  • In IIS Manager, expand server name, expand Web sites, and then click the Web site that you want to modify.
  • In Features view, double-click Default Document.
  • In the Actions pane, click Enable.
  • In the File Name box, type the name of the default document, and then click OK.
answered on Stack Overflow Nov 1, 2011 by Swapna Vallabhaneni • edited Nov 2, 2011 by Sathyajith Bhat
▲
0
▼

HTTP Error 500.19 - Internal Server Error

This also happens if the .Net Framework Version is not correct or the Managed Pipeline Mode is not set properly.

answered on Stack Overflow Feb 10, 2012 by Rahatur
▲
0
▼

Was facing the same error. This solved my issue http://blog.laksha.net/2009/08/http-error-50019-internal-server-error.html

answered on Stack Overflow Jul 17, 2012 by vighnu

User contributions licensed under CC BY-SA 3.0