4 replies to this topic

[DavidCahill]

Hi,
I am creating a major upgrade to be distributed via a full installation
routine and also as a patch.
Both the full installation and the patch are working as expected except from
one thing.
If I install Version 1 and install the path for Version 2 and then run the
full installation for Version 2, I get the following error 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 on the Control panel".

Shouldn't running the full installation of version 2 bring me into
Maintenance mode? Why is this error message being displayed?

Any ideas or suggestions would be much appreciated.

thanks,
David

[Ian Blake]

Try this checklist

1.  Used New Product Code
2.  Used New Package Code
3.  Used New Product Version
4.  Checked Upgrade code is the same
5.  Made entry in Upgrade table for previous versions
6.  Added property in upgrade table to SecureCustomProperties
7.  Moved RemoveExistingProducts Action to after InstallFinalize

[DavidCahill]

Hi Ian,
I've done everthing in your checklist.
I've tried putting the RemoveExistingProducts action after InstallFinalize and also after InstallValidate but with the same behaviour.

Am I right in saying that after installing the patch and then running the full installation that the full install should bring you into Maintenance mode?

thanks,
David

[Ian Blake]

Sorry I misread your original post.  
I assumed your upgrade was not working.

I would not expect the maintenace dialog to appear because v1+patch is not the same package as v2 even though the components are the same.

A possible work around is for v1+patch to make product version 2.0.0 and v2 to make the functionally identical 2.0.1, when v2 is run on the patched version it will then update the registration and version information and not much else (provided RemoveExistingProducts is after InstallFinalize).

You might also be able to fiddle the product and package code of v2 to match that of v1+patch then the install will run the cached package in maintenance mode.

Before I dig myself into big hole I better stop.  I have never done a patch so I am not sure of any ot this.