none
SCCM Client Installation Fail with error code 80070002 RRS feed

  • Question

  • Hello All.

    We're using SCCM 2012 R2 SP1. SCCM Client installation is getting failed again on a Windows 7 SP1 desktop.

    ccmsetup.log are as below:

    MSI: Setup failed due to unexpected circumstances. The error code is 80070002

    File C:\Windows\ccmsetup\{8971B736-FB0A-4D07-AE81-82D40BBCD630}\client.msi installation failed. Error text: ExitCode: 1603
    Action: CcmFixupServiceConfigInit.
    ErrorMessages: 

    Setup failed due to unexpected circumstances. The error code is 80070002

    Client.msi.log are as below:

    MSI (s) (84:10) [12:44:36:945]: Product: Configuration Manager Client -- Installation operation failed.

    MSI (s) (84:10) [12:44:36:946]: Windows Installer installed the product. Product Name: Configuration Manager Client. Product Version: 5.00.8239.1000. Product Language: 1033. Manufacturer: Microsoft Corporation. Installation success or error status: 1603.

    I've tried rebuilding the WMI repository (as described in the article http://blogs.catapultsystems.com/javery/archive/2009/07/01/sccm-client-installation-error-80041001), but again same error.

    Please help and advise.

    Many thanks in anticipation.

    Regards,

    Hasan Bin Hasib


    Tuesday, September 29, 2015 8:04 AM

Answers

  • Rebuilding WMI is not a cure all and is not harmless like a reboot; i.e., it doesn't make sense to blindly rebuild WMI every time you have an error.

    Based on the log snippet above, the custom action CcmFixupServiceConfigInit is failing. I don't have intimate knowledge of this custom action but based upon its name, it is attempting to manipulate some service in some way although the exact error is "Failed to cache service configuration". Also, error code 2 = file not found.

    Putting all of this together leads me to believe that the system is locked down or the anti-virus product in use is preventing the action. You need to review the logs for your AV product as well as the event viewer to see if you can find any correlating activity. ProcMon may also be helpful here in discovering what exactly is going on.


    Jason | http://blog.configmgrftw.com | @jasonsandys

    Tuesday, September 29, 2015 11:58 AM

