Video Screencast Help
Search Video Help Close Back
to help
Not able to make it to Vision this year? Get a sampling in the Best of Vision on Demand group.

lucheck returned 206

Updated: 16 Nov 2010 | 3 comments
v_anesh's picture
0 0 Votes
Login to vote
This issue has been solved. See solution.

Installing SEP on Windows 2008 R2 and i am getting the following error

MSI (s) (28:A4) [17:31:29:132]: Executing op: CustomActionSchedule(Action=InstallLiveUpdate_RB.FF07F38E_78C2_412E_B858_64488E808644,ActionType=3329,Source=BinaryData,Target=UnInstallLiveUpdate,CustomActionData=C:\Temp\WAGSHIVF\LiveUpdate\lucheck.exe)
MSI (s) (28:A4) [17:31:29:132]: Executing op: ActionStart(Name=InstallLiveUpdate.FF07F38E_78C2_412E_B858_64488E808644,,)
MSI (s) (28:A4) [17:31:29:132]: Executing op: CustomActionSchedule(Action=InstallLiveUpdate.FF07F38E_78C2_412E_B858_64488E808644,ActionType=3073,Source=BinaryData,Target=InstallLiveUpdate,CustomActionData=C:\Temp\WAGSHIVF\LiveUpdate\lucheck.exe)
MSI (s) (28:58) [17:31:29:132]: Invoking remote custom action. DLL: C:\WINDOWS\Installer\MSI172.tmp, Entrypoint: InstallLiveUpdate
LUCA: InstallLiveUpdate enter.
LUCA: C:\Temp\WAGSHIVF\LiveUpdate\lucheck.exe
LUCA: InstallLiveUpdate : CreateProcessAndWait( LUCHECK.EXE ) returned 206
MSI (s) (28:A4) [17:31:35:960]: User policy value 'DisableRollback' is 0
MSI (s) (28:A4) [17:31:35:960]: Machine policy value 'DisableRollback' is 0
Action ended 17:31:35: InstallFinalize. Return value 3.

I have followed the steps from the kb https://www-secure.symantec.com/connect/articles/how-troubleshoot-failed-install-sep-or-sepm still no go

 

  •    Check the  Windows Application and System Event logs if there is nothing clear from the install logs

 

  •    Try to install  it as Unmanaged from the Install DVD or CD  to rules out the issue with the package created in case of the SEP install.

 

  •    Try to  the install logged in as the Local Administrator.  This will rules out any permission issue\

 

  •    Click the TEMP folder and then verify that the SYSTEM account has full control.

 

  •    Then Check the language  and region selected in the OS? For English OS make sure you have International English language selected.

 

I also tried this

HKEY_USERS\.DEFAULT\Software\Microsoft\Windows\CurrentVersion\Explorer\User Shell Folders\AppData value=%USERPROFILE%\AppData\Roaming

If above registry value is not as written, please make the changes and after changes, reboot the machine and reinstall client. 

 

 

Still no go..any help would be appreciated

Discussion Filed Under:

Comments

pete_4u2002's picture
13
Nov
2010
1 Vote +1
Login to vote

1. Navigate to

1. Navigate to C:\ProgramData\Symantec and delete LiveUpdate (if present).

2 Navigate to C:\Documents and Settings\All Users\Application Data\Symantec and delete LiveUpdate (if present).

3. Start install of Symantec Endpoint Protection Client. 

if it fails then follow the steps in the link

 

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

Prachand's picture
13
Nov
2010
2 Votes +2
Login to vote

Check the DCOM and then

Check the DCOM and then reboot and then install

Correct the DCOM permission and reboot the machine.

Checking DCOM settings

The last place to check rights on a computer is in its DCOM settings.

To verify Distributed COM properties

  1. On the Windows taskbar, click Start > Run.
  2. Type the following, and then click OK:

    dcomcnfg
     

  3. Do one of the following, depending on your operating system:
    • In Windows XP/2003, click Component Services > Computers > My Computer. Then right-click My Computer and click Properties.
    • In all other versions of Windows, go on to the next step.
  4. On the Default Security or Default COM Security tab, under Default Access Permissions, click Edit Default.
  5. Verify that Administrators, Interactive, and System accounts are set to Allow Access, and then click OK.
  6. Under Default Launch Permissions, click Edit Default.
  7. Verify that the Administrators, Interactive, and System accounts are set to Allow Launch, and click OK.
  8. Do one of the following, depending on your operating system:
    • In Windows XP/2003, skip the two following steps.
    • In all other versions of Windows, go on to the next step.
  9. In the Default Configuration Permissions section, click Edit Default.
  10. In the Registry Key Permissions window, verify that the following are set to Full Control, and then click OK:

    CREATOR OWNER
    ...\Administrators
    SYSTEM
     

  11. On the Default Properties tab, verify that Default Impersonation Level is set to Identify.
  12. Click Apply, and then click OK.
  13.  Restart the computer for the changes to take effect

Prachand Kumar MCSE-2003 Symantec Technical Specialist (SCTS)

v_anesh's picture
16
Nov
2010
0 Votes 0
Login to vote

System account was missing in

System account was missing in DCOM, added it and resolved the issue.