OpenEdge Command Center server fails to start after installation

This topic describes how to troubleshoot the case where the OpenEdge Command Center server does not start after a successful installation. It outlines common causes and provides recommended solutions to help you start the OpenEdge Command Center server.

Possible Cause	Recommended Solution
Unknown error during installation or startup.	Navigate to the installation log directory at <Server_Installed_Dir>/install_logs/, and open the Install_<MM_DD_YYYY_H_M_S>.log log file. Review the log file for any errors or failures related to MongoDB startup.
Certificate validation failure due to invalid host information in certificates.	Navigate to the installation log directory at <Server_Installed_Dir>/install_logs/, and open the Install_<MM_DD_YYYY_H_M_S>.log log file. Review the log file for any nohostverify errors. If the log contains an error about connection failure to the Authorization server with host validation, then the certificates used for secure communication do not have valid host information. Navigate to the <Server_Installed_Dir>/conf/server-config.json file and update the value of nohostverify flag to true.
No permission to data directory in multi-node setup.	Ensure that all the non-primary OpenEdge Command Center servers have permissions to the data directory on the system where the primary server is installed.