Policy Manager Server failed to start with error “Server process exited because of misconfiguration (exit code 3)”

Issue:

Policy manager Server service fails to start. fspms-service.log shows "Server process exited because of misconfiguration (exit code 3), see fspms-webapp-errors.log for details" 

Resolution:

If Policy Manager Server service fails to start and you are unable to connect with the Policy Manager Console to the server, the most likely cause for the issue is that either the HTTP or HTTPS port that Policy Manager Server has been configured to listed was in use during startup. 

Navigate to the log folder on the server: C:\ProgramData\WithSecure\NS\Policy Manager\Policy Manager Server\log

Then check the fspms-stderrout.log if you see similar error messages related to failing to bind port:

WARN:cffur.NettyHttpServer:main: Http server failed to bind port
reactor.netty.ChannelBindException: Failed to bind on [0.0.0.0:80]
Suppressed: 
|java.lang.Exception: #block terminated with an error

WARN:cffur.NettyHttpServer:main: Http server failed to bind portreactor.netty.ChannelBindException: Failed to bind on [0.0.0.0:443]Suppressed:  |java.lang.Exception: #block terminated with an error

If you see these errors, run the command "netstat -anb" in a Command Prompt to check and ensure that there is no port conflict present. If there is, you need to stop the service that is using the port or you need to change with port the service is using.