none
Service Pack for Proliant installing successfully but returning failure in OSD task sequence

    Question

  • Building bare metal servers with SCCM 2012 SP1 CU2 OSD and running into an issue with HPs where they attempt to install the Service Pack for Proliant 2013.02.0.  I am using a package with a program.  Here is the program command line:

    Hpsum.exe /use_latest /allow_non_bundle_components /current_credential /silent

    The application installs successfully but there is a distinct delay and then errors thrown that fails the TS.  Setting 'continue on error' is a work around but not what I want to have in the production environment.  How can I get around this issue?  This is the same exact package and program that ran perfectly fine in SCCM 2007, but we are seeing this as a new issue since the migration to SCCM 2012.

    I'd like to solve this issue as well as get rid of the "Waiting for job status notification....InstallSoftware"

    Any suggestions?

    SMSTS.LOG

    Invoking Execution Manager to install software InstallSoftware 12/3/2013 9:59:49 AM 1568 (0x0620)
    Installing software for PackageID='WCD002D2' ProgramID='Silent install' AdvertID='WC120008' has started, jobID='{8B4082A9-9477-4D1F-9DEC-6A3F19EC3F6F}' InstallSoftware 12/3/2013 9:59:50 AM 1568 (0x0620)
    Setting TSEnv variable 'SMSTSInstallSoftwareJobID_WCD002D2_WC120008_Silent install'='{8B4082A9-9477-4D1F-9DEC-6A3F19EC3F6F}' InstallSoftware 12/3/2013 9:59:50 AM 1568 (0x0620)
    Waiting for installation job to complete.. InstallSoftware 12/3/2013 9:59:50 AM 1568 (0x0620)
    Waiting for job status notification... InstallSoftware 12/3/2013 10:00:20 AM 1568 (0x0620)
    Waiting for job status notification... InstallSoftware 12/3/2013 10:00:50 AM 1568 (0x0620)
    Waiting for job status notification... InstallSoftware 12/3/2013 10:01:20 AM 1568 (0x0620)
    Waiting for job status notification... InstallSoftware 12/3/2013 10:01:50 AM 1568 (0x0620)
    Waiting for job status notification... InstallSoftware 12/3/2013 10:02:20 AM 1568 (0x0620)
    Waiting for job status notification... InstallSoftware 12/3/2013 10:02:50 AM 1568 (0x0620)
    Waiting for job status notification... InstallSoftware 12/3/2013 10:03:20 AM 1568 (0x0620)
    Waiting for job status notification... InstallSoftware 12/3/2013 10:03:50 AM 1568 (0x0620)
    Waiting for job status notification... InstallSoftware 12/3/2013 10:04:20 AM 1568 (0x0620)
    Launching command shell. OSDSetupHook 12/3/2013 10:04:25 AM 2696 (0x0A88)
    Windows station: WinSta0 OSDSetupHook 12/3/2013 10:04:25 AM 2696 (0x0A88)
    Desk"Apple-tab-span" style="white-space:pre;"> OSDSetupHook 12/3/2013 10:04:25 AM 2696 (0x0A88)
    executing command: C:\WINDOWS\system32\cmd.exe /k OSDSetupHook 12/3/2013 10:04:25 AM 2696 (0x0A88)
    executed command: C:\WINDOWS\system32\cmd.exe /k OSDSetupHook 12/3/2013 10:04:25 AM 2696 (0x0A88)
    Waiting for job status notification... InstallSoftware 12/3/2013 10:04:50 AM 1568 (0x0620)
    Waiting for job status notification... InstallSoftware 12/3/2013 10:05:20 AM 1568 (0x0620)
    Waiting for job status notification... InstallSoftware 12/3/2013 10:05:50 AM 1568 (0x0620)
    Waiting for job status notification... InstallSoftware 12/3/2013 10:06:20 AM 1568 (0x0620)
    Waiting for job status notification... InstallSoftware 12/3/2013 10:06:50 AM 1568 (0x0620)
    Waiting for job status notification... InstallSoftware 12/3/2013 10:07:20 AM 1568 (0x0620)
    Waiting for job status notification... InstallSoftware 12/3/2013 10:07:50 AM 1568 (0x0620)
    Waiting for job status notification... InstallSoftware 12/3/2013 10:08:20 AM 1568 (0x0620)
    Waiting for job status notification... InstallSoftware 12/3/2013 10:08:50 AM 1568 (0x0620)
    CompleteExecution received InstallSoftware 12/3/2013 10:09:00 AM 3320 (0x0CF8)
    CompleteExecution processed InstallSoftware 12/3/2013 10:09:00 AM 3320 (0x0CF8)
    Received job completion notification from Execution Manager InstallSoftware 12/3/2013 10:09:00 AM 1568 (0x0620)
    Installation completed with exit code 0x80070001 InstallSoftware 12/3/2013 10:09:00 AM 1568 (0x0620)
    Installation failed with error (0x80070001) InstallSoftware 12/3/2013 10:09:00 AM 1568 (0x0620)
    Setting TSEnv variable 'SMSTSInstallSoftwareJobID_WCD002D2_WC120008_Silent install'='' InstallSoftware 12/3/2013 10:09:00 AM 1568 (0x0620)
    GetExecRequestMgrInterface successful InstallSoftware 12/3/2013 10:09:00 AM 1568 (0x0620)
    Releasing job request, jobID='{8B4082A9-9477-4D1F-9DEC-6A3F19EC3F6F}' InstallSoftware 12/3/2013 10:09:00 AM 1568 (0x0620)
    Releasing of Job Request successful InstallSoftware 12/3/2013 10:09:00 AM 1568 (0x0620)
    CompleteJob successful InstallSoftware 12/3/2013 10:09:00 AM 1568 (0x0620)
    Entering ReleaseSource() for D:\_SMSTaskSequence\Packages\WCD002D2 InstallSoftware 12/3/2013 10:09:00 AM 1568 (0x0620)
    reference count 1 for the source D:\_SMSTaskSequence\Packages\WCD002D2 before releasing InstallSoftware 12/3/2013 10:09:00 AM 1568 (0x0620)
    Released the resolved source D:\_SMSTaskSequence\Packages\WCD002D2 InstallSoftware 12/3/2013 10:09:00 AM 1568 (0x0620)
    pInstall->Install(sPackageID, sProgramName), HRESULT=80070001 (e:\nts_sccm_release\sms\client\osdeployment\installsoftware\main.cpp,361) InstallSoftware 12/3/2013 10:09:00 AM 1568 (0x0620)
    Install Software failed, hr=0x80070001 InstallSoftware 12/3/2013 10:09:00 AM 1568 (0x0620)
    Process completed with exit code 2147942401 TSManager 12/3/2013 10:09:00 AM 3372 (0x0D2C)
    !--------------------------------------------------------------------------------------------! TSManager 12/3/2013 10:09:00 AM 3372 (0x0D2C)
    Failed to run the action: HP Server Pack for ProLiant 2013.02. 
    Incorrect function. (Error: 80070001; Source: Windows) TSManager 12/3/2013 10:09:00 AM 3372 (0x0D2C)
    MP server http://MP_server.company.com. Ports 80,443. CRL=false. TSManager 12/3/2013 10:09:00 AM 3372 (0x0D2C)
    Setting authenticator TSManager 12/3/2013 10:09:00 AM 3372 (0x0D2C)
    Set authenticator in transport TSManager 12/3/2013 10:09:00 AM 3372 (0x0D2C)
    Sending StatusMessage TSManager 12/3/2013 10:09:00 AM 3372 (0x0D2C)
    Setting message signatures. TSManager 12/3/2013 10:09:00 AM 3372 (0x0D2C)
    Setting the authenticator. TSManager 12/3/2013 10:09:00 AM 3372 (0x0D2C)
    CLibSMSMessageWinHttpTransport::Send: URL: MP_server.company.com:80  CCM_POST /ccm_system/request TSManager 12/3/2013 10:09:00 AM 3372 (0x0D2C)
    Request was succesful. TSManager 12/3/2013 10:09:00 AM 3372 (0x0D2C)
    Set a global environment variable _SMSTSLastActionRetCode=-2147024895 TSManager 12/3/2013 10:09:00 AM 3372 (0x0D2C)
    Set a global environment variable _SMSTSLastActionSucceeded=false TSManager 12/3/2013 10:09:00 AM 3372 (0x0D2C)
    Clear local default environment TSManager 12/3/2013 10:09:00 AM 3372 (0x0D2C)
    Let the parent group (System Management Install) decides whether to continue execution TSManager 12/3/2013 10:09:00 AM 3372 (0x0D2C)
    The execution of the group (System Management Install) has failed and the execution has been aborted. An action failed.
    Operation aborted (Error: 80004004; Source: Windows) TSManager 12/3/2013 10:09:00 AM 3372 (0x0D2C)
    Failed to run the last action: HP Server Pack for ProLiant 2013.02. Execution of task sequence failed.
    Incorrect function. (Error: 80070001; Source: Windows) TSManager 12/3/2013 10:09:00 AM 3372 (0x0D2C)

    Tuesday, December 03, 2013 3:34 PM

