After upgrading successfully to version 14, we were no longer able to log into Symantec Endpoint Protection Manager with the error - "Failed to connect to the server.
Make sure that the server is running and your session has not timed out.
If you can reach the server but cannot log on, make sure that you provided the correct parameters.
If you are experiencing network issues, contact your system administrator."
The correct ports were open and the clients were still talking to the server correctly. Upon investigation, I found that the logs I were looking for were in: <SEPM Install Location>\tomcat\logs\scm-server-0.txt
The following errors were found:
"com.sygate.scm.common.communicate.CommunicationException: Failed to connect to the server.
Make sure that the server is running and your session has not timed out.
If you can reach the server but cannot log on, make sure that you provided the correct parameters.
If you are experiencing network issues, contact your system administrator. ErrorCode: 0x80020000
javax.net.ssl.SSLException: java.lang.RuntimeException: Could not generate DH keypair
Caused by: java.security.InvalidAlgorithmParameterException: Prime size must be multiple of 64, and can only range from 512 to 2048 (inclusive)"
Our standard is to have all SSL certificates have a key of 4096 bit unless the application cannot support it. This worked fine before.
Inside <SEPM Install Location>\tomcat\conf\server.xml you should see "Connector SSLCertificateFile", you will find the location of the crt and key file.
Generate a new certificate with a 2048 bit key and replace these files.
Restart these services:
Symantec Endpoint Protection Manager Webserver
Symantec Endpoint Protection Manager API Service
Symantec Endpoint Protection Manager
After doing this I was able to successfully log back into the SEPM console.
Hope this helps anyone that runs into a similar issue.