IIS server Debugging Guide and error code encyclopedia

iis| Error | server

The reason for the IIS server error is complex. Errors such as service startup failure, an IIS process outage, or a site failure to start will record an error event in the system log. Regardless of what is wrong with IIS, you should use Event Viewer to refer to the related events that are logged in the system log before you determine the scheduling scheme. Some of the errors are obviously caused by damage to the server's hardware, while others are often difficult to detect due to software-led errors. This section provides a guided introduction to general IIS scheduling.

Restart IIS

Most software problems can be resolved by restarting to the method, according to the general troubleshooting and failure solutions of Microsoft products. As one of the new features of IIS5.0, we can restart the IIS service without restarting the computer, and even a fairly serious problem 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 for restarting IIS is primarily used when the Web site application is paralyzed, is not effectively controlled, and the site 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 during the reboot are not working. If restarting the IIS service does not resolve the issue, restarting the server will not work.

When the site application is not working properly, restart the server's IIS service by following these steps:

1. In the IIS Management control tree, expand the IIS node and select the computer on which you want to restart the IIS service.

2. Click the Action menu and select Restart IIS.

3. In the Stop/Start/Restart dialog box, select Restart Server IIS in the what you do to IIS Drop-down list, and click OK.

4. Closing dialog box displays the progress of restarting IIS, and if the dialog box does not respond for a long time, click End Now and do the above again.

Note: You cannot use the HTML based IIS Manager (Remote Administration mode) for the above reboot operation.

For stability issues for a single site, you do not have to restart the entire IIS process, as long as you restart the site. IIS is in a wrong row

Backup/Restore IIS

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

The implementation mechanism for IIS includes a database similar to the registry: MetaBase, where the configuration properties for IIS itself and the site are all stored in Windows 2000 and metabase MetaBase. As a result, you can save all of the site-related configurations by backing up the relevant registry and metabase. Even after you delete a site or even reinstall IIS, you can still use the backup to revert to its original state.

The steps for backing up IIS are as follows:

1. In IIS Manager, expand the IIS node and select the computer you want to back up.

2. Click the Action menu and choose 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, the backup files are saved in the Winntsystem32inetsrvmetaback directory.

How to restore a backup similar to this, 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 some time, the IIS server reverts to the state it was in when the backup was made.

If you need to restore the backup after the server has installed IIS, you should take additional action on the basis of the above recovery operation 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 settings listed, look for values for WAMUserName and related WAMUserPass.

2. In Control Panel, double-click Administrative Tools, and then double-click Computer Management.

3. Select Local User Manager, and then click Users. 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 that you created, and then click Restore. The configuration will be fully restored at this time.

IIS is in a wrong row

TCP/IP Scheduling error

TCP/IP protocol problems are often the cause of IIS not working properly. When IIS errors but can determine the IIS service itself is not a problem, we should consider whether the network connectivity problems, simple to eliminate the network hardware damage caused by the problem, our attention should be focused on the network protocol, mainly TCP/IP protocol.

Windows 2000 provides a range of TCP/IP troubleshooting tools, which are primarily based on command prompt lines, providing powerful tools for diagnosing network problems.

Using the Ipconfig tool to check TCP/IP configuration

Ipconfig is a command prompt line tool that looks up and manages the state of client TCP/IP configuration. At the command prompt, type: ipconfig and enter to obtain the basic TCP/IP configuration properties, including the IP address, subnet mask, and default gateway, as shown in the picture on the right.

At the command prompt, type: Ipconfig/all and enter to get the TCP/IP configuration status in verbose mode, in addition to the basic information, including host name, DNS settings, WINS settings, DHCP settings, and physical addresses, node types, and other TCP/IP information.

If your computer enables DHCP and uses a DHCP server to obtain configuration, you can start refreshing the lease using the Ipconfig/renew command. You can also use the ipconfig command with the/release option to immediately release the current DHCP configuration of the host.

For Windows 95 and Windows 98 clients, use the winipcfg command instead of the ipconfig command.

To test a connection by using the ping command

The ping command helps verify IP-level connectivity, and you can use ping to send an ICMP response request to the destination host name or IP address when a problem is discovered and resolved. Use ping when you need to verify that the host can connect to TCP/IP network and network resources.

The ping command actually sends several (default 4) packets to the target host, and if the local computer is connected to the target host, the target host responds with a response message, as shown in the upper right figure, and the response information includes response time and TTL values. Successful Ping the same host indicates that IP data can be transferred between local and target hosts.

If you receive time-out information, as shown in the following illustration, the TCP/IP connection between the local host and the target host cannot be established, including network failures, protocol errors, TCP/IP configuration errors, and so on when confirming network connectivity, you should ping them in the following order:

1. Ping the local circular 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 line.

2. Ping the native address to verify that the local IP address settings are correct.

3. Ping the default gateway address to verify that it can communicate with a host other than the local subnet.

4. Ping the hosts on the remote subnet to verify that remote communication is possible over the router.

If the ping command above can be answered, the TCP/IP configuration can support network traffic. Otherwise, set the check for the appropriate network components.

Display connection statistics using the Netstat tool

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

The netstat-a command displays all connections, while NETSTAT-R displays the routing table and active connections. The NETSTAT-E command displays Ethernet statistics, and netstat-s displays statistics for each protocol.

If you use Netstat-n, you cannot convert addresses and port numbers to names.

IIS Error Code Encyclopedia

400 cannot resolve this request.

401.1 Unauthorized: Access denied due to invalid credentials.

401.2 Unauthorized: Access was rejected because the server configuration tended to use alternate authentication methods.

401.3 Unauthorized: Access because the ACL's settings for the requested resource are denied.

401.4 Unauthorized: The filter authority installed on the WEB server failed.

401.5 Unauthorized: ISAPI/CGI application authorization failed.

401.7 Unauthorized: Access is denied because of a URL authorization policy on the WEB server.

403 Prohibit access: Access is denied.

403.1 Prohibit access: execution access is denied.

403.2 Prohibit access: Read access is denied.

403.3 Prohibit access: Write access is denied.

403.4 No access: You need to view the resource using SSL.

403.5 No access: You need to view the resource using SSL 128.

403.6 Prohibit access: The IP address of the client is denied.

403.7 No access: SSL client certificate required.

403.8 Prohibit access: The DNS name of the client is denied.

403.9 No access: Too many clients are trying to connect to the WEB server.

403.10 Prohibit access: The WEB server is configured to deny execution of access.

403.11 No access: password has changed.

403.12 Prohibit access: The server certificate mapper has denied client certificate access.

403.13 Prohibit access: The client certificate has been revoked on the WEB server.

403.14 No access: The directory list has been rejected on the WEB server.

403.15 No access: The WEB server has exceeded the Client Access License limit.

403.16 No access: The client certificate is malformed or not trusted by the WEB server.

403.17 No access: The client certificate has expired or has not yet taken effect.

403.18 Prohibit access: The requested URL cannot be executed in the current application pool.

403.19 No access: CGI cannot be performed for clients in this application pool.

403.20 No access: Passport Login failed.

404 the file or directory could not be found.

404.1 the file or directory was not found: The Web site cannot be accessed on the requested port.

Note that the 404.1 error will 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 requests received from port 80 by another IP address will cause IIS to return 404.1 errors. This error should only be set at this service level because it is returned to the client only when multiple IP addresses are used on the server.