Im not that used to work with the SCCM so i just wanna see if this is a common issue.

A package needs to be installed asap on a client, i added the client as a direct membership rule to speed things up (ad-sync takes forever). Gave it a few minutes then checked the log, everything seemed raised the adv for install and yada yada yada....then nothing happens and the last thing in the log is: "spRebootRequest->JobStart failed 0x80004005", though it's a no brainer that a reboot surely would solve my problem i cant do it beacuse the user has left her computer with jobs unsaved...
The package had been downloaded localy so i tried rerun adv in client center and then the log went banans, every second it raises the installadv and ends with that spRebootRequest fail.
Execmgr log:
spRebootRequest->JobStart failed 0x80004005
Execution Request for package C11005D0 program CiscoHistoricalReportClient install state change from Ready to Ready
Persisting request for program CiscoHistoricalReportClient install package C11005D0 in state Ready
CExecutionRequest::Overriding Service Windows as per policy.
CExecutionRequest::EnterRsRuningState CiscoHistoricalReportClient install
Executing program msiexec.exe /qn /i "CiscoCCX.msi" ALLUSERS=2 /le "%systemdrive%\loggar\CiscoHistoricalReportClient_7.0.log" /m OTSOPNI in Admin context
spRebootRequest->JobStart failed 0x80004005

Is it another job that needs a reboot and makes my action obsolete until the client acctually is rebooted?
And no my package has no "ConfigMgr restarts client" or anything like that.
Googled it and found simular problem:

This will surely be solved before i get an answer(The user contacts me and i tell her to reboot client)...but still interesting to learn from the experts ^^
Answer Summary:
0 Comments   [ + ] Show Comments


Please log in to comment

Community Chosen Answer

We had a similar issue with SCCM 2007 Clients on WinXP SP2. There was a WMI problem preventing the Client from running spRebootRequest. Once we updated the Clients to SP3, this WMI issue was resolved. It doesn't happen on every XP SP2 machine though. It was very strange behavior. I hope this helps.
Answered 03/26/2012 by: Trinity
Brown Belt

  • Okey, that can acctually be the answer at that place, but its not my problem :)
Please log in to comment


Client rebooted and package installed fine (ofc)
Answered 03/26/2012 by: asman
Purple Belt

Please log in to comment
Answer this question or Comment on this question for clarity