Software Centre prompting for restart but cannot restart
Using SCCM 2012 SP1
Have pushed software to machines the user has initiated the install, the install completed but didn't prompt a restart, user rebooted machine. Now Software Centre is notifiying user for a restart, when you go to SC and click restart you get the following
error:-
and see this error in the RebootCoordinator.log
Attempted reboot without scheduling one first RebootCoordinator 26/02/2013 10:05:46 7532 (0x1D6C)
How do we get SC to acknowledge the restart and restart the machine?
February 26th, 2013 3:22pm
Just to clarify, what happens when you click OK to the above dialog? Does the system tray notification persist?
February 26th, 2013 9:43pm
Hi Jason
Yes it does, tried several manual restarts but still comes up no matter what. looking at the SCCM console the app that was installed has been marked as successful. Its happened on two machines, have installed the same app on several others without an issue.
not sure if its a bug in the sccm client or something specific to those 2 machines. but need to figure it out before deploying to over 500 machines.
thanks
February 26th, 2013 10:39pm
Hi Cumbrianblues,
can you check if any update installtion is still runing?
Has had an simmilar problem, an mandatory update was running but Softwarecenter has not shown to me, after i have hit the F5 button the update appears and after this update has been installed the restart works.
February 26th, 2013 11:54pm
If that doesn't work, I suggest you contact CSS or use connect to file a bug.
February 27th, 2013 12:26am
Its not an update but an application install for the device, which is updating a previous version of the software if it is present - like I said this has installed and is working on both devices.
The application shows up in the Installation Status Tab in Software Centre and on the Installed Software Tab. However on the Installation Status tab it is prompting for the restart, and we are getting a notifications in the taskbar too. Neither option
lets us restart the machine which is when we get the error posted in the original post.
Its as if its missed the transition from 'installing' to 'installed'
February 27th, 2013 12:57am
with a bit more digging i think i may have uncovered part of the issue - in the AppEnforce.log I've come accross the following error:
Unmatched exit code (1073807364) is considered an execution failure.
This is the same for both machines that have the restart issue. Yet the application is installed and working.
Do you think a manual install of the msi, outside of SCCM will work?
February 27th, 2013 2:49pm
figured this one out, we added the exit code from the logs into the return codes as soft reboot, re ran it and it picked up that it needed a reboot.
September 6th, 2013 4:43am