For one of our customers we've migrated the SEP Manager through replication to another server. While migrating, we've chosen to use a dedicated MS SQL Server for the semdb. Everything (console, updates, clients, ...) works normal and as expected, but in the console log an "Unexpected server error" is shown one time when the server starts:
In the scm-server-0.log I've found this:
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
The user connecting to the semdb is sysadmin on the SQL server and local admin on the SEP Manager server.
Any ideas on the root cause, and how it could be solved?