srinivas

Hello:
I have a problem which many of you might've seen it at
some point or the other.
I have installed a version 1.1 of the software and upgraded
(Major upgrade) to 1.3.
After that I'm seeing two versions of Software
in "Add/Remove Programs".

I've to undergo a painful process to uninstall the
software,which I can't recommend to my manager nor to the
customer.(U know Why))

I've changed the ProductCode,Version number keeping the
UpgradeCode same in VS.NET
My Upgrade table looks something like below:
UpgradeCode:{ACE676A9-9BEF-447C-8CDC-B2E5A06B63B5}
VersionMin:1.0.0
VersionMax:1.3
Attributes:256
ActionProperty:PREVIOUSVERSIONSINSTALLED(Listed against
SecureCustomProperties in property table)

And I've put RemoveExistingProducts just after
InstallValidate in InstallExecuteSequence table.

Am I doing some thing wrong???

Below is the logfile snippet:

Action ended 16:50:11: InstallValidate. Return value 1.
MSI (s) (4C:4C): Doing action: RemoveExistingProducts
Action start 16:50:11: RemoveExistingProducts.
MSI (s) (4C:4C): Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (4C:4C): Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (4C:4C): Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (4C:4C): Note: 1: 2262 2: Error 3: -2147287038
Action ended 16:50:11: RemoveExistingProducts. Return
value 1.
MSI (s) (4C:4C): Doing action: InstallInitialize
Action start 16:50:11: InstallInitialize.

kallely sajan

Obviously removal of the old version is failing. Probably one of the CA in
there is failing, may be b'cos a file required is missing.


--
Regards,
Sajan.

PS: Please don't send me direct emails, use the newsroom.

kallely sajan

Can you post the complete verbose log here
--

Regards,
Sajan.

PS: Please don't send me direct emails, use the newsroom.

phil wilson

If you've used Visual Studio.NET you may have run into an issue with major upgrades. Windows
Installer will not let a per-user install cannot upgrade a per-system install. If your first install
was per-system, the major upgrade install then comes along but unfortunately it's still in per-user
mode when FindRelatedProducts runs, so it fails to replace the old version. This should show in the
log if it's really the case.

A fix is to go into the new MSI file with Orca and resequence the InstallUISequence table so that
FindRelatedProducts is just before ExecuteAction (you'll need to increase ExecuteAction's sequence
number). This makes FindRelatedProducts in the UI sequence run after you've selected per user or per
system.
--
Phil Wilson [MVP Windows Installer]
----

phil wilson

Installer will not let a per-user install upgrade a per-system install.

This is in the log - this looks like your problem. It's fixed in VS 2003, by the way.
--
Phil Wilson [MVP Windows Installer]
----

kallely sajan

Two comments before getting into the log file.
- Take care care as many ICE errors as possible
- Do you have PREVIOUSVERSIONSINSTALLED defined as a property in the
property table?
--

Regards,
Sajan.

PS: Please don't send me direct emails, use the newsroom.