Comparing the component GUIDs in the original (broken 3.0 MSI) against the same version MSI built with 3.5 shows that the hard-coded GUIDs are the same, no surprise there. Now, the heat generated component GUIDs are different, these use the "*".
I am not sure why this would be? I am building the MSI at my desk versus our build server so the build paths might be different, however the component paths (where the files go on the system) are identical. Either way, these are just file components and although messy, should not be causing me any problems when I attempt to install my new version of the product after the uninstall. However, when performing the uninstall against the updated cache DB, even the components with the *same* GUID are not being removed either. I don't understand why this would be, unless the package GUID somehow plays a role here? I don't see the package GUID defined in any of the tables. Where do I find this so that I can make the package GUID in my replacement MSI the same? This is all assuming the package GUID has anything to do with the issue I am seeing. Thanks. On Thu, Aug 30, 2012 at 10: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
