Rob, I am not doing a minor upgrade, this product follows a major upgrade life cycle. Ultimately, I want to do a major upgrade, however from the original WiX 3.0 MSI the upgrade fails because of the bug with the IISExtension. The uninstall also fails. Hence, my attempt to replace the cached DB with an MSI built against WiX 3.5 (which seems to have fixed the IISExtension issue).
I compared some test builds of 3.0 against 3.5 and the GUIDs are the same, however they are different than the GUIDs from the original 3.0 MSIs generated on our build server. Not sure why this is... historically, I have compared the 3.0 builds from our build server and all the GUIDs match. My next step was to try the hack of using the IISExtension from 3.5 with a 3.0 generated cache-replacement MSI. In general, what might the reason be that the replacement MSI is not uninstalling the components with properly maintained GUIDs? Is this some sublety between WiX 3.0 and 3.5 that might be causing issues? There are no other changes. Thanks. On Thu, Aug 30, 2012 at 11:23 AM, Rob Mensching <r...@robmensching.com>wrote: > First try this: > > http://robmensching.com/blog/posts/2007/1/4/Doing-a-small-update-or-minor-upgrade-in-MSI-Use > > That will point out if your minor upgrade is breaking component rules. > > "*" GUIDs in Components are supposed to make stable GUIDs. However, it is > posible (I forget, it was a long time ago) that there was a fix in the GUID > generation across WiX v3.0 to WiX v3.5. In general, when you upgrade WiX > toolset versions, you need to do major upgrade MSIs. There are too many > subtle things that must stay the same that are not always possible to keep > static when fixing bugs. > > I know that's not what you want to hear but at least we'll understand the > problem. The next best thing may be to try to build your MSI using WiX > v3.0 but with the WiX v3.5 IIS extension. That's not technically supported > either but it *may* work out. > > On Thu, Aug 30, 2012 at 7:09 AM, Andy Clugston <clug...@gmail.com> wrote: > > > Well, like I said I am using "*" for the components that allow for it for > > better automation. My impression (I did a lot of research before using > "*" > > to make sure I would not have any issues in the future, asked on the > > mailing list, etc.) was that "*" should work in all cases as long as the > > component paths (however WiX determines this) did not change. So, in this > > case the MSI is identical other than it being built with 3.0 versus 3.5. > > > > Is this a corner case that no one considered? > > > > My issue with the install after the removal is due to the components > being > > left on the system. I can see this from the verbose log. > > > > Thanks. > > > > On Thu, Aug 30, 2012 at 9:23 AM, Pally Sandher <pally.sand...@iesve.com > > >wrote: > > > > > Sounds like your Component GUIDs are different & thus you've broken the > > > Component Rules -> > > > http://robmensching.com/blog/posts/2003/10/18/Component-Rules-101 > > > > > > Palbinder Sandher > > > Software Platform Engineer > > > T: +44 (0) 141 945 8500 > > > F: +44 (0) 141 945 8501 > > > http://www.iesve.com > > > > > > **Design, Simulate + Innovate with the <Virtual Environment>** > > > Integrated Environmental Solutions Limited. Registered in Scotland No. > > > SC151456 > > > Registered Office - Helix Building, West Of Scotland Science Park, > > Glasgow > > > G20 0SP > > > Email Disclaimer > > > > > > > > > > > > -----Original Message----- > > > From: Andy Clugston [mailto:clug...@gmail.com] > > > Sent: 30 August 2012 12:57 > > > To: General discussion for Windows Installer XML toolset. > > > Subject: [WiX-users] Replacing Cached MSI DB > > > > > > Due to an issue with the IISExtension and how it handles certs in WiX > 3.0 > > > we are unable to uninstall/upgrade our product (see other recent > issues I > > > have been asking about). I have attempted to create a substitute MSI DB > > to > > > replace the cached DB file per Rob's recommendations here: > > > > > > > > > > > > http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Possible-to-force-an-uninstall-and-ignore-errors-td6029032.html > > > > > > The substitute DB is built with WiX 3.5, the original was built with > WiX > > > 3.0. The thought here was that since the cert uninstall issue seems to > be > > > resolved in 3.5, this would allow the product to be uninstalled. > > > > > > The cache is updated, and the product can then be uninstalled. However, > > > when running the uninstall although it cleans itself out of ARP, all of > > the > > > components appear to be left on the system. The new DB file has the > same > > > product GUID, Upgrade GUID, version, and product/MSI name, however the > > > package GUID is different (which I don't think matters). For component > > GUID > > > generation, I am using "*" (where applicable), not sure if this matters > > in > > > this case, just wanted to mention it. > > > > > > When I then attempt to install a major upgrade release of a later > version > > > of the product, the install fails (1603). The only thing that I see in > > the > > > (non-verbose) log is "RemoveFiles. Return value 0", otherwise it looks > > > okay. I am going to rerun the test with verbose logging. > > > > > > So, two questions, is the way I regenerated the updated cache DB > > accurate, > > > and if so, why does it not uninstall the components? > > > > > > Second, even with the components left on the system, should the new > major > > > version release install not just overwrite everything and install > > > successfully? > > > > > > Thanks. > > > > > > > > > ------------------------------------------------------------------------------ > > > 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 > > > > > > > > > > > > > > > > > > ------------------------------------------------------------------------------ > > > 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 > > > > > > > > ------------------------------------------------------------------------------ > > 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 > > > > ------------------------------------------------------------------------------ > 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 > ------------------------------------------------------------------------------ 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
