Troubleshoot IIS server errors step by step

The cause of an error on the IIS server is complex. If the service fails to start, the IIS process is interrupted, or the site cannot start, an error event is recorded in the system log. No matter what errors occur in IIS, you should use the Event Viewer to view related events recorded in system logs before determining the troubleshooting solution. Some errors are apparently caused by hardware damage to the server, while others are often imperceptible due to software.

Restart IIS

According to the general troubleshooting methods and fault solutions of Microsoft products, most software problems can be solved by restarting them. As one of the new features of IIS 5.0, we can restart the IIS service without restarting the computer, and even solve serious problems. Restarting the IIS service forces the system to reset the memory space of the IIS process. Therefore, problems caused by memory errors can be solved. The method of Restarting IIS is mainly used in the following situations: the website application is paralyzed and cannot be effectively controlled; the website application is abnormal or unstable. [/TD] [/TR] [/TABLE] When the IIS service is restarted, all current connections cannot be retained, and all sites on the server cannot work during restart. If you cannot solve the problem by restarting the IIS service, the restart of the server will not be effective.

When the site application does not work properly, restart the IIS service of the server following the steps below:

1. Expand the IIS node in the IIS Management Control tree and select the computer to restart the IIS service.

2. Click the operations menu and Select Restart IIS ].

3. In the [What do you want to do to IIS] drop-down list in the [Stop/start/restart] dialog box, select [restart server's IIS] and click [OK ].

4. In the close dialog box, the IIS restart progress is displayed. If the dialog box does not respond for a long time, click end now and perform the preceding operations again.

Note: The preceding restart operation cannot be performed using the HTML-based IIS Manager (remote management mode.

For the stability of a single site, you do not have to restart the entire IIS process, as long as you restart the site.

Back up/restore IIS

If there is a 10 thousand foolproof server security plan in the world, it is backup. Someone once pointed out that the three most important tasks a good system administrator has done are backup, backup, and backup.

The implementation mechanism of IIS includes MetaBase, A MetaBase similar to the Registry. The configuration attributes of IIS itself and the site are all stored in Windows 2000 and MetaBase. Therefore, you only need to back up the relevant registry and metadata to save all site-related configurations. Even after the site is deleted or IIS is re-installed, the backup can still be used to restore the original status.

To back up IIS, follow these steps :,

1. Expand the IIS node in the IIS manager and select the computer to be backed up.

2. Click the operations menu and select backup/restore configuration ].

3. In the backup/restore configuration dialog box, list all backup files and backup time. Click Create backup.

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 file is saved in the Winntsystem32inetsrvMetaBack directory.

The backup recovery method is similar. In the backup/recovery configuration dialog box, select a backup file in the backup list and click Restore ]. Then, click OK in the prompt dialog box. After a period of time, the IIS server is restored to the status during Backup.

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

1. In the command line, click cscript.exe X: InetPubAmdinScriptsAdsutil. vbs enum w3svc. Here "X" is the IIS installation drive letter. Find the WamUserName and related WAMUserPass values from the settings listed.

2. on the control panel, double-click Administrative Tools, and then double-click computer management ].

3. Select Local User Manager and click User ]. Double-click IWAM_computername. Enter the WAMUserPass value found in the previous step and click OK ].

4. In the configure backup name dialog box, select the created backup file and click Restore ]. The configuration is completely restored.

 

TCP/IP troubleshooting

TCP/IP protocol problems are often the cause of IIS failure. When an IIS error occurs but the IIS service itself can be determined to be normal, consider whether there is a network connection problem and simply eliminate the problem caused by network hardware damage, our attention should be focused on the network protocol, mainly the TCP/IP protocol.

Windows 2000 provides a series of TCP/IP troubleshooting tools, which are mainly based on command prompt lines and provide powerful means to diagnose network problems.

Use ipconfig to check TCP/IP configurations

Ipconfig is a command prompt line tool for viewing and managing the client's TCP/IP configuration status. In the command prompt line, Type ipconfig and press enter to obtain the basic TCP/IP configuration attributes of the computer, including the IP address, subnet mask, and default gateway.

In the command prompt line, Type ipconfig/all and press enter to get the TCP/IP configuration status in verbose mode. In addition to the basic information, it also includes the host name, DNS settings, WINS settings, DHCP settings, physical addresses, node types, and other TCP/IP information.

If the computer enables DHCP and uses the DHCP server to obtain the configuration, 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 current DHCP configuration of the host.

Use the ping command to test the connection

The Ping command is used to verify IP-level connectivity. When detecting and resolving problems, you can use Ping to send ICMP response requests to the target host name or IP address. Use Ping to verify whether the host can connect to the TCP/IP network and network resources.

The Ping Command actually sends several (4 by default) packets to the target host. If the local computer can communicate with the target host, the target host will return a response message, the response information includes the response time and TTL value. Successfully Ping the same host indicates that IP data can be transmitted between the local host and the target host.

If a timeout message is received, the TCP/IP connection between the local host and the target host cannot be established. Possible causes include network faults, protocol errors, and TCP/IP configuration errors.

Ping tests should be conducted in the following order when network connectivity is confirmed:

1. Ping the local loop address 127.0.0.1 to check whether the local TCP/IP configuration is correct.

In the command prompt line, type Ping 127.0.0.1.

2. Ping the local IP address to check whether the local IP address is set correctly.

3. Ping the default gateway address to check whether it can communicate with hosts outside the local subnet.

4. Ping the host on the remote subnet to check whether the vro can communicate remotely.

If the above Ping command can receive a response, the TCP/IP configuration can support network communication. Otherwise, check the settings for the corresponding network components.

Use 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 displays all connections, while the netstat-r command displays the route table and active connections. The netstat-e command displays Ethernet statistics, while netstat-s displays statistics for each protocol. If netstat-n is used, the address and port number cannot be converted to the name.