Policy Manager and Server Security was installed on server, but had to be uninstalled and reinstalled due to power cut.
Reinstallation of Policy Manager failed due to host module error on http port 80
Check if port 80 is used by service by launching a web browser locally on the server. Open the following page:
This will show the homepage of application currently running and hosted on port 80. This application is currently the reason for blocking the Policy Manager Server (re)installation.
To resolve the issue and to reinstall Policy Manager, several options are available and listed below in the order of preference.
1. Stop the service currently running on port 80. Consult the product documentation to understand how to do this. E.g. Microsoft webserver (IIS) using port 80 can be temporarily stopped b typing NET STOP HTTP in a command prompt.
2. Change the default port for the application running on port 80.Consult the product documentation to understand how to do this.
3. Reinstall Policy Manage server and during installation, select a different http port (e.g. 81). However, keep in mind that if you have existing end-points currently running for instance F-Secure Client Security or Server Security, they will no longer be able to contact the Policy Manager Server to download updates, until you distribute a policy with the correct http port (see screenshot).
Article no: 000016173