Prior to 3.10.0.1403 (?) if an app is running in a different user context than the setup, (i.e. app running under LocalServices) then the wix RestartManager code in src\libs\dutil\rmutil.cpp (::RmuAddProcessById) failed, which resulted in the setup doing a rollback, because OpenProcessToken did not have the appropriate privileges. See Wix bug 4592 and devs discussion here <http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/4592-RestartResource-solution-and-review-td7598149i20.html> . From your description I don't know if this is related to your situation.
In 3.10.0 if the setup is elevated, then the appropriate privilege is added so that the OpenProcessToken is successful. However if the setup is not elevated, and if OpenProcessToken fails (the instance of the application is in a different user context), then the attempt to register that instance is skipped (so that the setup does not fail). Calls to use the Restart Manager are 'best effort'. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Restart-Manager-failed-to-open-session-tp7599199p7599205.html Sent from the wix-users mailing list archive at Nabble.com. ------------------------------------------------------------------------------ Dive into the World of Parallel Programming. The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net/ _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
