Web server port in use when installing SQL Monitor

When installing SQL Monitor you may find that it shows the web port is not available and there are several reasons this can happen.  You will only see this when using the built in web server option, otherwise you'll be setting the port binding for the site in IIS.

First install

If this is the first time you are installing SQL Monitor then another application is using the port.  You may be able to find more information about what that is by running the following from an elevated command prompt (substitute in your port number):

netstat -ano | findstr :8080

This should hopefully give you the PID of the process using the port and you can find the name by running the following (substituting <PID> for the actual number returned e.g. 15824):

tasklist /svc /FI "PID eq <PID>"

You can then decide to stop this application or use a different port.

Subsequent install

For updating versions of SQL Monitor after 10.1.0 this should no longer apply as HKLM is now used.

If SQL Monitor is currently installed and you are entering the same port as it currently uses, then it's likely now being installed by a different user than it originally was.  The user registry is used to store the port and some other information when SQL Monitor is installed so if it's being installed by a different user, the installer doesn't know that it's SQL Monitor that's using the port as it doesn't have access to the other users registry.

In this case, all you need to do is to stop the currently running "SQL Monitor Web Service" service and continue the installation.

Was this article helpful?

0 out of 0 found this helpful
Have more questions? Submit a request