Click here to Skip to main content
15,890,717 members
Please Sign up or sign in to vote.
0.00/5 (No votes)
I want to run a project on IIS 8.5, but fails. Please help me.
XML
HTTP Error 500.19 - Internal Server Error
The requested page cannot be accessed because the related configuration data for the page is invalid.

Detailed Error Information:
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 File    \\?\F:\SERVER_ASP\Website\web.config
Requested URL      http://192.168.1.101:2014/
Physical Path      F:\SERVER_ASP\Website
Logon Method       Not yet determined
Logon User     Not yet determined

Config Source:
   54:     <validation validateIntegratedModeConfiguration="true" />
   55:     <handlers>
   56:       <remove name="ExtensionlessUrlHandler-ISAPI-4.0_32bit" />
Posted

1 solution

 
Share this answer
 
Comments
Member 8070609 5-May-14 23:58pm    
I did this and the following error:
HTTP Error 500.21 - Internal Server Error
Handler "ExtensionlessUrlHandler-Integrated-4.0" has a bad module "ManagedPipelineHandler" in its module list

Most likely causes:
Managed handler is used; however, ASP.NET is not installed or is not installed completely.
There is a typographical error in the configuration for the handler module list.
During application initialization, either the application initialization feature has set skipManagedModules to true, or a rewrite rule is setting a URL that maps to a managed handler and is also setting SKIP_MANAGED_MODULES=1.

Things you can try:
Install ASP.NET if you are using managed handler.
Ensure that the handler module's name is specified correctly. Module names are case-sensitive and use the format modules="StaticFileModule,DefaultDocumentModule,DirectoryListingModule".
Ensure that any application initialization rewrite rules set SKIP_MANAGED_MODULE=0 when setting a URL that maps to a managed handler (such as .aspx, for example.)
As an alternative, ensure that application initialization rewrite rules map the request to an unmanaged handler (for example, to an .htm file, which is mapped to the StaticFileHandler.)
DamithSL 6-May-14 0:05am    
what is the target framework of your web application? what is the application pool .net framwork for your iis web application?
Member 8070609 6-May-14 0:07am    
Net framwork 4.5, mvc 4
Sanket Saxena 6-May-14 0:15am    
check your application pool
DamithSL 6-May-14 1:53am    
check http://www.codeproject.com/Articles/674930/Configuring-IIS-ASP-NET-and-SQL-Server

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)



CodeProject, 20 Bay Street, 11th Floor Toronto, Ontario, Canada M5J 2N8 +1 (416) 849-8900