You should be able to use "msiexec /fv [original.msi]" to recache the source although it would also run a repair of the installation.
The root of the problem is the missing cached MSI. You need to fix that to be able to uninstall as otherwise Windows Installer has no idea what to actually uninstall when your RemoveExistingProducts is scheduled. I've seen this happen when users run disk cleanup/space recovery programs. Some of the extremely badly written ones delete the MSI's cached by Windows Installer because they assume they know better than the Windows Installer team. Palbinder Sandher Software Deployment & IT Administrator 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: Tim Haloun [mailto:thal...@google.com] Sent: 27 January 2011 20:08 To: wix-users@lists.sourceforge.net Subject: [WiX-users] Error 1612 in RemoveExistingProducts Prevents Upgradesor Uninstalls Hi, A small proportion of our users are reporting the following failure. Unfortunately as far as I can tell it is a terminal situation so the proportion is likely to simply grow. The full msiexec logs contain these lines: Action start 15:23:53: RemoveExistingProducts. MSI (s) (14:68) [15:23:54:464]: Product: <PRODUCT> -- Error 1714. The older version of <PRODUCT> cannot be removed. Contact your technical support group. System Error 1612. Error 1714. The older version of <PRODUCT> cannot be removed. Contact your technical support group. System Error 1612. Action ended 15:23:54: RemoveExistingProducts. Return value 3. Action ended 15:23:54: INSTALL. Return value 3. Error 1612 means "The installation source for this product is not available". I'm trying to understand what that means. I thought that the windows installer system cached all msis somewhere so that they could be run when the user wants to uninstall? Or, could an individual keypath element be missing or missing read permissions? Is there documentaion explaining the causes or workarounds for this state? If I could even find manual steps to remove my product from the list of installed programs so that a new installation overwrote and replaced any missing "installation source", that would be good enough. Several cleanup tools for removing orphaned installs like that existed, but this is not really their intended use. Thanks! Tim ------------------------------------------------------------------------ ------ Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)! Finally, a world-class log management solution at an even better price-free! Download using promo code Free_Logger_4_Dev2Dev. Offer expires February 28th, so secure your free ArcSight Logger TODAY! http://p.sf.net/sfu/arcsight-sfd2d _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users ------------------------------------------------------------------------------ Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)! Finally, a world-class log management solution at an even better price-free! Download using promo code Free_Logger_4_Dev2Dev. Offer expires February 28th, so secure your free ArcSight Logger TODAY! http://p.sf.net/sfu/arcsight-sfd2d _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
