Question : HTTP Error 500.19 - Internal Server Error

I have this error in My Web Application :  (Windows Server 2008 + IIS 7.5)

This Web application runs on a test server with Windows Server + IIS 7
but don'twork on an athor machine whit Windows Server + IIS 7.5.

I tried all (Permissions in folders, installed .Net Feature, Check errors in the web configuration ...).

Please help me.
--------------------------

Error Summary:
HTTP Error 500.19 - Internal Server Error
The requested page cannot be accessed because the related configuration data for the page

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      \\?\C:\TEST\WebSite\web.config

equested URL      http://localhost:80/
Physical Path      C:\TEST\WebSite
Logon Method      Not yet determined
Logon User      Not yet determined

Config Source:

   9:    </modules>
   80:     <handlers>
   81:       <remove name="WebServiceHandlerFactory-Integrated" />

Answer : HTTP Error 500.19 - Internal Server Error

You could also try just removing the handler mapping via the IIS 7 interface instead of using your web.config.

As far as the config files you've posted, not really sure what website your trying to modify here but you have a few different location elements in your applicationhost.config. It looks like your have the default override for the handlers section to be allowed, so it must be explicitly set to deny somewhere. I saw you have to location elements for the "default web site" path and one is set to overidemode="deny", not sure if thats causing conflicts or not.

<location path="Default Web Site" overrideMode="Deny">

What you could do if your not really worried about security is add the override to the base location. The location element without a path assigned to it. Basically the location element is just letting you group items together and specify what level the items are affecting. The base level would be the whole IIS server, setting a path to "BobSite" would modify the site named "BobSite" and "BobSite/ApplicationBob" would modify the ApplicationBob application starting point within BobSite.

Hope that kind of clears things up. Read that article I gave you it will explain it a little more clearly.

If your basically shooting in the dark at this point you can just use process of elimination or add the overridemode="allow" to all the location elements.