IIS Information Server debugging instructions

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] [All current connections are not preserved during/table] restart of the IIS service, 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 that needs 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. The Close dialog box displays the progress of restarting IIS, and if the dialog box does not respond for a long time, click End Now and repeat the action.

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