Endpoint Protection

 View Only
  • 1.  SescLU event ID 13

    Posted Mar 18, 2009 04:56 AM

     I have a problem with 3 computers out of 90 - they keep showing me this error - sesclu 13. 

    On these 3 computers the automatic liveupdate doesn't work - my configuration is domain on 2k3 with SP1 and XP Profs on all clients. I'm using Symantec Endpoint Prot. since first released version. 

    The weird thing is that when i put these clients into manual LiveUpdate group they update with no problems - but when i put them back in an automatic update installation group, they keep on reporting errors...

    All clients have 11.0.4000.2295 version installed, SEPM is 11.0.4000.2295 and i use LUA 2.2.1.13 

    One more thing - i tried reinstalling these computers (just symantec client) for several times and unfortunatelly the errors keep on showing... Reinstallation of XP CANNOT BE DONE (because these computers are used almoust permanently)

    What i need is a tool to completly remove Symantec Endpoint Protection Client - maybe installing on clean system will fix these errors



  • 2.  RE: SescLU event ID 13

    Posted Mar 18, 2009 05:58 AM

    Symantec has a Tool called CleanWipeUtility.

    Just call Symantec Support for this tool.



  • 3.  RE: SescLU event ID 13
    Best Answer

    Posted Apr 01, 2009 02:44 AM
     Actually i downloaded the file (CleanWipe) and i did the total uninstall of one of these clients - unfortunatelly it didn't help... 
    But what DID help was :

    I checked the configuration of Symantec LiveUpdate on this computer - and there was HTTP and FTP configuration. The both used configuration defined in Internet Options - we use proxy in our company to access Internet, but the proxy is disabled for local addresses. What i did was changing configuration both for HTTP and FTP to not use proxy at all. It worked like charm!! Poof - all errors gone - the clients are updating....

    What is strange in this situation is that all other clients work with default configuration (use Internet Options conf.) and they work without any problems (we use local LiveUpdate Server).... But everything is okay for now so i can say that the case is closed for me.