All replies

  • Log snippets usually don't help. Examine client.msi.log, search for "return value 3". The failure reason should be listed a few lines above. 

    Torsten Meringer | http://www.mssccmfaq.de

    Tuesday, September 29, 2015 8:22 AM
    Moderator
  • client.msi.log are as below:

    Action start 14:20:45: CcmFixupServiceConfigInit.
    MSI (s) (20!84) [14:20:45:868]: Closing MSIHANDLE (5002) of type 790531 for thread 2692
    MSI (s) (20!84) [14:20:45:868]: Creating MSIHANDLE (5003) of type 790531 for thread 2692
    MSI (s) (20!84) [14:20:45:868]: Creating MSIHANDLE (5004) of type 790531 for thread 2692
    [14:20:45] ERROR: Failed to cache service configuration (80070002)
    MSI (s) (20!84) [14:20:45:868]: Closing MSIHANDLE (5004) of type 790531 for thread 2692
    [14:20:45] @@ERR:25001
    Error 25001. Setup failed due to unexpected circumstances
    The error code is 80070002
    MSI (s) (20!84) [14:20:45:869]: Product: Configuration Manager Client -- Error 25001. Setup failed due to unexpected circumstances
    The error code is 80070002

    MSI (s) (20!84) [14:20:45:870]: Closing MSIHANDLE (5003) of type 790531 for thread 2692
    MSI (s) (20!84) [14:20:45:870]: Closing MSIHANDLE (5001) of type 790541 for thread 2692
    MSI (s) (20:78) [14:20:45:871]: Closing MSIHANDLE (5000) of type 790542 for thread 5100
    CustomAction CcmFixupServiceConfigInit returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)
    MSI (s) (20:EC) [14:20:45:892]: Machine policy value 'DisableRollback' is 0
    MSI (s) (20:EC) [14:20:45:892]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2 
    Action ended 14:20:45: CcmFixupServiceConfigInit. Return value 3.
    MSI (s) (20:EC) [14:20:45:893]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2 
    MSI (s) (20:EC) [14:20:45:893]: No System Restore sequence number for this installation.
    MSI (s) (20:EC) [14:20:45:893]: Unlocking Server
    Action ended 14:20:46: INSTALL. Return value 3.

    Tuesday, September 29, 2015 10:01 AM
  • Hi..

    let us know...Which client installation method used, SP1 CU1 is released. Try after upgrading with CU1.


    Regards, kanna

    Tuesday, September 29, 2015 11:51 AM
  • Rebuilding WMI is not a cure all and is not harmless like a reboot; i.e., it doesn't make sense to blindly rebuild WMI every time you have an error.

    Based on the log snippet above, the custom action CcmFixupServiceConfigInit is failing. I don't have intimate knowledge of this custom action but based upon its name, it is attempting to manipulate some service in some way although the exact error is "Failed to cache service configuration". Also, error code 2 = file not found.

    Putting all of this together leads me to believe that the system is locked down or the anti-virus product in use is preventing the action. You need to review the logs for your AV product as well as the event viewer to see if you can find any correlating activity. ProcMon may also be helpful here in discovering what exactly is going on.


    Jason | http://blog.configmgrftw.com | @jasonsandys

    Tuesday, September 29, 2015 11:58 AM
  • SCCM Client is getting installed smoothly on most computers, but this error on a very few computers.

    Anybody please help me.

    MSI: Action 15:24:28: CcmFixupServiceConfigInit. Gathers the services or load ordering groups which must be started before ccmexec starts.

    File C:\Windows\ccmsetup\{8971B736-FB0A-4D07-AE81-82D40BBCD630}\client.msi installation failed. Error text: ExitCode: 1603
    Action: CcmFixupServiceConfigInit.
    ErrorMessages:
    Setup failed due to unexpected circumstances
    The error code is 80070002

    Wednesday, October 7, 2015 10:35 AM
  • Please see my reply above. We don't have crystal balls. It seems that you've stumbled onto something no else has ever seen so you will need to do some troubleshooting and investigation to find the root cause here.

    Jason | http://blog.configmgrftw.com | @jasonsandys

    Wednesday, October 7, 2015 1:44 PM
  • Then you really should start a new thread (this one is two and half years old) and provide actual technical details like the complete, unedited, and relevant portion (not just the error line) of the ccmsetup.log or the entire log (posted on a file sharing service and linked to here).

    Jason | https://home.configmgrftw.com | @jasonsandys

    Friday, February 23, 2018 3:32 PM
  • I saw this recently and it was due to some of the SCCM services being left in a dodgy state after a removal of the ccmclient via unapproved methods.

    eg. May 19, 2017 post from this site:
    https://forums.prajwaldesai.com/threads/sccm-client-install-failed-with-exit-code-1603.1047/

    So if you've fallen into the trap of having ran this powershell script and are getting the following error message:

    Error text: ExitCode: 1603
    Action: CcmFixupServiceConfigInit.
    ErrorMessages: 

    Setup failed due to unexpected circumstances. The error code is 80070002

    have a look in your services and see if you can see any of the following in the description fields:

    [Failed to read Description. Error Code: bla]

    If so you might need to use the following commands to remove the left over services which can no longer be self-healed by the CcmFixupServiceConfigInit action in the client.msi

    sc /delete "ccmexec"

    sc /delete "cmrcservice"

    sc /delete "smstsmgr"

    open task manager and kill any running msiexec.exe (provided you haven't got something installing) ccmsetup.exe

    then attempt the reinstall again via ccmsetup.exe... should work fine now.

    • Proposed as answer by Tuckwell Friday, December 14, 2018 4:01 AM
    Thursday, December 13, 2018 6:13 AM