Resolution of IIS startup failure

IIS cannot be started, and "the service does not respond to the start or control request" is displayed. I have not solved either of the following methods:
1. You Cannot uninstall or reinstall IIS;
2. the World Wide Web Publishing Service cannot be started in the service, and the error 127 is prompted. The dependency service cannot be started either.

So there was no way, and there was no debugging site in a few weeks. I checked online today and found a solution that seems reasonable:

Haha, I also encountered this problem and suspected it was caused by the patch. Because we all played the patch in the afternoon, the first thing after the problem was restored in the evening was to check that IIS was okay, after confirming that there is no problem, patch it again, and then there is a problem with IIS.
I found this patch for Windows xp-kb939373-x86-chs.exe, which seems to be a patch to Prevent IIS Remote code from running. It was just recently discovered that this problem occurred in a large area after July 10, 2007.
Solution: Go to control panel-join? /Delete the program, click "display Update" at the top, find "Windows XP software update", uninstall several patches after January 1, July 10, and the World Wide Web Publishing Service will start.
(Note: The premise is that the directory starting with $ in the Windows directory of drive C is not deleted)

Other causes and solutions on the Internet:

1. Firewall Rules are restricted.
The system environment is Windows XP SP2 and iis5.1. The process cannot be started. check whether there are any processes related to the firewall or anti-virus software. The executable file "World Wide Web Publishing" is "inetinfo.exe ", find "inetinfo.exe" in the asked rule of the rising firewall to allow all requests. Start "World Wide Web Publishing" again, and then start IIS. Everything is OK.

