http error 500.19 internal server errorRSS

7 replies

Last post Jul 01, 2014 03:54 AM by 4hmeT

  • http error 500.19 internal server error

    Jul 31, 2008 01:38 AM|mubashirkhan|LINK

    hi .. i put the same question in forum but couldnt get any help .. i hope it will be resolved here ...

     i have installed vs2008(on vista home premium edition)  but i am not able to run websites correctly ... when i try to run the website from within vs2008 it gives following error

    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/WebSite1/Default.aspx

    Physical Path: C:\inetpub\wwwroot\WebSite1\Default.aspx

    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:\inetpub\wwwroot\WebSite1\web.config

    Config Source:
      139:       </modules>
      140:       <handlers>
      141:         <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.

    any bdy knows wats the problem ...

    IIS7 ASP.NET Integrated mode Vista visual studio 2008 iis7 error code 0x80070021 internal server error

    Learn by Sharing
  • Re: http error 500.19 internal server error

    Aug 04, 2008 07:12 AM|Zhao Ji Ma - MSFT|LINK


    This error happens when the section has been locked globally in IIS configuration. You can see this thread for solution: 

    Zhao Ji Ma
    Microsoft Online Community Support
  • Re: http error 500.19 internal server error

    Mar 11, 2010 07:42 AM|rozi|LINK

    I had the same problem on some computers only. It turned out that the order of .NET Framework and IIS instalation was the problem. If .NET Framework was installed first and IIS second, I had to run aspnet_regiis -i to register .NET Framework to the newly installed IIS.

  • Re: http error 500.19 internal server error

    Jun 03, 2010 07:23 PM|tevya|LINK

     I am seeing something similar and with IIS installation following .NET framework installation.   However, running aspnet_regiis -i does not solve the problem(!).  I am running with .NET 4.0.   Does that make a difference?

    http error 500.19 internal server error

  • Re: http error 500.19 internal server error

    Dec 03, 2010 02:26 AM|ankur.dholakiya|LINK

    <div class="container"><div class="body">

    I found the solution.

    Simply change the applicationHost.Config file to this;

    <section name="modules" allowDefinition="MachineToApplication"
    overrideModeDefault="Allow" />

  • Re: http error 500.19 internal server error

    Feb 15, 2011 09:00 PM|rajNepal|LINK


    I tried as Ankur has mentioned but it didn't help me.

    So I change it back as before "Deny".

    First I removed ASPNet from IIS using "Turn Windows feature on or off".

    Then I reinstall it back.

    I went to back to applicationHost.Config and check modules section and it has Deny but the problem is solved.


  • Re: http error 500.19 internal server error

    Jun 01, 2013 02:49 PM|technologycrowds|LINK

    This errror can be  caused if .net framework is not installed when you run the site from IIS on localhost. The detail on how to sort out this error is mentioned in the article given  below:

  • Re: http error 500.19 internal server error

    Jul 01, 2014 03:54 AM|4hmeT|LINK

    Please <staticContent /> line erased it from the web.config.