Answers

  • "Installation completed with exit code 0x80070001"

    If it's not 0, its a failure -- this is a general industry standard that HP seems to buck for some unknown strange reason. If you are using a run command-line task, you can specify additional successful return codes. Alternatively, wrap the command-line in a batch file and have the batch file return 0.


    Jason | http://blog.configmgrftw.com

    • Marked as answer by C. Baum Monday, December 09, 2013 7:39 PM
    Tuesday, December 03, 2013 6:25 PM

All replies

  • "Installation completed with exit code 0x80070001"

    If it's not 0, its a failure -- this is a general industry standard that HP seems to buck for some unknown strange reason. If you are using a run command-line task, you can specify additional successful return codes. Alternatively, wrap the command-line in a batch file and have the batch file return 0.


    Jason | http://blog.configmgrftw.com

    • Marked as answer by C. Baum Monday, December 09, 2013 7:39 PM
    Tuesday, December 03, 2013 6:25 PM
  • Thanks Jason.  I took the existing command line and put it in a batch file ending with EXIT /B 0

    No more failure.  

    I still have the lingering/annoying "Waiting for job status notification" that I need to tackle.

    Monday, December 09, 2013 7:40 PM
  • I havent looked into the latest versions but HP did return status 1 as a sucessfull installation in earlier versions. 

    I did wrap the HP installer in a script that returned zero if it got return one from PSP. 

    THe right fix is naturally for HP to start returning the right returncodes from the begining

    Tuesday, December 10, 2013 9:51 AM
  • Hello Guys!

    HP ProLiant Support Pack / Service Pack uses different Exit Codes, due to that this software support other operating systems than Windows. Therefore HP has standardized to use other Exit Codes, which Windows Detect as failures.

    HPSum Exit Codes:
    ExitCode 1 = "Installation Successful"
    ExitCode 2 = "Installation Successful, but a reboot is required"
    ExitCode 3 = "Installation was canceled, or no components were updated"
    EcitCode 9009 = "Installation did not complete.  Check the path and make sure that the Installation exists at the specified location"

    HP recommends to use following Batch File to workaround this issue for SCCM:

    =======================START_BatchFile=============================
    :Init
      @Echo Off
      Cls
     
    :Main
      Echo HP Proliant Service Pack Setup
      Echo Source : %~dp0
      Echo ===============================================================================
      Echo Installing the HP Proliant Service Pack Setup
      Echo Command: "%~dp0hpsum.exe" /use_latest /target:%COMPUTERNAME% /force /Use_WMI /s
      "%~dp0hpsum.exe" /use_latest /target:%COMPUTERNAME% /force /Use_WMI /s

     
    :CheckForErrors
      Echo HP Proliant Service Pack Stauts:
      If "%errorlevel%"=="0" (
         Echo *******************************************************************************
      Echo                            INSTALLATION FAILED!
      Echo *******************************************************************************
      exit 1
      )
     
      If "%errorlevel%"=="1" (
         Echo Installation Successful!
         exit 0
      )
     
      If "%errorlevel%"=="2" (
         Echo Installation Successful, but a reboot is required.
         exit 3010
      )
     
      If "%errorlevel%"=="3" (
         Echo Installation was canceled, or no components were updated
         exit 0
      )
     
      If "%errorlevel%"=="9009" (
         Echo Installation did not complete.  Check the path and make sure that the
      Echo Installation exists at the specified location:
      Echo Path: %~dp0
      Exit 1
      )
     
    :End
      Echo An unknown status code was returned from the PSP.
      Echo This status code is [%errorlevel%].  This will be treated as a success,
      Echo but please check the installation to make sure it completedly properly!
      Exit 0

    =======================STOP_BatchFile=============================

    God Luck!


    Best Regards Anders Horgen


    Tuesday, January 21, 2014 8:26 AM