Endpoint Protection

 View Only
Expand all | Collapse all

No Symantec Protection Technologies... after clean wipe and reinstall.

  • 1.  No Symantec Protection Technologies... after clean wipe and reinstall.

    Posted Jun 07, 2010 02:14 PM
    I am now facing the dreaded, "No Symantec protection technologies are installed" in Windows 7.  I think mine is different than most I have read on here which is why I created a new discussion.  SEP RU5 was working fine on this machine.  The machine then started acting up and the PC group felt that it was related to SEP so they uninstalled it and performed a clean wipe.  The issue persisted and it was determined that the machine's motherboard was the issue.  A new motherboard was installed and the machine was back to normal.  SEP was reinstalled and the error about no symantec protection technologies first occurred.  I tried several fixes including http://service1.symantec.com/SUPPORT/ent-security.nsf/docid/2009042115381848 the articles referencing permissions both at the registry and file level.  I ensured NTFS permissions were correct and sent all changes to the child objects.  It did not seem to help.  I uninstalled SEP and installed Comcast's Norton Internet Security as a test, it worked fine.  I uninstalled and cleanwiped again to make sure.  I then logged in with a local admin account instead of a domain admin account and installed RU6a thinking it might resolve the problem.  It did not.  As it stands, I have tried every suggestion in any of the related discussions and cannot figure it out.  I do not think it is related to a domain admin/regular user permission issue as I'm running as a local admin on the box and also a domain admin and the message is still there.

    I even tried manually installing live update first and then running setup and installing Anti-Virus and Anti-Spyware with no other options.  I still get the same issue.

    Here are some snippets from my SEP_INST log that I found interesting... maybe they will make sense to someone else.


    Action ended 16:17:13: CommonFilesFolder.14DD7176_DF3C_4FFC_B723_66069FF29729. Return value 1.
    MSI (c) (0C:14) [16:17:13:752]: Doing action: SetInstallStateFailed.1CBEC0D3_E547_4E51_828B_44B9C47C0EA5
    Action 16:17:13: SetInstallStateFailed.1CBEC0D3_E547_4E51_828B_44B9C47C0EA5.
    Action start 16:17:13: SetInstallStateFailed.1CBEC0D3_E547_4E51_828B_44B9C47C0EA5.
    MSI (c) (0C:30) [16:17:13:862]: Invoking remote custom action. DLL: C:\Users\username\AppData\Local\Temp\MSID043.tmp, Entrypoint: SetInstallStateFailed

    MSI (c) (0C:14) [16:19:04:393]: Note: 1: 1708
    MSI (c) (0C:14) [16:19:04:393]: Product: Symantec Endpoint Protection -- Installation operation failed.

    MSI (c) (0C:14) [16:19:04:393]: Windows Installer installed the product. Product Name: Symantec Endpoint Protection. Product Version: 11.0.6005.562. Product Language: 1033. Manufacturer: Symantec Corporation. Installation success or error status: 1603.

    MSI (c) (0C:14) [16:19:04:409]: Grabbed execution mutex.
    MSI (c) (0C:14) [16:19:04:409]: Cleaning up uninstalled install packages, if any exist
    MSI (c) (0C:14) [16:19:04:409]: MainEngineThread is returning 1603
    === Verbose logging stopped: 6/4/2010  16:19:04 ===

    Can anyone think of something else to try before I wipe the machine entirely to resolve the issue?

    Thanks!


  • 2.  RE: No Symantec Protection Technologies... after clean wipe and reinstall.
    Best Answer

    Posted Jun 07, 2010 02:42 PM
    Please check following articles

    Title: 'Symantec Endpoint Protection installation rolls back while upgrading'
    Web URL: http://service1.symantec.com/support/ent-security.nsf/docid/2009110712450848?Open&seg=ent
     
    Title: 'Windows 7 / 2008 R2 - SEP Client installation rolls back.'
    Web URL: http://service1.symantec.com/support/ent-security.nsf/docid/2009110411364348?Open&seg=ent
     
    Title: 'Symantec Endpoint Protection Client installation fails on LUCHECK 206'
    Web URL: http://service1.symantec.com/support/ent-security.nsf/docid/2010012509092648?Open&seg=ent

    Not exactly refer to this issue but can be used.