System service listening on port 80

Got this error after rebooting a SCOM server (a single server holding both SCOM and SQL):

[error]

The World Wide Web Publishing Service (WWW Service) did not register the URL prefix http://*:80/ for site 1. The necessary network binding may already be in use. The site has been disabled. The data field contains the error number.

[/error]

 

Usually I see this error when I install Apache on a server already running IIS and they both use the same port 80. In this situation, I had only IIS running with the OperationManager WebConsole and that’s it. So what on earth was taking a hold of port 80?

To find out, I used the following command:

 netstat -ano -p tcp | findstr ":80" 

Reviewing the output I found out that port 80 was in use by the system process??? process id 4 is system.

 TCP    0.0.0.0:80             0.0.0.0:0              LISTENING       4 

I then remembered that SQL Reporting service my take up port 80. I stopped the server and viola – port 80 is now open again!

To solve this, I had to reconfigure the SQL Reporting to use a different port.

Go to your Reporting Services Configuration Manager and change the port for the Web Service Url and Reporting Service Url.

Now my web site is running on port 80 again 🙂

Incoming search terms:

  • Child 3452: Listening on port 80
  • listen port 80 with scom

What do you think about this post?