Troubleshooting Tip: The EMS server cannot start due to Apache service failure

[JHelio]

Description	This article discusses the issue that can be met when the FortiClient EMS server cannot be opened due to Apache service failure.
Scope	FortiClient EMS v7.2.5.
Solution	Reviewing FortiClient EMS services in Windows server, the Apache Service can show the error below and cannot be started: The steps to confirm the solution is to collect and check the Apache logs in the FortiClient EMS diagnostic tool: Technical Tip: How to collect FortiClient EMS on-premise logs by Diagnostic tool The error below should be recorded: ..AH025XXX: Certificate and private key localhost:443:0 from C:/Program Files (x86)/Fortinet/FortiClientEMS/Apache24/conf/ssl.crt/FCTEMSTA200XXXX.1.cert and C:/Program Files (x86)/Fortinet/FortiClientEMS/Apache24/conf/ssl.key/FCTEMSTA2000XXXX.1.cert.key do not match AH00016: Configuration Failed This issue is caused due certs/keys being mismatched in the database and filesystem. If the log record is confirmed, a hotfix can be applied to restore Apache Services. The next step is to contact TAC Support to receive the hot-fix solution. The final solution is confirmed in v7.2.6 GA.