8 replies to this topic

[abryum]

Hi All,

I have a problem with my basic MSI project (InstallShield 11 Professional) for a small .NET application.

I have changed file version for application EXE from 2.0.0.0 to 2.1.0.0 and even changed file property to "Always Overwrite" but EXE does not get replaced by the new install.

What would be the best way to approach this?

Thank you for your help.

[luke_s]

Run the upgrade / installation with verbose logging.

msiexec /i <msifile.msi> /L*V c:\mylog.log

You can then search for your executable in the log and it should say why it hasnt been upgraded.

[abryum]

Thanks a lot for you help.

I keep the same Product Code and Upgrade Code but change the Package Code.

With /i key, I got the following message:

"Another version of this product is already installed.
Installation of this version cannot continue.
To configure or remove the existing version of this product,
use Add/Remove Programs on the Control Panel."

When I tried /fa key to reinstall all the files, I got the following:
"This action is only valid for products that are currently installed."


What is the best way to force reinstallation of all the files with logging?

Thank you very much again.

Edited by abryum, 29 October 2008 - 16:36.

[abryum]

I managed to produce verbose log by means of setup.exe and its /v key.

The log contains the following fragment:

Component: Acc.exe; Installed: Local; Request: Null; Action: Null

Why doesn't install take into account the newer version of the file?

Thank you for your help.

[luke_s]

From your posting, it looks more like the component is the problem, not the file.

You need to trace back and see why the component state is set to not install.

Do you have any special attributes set on the component? What about the key file for the component?

What about the feature that this component is under? is that set to install?

[abryum]

Thank you for your help.

There is only one feature and it's getting reinstalled:

Feature: NewFeature1; Installed: Advertise; Request: Reinstall; Action: Reinstall

However, for the component I have:
Component: ... Installed: Local; Request: Null; Action: Null

Here is the list of component attributes:

Destination permissions : 0 Permission(s) defined
Shared : Yes
Permanent : No
Condition : <blank>
Remote Installation : Favor Local
COM Extract at Build : No
.Net Installer Class : No
.Net COM Interop : No
.Net Precompile Assembly : No
Reevaluate Condition : No
Never Overwrite : No
64-Bit Component : No

The rest of them are blanks.

All the properties of the key file for the component have default values.

What could be the cause for Request: Null?

[luke_s]

I would say its because your are doing a re-install.

The component key file is probably being detected as "ok", as in nothing needs to be re-installed for the component so everything else is nor re-installed.

Do you have a key file set for the component?

The best way to make all of the files install is to either delete them all, or run a major upgrade.

[abryum]

Thank you for your help.

For the major upgrade, Product Code needs to be changed. Does it mean that every time I run my package a "new" application will appear in the list of programs installed under "Add or Remove Programs"?

It's still not clear to me why reinstall does not detect that the version of the component's key file is modified and requires substitution. But I am ready to do everything to make the process work. By the way, I tried to recreate my package from scratch but it didn't help.

Edited by abryum, 31 October 2008 - 14:54.

[Stefan Krueger]

For your Minor Update problem look for SELGR errors in the log. I guess you violated some component update rules.

Regarding Major Upgrades: Installing the major upgrade will automatically uninstall the old version, so you get only one entry in Add/Remove Programs