Features selected for reinstall, but components are not reinstalled?
![Rich [Microsoft Windows Installer MVP]'s profile photo](https://lh3.googleusercontent.com/a/default-user=s40-c)
Rich [Microsoft Windows Installer MVP]
We are attempting to create a minor upgrade package for our product.
The relevant codes for the original package and upgrade package are:
version 136c:
PackageCode {15BA0955-92F5-44A7-A365-1BF033C7B5C3}
ProductCode {2B8C6061-F2E5-4C97-AD93-16F31968AE50}
ProductVersion 8.00.0000
UpgradeCode {4D7C4448-B8FE-4010-9677-83D9335BE16A}
version 160:
PackageCode {63B3E278-E29D-4BA1-92CC-2015C60239EB}
ProductCode {2B8C6061-F2E5-4C97-AD93-16F31968AE50}
ProductVersion 8.00.0001
UpgradeCode {4D7C4448-B8FE-4010-9677-83D9335BE16A}
Our Upgrade table is empty; I'm not sure if that is correct.
At any rate, we attempt to do an upgrade install with REINSTALL=ALL
and REINSTALLMODE=vomus. The verbose log file says that the requested
action for the installed features is to reinstall and that the action
to be taken for these same features is reinstall. However, the
components in these features all have their requested and action
states listed as 'null', even though they are listed as installed
locally.
We have updated all the versions on our DLLs from 8.0.0.<build> to
8.0.1.<build>, so the versioning rules should reinstall all the newer
DLLs, but only a very small fraction of the new DLLs get installed.
(I'm analyzing the difference right now, but I suspect that the DLLs
that are installed are those that are in new components not present in
the original install.)
Can anyone tell me what we are doing wrong? This is a very large
project created with InstallShield Developer 8. Unfortunately it uses
quite a bit of InstallScript at the moment, but we are trying to move
away from the use of InstallScript.
I'm stumped on why this is failing, so any suggestions would be
greatly appreciated!
--
"The Direct3D Graphics Pipeline"-- code samples, sample chapter, FAQ:
<http://www.xmission.com/~legalize/book/>
Pilgrimage: Utah's annual demoparty
<http://pilgrimage.scene.org>
Kallely Sajan
--
Regards,
Sajan.
PS: Please don't send me direct emails, use the newsroom.
"Rich [Microsoft Windows Installer MVP]" <legaliz...@mail.xmission.com>
wrote in message news:uGvkNvts...@TK2MSFTNGP10.phx.gbl...
Rich [Microsoft Windows Installer MVP]
"Kallely Sajan" <saj...@hotmail.com> spake the secret code
<e#YS7ztsD...@tk2msftngp13.phx.gbl> thusly:
>Do you want to post the verbose log here?
Its >5 MB. Here is a snippet of the feature and component states
portion:
MSI (s) (5C:80): Feature: Console;
Installed: Advertise; Request: Reinstall; Action: Reinstall
MSI (s) (5C:80): Feature: Console_CHS;
Installed: Absent; Request: Null; Action: Null
MSI (s) (5C:80): Feature: Console_DEU;
Installed: Absent; Request: Null; Action: Null
MSI (s) (5C:80): Feature: Console_ENU;
Installed: Advertise; Request: Reinstall; Action: Reinstall
MSI (s) (5C:80): Feature: Console_ESP;
Installed: Absent; Request: Null; Action: Null
MSI (s) (5C:80): Feature: Console_FRA;
Installed: Absent; Request: Null; Action: Null
MSI (s) (5C:80): Feature: Console_ITA;
Installed: Absent; Request: Null; Action: Null
MSI (s) (5C:80): Feature: Console_JPN;
Installed: Absent; Request: Null; Action: Null
MSI (s) (5C:80): Feature: Console_PTB;
Installed: Absent; Request: Null; Action: Null
....
MSI (s) (5C:80): Component:
C__097FC01560994A36AA54310A70F7AA21.130A144D173346F08401914A6933342B;
Installed: Local; Request: Null; Action: Null
MSI (s) (5C:80): Component:
C__34090AB382FC488BA1D30D19A7C183D6.130A144D173346F08401914A6933342B;
Installed: Local; Request: Null; Action: Null
MSI (s) (5C:80): Component:
C__51811E1C51774534BE211823CB6B6E9B.130A144D173346F08401914A6933342B;
Installed: Local; Request: Null; Action: Null
MSI (s) (5C:80): Component:
C__655F85BD0ED940E38C6F2E23B61A8034.130A144D173346F08401914A6933342B;
Installed: Local; Request: Null; Action: Null
MSI (s) (5C:80): Component:
C__6BEECAFBAFB645469A78BE189702E968.130A144D173346F08401914A6933342B;
Installed: Local; Request: Null; Action: Null
MSI (s) (5C:80): Component:
C__7B81773383DA4DD1907F246F5A71FACA.130A144D173346F08401914A6933342B;
Installed: Local; Request: Null; Action: Null
MSI (s) (5C:80): Component:
C__8EC375D39A9F45C7B5C188701BFD73A0.130A144D173346F08401914A6933342B;
Installed: Local; Request: Null; Action: Null
MSI (s) (5C:80): Component:
C__BCF29B2DAE3543B7AEE0AB0F8CB87AD3.130A144D173346F08401914A6933342B;
Installed: Local; Request: Null; Action: Null
etc.
Kallely Sajan
advertised and not yet actually installed.
--
Regards,
Sajan.
PS: Please don't send me direct emails, use the newsroom.
"Rich [Microsoft Windows Installer MVP]" <legaliz...@mail.xmission.com>
wrote in message news:OMOKk3ts...@TK2MSFTNGP12.phx.gbl...
Rich [Microsoft Windows Installer MVP]
"Kallely Sajan" <saj...@hotmail.com> spake the secret code
<#UxJqVxs...@TK2MSFTNGP11.phx.gbl> thusly:
>The feature state says advertised. It looks like the feature is just
>advertised and not yet actually installed.
Yes, that kinda confused me as well. The advertise flag is not set in
the table and the components for those features are most definately
installed. We have those features in the ADDLOCAL property and the
ADVERTISE property is not specified. I'll post a URL to the full log
tomorrow when I'm at work, if you're willing.
Stefan Krueger [MVP]
component GUID, removed a component from a feature, or the like). This
confuses MSI and makes it think the feature is advertised. Reinstalling an
advertised feature will not install its files.
Run an update validation in InstallShield, this should give you a hint.
--
Stefan Krueger
Microsoft Windows Installer MVP
Please post your questions in the newsgroup or vist one of these web sites:
Windows Installer FAQ
http://www.msifaq.com - http://www.msifaq.de
InstallSite - Resources for Setup Developers
http://www.installsite.org
http://www.installsite.de (GERMAN)
"Rich [Microsoft Windows Installer MVP]" <legaliz...@mail.xmission.com>
schrieb im Newsbeitrag news:ush$98xsD...@tk2msftngp13.phx.gbl...
Frank Gales
usually a verbose log tells or gives some hints what could have been wrong.
Search for errors in the log file.
If a component is missing or the GUID has been changed and this component
belongs to a feature to be upgraded the feature is set to advertised.
We had also the case that in the log an entry ...MGR was there and the whole
feature was not upgraded at all. The reason was mismatch of component
GUIDs of components automatically created by InstallShield.
So analyse of the log file will be the thing to do.
Good luck,
Frank Gales
"Stefan Krueger [MVP]" <ms0...@nwsgrp.REMOVETHIS.installsite.net> wrote in
message news:O053esDt...@tk2msftngp13.phx.gbl...
Rich [Microsoft Windows Installer MVP]
"Stefan Krueger [MVP]" <ms0...@nwsgrp.REMOVETHIS.installsite.net> spake the secret code
<O053esDt...@tk2msftngp13.phx.gbl> thusly:
>This almost certainly means that you boke some upgrade rule (e.g. changed a
>component GUID, removed a component from a feature, or the like). [...]
Yes, I believe this was the case, so we switched from doing a minor
upgrade to a major upgrade.
However, that just resulted in InstallShield inserted custom actions to
fail or cause Windows Installer to go into an infinite loop
complaining about leaked handles....
Oh yeah, now I remember why I call them InstallSUCK.
Stefan Krueger [MVP]
an infinite loop on a Major Upgrade. Could it be that there's a problem in
your project? Did you generate a log of the Major Upgrade? Can you post the
exact error messages? Did you test on a clean machine? Can you reproduce the
problem with a simple test project?
--
Stefan Krueger
Microsoft Windows Installer MVP
Please post your questions in the newsgroup or vist one of these web sites:
Windows Installer FAQ
http://www.msifaq.com - http://www.msifaq.de
InstallSite - Resources for Setup Developers
http://www.installsite.org
http://www.installsite.de (GERMAN)
"Rich [Microsoft Windows Installer MVP]" <legaliz...@mail.xmission.com>
schrieb im Newsbeitrag news:eN74taEt...@TK2MSFTNGP10.phx.gbl...
Rich [Microsoft Windows Installer MVP]
"Stefan Krueger [MVP]" <ms0...@nwsgrp.REMOVETHIS.installsite.net> spake the secret code
<uHEHxrQt...@TK2MSFTNGP10.phx.gbl> thusly:
>Which project type are you using? (I recommend BasicMSI)
I also recommend BasicMSI, but I wasn't around when this setup project
was created :-(. At this point I believe its an InstallScript project
type.
>You should not get
>an infinite loop on a Major Upgrade.
Yeah, I know. We've seen this problem with InstallScript related
custom actions before on just a plain install.
>Could it be that there's a problem in
>your project?
Oh, I'm sure there are multiple problems in there. While we're
addressing them in the future, at the moment we were trying to get an
upgrade install to work. (Its a long story.)
>Did you generate a log of the Major Upgrade? Can you post the
>exact error messages? Did you test on a clean machine? Can you reproduce the
>problem with a simple test project?
Yes, Yes, Yes, haven't tried yet. At the moment, we could not get
anything to work except for changing the upgrade code and installing
over top. Disgusting, yes, but it was the only way we found to get
the updated product to install properly over top of the original
product release. Basically we tell WI that we are a separate product,
even though we install many of the same component IDs. This makes the
newer version install over top of the older version of the product.
Our longer term plan is to remove all InstallScript from our install
as it just generates too many problems and its nothing we can't do in
custom actions or using existing WI tables.