This is the problem that a single transaction over multiple MSI installs can solve. At the risk of stating the obvious, the transaction (a.msi+b.msi) is not committed until b.msi is successful. The failure of b.msi will roll back b.msi AND a.msi, and the rollback of a.msi will reinstall the older version of a.msi. A rollback of a major upgrade will reinstall the previous product because RemoveExistingProducts will be rolled back if it is part of the transaction (between InstallInitialize and InstallFinalize). As I say, I don't know if Burn supports multiple MSI single transaction installs.
Phil -----Original Message----- From: Simon Fogliato [mailto:sfogli...@deltacontrols.com] Sent: Wednesday, June 26, 2013 3:01 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Bootstrapper multiple MSI's don't rollback to a working installed state You are correct this is how it is currently working in WiX 3.7 and this is my problem. The MSI that fails (b.msi) does rollback correctly, my issue is that the installed files of a.msi are lost until I manually repair the previous bootstrapper version from add/remove programs. A RollbackBoundary only makes the problem worse because then I have 2 bootstrapper installed listed applications that are not completely installed over 1. To my knowledge the bootstrapper just doesn't do a complete multiple MSI rollback. -----Original Message----- From: Nick Ramirez [mailto:nickra...@hotmail.com] Sent: Wednesday, June 26, 2013 12:42 PM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Bootstrapper multiple MSI's don't rollback to a working installed state The MajorUpgrade schedule is important for the MSI that failed. If an MSI will be rolled back, having the original MSI reinstalled is dependent on the MajorUpgrade element. On the other hand, the first MSI, which installed fully, will not roll back. At best, when the Chain fails, it will probably just be uninstalled. I am thinking that right after it was installed, the old A.msi was removed from the Package Cache (replaced by the upgraded A.msi). So, I'm not sure that Burn will support reinstalling the older, replaced package. I'm guessing, this is the problem: - MSI A installs sucessfully - MSI B fails midway through, triggers rollback of itself and the chain - MSI B is rolled back and its older version is reinstalled (if MajorUpgrade is set up to do this) - MSI A is uninstalled <-- and that's where it ends Someone with more insight regarding how major upgrades and rollbacks work could probably say if this is how it works. But I think it has to do with not keeping the old package in the cache and not having a mechanism to resurrect it. You could add Rollback Boundaries to not uninstall A.msi, but that may not be the behavior you want. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Bootstrapper-m ultiple-MSI-s-don-t-rollback-to-a-working-installed-state-tp7586867p7586885. html Sent from the wix-users mailing list archive at Nabble.com. ---------------------------------------------------------------------------- -- This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users ---------------------------------------------------------------------------- -- This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users ------------------------------------------------------------------------------ This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
