Endpoint Protection

 View Only
  • 1.  failed to start

    Posted Oct 05, 2012 01:38 PM

    Error : 1920, "SepMasterService" failed to start the Symantec endpoint Service.



  • 2.  RE: failed to start

    Posted Oct 05, 2012 01:40 PM

    Solution is attach here

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

     

    Hope it will help you



  • 3.  RE: failed to start

    Broadcom Employee
    Posted Oct 05, 2012 01:43 PM

    does restart of machine helps?

     



  • 4.  RE: failed to start

    Posted Oct 05, 2012 01:44 PM

    This issue is occured while installing the SEP Client. error attached here



  • 5.  RE: failed to start

    Trusted Advisor
    Posted Oct 05, 2012 01:53 PM

    Hello,

    What version of SEP 11.x are you running? OR Are you running SEP 12.1 ?

    What OS are is this issue occurying on?

    Could you upload us the SEP_Inst.log from %temp%?

    Also, try the steps below:

    • Browse to HKEY_LOCAL_MACHINE\SOFTWARE\Symantec\Symantec Endpoint Protection\SMC
    • Select and right click SMC and choose Permission from the drop down menu
    • In permissions add the User, Administrator and SYSTEM with full permission
    • Reboot the machine

    Try again installing SEP.

    Hope that helps!!



  • 6.  RE: failed to start

    Posted Oct 05, 2012 10:58 PM

     Resolution 1

    1. Click Start
    2. Click Run.
    3. Type regedit
    4. Click OK.
    5. Navigate to the following subkeys:
      • HKEY_LOCAL_MACHINE\Software\Intel
      • HKEY_LOCAL_MACHINE\Software\Symantec
      • HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion
      • HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\App Paths
      • HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services
         
    6. For each of these keys, ensure that "Administrator", "Administrators" and "System" have Full Control.

    Warning: If all of the groups: "Administrator", "Administrators" and "System" have Full Control, DO NOT CHANGE ANYTHING, instead proceed to Resolution 2.
     

    Resolution 2
    The Trusted Publishers Properties must have "Allow the following users to Select Trusted publishers" configured to "End Users." To change this setting follow the below steps:

    1. Go to Default Domain Controller Security Settings> Software Restriction Policies> Trusted publishers
    2. Change the settings from "Enterprise Administrators" to "End Users."
      • This sets AuthenticodeFlags = 0 under the following registry locations.
        • HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\SystemCertificates\TrustedPublisher\Safer\AuthenticodeFlags
        • HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SystemCertificates\TrustedPublisher\Safer\AuthenticodeFlags
        • HKEY_CURRENT_USER\Software\Policies\Microsoft\SystemCertificates\TrustedPublisher\Safer\AuthenticodeFlags
           
    3. Perform the following: gpupdate /force, to force a refresh of the Group Policy on the AD Server.
    • Resolution 3
      If the CustomSD entry for the Application Eventlog has been modified, then the "Symantec Settings Manager" will not be able to read/write to that Application Eventlog.

      Please read and follow the directions in the following Microsoft document to ensure that the CustomSD entry for the Application Eventlog is set to default:
      "How to set event log security locally or by using Group Policy in Windows Server 2003" at URL: http://support.microsoft.com/kb/323076

    http://service1.symantec.com/SUPPORT/ent-security.nsf/7bc18d1a4d5824eb882573410063493f/1b2e84935a72a896652573c40078a0b4?OpenDocument



  • 7.  RE: failed to start
    Best Answer

    Posted Oct 07, 2012 12:13 AM

    Also try following article

    Symantec AntiVirus: "Error 1920". "The Service failed to start. Verify that you have sufficient privileges to start system services."

     
     
    Hope it can helpful to you


  • 8.  RE: failed to start

    Posted Oct 07, 2012 12:21 AM

    Hi,

    Did you check the permission on the service? Are you logged in as with less previlege?



  • 9.  RE: failed to start

    Posted Oct 25, 2012 05:18 PM

    Syed- our issue close or still pending?