Skip to main content

HTTP Error 500.19 - Internal Server Error

THE ERROR:

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

ERROR DETAILS:

Module: RequestFilteringModule
Notification: BeginRequest
Handler: StaticFile
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: \\?\C:\RnDInternet\web.config

152: <security>
153: <requestFiltering allowDoubleEscaping="true"/>
154: </security>

ERROR SCREEN SHOT:

image

KB Article for this error:

http://support.microsoft.com/kb/942055/ does discuss other error code but does not talk about this Error Code: 0x80070021.

STEPS TO RESOLVE - HOW TO CORRECT:

Most of the time following steps correct this issue:

  • Go to C:\Windows\System32\inetsrv\config folder and open applicationHost.config file. Search for <section name="handlers"
    Change

    <section name="handlers" overrideModeDefault="Deny" />
    TO
    <section name="handlers" overrideModeDefault="Allow" />
  • Alternatively you can use appcmd.exe command to unlock this section.

    Use following command to unlock this section globally:

    %windir%\system32\inetsrv\appcmd.exe unlock config -section:system.webServer/security/requestFiltering

    Use following command to unlock this section for a particular site/app:

    %windir%\system32\inetsrv\appcmd.exe unlock config "SiteName/app/url" -section:system.webServer/security/requestFiltering

But in my case I already had the required changes in applicationHost.config file. Also I notice the error code is different then normally error code. To resolve the issue I had to uninstall the IIS feature and add it back. Just by doing this everything works.

To uninstall & Install the IIS feature, go to Control Panel –> Programs and Features and then click at “Turn windows feature on or off”.

image

It will open a new dialog box in which select & expand the “Internet Information Services” –> “World Wide Web services” –> “Application Development Features” and uncheck everything. Click OK to start uninstall process.

 image

After the uninstall is done, follow the same process to open Windows Feature dialog box and select the features you want. I normally install following features.

image

I hoe this article will help other facing similar issue. Please feel free to share more tips and suggestions.

Comments

  1. Configuration Error
    Description: An error occurred during the processing of a configuration file required to service this request. Please review the specific error details below and modify your configuration file appropriately.

    Parser Error Message: It is an error to use a section registered as allowDefinition='MachineToApplication' beyond application level. This error can be caused by a virtual directory not being configured as an application in IIS.


    I converted the virual directory to the application and the it could get to the install page! thanks

    ReplyDelete

Post a Comment

Popular posts from this blog

SharePoint WebPart Error - Unable to add selected web part (s) – MOSS 2007

ISSUE: Recently I faced this issue that when I try to deploy my WebPart.  Unable to add selected web part(s). WebPartName: Cannon unregister UpdatePanel with ID ‘ctl00RTMPanel’ since it was not registerd with the ScripManager. This might occure if the UpdatePanel was removed from the control tree and later added again, which is not supported. Parameter name: updatePanel.   I faced this issue twice and both the time the issue was not what display here. This could be sure to any error in the WebPart. Following are list resolution from multiple instances.   RESOLUTION: 1. Check the WebPartName.webpart file. Check whether you have a proper PublicKeyToken value. When I face the issue the value was PublicKeyToken=$PublicKeyToken$. If you have used WSP builder then in the Visual Studio you will find this file at \WebPartsProject\12\TEMPLATE\FEATURES\WebPartName\WebPartName.webpart. Sometime when you create a new WebPart using WSP builder then you do not get

Could not open virtual machine – vmx is not a valid virtual machine configuration file

I recently faced an issue with one of my VMWare virtual machine that when I try to run this virtual machine it did not work. VMWare display this message that “Could not open virtual machine: .vmx. ".vmx" is not a valid virtual machine configuration file.” ISSUE: Could not open virtual machine: G:\VPC\RakhiQAXPProfQtp\Windows XP Professional.vmx. "G:\VPC\RakhiQAXPProfQtp\Windows XP Professional.vmx" is not a valid virtual machine configuration file. I try to open .vmx file [G:\VPC\RakhiQAXPProfQtp\Windows XP Professional.vmx] in notepad then I found it was empty (0 KB). Resolution: I wanted to resolve it quickly so I try following method and it worked very well. But this is not a valid documented process so please try with caution. Following are the steps 1. First of all go to the folder where you have your virtual machine and delete all .lck folders. 564df2d4-03de-04e8-d1c3-bd2d53dcb1b7.vmem.lck Windows XP Professional.vmdk.lck

How To Create Virtual Machine Using Existing vmdk file in VMWare Workstation

vmdk file is hard disk of the VMWare virtual machine. There are many scenarios where you may need to create a new virtual machine for an existing vmdk file. This is also an alternate Method to the “ vmx is not a valid virtual machine configuration file – Could not open virtual machine ” issue. Please refer to the previous post “ Could not open virtual machine – vmx is not a valid virtual machine configuration file ” for a full list of possible resolution. This post is to describe one of the solution in more details. How To Create a new virtual machine & attach the existing .vmdk file: 1. Open VMware and select create a new virtual machine with custom (advanced) configuration option. 2. Chose “I will install the operating system later”. and chose “I will install the operating system later”. 3. Select the operating system that matches the operating system in your existing .vldk file. 4. Select a location of the new virtual machine 5. Chose “Use an exis