Unable to connect to Policy Manager Server via the Policy Manager console

Issue:

Unable to connect to Policy Manager Server via the Policy Manager console. 
​

Resolution:

If logging in to Policy Manager Console fails, make sure that the WithSecure Policy Manager (wspms) service is running. If it is not running, check the fspms-service.log if you see the following is logged repeatedly in:

[ERROR]    Server process crashed, exit code was 1

This suggest that the Policy Manager Java process crashes at startup, which could stop the Policy Manager admin to logon to the Policy Manager Console since the Policy Manager Server service is not running. 

You would need to make sure that the listening ports used by Policy Manager Server service are not in use by any other process. This is the most common reason why the Policy Manager Server service (wspms) fails to start. 

1. Open a Command Prompt and run the command "netstat -anb" to check and ensure that there is no port conflict present by checking that no other process that is currently using the default 80 and 443 ports that Policy Manager Server service will try to use as listening ports. Alternatively, look into netstat-anb.log in the wsdiag. 

If the issue happens due to port conflicts, you should as first choice either stop the conflicting service or reconfigure it to use another port. As a second choice, you may consider changing the host module's port numbers from 80 and 443 to other available ports, such as 85 and 455 by using these steps:

1. Stop the Policy Manager Server service (net stop wspms)
2. Open the Registry Editor
3. Navigate to HKLM\Software\WithSecure\Policy Manager\Policy Manager Server
4. Modify the values of HttpPortNum and HttpsPortNum to the new ports (e.g., 85 and 455).
5. Start the Policy Manager Server service (net start wspms)

Remember to configure the clients to connect to the new port. 

If no port conflict is present, move to the next step. 

2. Stop the Policy Manager Server service, and backup the H2DB folder in the directory: C:\ProgramData\WithSecure\NS\Policy Manager\Policy Manager Server\Data\

3. Run the H2DB recovery tool (fspms-db-recover.bat), and the database maintenance tool (fspms-db-maintenance-tool.exe) to fix the potential corruption in the H2DB. You can find the tools in the directory,C:\Program Files\WithSecure\Policy Manager\Policy Manager Server\bin\ where Policy Manager Server is installed.

NOTE: Refer to README-recover-db.txt in the same directory on how to use the H2DB recovery tool.

If none of the above-mentioned help, proceed to re-install the Policy Manager Server on top of the existing installation.

If the h2database.log has a number of errors similar to the following:

ERROR [h2database] – fspms:jdbc[10] exception
org.h2.jdbc.JdbcSQLException: General error: "java.lang.ArrayIndexOutOfBoundsException"; SQL statement:
SELECT oid_id, value FROM status WHERE domain_id=? [50000-164]

Caused by: org.apache.http.conn.HttpHostConnectException: Connect to localhost:8000 [localhost/127.0.0.1, localhost/0:0:0:0:0:0:0:1] failed: Connection refused: connect

To resolve the issue, we can do the following:

1. Stop the WithSecure Policy Manager service (net stop wspms)
2. Back up the H2DB located at: C:\ProgramData\WithSecure\NS\Policy Manager\Policy Manager Server\data
3. Run the database maintenance tool, fspms-db-maintenance-tool.exe located at: C:\Program Files\WithSecure\Policy Manager\Policy Manager Server\bin
4. Start the WithSecure Policy Manager service (net start wspms)
5. Try logging in to the Policy Manager Console again