Endpoint Protection

 View Only
Expand all | Collapse all

Error in SEPM log

AndrewIT

AndrewITApr 22, 2013 09:52 AM

Migration User

Migration UserApr 23, 2013 01:02 PM

  • 1.  Error in SEPM log

    Posted Apr 22, 2013 08:45 AM
      |   view attached

    hi,

    i installed a SEPM v12.1 RU2 MP1 on win 2003 server and all works fine.

    but on SEPM log window i can see every hour a message "Unexpected server error"

    see the attached file (in italian language)

    what is this ? and what can i do ?

    thank's



  • 2.  RE: Error in SEPM log

    Posted Apr 22, 2013 08:58 AM

    Per this article, turn on SEPM debugging and post the logs here for review

    How to debug the Symantec Endpoint Protection Manager

    Article:TECH102413  |  Created: 2007-01-06  |  Updated: 2013-02-26  |  Article URL http://www.symantec.com/docs/TECH102413

     



  • 3.  RE: Error in SEPM log

    Posted Apr 22, 2013 09:52 AM
      |   view attached

    i attached the symhelp result

    Attachment(s)



  • 4.  RE: Error in SEPM log

    Posted Apr 22, 2013 10:01 AM

    Follow these articles

    http://www.symantec.com/business/support/index?page=content&id=TECH166923

     

    This happens due to lu failure.

    Take reg back up and data backup first .

     

    Do reboot on server if possible and then do luall.



  • 5.  RE: Error in SEPM log

    Posted Apr 23, 2013 07:33 AM

    Hi

    Please follow the link below

    http://www.symantec.com/business/support/index?page=content&id=TECH165557&actp=search&viewlocale=en_US&searchid=1366716710391

    Regards

     



  • 6.  RE: Error in SEPM log

    Posted Apr 23, 2013 08:05 AM

    i saw the link

    but i didn't done a migration. i had a new installation on another server



  • 7.  RE: Error in SEPM log

    Posted Apr 23, 2013 01:02 PM

    Did you try the article which i have shared ?



  • 8.  RE: Error in SEPM log

    Posted Apr 24, 2013 02:35 AM

    no, because my clients have the right virus definitions



  • 9.  RE: Error in SEPM log



  • 10.  RE: Error in SEPM log

    Posted Apr 24, 2013 06:43 AM

    1) i can login to SEPM console

    2) i didn't upgrade. i had a new installation. however FcgidImpersonation Off in my httpd.conf file

    3) i cannot find IIS Administration. i saw IIS is NOT installed on my SEPM server machine. is this a problem ?



  • 11.  RE: Error in SEPM log
    Best Answer

    Trusted Advisor
    Posted Apr 24, 2013 02:13 PM

    Hello,

    Is this a new machine with a New SEPM installation?

    Did the machine ever had earlier version of SEPM installed on it?

    Upon checking the Logs, we see the scm-server-0.log and found as following:

    com.sygate.scm.server.agentmanager.InvalidDomainIdRegistrationException: UT7 The client is trying to register with an invalid domain ID 7B658099C0A8C8D60024B94374D8B180.
    at com.sygate.scm.server.agentmanager.AgentRequestHandler.registerClient (AgentRequestHandler.java: 1698)

    Cause: SEP clients were trying to register to the SEPM with an invalid Domain ID.

    Solution: Replace the sylink.xml file on all clients that were trying to register with an invalid Domain ID.

    Check this Article:

    SEP 12.1 RU2 and Reset Client Communication

    https://www-secure.symantec.com/connect/articles/sep-121-ru2-and-reset-client-communication

    Restoring client-server communications with Communication Update Package Deployment

    http://www.symantec.com/docs/HOWTO81109

    How do I replace the client-server communications file on the client computer?

    http://www.symantec.com/docs/HOWTO81116

    Hope that helps!!



  • 12.  RE: Error in SEPM log

    Posted Apr 26, 2013 02:49 AM

    yes, it is a new installation on a machine that had not ever had SEPM

    it had a sep client

    thank for the help regarding the log file

    i'll try to replace the comunication file on that client



  • 13.  RE: Error in SEPM log

    Posted Apr 26, 2013 05:48 AM

    great Mithun Sanghavi !

    "Replace the sylink.xml file on all clients that were trying to register with an invalid Domain ID" should be the solution !

    at the moment I no longer have the error ...