none
Task Sequence Failed 16389

    Question

  • I have a task sequence that although it says it failed seems to have ran the command line successfully. When I check in Software Center where it states failed and click on more information it shows "task sequence Error: 0x4005(16389)". The task sequence runs wusa to uninstall a Windows Update which then forces a restart. It looks like it uninstalled the update but on over a hundred machines it has "failed".

    In deployment status it shows error and desciption is "The task sequence manager could not successfully complete execution of the task sequence".

    The execmgr.log shows Execution is complete for program *. The exit code is 0, the execution status is Success.

    I have smsts.log below and it even says the requested operation completed successfully. Could it have something to do with the command line forcing a restart? If so is there something I could do so that the TS doesn't think it failed?

    Here is smsts.log:

    Expand a string: WinPEandFullOS TSManager 12/30/2014 10:00:07 PM 6244 (0x1864)
    Executing command line: smsswd.exe /run: wusa /uninstall /kb:3008923 /quiet /forcerestart TSManager 12/30/2014 10:00:07 PM 6244 (0x1864)
    [ smsswd.exe ] InstallSoftware 12/30/2014 10:00:08 PM 9680 (0x25D0)
    PackageID = '' InstallSoftware 12/30/2014 10:00:08 PM 9680 (0x25D0)
    BaseVar = '', ContinueOnError='' InstallSoftware 12/30/2014 10:00:08 PM 9680 (0x25D0)
    ProgramName = 'wusa /uninstall /kb:3008923 /quiet /forcerestart' InstallSoftware 12/30/2014 10:00:08 PM 9680 (0x25D0)
    SwdAction = '0001' InstallSoftware 12/30/2014 10:00:08 PM 9680 (0x25D0)
    Working dir 'not set' InstallSoftware 12/30/2014 10:00:08 PM 9680 (0x25D0)
    Executing command line: Run command line InstallSoftware 12/30/2014 10:00:08 PM 9680 (0x25D0)
    Process completed with exit code 1641 InstallSoftware 12/30/2014 10:01:10 PM 9680 (0x25D0)
    Command line returned 1641 InstallSoftware 12/30/2014 10:01:10 PM 9680 (0x25D0)
    Process completed with exit code 1641 TSManager 12/30/2014 10:01:10 PM 6244 (0x1864)
    !--------------------------------------------------------------------------------------------! TSManager 12/30/2014 10:01:10 PM 6244 (0x1864)
    Failed to run the action: Run Command Line.
    The requested operation completed successfully. The system will be restarted so the changes can take effect. (Error: 00000669; Source: Windows) TSManager 12/30/2014 10:01:10 PM 6244 (0x1864)
    Set authenticator in transport TSManager 12/30/2014 10:01:10 PM 6244 (0x1864)
    Set a global environment variable _SMSTSLastActionRetCode=1641 TSManager 12/30/2014 10:01:10 PM 6244 (0x1864)
    Set a global environment variable _SMSTSLastActionSucceeded=false TSManager 12/30/2014 10:01:10 PM 6244 (0x1864)
    Clear local default environment TSManager 12/30/2014 10:01:10 PM 6244 (0x1864)
    Failed to run the action: Run Command Line. Execution has been aborted TSManager 12/30/2014 10:01:10 PM 6244 (0x1864)
    Set authenticator in transport TSManager 12/30/2014 10:01:10 PM 6244 (0x1864)
    Failed to run the last action: Run Command Line. Execution of task sequence failed.
    The requested operation completed successfully. The system will be restarted so the changes can take effect. (Error: 00000669; Source: Windows) TSManager 12/30/2014 10:01:11 PM 6244 (0x1864)
    Set authenticator in transport TSManager 12/30/2014 10:01:11 PM 6244 (0x1864)
    Task Sequence Engine failed! Code: enExecutionFail TSManager 12/30/2014 10:01:11 PM 6244 (0x1864)
    **************************************************************************** TSManager 12/30/2014 10:01:11 PM 6244 (0x1864)
    Task sequence execution failed with error code 80004005 TSManager 12/30/2014 10:01:11 PM 6244 (0x1864)
    Cleaning Up. TSManager 12/30/2014 10:01:11 PM 6244 (0x1864)
    Removing Authenticator TSManager 12/30/2014 10:01:11 PM 6244 (0x1864)
    Cleaning up task sequence folder TSManager 12/30/2014 10:01:11 PM 6244 (0x1864)
    File "E:\_SMSTaskSequence\TSEnv.dat" does not exist. (Code 0x80070002) TSManager 12/30/2014 10:01:11 PM 6244 (0x1864)
    Deleting volume ID file C:\_SMSTSVolumeID.7159644d-f741-45d5-ab29-0ad8aa4771ca ... TSManager 12/30/2014 10:01:11 PM 6244 (0x1864)
    Deleting volume ID file E:\_SMSTSVolumeID.7159644d-f741-45d5-ab29-0ad8aa4771ca ... TSManager 12/30/2014 10:01:11 PM 6244 (0x1864)
    Successfully unregistered Task Sequencing Environment COM Interface. TSManager 12/30/2014 10:01:11 PM 6244 (0x1864)
    Executing command line: "C:\Windows\CCM\TsProgressUI.exe" /Unregister TSManager 12/30/2014 10:01:11 PM 6244 (0x1864)
    ==========[ TsProgressUI started in process 12804 ]========== TsProgressUI 12/30/2014 10:01:11 PM 11912 (0x2E88)
    Unregistering COM classes TsProgressUI 12/30/2014 10:01:11 PM 11912 (0x2E88)
    Shutdown complete. TsProgressUI 12/30/2014 10:01:11 PM 11912 (0x2E88)
    Process completed with exit code 0 TSManager 12/30/2014 10:01:11 PM 6244 (0x1864)
    Successfully unregistered TS Progress UI. TSManager 12/30/2014 10:01:11 PM 6244 (0x1864)
    Start to cleanup TS policy TSManager 12/30/2014 10:01:12 PM 6244 (0x1864)
    End TS policy cleanup TSManager 12/30/2014 10:01:14 PM 6244 (0x1864)
    RegQueryValueExW is unsuccessful for Software\Microsoft\SMS\Task Sequence, SMSTSEndProgram TSManager 12/30/2014 10:01:14 PM 6244 (0x1864)
    GetTsRegValue() is unsuccessful. 0x80070002. TSManager 12/30/2014 10:01:14 PM 6244 (0x1864)
    End program:  TSManager 12/30/2014 10:01:14 PM 6244 (0x1864)
    Error executing Task Sequence Manager service. Code 0x80004005 TSManager 12/30/2014 10:01:14 PM 6244 (0x1864)
    Sending error status message TSManager 12/30/2014 10:01:14 PM 6244 (0x1864)
    Set authenticator in transport TSManager 12/30/2014 10:01:14 PM 6244 (0x1864)

    Wednesday, December 31, 2014 12:48 PM

