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

I don't get this error when I run my default.aspx page using the built in VS web server (VS 2008)

I do get this error when I load my localhost\default.aspx in my .NET 3.5 Web application on my Vista Ultimate Box using IIS (not the built in VS web server):

HTTP Error 500.19 - Internal Server Error

Description: The requested page cannot be accessed because the related configuration data for the page is invalid.

Error Code: 0x80070021

Notification: BeginRequest

Module: IIS Web Core

Requested URL: http://localhost:80/

Physical Path: C:\www\Projects\3.5 VS 2008 Beta\Elbalazo\Web

Logon User: Not yet determined

Logon Method: Not yet determined

Handler: Not yet determined

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 File: \\?\C:\www\Projects\3.5 VS 2008 Beta\Elbalazo\Web\web.config

Config Source:

  170:     </modules>

  171:     <handlers>
  172:       <remove name="WebServiceHandlerFactory-Integrated" />

More Information... This error occurs when there is a problem reading the configuration file for the Web server or Web application. In some cases, the event logs may contain more information about what caused this error.

Server Version Information: Internet Information Services 7.0.

The handlers section is talking about this in my web.config which I believe is there by default when you create a new web application in the .NET 3.5 framework:

 <!-- 
        The system.webServer section is required for running ASP.NET AJAX under Internet
        Information Services 7.0.  It is not necessary for previous version of IIS.
    -->
  <system.webServer>
    <validation validateIntegratedModeConfiguration="false" />
    <modules>
      <add name="ScriptModule" preCondition="integratedMode" type="System.Web.Handlers.ScriptModule, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35" />
    </modules>
    <handlers>
      <remove name="WebServiceHandlerFactory-Integrated" />
      <add name="ScriptHandlerFactory" verb="*" path="*.asmx" preCondition="integratedMode" type="System.Web.Script.Services.ScriptHandlerFactory, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35" />
      <add name="ScriptHandlerFactoryAppServices" verb="*" path="*_AppService.axd" preCondition="integratedMode" type="System.Web.Script.Services.ScriptHandlerFactory, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35" />
      <add name="ScriptResource" preCondition="integratedMode" verb="GET,HEAD" path="ScriptResource.axd" type="System.Web.Handlers.ScriptResourceHandler, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35" />
    </handlers>
    <defaultDocument>
      <files>
        <clear />
        <add value="default.aspx" />
        <add value="index.aspx" />
      </files>
    </defaultDocument>
  </system.webServer>

Initially I thought this problem was because I needed to change overrideModeDefault="Deny" to overrideModeDefault="Allow" so I changed all instances of this to Allow in my C:\Windows\System32\inetsrv\config\applicationHost.xml file on my Vista Ultimate machine. That made this error go away but then the second error stated that a handler that is mapped in my web.config has a problem.

I then get this second error:

HTTP Error 404.3 - Not Found

Description: The page you are requesting cannot be served because of the Multipurpose Internet Mail Extensions (MIME) map policy that is configured on the Web server. The page you requested has a file name extension that is not recognized, and is not allowed.

Error Code: 0x80070032

Notification: ExecuteRequestHandler

Module: StaticFileModule

Requested URL: http://localhost/Default.aspx

Physical Path: C:\www\Projects\3.5 VS 2008 Beta\Elbalazo\Web\Default.aspx

Logon User: Anonymous

Logon Method: Anonymous

Handler: StaticFile

Most likely causes:

It is possible that a handler mapping is missing. By default, the static file handler processes all content.
The feature you are trying to use may not be installed.
The appropriate MIME map is not enabled for the Web site or application. (Warning: Do not create a MIME map for content that users should not download, such as .ASPX pages or .config files.)

What you can try:

In system.webServer/handlers:
Ensure that the expected handler for the current page is mapped.
Pay careful attention to preconditions (e.g. runtimeVersion, pipelineMode, bitness) and compare them to the settings for your application pool.
Pay careful attention to typographical errors in the expected handler line.
Please verify that the feature you are trying to use is installed.
Verify that the MIME map is enabled or add the MIME map for the Web site using the command-line tool appcmd.exe.
1. Open a command prompt and change directory to %windir%\system32\inetsrv.
2. To set a MIME type, use the following syntax: appcmd set config /section:staticContent /+[fileExtension='string',mimeType='string']
3. The variable fileExtension string is the file name extension and the variable mimeType string is the file type description.
4. For example, to add a MIME map for a file which has the extension ".xyz", type the following at the command prompt, and then press Enter:
5. appcmd set config /section:staticContent /+[fileExtension='.xyz',mimeType='text/plain']
Warning: Ensure that this MIME mapping is needed for your Web server before adding it to the list. Configuration files such as .CONFIG or dynamic scripting pages such as .ASP or .ASPX, should not be downloaded directly and should always be processed through a handler. Other files such as database files or those used to store configuration, like .XML or .MDF, are sometimes used to store configuration information. Determine if clients can download these file types before enabling them.
Create a tracing rule to track failed requests for this HTTP status code. For more information about creating a tracing rule for failed requests, click here.

More Information... This error occurs when the file extension of the requested URL is for a MIME type that is not configured on the server. You can add a MIME type for the file extension for files that are not dynamic scripting pages, database, or configuration files. Process those file types using a handler. You should not allows direct downloads of dynamic scripting pages, database or configuration files.

