Unable to connect to the Policy Manager Server using Policy Manager Console

Issue:

When trying to connect to the Policy Manager Server, Policy Manager Console prompts an error message: "Cannot connect to the server: localhost:8080. Check that the host name and port number are correct. Port number 8080 is used by default."

Policy Manager Server doesn't start and checking the Status Monitor, all ports are shown with red color, signifying a problem.

End-points cannot connect to the Policy Manager Server to download policies or database updates.

Resolution:

Ensure that Policy Manager Console and Policy Manager Server are running the same version.

For Policy Manager for Windows:

Follow this Knowledge base Article
You can also check in the log files if WebUI-Deamon is working. If not, start it first and then try again to connect to the Policy Manager Console.

If the problem still persist

1. Make sure that there is not a port conflict:

Run command prompt (cmd.exe) as an administrator
Enter the command "netstat -a -b > C:\port.txt"
Check in port.txt the ports set in the F-Secure Policy Manager are not used. If the listening port configured for Policy Manager Server service is active and listening, also ensure the port returns the Policy Manager home page when you access the relevant page locally or over the network (use a browser e.g. locally -> http:\\localhost).

Note: if you find a conflict, you can solve it changing the ports or by uninstalling / deactivating the service causing the conflict.

If the problem still persist, maybe is the WithSecure Policy Manager installation broken, in this case contact our WithSecure Support directly.

2. Invalid startup parameters in registry can also prevent Policy Manager Server from starting. Please review the settings:


HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Data Fellows\F-Secure\Management Server 5
additional_java_args

Valid configuration settings for the additional_java_args are listed and available in WithSecure Community.

This is an example of valid settings:


-DmaxUploadedPackageSize=10485760 -DforbidDownloadingPublicKey=false -Dh2ConsoleEnabled=true -DallowUnsignedWithRiwsAndMibs=true

Below are some examples of invalid settings:


\f-secure\backup-folder

-maxUploadedPackageSize=10485760

DmaxUploadedPackageSize=10485760

3. Re-install WithSecure Policy Manager on top of the current installation .

For Policy Manager for Linux:

Edit the /etc/opt/f-secure/fspms/fspms.conf configuration file as below.

Create a new line with the parameter additional_java_args.
Specify the Java system properties with the value in quotes in the following format:
```
-DpropertyName=value
```
If you want to specify multiple properties, use space as the delimiter. Property names and values are case-sensitive. An example:
```
additional_java_args="-DmaxUploadedPackageSize=10485760"
```
Restart the Policy Manager Server service to make the new configuration settings take effect.

In case MySQL database is in used:
We recommend to do the following:

Ensure that the following entry is there in MySQL configuration file, my.ini:
- max_allowed_packet=100M
Restart MySQL service.

Article no: 000001526