Answers

  • Additionally I would replace /forcerestart with /norestart to make sure no restart is performed :)
    Wednesday, December 31, 2014 12:59 PM
  • Your WUSA command line has the /forcerestart option.  So, WUSA is handling the restart and not the task sequence.  If the task sequence does not handle the restart, it will fail.  Try moving the restart from the WUSA command line to a step in the task sequence.

    Jeff

    • Proposed as answer by MK-Maddin Wednesday, December 31, 2014 12:58 PM
    • Marked as answer by Joyce LModerator Monday, January 5, 2015 6:40 AM
    Wednesday, December 31, 2014 12:54 PM

All replies

  • Your WUSA command line has the /forcerestart option.  So, WUSA is handling the restart and not the task sequence.  If the task sequence does not handle the restart, it will fail.  Try moving the restart from the WUSA command line to a step in the task sequence.

    Jeff

    • Proposed as answer by MK-Maddin Wednesday, December 31, 2014 12:58 PM
    • Marked as answer by Joyce LModerator Monday, January 5, 2015 6:40 AM
    Wednesday, December 31, 2014 12:54 PM
  • Additionally I would replace /forcerestart with /norestart to make sure no restart is performed :)
    Wednesday, December 31, 2014 12:59 PM
  • Just wanted to chime in here. Having the /forcerestart option will definitely cause it to fail.

    BUT, in every task sequence deployment that I have deployed this update in, it has caused the task sequence to fail. The issue is that this update should call a restart after it installs but it does not. When it installs and the task sequence subsequently fails, the log will show it installed but no reboot log entry.

    Just in case anyone else comes along to this issue, this update should be a separate step in the task sequence:

    KB3008923

    Thursday, January 29, 2015 10:03 PM