IIS7 Common Errors and solutions

Problem One: HTTP error 500.19-internal Server error cannot access the requested page because the related configuration data for the page is not valid.

Verbose error information module IIS WEB Core

Notify BeginRequest

Handler not determined

Error code 0x80070021

Configuration errors cannot be used with this configuration section in this path. This can occur if the section is locked at the parent level. The lock is set by default (overridemodedefault= "Deny"), or is explicitly set by a location tag that contains overridemode= "deny" or the old allowoverride= "false".

Configuration source

219: <add name= "Scriptmodule" precondition= "Managedhandler" type= "System.Web.Handlers.ScriptModule", Syst Em. Web.extensions, version=3.5.0.0, Culture=neutral, publickeytoken=31bf3856ad364e35 "/></modules>

221:

Workaround:

Control Panel--> programs and features--> turn Windows features on or off--> role

Here, if you have not installed Web server (IIS), select Add.

If it is already installed, select Web Server (IIS)--> to add the role service.

Select "Application Development (installed)"--> "asp.net".

Figures:

Problem two: HTTP error 500.22-internal Server error

Error Summary: HTTP error 500.22-internal Server error detects asp.net settings that are not applicable in integrated managed piping mode.

Workaround:

When you configure a local Web site, you receive the following error message:

HTTP Error 500.22-internal Server error
Detects asp.net settings that are not applicable in integrated managed piping mode.

The environment is IIS7, net3.5.

I used to have IIS7 on other computers, and I don't seem to have encountered this problem. Look for it, find the problem with IIS settings. Select the application pool in [Advanced settings] on the right side of the IIS configuration [browse Web site] as the [Classic. NET AppPool] Classic mode. The default is DefaultAppPool.

Website Setup everything else is OK.

-----------Common error 2----------

1: Authorization: Unable to verify access to the path

Workaround: IIS7 cannot verify access to the path

1, open the IIS 7 Manager, mouse click to locate the site where this error occurred.

2, on the right side of the IIS 7 Manager, select Basic Settings.

3, in the pop-up Edit Web Site dialog box, click the Connect as button.

4. In the "Connect as" dialog box, select the "Specific user" radio button.

5, and click the "Settings" button on the right.

6 in the "Set Credentials" dialog box that pops up, enter your username, password, and confirmation password.

Note that the username should be a user who has access to this site directory, such as an administrator account. If you set these up, the error will be eliminated immediately.

2:403.14 Error: Web server is configured not to list contents of this directory

Workaround:

This error can be eliminated by clicking on the button, which will become disabled under actions

3: The page you requested is not available due to extended configuration issues. If the page is a script, add the handler. If you should download the file, add a MIME map.

Treatment method: 1. Control Panel → program and function → turn windwos function on or off

2. Expand the Internet Information services → Web services → application development feature in the open Windows Features window, and then confirm the installation by checking the front of the server-side Include option. I really can't understand, you are all on the hook, huh?