What do you have in your deploy job, Job Options tab under reboot options selected?
Configuration => Patch Global Configuration => Windows => Patch deploy reboot return codes
On the target navigate to <RSCD_DIR>\Transcations\log
Attach the bldeploy*.log and bltargetjobmanager*.log for the job where you got the 3010
I've tried every options.
- is 3010 set as a success code in the patch global config?
- please attach the bldeploy log from a deploy where you think the reboot should have happened and you are getting 3010 exit codes.
Please find attached screens.
I try many options.
The problem is than I see in logs
"05/06/15 12:40:06.228 DEBUG bldeploy - [Windows6.1-2008-R2-SP1-KB2900986-x64.msu-MS13-090-en-WINDOWS SERVER 2008 R2 DATACENTER (X64)-SP1] In RunProcess: exitCode = 3010
"Reboot request made based on the return code from command (3010)"
But nothing happened.
And reboot occurs at the end of job. Job failed (red icon). But patch analysis after all shows that all patches have been installed.
Lack of logic?
i think you should not have the 'use item defined reboot' setting - just reboot at the end of job ?
also - can you attach the bldeploy log ?
What I need to archive?
- deploy all require patches
- when reboot is require then box is rebooted, doesn't matter when and how many times (I have more than 50 hot-fixes)
- when all patches have been deployed despite reboot (or not) I expect exit as should be (not failed).
Please also attach bltargetjobmanager log for the same deploy job as the the bldeploy log you already attached
the job is failing because of failed patch installs:
05/06/15 12:56:01.781 ERROR bldeploy - [Windows6.1-2008R2-KB2705219-v2-x64.msu-MS12-054-en-WINDOWS SERVER 2008 R2 DATACENTER (X64)-SP1] Command returned non-zero exit code: 2359302
you need to lookup on the vendor's site why that patch install would throw that exit code.
i don't think there is an issue w/ the reboot settings.
And exit code 2359302 means than patch has been already installed but but box need to be rebooted. And reboot haven't occurred.
And I think this is a reboot settings issue.
I need holistic approach of Job Options/Phase Options in File Deploy Job.
Please attach bltargetjobmanager log for the same deploy job as the the bldeploy log you already attached
1 of 1 people found this helpful
where do you see that it has anything to do w/ a reboot?
2359302 is 0x00240006 in hex.
according to microsoft that means:
0x00240006 WU_S_ALREADY_INSTALLED The update to be installed is already installed on the system
i don't see any mention of needing a reboot. if the patch is already installed perhaps you need to add that exit code as one of the success return codes. that should stop it being seen as an error.