2. There is no administrator connection.
System Environment: WindowsXP + SP2, ii5.0
Fault description: After the IIS service is stopped in the morning, the program does not respond for a long time. When the Task Manager is closed, the system prompts "the service did not respond to the startup or control request in a timely manner ", failed to restart the computer.
Solution: If you have a local computer (computer name) under Internet Information Service, click the name key and select disconnect. Is the prompt that you want to disconnect the Local Computer (computer name? Select OK.
Right-click Internet, select connection, enter the local name for the computer name, enter the local administrator account for username, and click OK.

3. The dependency service is not started.
On the last day, I found that my company could not start IIS on this computer. This morning I tried to solve the problem and found that the problem was not simple. Find it, find it, and find that "worldwidewebpublishing" is disabled, the startup also prompts that the startup failed. Let's calm down and look at other closed services. One EventLog starts it and then starts worldwidewebhing Hing. The problem lies here.
Although the "EventLog" service is not mentioned in the dependency list of the "worldwidewebpublishing" service and SMTP service, if the "EventLog" service is not started, the above problems will occur. Start the "EventLog" service and then start the "worldwidewebpublishing" service. The above problem disappears.
View the dependencies required by World Wide Web Publishing Services. The IIS Admin Service is displayed. The IIS Admin Service cannot be started. Check the dependencies of the IIS Admin Service. The result is protected storage and RPC (Remote Procedure Call, start IIS Admin Service and start World Wide Web Publishing Services, so IIS returns to normal.

4. the IIS metadatabase may be broken.
Try again.
Try to enumerate metabase:
1. Open a command prompt and change to the C:/inetpub/adminscripts folder.
2. At the command line, type "cscript adsutil. vbs Enum" (without
Quotation marks ).
If this command is successful, it enumerates the settings in
Metabase.
If the command is not successful, you receive the-2146893792
(0x80090020) error code.
If there is a backup, restore the data.
If no, skip the exam.
How to manually restore the metabase when no proper backup exists or when
The MMC does not start
Http://support.microsoft.com /? Id = 234429
How to: Download, install, and remove the IIS metaedit 2.2 Utility
Http://support.microsoft.com /? Id = 232068

It may be that metabase. bin or metabase is broken. The solution is as follows:
For information about how to use MMC to back up and restore metabases, see the IIS readme file, which is located at http: // localhost/IISHelp/IIS/htm/CORE/iisread.htm # General (assuming the product documentation has been installed on the local computer ).
Assume that the backup file created by MMC is available.
The following is the program code:

If you have created a backup file (filename. mdbackupnumber), but the MMC cannot be opened because the current metadatabase is damaged. Run the following steps to manually open the MMC from filename. restore the metadatabase in the mdbackupnumber file. 1. Stop all IIS services and other services dependent on IIS (such as third-party applications or Microsoft Site Server ).

Note: To stop IIS and its dependent services, use the net stop IISADMIN/y command. For other information, refer to the following Microsoft Knowledge Base Article:
236166 (http://support.microsoft.com/kb/236166/) use the net stop and Net start commands to force the IIS service to read the notebooks table again
2. Use a new name (such as metabase. Bad) to rename the corrupted metabase. BIN file. The file is located in the % SystemRoot %/system32/inetsrv directory.
3. copy the file filename. mdbackupnumber of the MMC backup metabase in the % SystemRoot %/system32/inetsrv/metaback directory to the % SystemRoot %/system32/inetsrv directory. Rename this file to metabase. Bin.
4. Start the computer again.

Assume that the old copy of The metabase. BIN file exists.

If the backup file created by MMC is unavailable, metabase exists elsewhere (usually in the system tape backup. run the following steps for the old copy of the BIN file: 1. stop all IIS services and other services dependent on IIS (such as third-party applications or Microsoft Site Server ).

Note: To stop IIS and its dependent services, use the net stop IISADMIN/y command. For other information, refer to the following Microsoft Knowledge Base Article:
236166 (http://support.microsoft.com/kb/236166/) use the net stop and Net start commands to force the IIS service to read the notebooks table again
2. Use a new name (such as metabase. Bad) to rename the corrupted metabase. BIN file. The file is located in the % SystemRoot %/system32/inetsrv directory.
3. Copy the old copy of The metabase. BIN file to the % SystemRoot %/system32/inetsrv directory.
4. Start the computer again.

Assume that there is no MMC backup or an old copy of The metabase. BIN file

If the backup file created by MMC is unavailable and there is no old copy of The metabase. BIN file, the temporary backup of the metabase may still exist.

When you update a metadatabase through MMC or other processes, temporary backup of the metadatabase may be created. If the update process is interrupted (the cause may be damaged in the first position), the temporary file may still exist.

You can name the temporary file metabase. Bak or metabase. bin. Bak and put it in the % SystemRoot %/system32/inetsrv directory. If the temporary file exists, perform the following steps to restore the metadatabase: 1. stop all IIS services and other services dependent on IIS (such as third-party applications or Microsoft Site Server ).

Note: To stop IIS and its dependent services, use the net stop IISADMIN/y command. For other information, refer to the following Microsoft Knowledge Base Article:
236166 (http://support.microsoft.com/kb/236166/) use the net stop and Net start commands to force the IIS service to read the notebooks table again
2. Use a new name (such as metabase. Bad) to rename the corrupted metabase. BIN file. The file is located in the % SystemRoot %/system32/inetsrv directory.
3. Rename the temporary backup file (metabase. Bak or metabase. bin. Bak) to metabase. Bin.
4. Start the computer again.

Assume that the metabase backup file does not exist.

If no backup file is available for the metabase, the only way to restore the IIS function is to complete the following operations. However, note that all IIS settings stored in the metabase will be lost. 1. uninstall Windows NT Option Pack. For other information, refer to the following Microsoft Knowledge Base Article:
187870 (http://support.microsoft.com/kb/187870/) how to delete and re-install Windows NT 4.0 Option Pack
2. Uninstall Internet Explorer.
3. Delete the metabase. BIN file from the % SYSTEMROOT/system32/inetsrv/directory.
4. Install Internet Explorer.
5. Install Windows NT Option Pack.
(C) Microsoft Corporation 2000 reserves all rights. Provided by Microsoft Corporation Kevin zollman.