Thanks Ranganatha. The attribute column shows 0 for virtually all of my components, but that got me digging more in my MSI. I think I've found the problem.
The DLL in question uses auto-generated values for build and revision pieces of the version number. Bad idea! We don't generally recompile this file since it rarely changes. However, it got recompiled this time (I probably did a "Rebuild Solution" instead of "Build Solution") and ended up with a smaller value in the third piece of the version number. So during component state evaluation, windows installer saw that it should not use the version from my new MSI, but RemoveExistingProducts still removed it resulting in a missing file. I'll update this DLL to use fixed values for the major, minor, and build pieces of the version number. I'll also make sure the rest of our DLLs and EXEs do the same so we don't run into this problem again. Regards, Don Ranganatha H C wrote: > Hi, > > What is there for your component causing issues in Attribute column in > Component table . (You can use ORCA to see the table content in MSI) > > The below link may help. > http://msdn.microsoft.com/hi-in/library/aa368007(en-us,VS.85).aspx<http://msdn.microsoft.com/hi-in/library/aa368007%28en-us,VS.85%29.aspx> > > > Ranganatha > > > On Wed, Sep 2, 2009 at 4:55 AM, Don Pratt <don.pr...@cox.net> wrote: > > >> Thanks Blair and Phil. >> >> We sequence RemoveExistingProducts before InstallInitialize, but do not >> use Side-by-Side or GAC. >> >> I'm pretty sure we're doing major upgrade correctly. We keep the >> UpgradeCode constant and put in a new ProductCode for each new version. >> We let WiX auto-gen the PackageCode. >> >> One thing I should have mentioned to start with is that this isn't the >> first major upgrade we've done for this product. Upgrade from v11.2.0 >> to 11.2.1 works fine. Upgrade from 11.2.x to 11.2.2 (the current >> release) ends up dropping this one file. >> >> Thanks again for the help. I know trying to troubleshoot remotely can >> be tricky. If there are other pieces of the log file or our WiX source >> that would be helpful, just let me know. >> >> Don >> >> Blair wrote: >> >>> 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 >>> >>> >>> >> ------------------------------------------------------------------------------ >> 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
