Resolved: some IIS sites cannot be started

1. Background

A few days ago, I installed the Serv-u ftp software for testing. When setting the listener, I used the default ports for HTTP and HTTPS. Later, when I started the mail server experiment, I stopped the IIS service and re-installed it, and found that the site could not be started.

Figure 1: port settings in Ser-U FTP

Figure 2: Simulate IIS uninstallation when the IIS service is stopped)

Figure 3: Simulate IIS installation after the IIS service is started)

Figure 4: unable to start some sites

2. Find the root cause of the problem

To exhaust interference, I usually first clear the system logs and then obtain a clean log list. In addition, unless the error message provided by the system is very clear, log information, especially system logs, is usually required.

Figure 5: displays related system logs.

Why should I introduce this article? It's easy, because I also agree with him.

You cannot register the URL prefix http: // *: 80/for Site 1 /. The site is released. Data Field inclusion Error

1. Some services continue to occupy some port resources.

2. The information prompted by the system is misleading. It is clear that the port is occupied. Why is the prompt that the file is occupied?

3. Verify the solution

Figure 6: After the port is modified, the site starts normally.

Figure 7: Process occupying port 80

4. Correct Solution

Step-1: stop the service Serv-U File Server

Step 2: Start sites in IIS

Step-3: Start the Serv-U File Server. A new problem will occur. Next:

Step-3.1 modify listener port settings on the Serv-u ftp Console

Step-3.2 restart the Serv-U File Server

This article is no graph version, the original please view "CTO-360" blog, http://penzhaohui.blog.51cto.com/3311602/637097