- An attempt to start Plesk Panel site in IIS fails with the error below
All websites are stopped in IIS, an attempt to start it fails with the error below
The process cannot access the file because it is being used by another process. (Exception from HRESULT: 0x80070020)
Additionally, the following events are being logged in the System event log on the Microsoft Windows Server 2008-based computer that is running IIS:
Event Source: W3SVC
Event ID: 1004
Description: The World Wide Web Publishing Service (WWW Service) did not register the URL prefix http://my.domain.com:80:12.123.123/ for site 106. The site has been disabled. The data field contains the error number.
Event Source: HTTP
Event ID: 15005
Description: Unable to bind to the underlying transport for [::]:80. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine. The data field contains the error number.
If the issue occurs only on Plesk Panel site, then the 8880 port/ SSL default * 8443 is probably listened by some other website in IIS.
If the issue occurs with all websites in IIS, it means that some process is already using port 80 and IIS could not initialize the socket. Usually it means that another web server is running like Apache or webmail web server on port 80.
Make sure that only Plesk Control Panel is binding to 8880 and 8443 ports
Run the following command to find the PID of the process that listens corresponding ports:
netstat -aon | findstr ":8880"
netstat -aon | findstr ":8443"
The output will look like:
C:\\Users\\Administrator>netstat -ano | findstr ":8443"
TCP 0.0.0.0:8443 0.0.0.0:0 LISTENING 4
TCP [::]:8443 [::]:0 LISTENING 4
To find the corresponding process use the following command:
C:\\Users\\Administrator>tasklist /fi "PID eq 4"
Image Name PID Session Name Session# Mem Usage
========================= ======== ================ =========== ============
System 4 Services 0 304 K
Please refer to the following #973094 article.
Please pay attention to the HTTPMail that uses 8080 port, please refer to the mailenable me020202 article.