TSSA/BBSA: Windows Deploy Job fails to reboot, reports "Reboot required but did not occur. Manual reboot needed to complete operation, exitCode = -4003"

Version 5
    Share This:

    This document contains official content from the BMC Software Knowledge Base. It is automatically updated when the knowledge article is modified.


    TrueSight Server Automation Suite


    TrueSight Server Patch Management


    BMC BladeLogic Server Automation Suite



    in TrueSight Server Automation (TSSA) a Windows Deploy Job fails to reboot the target server, with the following traces found in the bldeploy log on the target:


    [date] 01:23:52.886 INFO     bldeploy - Attempting shutdown REBOOT=true TIMEOUT=0 MSG=System is rebooting
    [date] 01:24:52.902 DEBUG    bldeploy - Metabase initialization skipped because it was not needed
    [date] 01:24:52.902 INFO     bldeploy - Apply Succeeded
    [date] 01:24:52.917 WARN     bldeploy - Reboot required but did not occur. Manual reboot needed to complete operation.


    Below is the Exit Code in the Job run log :

    Info 03/18/2019 15:16:10 Bldeploy done - nRet = 11 (Apply partially successful with failed items, overall job phase failure) exitCode = -4003 (Deployment failed and requires manual reboot)
    (Time in agent's deploy log:: 03/18/2019 15:16:02)
    Warning 03/18/2019 15:16:10 Deploy partially succeed with failure items. Preserve on failure not enabled; cleaning up staging area. 
    (Time in agent's deploy log:: 03/18/2019 15:16:01)
    Warning 03/18/2019 15:16:10 Reboot required but did not occur. Manual reboot needed to complete operation. 
    (Time in agent's deploy log:: 03/18/2019 15:16:01)



    The reboot request was not allowed by the Operating System.



    Legacy ID:KA372192


    Please check the bldeploy logs from <RSCD_Install_Folder>/Transactions/log/bldeploy*.log. 
    The bldeploy logs should have a more-detailed error why the reboot was not allowed.

    Below are two examples of such errors from the bldeploy log :

     ******************** Example 1 *********************************
    05/30/19 11:41:39.765 ERROR    bldeploy - Auto-reboot unable to initiate reboot, please reboot manually. Error code:1115 A system shutdown is in progress. 

    This is an OS error and following is the reason of this error :

    The 1115 error may be caused by windows system files damage. The corrupted windows system files entries can be a real threat to the well being of your computer.

    There can be many events which may have resulted in the system files errors. An incomplete installation, an incomplete uninstall, improper deletion of applications or hardware. It can also be caused if your computer is recovered from a virus or adware/spyware attack or by an improper shutdown of the computer. All the above actives may result in the deletion or corruption of the entries in the windows registry. This corrupted registry will lead to the missing and wrongly linked information and files needed for the proper working of the application.

    ********************* Example 2 *********************************

      07/16/19 18:56:06.239 ERROR    bldeploy - Auto-reboot unable to initiate reboot, please reboot manually. Error code:1717 The interface is unknown.
      From the post below it seems that this is a permission issue :


    If the root cause is not clear and further assistance is required, please create a case with BMC Customer Support and provide the following details :

    1) The rscd.log, bltargetjobmanager*.log and bldeploy*.log from the target server.
    2) Application server logs from all the application servers covering the time of the failed job run.
    3) Job run logs exported from TSSA Console.
    4) Windows Event logs from the target server at the time of the error.
    5) Windows Update Log from the target server.



    Article Number:


    Article Type:

    Solutions to a Product Problem

      Looking for additional information?    Search BMC Support  or  Browse Knowledge Articles