IIS troubleshooting guide and error code full

The cause of the IIS server error is complicated. An error event is logged in the system log if the service fails to start, the IIS process is interrupted, or the site cannot start. Regardless of the error in IIS, you should use the Event Viewer to check the related events recorded in the system log before determining the troubleshooting scheme. Some errors are obviously caused by damage to the server hardware, while other errors due to software are often not noticeable. This section provides a guiding introduction to general IIS troubleshooting.

Restarting IIS

According to Microsoft's general troubleshooting methods and troubleshooting solutions, most software problems can be resolved by rebooting to the method. As one of the new features of IIS 5.0, we can restart the IIS service without restarting the computer. Even serious problems can be solved by this method. Restarting the IIS service can force the system to reset the memory space of the IIS process, so problems caused by memory errors can be resolved. The method of restarting IIS is mainly used in the following situations: the web application is flawed and cannot be effectively controlled; the web application is not working properly or is unstable. [/TD] [/TR][/TABLE] During the restart of the IIS service, all current connections cannot be retained, and all sites on the server will not work during the restart. If restarting the IIS service does not solve the problem, restarting the server will not work.

When the site application is not working properly, restart the server's IIS service as follows:

1. Expand the IIS node in the IIS Admin Control Tree and select the computer that needs to restart the IIS service.

2. Click the [Operation] menu and select [Restart IIS].

3. In the [Stop/Start/Restart] dialog box, select [Restart Server IIS] from the [What do you want to do with IIS] drop-down list, and click [OK].

4. The Closed] dialog box displays the progress of restarting IIS. If the dialog box does not respond for a long time, click [End Now] and repeat the above operation.

Note: You cannot use the HTML-based IIS Manager (remote management mode) to perform the above reboot.

For the stability of a single site, you don't have to restart the entire IIS process, just restart the site. IIS Troubleshooting

Backup/Restore IIS

If there is a foolproof server security plan in the world, it is a backup. It has been pointed out that the three most important tasks that a good system administrator does are backup, backup, and backup.

The implementation mechanism of IIS includes a registry-like metabase: MetaBase. The configuration properties of IIS itself and the site are all stored in Windows 2000 and metabase MetaBase. Therefore, as long as the relevant registry and metabase are backed up, all the configurations related to the site can be saved. Even after deleting the site or even reinstalling IIS, you can still use the backup to restore the original state.

The steps to back up IIS are as follows:

1. Expand the IIS node in IIS Manager and select the computer you want to back up.

2. Click the [Operation] menu and select [Backup/Restore Configuration].

3. List all backup files and backup time in the [Backup] list in the [Backup/Restore Configuration] dialog box. Click the [Create Backup] button.

4. In the [Backup Configuration] dialog box, specify the name of the new backup and click [OK].

5. Click [Close] to complete the backup.

By default, backup files are saved in the Winntsystem32inetsrvMetaBack directory.

To restore the backup, similarly, select a backup file in the [Backup] list in the [Backup/Restore Configuration] dialog box, and click [Restore]. Then click [OK] in the prompt dialog box shown on the left, and after a while, the IIS server will return to the state it was in when it was backed up.

If the server needs to restore the backup after reinstalling IIS, on the basis of the above recovery operation, additional operations should be performed as follows:

1. At the command prompt, type cscript.exe X: InetPubAmdinScriptsAdsutil.vbs enumw3svc, where "X" is the drive letter where IIS is installed. From the listed settings, look for the value of WamUserName and the associated WAMUserPass.

2. Double-click [Administrative Tools] in the Control Panel, and then double-click [Computer Management].

3. Select [Local User Manager] and click [User]. Double-click the [IWAM_computername] user account. Type the WAMUserPass value found from the previous step and click OK.

4. In the [Configure Backup Name] dialog box, select the backup file you created, and then click [Restore]. The configuration will now be fully restored.

IIS Troubleshooting

TCP/IP Troubleshooting

TCP/IP protocol problems are often the cause of IIS not working properly. When IIS has an error but can judge that there is no problem with the IIS service itself, it is necessary to consider whether there is a problem with the network connection. After simply eliminating the problem caused by network hardware damage, our attention should focus on the network protocol, mainly TCP/IP. Agreement.

Windows 2000 provides a range of TCP/IP troubleshooting tools. These tools, based primarily on command prompts, provide a powerful means of diagnosing network problems.

Checking TCP/IP Configuration Using the ipconfig Tool

