Endpoint Protection

 View Only
  • 1.  SEP Manager 12.1.6168.6000 Unexpected Server Error

    Posted Nov 20, 2015 03:24 AM

    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:​

    kbeheede-sepm-logerror.jpg

    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?

     



  • 2.  RE: SEP Manager 12.1.6168.6000 Unexpected Server Error

    Posted Nov 23, 2015 06:12 PM

    Enable FINEST logging and re-produce the issue. Post the scm-server-0.log file here once done.

    Debugging Symantec Endpoint Protection Manager



  • 3.  RE: SEP Manager 12.1.6168.6000 Unexpected Server Error

    Posted Nov 25, 2015 10:32 AM
      |   view attached

    Hi Brian,

    I've enabled the FINEST logging, the log is in attachement.

    At first sight, there isn't any extra information...

     

    Attachment(s)

    zip
    scm-server-0_58.zip   7 KB 1 version


  • 4.  RE: SEP Manager 12.1.6168.6000 Unexpected Server Error

    Posted Nov 25, 2015 11:16 AM