Server Version Information: Internet Information Services 7.0.

I have still no clue how to resolve this after trying to look at the web.config and IIS.

Re: 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

I have not tried these steps but take a look at http://blog.donnfelker.com/CommentView,guid,1ff098d5-bba0-491e-b13c-e0a42d95f999.aspx

Re: 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

I stated in my initial post that I did that...Please re-read...thanks.

Also I confirmed that this happens to any web project I create in VS 2008. I tried just a simple test project and tried to run http://localhost/, same error message in it's out of box default.aspx page for this test project.

Re: 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

Good God, I swear I had selected everything in IIS when enabling it but didn't...missed some of the asp.net stuff. Duh

http://www.netomatix.com/Development/IIS7_404Error.aspx

Re: 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

Received this same issue after installing IIS 7 on Vista Home Premium. To correct error I changed the following values located in the applicationHost.config file located in Windows\system32\inetsrv.

Change all of the following values located in section <configSections> --> <sectionGroup name="system.webServer">

<div mce_keep="true"><section name="handlers" overrideModeDefault="Deny" /> change this value from "Deny" to "Allow"</div>
<div mce_keep="true"><section name="modules" allowDefinition="MachineToApplication" overrideModeDefault="Deny" /> change this value from "Deny" to "Allow"</div>

Re: 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

ddeputy,

Thank you! That's exactly what I needed.

Re: 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

Great! Thanks did the trick for me too

regards

Liam

Re: 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

In windows 2008, where the config should be (applicationhost.config) for handlers allow??? Is there any difference in windows 2008?

Re: 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

%windir%\system32\inetsrv\config\. -> thats the location

Re: 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

I did exactly what is written here,but I still have the second Error "The page you are requesting cannot be served because of the extension configuration. If the page is a script, add a handler. If the file should be downloaded, add a MIME map."

Is there anybody,who knows how to fix it???

Thanks.

Re: 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

ddeputy

Received this same issue after installing IIS 7 on Vista Home Premium. To correct error I changed the following values located in the applicationHost.config file located in Windows\system32\inetsrv.

Change all of the following values located in section <configSections> --> <sectionGroup name="system.webServer">

<div><section name="handlers" overrideModeDefault="Deny" /> change this value from "Deny" to "Allow"</div>
<div><section name="modules" allowDefinition="MachineToApplication" overrideModeDefault="Deny" /> change this value from "Deny" to "Allow"</div>

Is there anybody,who knows how to fix it???

Thanks.

P.S. I use Windows 7

Re: 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

mikehac

I did exactly what is written here,but I still have the second Error "The page you are requesting cannot be served because of the extension configuration. If the page is a script, add a handler. If the file should be downloaded, add a MIME map."

Is there anybody,who knows how to fix it???

Thanks.

P.S. I use Windows 7

mikehac,

I was able to resolve this issue in my own Windows 7 webserver using the Microsoft Web Installer Platform (http://www.microsoft.com/web/downloads/platform.aspx).

From the GUI or finding it in the IIS MMC manager, Click on the Web Platform tab
Then click on the Customize link below the Frameworks and Runtimes options.
Select ASP.NET and ASP.NET MVC 1.0 (if necessary)
and then click install.

Should resolve your issue. You can also probably do this without using the Web Installer Platform, but this was specifically the way I was able to resolve the same problem.

Regards

Re: 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

Thanks from me too. been looking around to solve this issue for quite long.

Re: 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

yes this is working

http://www.microsoft.com/web/downloads/platform.aspx

the microsoft web platform installer 2.0 solution provided about is working , thanks to ngarvey

<------------------------------------------------------------>

I was able to resolve this issue in my own Windows 7 webserver using the Microsoft Web Installer Platform (http://www.microsoft.com/web/downloads/platform.aspx).

From the GUI or finding it in the IIS MMC manager, Click on the Web Platform tab
Then click on the Customize link below the Frameworks and Runtimes options.
Select ASP.NET and ASP.NET MVC 1.0 (if necessary)
and then click install.

Should resolve your issue. You can also probably do this without using the Web Installer Platform, but this was specifically the way I was able to resolve the same problem.

<------------------------------------------------------------>

Re: 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

this worked for me too

http://www.microsoft.com/web/downloads/platform.aspx

thanks

Re: 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

I had the same problem.I reinstalled ASP.NET from command prompt.

Follow the steps:

1. Goto command prompt

2. goto C:\Windows\Microsoft.NET\Framework64\v2.0.50727 and execute aspnet_regiis -i

Thanks.

AWESOME.

When will Microsoft simplify this??? i felt like i was giving everybody permissions, then your link points out more configuration is required for your pc, like allowing .Net development. what???

i guess this is life-time employment for MS engineers and us developers. ugh.

Re: 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

You need to go to Control Panel > Programs > Turn Windows Features on or off

Then navigate to Internet Information Services > World Wide Web Services > Application Development Features

and tick ASP.NET. This adds the relevant mappings to handle ASP.NET extensions correctly ad I believe is what using the Web Platform Installer is essentially doing for you. This worked for me on Windows 7 x64 Professional running IIS 7.5