OpenEdge Command Center server startup failure in high availability setup

This topic describes how to troubleshoot the case where the OpenEdge Command Center server fails to start in a High Availability (HA) setup. It outlines common causes and provides recommended solutions to help you complete the startup process successfully.

Possible Cause	Recommended Solution
Database connectivity issue	Navigate to the installation log directory at <Server_Installed_Dir>/install_logs/, and open the log file named Install_<MM_DD_YYYY_H_M_S>.log. Check for error messages, such as Closed DB Connections, which indicate a database connectivity issue. If such errors are present, navigate to the <Data_Dir>/conf/ folder and open the db-config.json file. Verify the values for DB Hostname and DB Port and update them if necessary.
Database unreachable from the non-primary server	Check the connectivity from the non-primary server to the database host and port. Ensure that the non-primary server is connected to a stable internet network. Check if the firewall or proxy settings on the non-primary server system is blocking outbound connections. If necessary, update the settings to allow connectivity to the database host and port.