Minor Upgrade doesn't update the files.

[leo]

Hello:
I've a minor upgrade (v1.2.2,say) that I included all the
files from the previous install and some new files.

I would like to install this(Minor upgrade) as
A) stand alone complete install when no previous version
of my SW is installed on the client machine.

OR

B)Act as a Minor Upgrade when trying to install on top of
the (v1.2.0 v1.2.1,earlier versions)


So far I'm able to do (A) correct,when I try to do aminor
upgrade with below command:

msiexec /i abc.msi REINSTALLMODE=vomus REINSTALL=ALL /L*v
verbose.log

it's not installing all the files,rather it's running the
cached version of the MSI always.
The files never gets updated nor the installer complains
about it.

Am I doing anything wrong???

When I try to install the MSI on a clean machine with out
any of the previous versions of my SW,it installs fine.
But why is the Upgrade failing??
I've changed the product version,package code,Upgrade code.

Thanks,
LEO

 

[Latch]

Are the files to be replaced versioned? Do the files that you want
overwritten have a lower version that their replacements?

If it's bringing up the old install in maintenance mode, then it sounds like
you didn't change the product code. I believe that you should only need to
change the version & product code and then fill the upgrade table and that
should be it.

 

[leo]

I updated the version and the product code values...and
changed the Upgrade table to reflect the previous "Upgrade
code"..etc.

and when I do "msiexec /i abcd.msi REINSTALLMODE=vomus
REINSTALL=ALL /L*v verbose.log"
No file gets update..not even single file...
I've no clue..what's happening..
Thanks for your comments.

 

[Kallely Sajan]

You said you added few new files. Did you add a new feature to include those
files? If you have a new feaure added, those features are to be specified
for ADDLOCAL, REINSTALL=ALL will not do the job

--

Regards,
Sajan.

PS: Please don't send me emails, use the news room, so that others also will
be benefited.

 

[Phil Wilson]

You don't change the ProductCode if you want a minor upgrade with that REINSTALL=ALL and
REINSTALLMODE=vomus command line. You need to very explicit about what you want to do. A minor
upgrade changes only the product version and package code, then you use that command line. If you
want a major upgrade (which replaces the old version completely) you need to keep the same
upgradecode as the original, increment product version (and change package code) and populate the
upgrade table (in Visual Studio this happens if you set the project's RemovePreviousVersions
property).

 

[leo]

All I need is a minor upgrade..but the client doesn;t want
tinstall the Major version and a patch..so I thought of
bundling all of em together...and update the version too..
This "Bundle"(MSI) works fine as it..is if installed on a
Plain Vanilla...machine with out any prior versions of my
SW.

But..if I'm installing on top of previous version
(Software)...it's not reinstalling the Files and there is
a CA that needs to be executed;which is not.


Below is the glimpse of Log File :

I (s) (F4:14): Note: 1: 2262 2: BindImage 3: -2147287038
MSI (s) (F4:14): Note: 1: 2262 2: Patch 3: -2147287038
Action ended 15:23:46: CostFinalize. Return value 1.
MSI (s) (F4:14): Skipping action: SetODBCFolders
(condition is false)
MSI (s) (F4:14): Doing action: InstallValidate
Action start 15:23:46: InstallValidate.
MSI (s) (F4:14): Feature: DefaultFeature; Installed:
Advertise; Request: Reinstall; Action: Reinstall
MSI (s) (F4:14): Component:
C__00E098D55C2C40D9AFB2FF8AF37873B2; Installed: Local;
Request: Null; Action: Null
MSI (s) (F4:14): Component:
C__06FA912D6DD84C38B831E92390493195; Installed: Local;
Request: Null; Action: Null
MSI (s) (F4:14): Component:
C__0967E3BEAFCC43DD8F92A5B29805D361; Installed: Absent;
Request: Null; Action: Null
MSI (s) (F4:14): Component:
C__0B731C366B4041BFA236111DF57F2DB4; Installed: Local;
Request: Null; Action: Null
MSI (s) (F4:14): Component:
C__18AEF0C939004EF78BBA6B477B3A5D32; Installed: Local;
Request: Null; Action: Null
MSI (s) (F4:14): Component:
C__1BAE9D76BE6142E08B87536F84F9C2BD; Installed: Local;
Request: Null; Action: Null
MSI (s) (F4:14): Component:
C__1DB7DAC2A24946858BCAD4CC79E2A432; Installed: Local;
Request: Null; Action: Null
MSI (s) (F4:14): Component:
C__22674D23A5704944B7797CA300435C1C; Installed: Local;
Request: Null; Action: Null
MSI (s) (F4:14): Component:
C__22FF834FFAF8491899F92EC76AE95D66; Installed: Local;
Request: Null; Action: Null

Suggestions Please...

-----Original Message-----
You don't change the ProductCode if you want a minor

upgrade with that REINSTALL=ALL and

REINSTALLMODE=vomus command line. You need to very

explicit about what you want to do. A minor

upgrade changes only the product version and package

code, then you use that command line. If you

want a major upgrade (which replaces the old version

completely) you need to keep the same

upgradecode as the original, increment product version

(and change package code) and populate the

upgrade table (in Visual Studio this happens if you set

the project's RemovePreviousVersions

property).
--
Phil Wilson [MVP Windows Installer]
----

I updated the version and the product code values...and
changed the Upgrade table to reflect the previous "Upgrade
code"..etc.

and when I do "msiexec /i abcd.msi REINSTALLMODE=vomus
REINSTALL=ALL /L*v verbose.log"
No file gets update..not even single file...
I've no clue..what's happening..
Thanks for your comments.
mode,
then it sounds like top
of

.

 

[Andrew Stickler]

Leo,

I have experienced exactly the same problem, but only when sing MSI
version 1.10 or 1.11. With MSI V2.0 , my minor upgrade is successful.

Even a repair does not seem to fix this problem, and if I edit the
cached MSI file with ORCA, I can see that the correct file is present,
but MSISpy tells me that my features have been set to 'Advertised'.

Did you get a resolution to this problem?
What version of MSI are you using?

regards,
Andrew