On 22-May-12 08:22, Pally Sandher wrote: > On a machine which has an existing v2.0 or later MSI installation, the MSP > should be applied to update to v2.2 > On a machine which has nothing installed, v2.2 should be installed > On a machine which has an existing installation older than v2.0 a Major > Upgrade should be applied to update to v2.2 > > The above scenarios all work when manually executing the relevant MSI or MSP& > show the expected errors when attempted outside of those conditions. When you say "v2.2 should be installed," you mean, v2.0 should be installed and then patched to v2.2, right?
The second case (fresh v2.0 plus slipstreamed patch) appears to be hung inside MSI (or at least there's nothing in the MSI log to indicate progress). On the third case (major upgrade plus patch), I suspect it's failing because MSI doesn't support it. The logs look like MSI is trying to apply the patch to the v1.4 installed product instead of slipstreamed to the v2.0 product. It's not clear that MSI supports applying a major upgrade with a slipstreamed patch view applied. Please try the following on a machine with and without v1.4 installed and upload the logs. msiexec /l*vx! /i VESharedContent.msi ALLUSERS="1" MSIFASTINSTALL="7" PATCH="VESharedContent.msp" That's equivalent to what Burn is doing in both cases. -- sig://boB http://joyofsetup.com/ ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
