/build/static/layout/Breadcrumb_cap_w.png

Minor upgrade does not remove old registry value

Hello,


I'm having a problem with a minor upgrade we are trying to do with WPS 7 SP3. We have an old package and we need to modify 3 files in it and a registry value. I followed this procedure to do a minor upgrade:

http://www.symantec.com/community/article/1377/upgrades-walkthrough

So, I copied the old WSI file and renamed it, added my new files, changed the registry value. I ran the upgradesync tool. It corrected a few problems and stated that "'registry' exists in the previous version and the keypath does not exist in the current install. The component's contents will be deleted during an upgrade." and I would think that would be all right because we want to change the value.

So, we try installing the upgrade package over the old package. The new files are copied but the old value stays there and the new value is not written. When installing the upgraded package on a clean workstation, it works fine. I followed the walkthrough again and again and I can't find what I'm doing wrong.

Thanks.


Syl

0 Comments   [ + ] Show comments

Answers (4)

Posted by: AngelD 16 years ago
Red Belt
0
Where did you sequence the RemoveExistingProducts action?
Try adding the registry entry to the RemoveRegistry table and see if that solves your problem as a workaround.
Posted by: sylvain_langlois 16 years ago
Orange Belt
0
The removeexistingproducts is at 1450, between InstallValidate and InstallInitialize. I already tried to remove the value during the install (upgrade). It does not work and the new value is not written either.

The command line I use to upgrade is "MSIEXEC.EXE /I "upgrade.msi" REINSTALL="ALL" REINSTALLMODE=VOMU /QB".
Posted by: anks_09 16 years ago
Orange Senior Belt
0
Hi,

I dnt know what sync tool you are using.But i can tell you basic of how minor upgrade work.First of all for minor upgrade to work through msi you need to keep the msi name same as the old version msi.Also there few rules to do minor upgrade that you can check on microsoft site.But be sure the name of the msi should be same as the old version msi name.For more information check out this blog may prove useful to you.

http://robmensching.com/blog/archive/2007/01/04/Doing-a-small-update-or-minor-upgrade-in-MSI-Use.aspx

Regards,
anks_09
Posted by: sylvain_langlois 16 years ago
Orange Belt
0
When adding the property mentioned in the article, I got the following error:

DEBUG: Error 2771: Upgrade of feature XXX has a missing component.

Turns out I shouldn't have deleted the registry value I wanted to replace, which I did in the first place. So, I started over with the old WSI, flagged the old registry value to be deleted (as suggested by AngelD) and added a new value and now it works fine.

Thanks for your help.
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