You may be able to use some combination of MSIRMSHUTDOWN and MSIRESTARTMANAGERCONTROL to get the result you want. Having said that, you seem to be saying that MSI/RM is already scheduling a reboot if it doesn't shut things down properly, but that seems to be the problem you're trying to solve, so perhaps you could clarify why you seem to want to do what is already happening anyway. It's definitely worth investigating why those processes won't shut down nicely, and if they can integrate with RM and preserve their internal state.
The ReplacedInUseFiles property might be what you need as an indication that a reboot is needed. I believe that when there is no UI the ScheduleReboot action does a reboot without asking (it is silent, after all) so a verbose log might be useful in the case that it appears a reboot is needed but doesn't happen. --------------- Phil Wilson On Sat, Feb 15, 2014 at 12:03 PM, Suryadeep Biswal <[email protected]> wrote: > Hi, > I need some help with coordinating a system reboot with specific restart > manager error codes during a major upgrade of a MSI.To be more specific - 1. > Suppose "A.dll", a binary which is installed by the MSI (and is upgraded by > higher versions) is loaded into memory by several processes.2. While > performing a major upgrade to a MSI which contains a higher version of A.dll, > Restart manager tries to shutdown and restart all these processes. In some > cases I have seen this failing and a message from RM in the installation logs > stating that a reboot is needed. we are investigate the cause for these > failures but from what i have read, it can be happen for cases where the > process running on a different session or under a different user credential. > What i would ideally like is to schedule a reboot in case restart manager > fails to shut down all the processes that are using any dll which is being > replaced. If there was a MSI property indicating the return code of Restart > Manager shutdown action, i could have simply used it, but i could not find > any such property. My goal is to avoid unnecessary reboots (thus discarding > the solution of reboot always). Is there a way to do it without duplicating > the Installer - Restart manager interaction code (in which case i can write > the error code into a WIX property)? > Please note that this is a silent upgrade and there are no UIs. Thanks for > any advice! > Regards,Surya > ------------------------------------------------------------------------------ > Android apps run on BlackBerry 10 > Introducing the new BlackBerry 10.2.1 Runtime for Android apps. > Now with support for Jelly Bean, Bluetooth, Mapview and more. > Get your Android app in front of a whole new audience. Start now. > http://pubads.g.doubleclick.net/gampad/clk?id=124407151&iu=/4140/ostg.clktrk > _______________________________________________ > WiX-users mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/wix-users ------------------------------------------------------------------------------ Managing the Performance of Cloud-Based Applications Take advantage of what the Cloud has to offer - Avoid Common Pitfalls. Read the Whitepaper. http://pubads.g.doubleclick.net/gampad/clk?id=121054471&iu=/4140/ostg.clktrk _______________________________________________ WiX-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wix-users
