Error 1:
HTTP Error 500.19-Internal Server Error
Configuration error: you cannot use this configuration section in this path. This situation occurs if this section is locked at the parent level. The lock is set by default (overridemodedefault = "deny"), or is explicitly set by the position that contains overridemode = "deny" or the old AllowOverride = "false.
This error occurs because IIS 7 adopts a safer web. Config Management Mechanism. By default, the configuration items are locked and cannot be changed. To cancel the lock, run the command line % WINDIR % \ system32 \ inetsrv \ appcmd unlock config-Section: system. webserver/handlers. Handlers indicates the node name displayed in the red letter in the error message.
If modules is also locked, run % WINDIR % \ system32 \ inetsrv \ appcmd unlock config-Section: system. webserver/modules.
In addition, if you are a friend of Asp.net, remember to check Asp.net when installing iis7. This option is not selected by default, and a similar error message will appear.
Error 2:
HTTP 500.19-Internal Server Error
The requested page cannot be accessed because the configuration data of the page is invalid.
Detailed error information module IIS Web Core
Notification beginrequest
The handler has not been determined
Error code 0x80070005
Configuration error Unable to read the configuration file due to insufficient Permissions
In the original folder, right-click its attributes and open the "Security" tab. The "group or user name" is displayed. Click "edit" to add a new user name "everyone ", then, change its permissions and set "modify" to allow the second permission.