Normally if the component was already installed the "Installed:" part of the spew would read Local, not Absent.
Does your component use either Side-by-Side or GAC? There are known issues with upgrades when RemoveExistingProducts is sequenced "too early" for Windows Installer's interface to those technologies (fusion). You are sure this is a major upgrade. The ProductCodes are different between the two packages, correct? -----Original Message----- From: Wilson, Phil [mailto:phil.wil...@wonderware.com] Sent: Tuesday, September 01, 2009 3:18 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Understanding component states I read that to mean that the component is already installed and doesn't need updating from your new setup, perhaps because the versions are identical. Your RemoveExistingProducts is probably sequenced to run at the end of your install, so it's applying update rules. In some cases you might see a message something like "{guid} will not be installed because the same or a higher-versioned keyfile is already installed", the same situation. Phil Wilson -----Original Message----- From: Don Pratt [mailto:don.pr...@cox.net] Sent: Tuesday, September 01, 2009 1:35 PM To: General discussion for Windows Installer XML toolset. Subject: [WiX-users] Understanding component states Hi, I'm having trouble understanding why one component is failing to get installed. I'm doing a major upgrade, and this component exists in both the old and new versions of my package. If I manually uninstall the old version and then do a normal install of the new version, the problem component does get installed. Looking in an MSI log, during the InstallValidate action I see: MSI (s) (C4:94) [15:51:13:079]: Component: SPCControls_dll; Installed: Absent; Request: Local; Action: Null I have a relatively simple installer with a single feature that contains everything. This component doesn't have any conditions. I dark'ed this MSI and our previous MSI (which handles a major upgrade just fine) and they both show identical markup for the component in question. None of the other components seem to have problems. What else should I look for to understand why the action for this component is getting set to 'Null'? Thanks, Don Pratt ---------------------------------------------------------------------------- -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users ---------------------------------------------------------------------------- -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