ipconfig is a command prompt tool for viewing and managing client TCP/IP configuration status. At the command prompt, type: ipconfig and press Enter to get the basic TCP/IP configuration properties of the computer as shown on the right, including the IP address, subnet mask, and default gateway.

At the command prompt, type: ipconfig /all and press Enter to get the detailed mode TCP/IP configuration status. In addition to the basic information, it also includes the host name, DNS settings, WINS settings, DHCP settings, and TCP/IP information such as physical address and node type.

If your computer has DHCP enabled and configured with a DHCP server, you can use the ipconfig /renew command to start refreshing the lease. You can also use the ipconfig command with the /release option to immediately release the host's current DHCP configuration.

For Windows 95 and Windows 98 clients, the winipcfg command should be used instead of the ipconfig command.

Using the ping command to test the connection

The ping command helps verify IP-level connectivity. When discovering and resolving problems, you can use Ping to send an ICMP echo request to the target hostname or IP address. Use Ping when you need to verify that the host can connect to TCP/IP networks and network resources.

The ping command actually sends a number of packets (the default is 4) to the target host. If the local computer and the target host can communicate, the target host will reply with a response message, as shown in the upper right figure. The response information includes response time and TTL value. Successful Ping the same host indicates that IP data can be transferred between the local and target hosts.

If you receive the timeout information, as shown in the figure below, the TCP/IP connection between the local host and the target host cannot be established. Possible causes include network failure, protocol error, and TCP/IP configuration. Errors, etc. When confirming network connectivity, the Ping test should be performed in the following order:

1. Ping the local loop address 127.0.0.1 to determine if the local TCP/IP configuration is correct.

Type Ping 127.0.0.1 at the command prompt.

2. Ping the local address and verify that the local IP address is set correctly.

3. Ping the default gateway address to verify communication with hosts outside the local subnet.

4. Ping the host on the remote subnet to verify that it can communicate remotely through the router.

If the above Ping commands are able to respond, the TCP/IP configuration can support network communication. Otherwise, perform a setup check for the corresponding network component.

Using the netstat tool to display connection statistics

You can use the netstat command to display protocol statistics and current TCP/IP connections.

The netstat -a command will show all connections, while netstat -r shows the routing table and active connections. The netstat -e command displays Ethernet statistics, while netstat -s displays statistics for each protocol.

If you use netstat -n, you cannot convert the address and port number to a name.

IIS Error Codes

400 Unable to resolve this request.

401.1 Unauthorized: Access is denied due to invalid credentials.

401.2 Unauthorized: Access is denied due to server configuration tendencies to use an alternate authentication method.

401.3 Unauthorized: Access is denied due to ACL settings for the requested resource.

401.4 Unauthorized: Filter authorization installed on the web server failed.

401.5 Unauthorized: ISAPI/CGI application authorization failed.

401.7 Unauthorized: Access is denied due to a URL authorization policy on the web server.

403 No access: Access is denied.

403.1 No access: Execution access is denied.

403.2 No access: Read access is denied.

403.3 Forbidden access: Write access is denied.

403.4 No access: You need to use SSL to view this resource.

403.5 Forbidden: You need to use SSL 128 to view this resource.

403.6 No access: The client's IP address is rejected.

403.7 No access: SSL client certificate required.

403.8 No access: The client's DNS name is rejected.

403.9 Forbidden access: Too many clients trying to connect to the web server.

403.10 Forbidden: The web server is configured to deny access.

403.11 No access: The password has been changed.

403.12 Forbidden: The server certificate mapper rejected client certificate access.

403.13 Forbidden: The client certificate has been revoked on the web server.

403.14 Forbidden: The list of directories has been rejected on the web server.

403.15 No access: The web server has exceeded the client access license limit.

403.16 Forbidden: The client certificate is malformed or not trusted by the web server.

403.17 No access: The client certificate has expired or is not yet valid.

403.18 Forbidden: The requested URL could not be executed in the current application pool.

403.19 Forbidden: CGI cannot be executed for clients in this application pool.

403.20 No access: Passport login failed.

404 File or directory not found.

404.1 File or directory not found: The website could not be accessed on the requested port.

Note 404.1 errors only appear on computers with multiple IP addresses. If a client request is received on a specific IP address/port combination and the IP address is not configured to listen on that particular port, IIS returns a 404.1 HTTP error. For example, if a computer has two IP addresses and only one of the IP addresses is configured to listen on port 80, any request received by another IP address from port 80 will cause IIS to return a 404.1 error. This error should only be set at this service level because it will only be returned to the client when multiple IP addresses are used on the server.