/build/static/layout/Breadcrumb_cap_w.png

Why not all components are reinstalled if I apply a majorUpgrade?

Hello
Why components are not reinstalled if I use a majorUpgrade?
I have several setups, where not all components are reinstalled if I use a majorUpgrade & the Action 'RemoveExistingProducts' in the MajorUpgrade is locatet after InstallValidate. The not reinstalled components are unversioned and have newer or equal dates in the newer package. 'CostFinalize' in MajorUpgrade notify Disallowing installation of component: {XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX} since the same component with higher versioned keyfile exists, but these files have'nt a version!!
If I move the 'RemoveExistingProducts' before CostInitialize all works fine. But I would like a answer for this effect. It's a error in Windows Installer?
I've found many of links for the same scenario:
http://community.macrovision.com/archive/index.php?t-116526.html
http://itninja.com/question/excellent-links-for-sus-information8&mpage=1&key=僮
http://community.macrovision.com/showthread.php?t=162356
...but no really answer.
Did you can help me?

0 Comments   [ + ] Show comments

Answers (1)

Posted by: Dominik Oberlin 18 years ago
Yellow Belt
0
german users can visit...
http://www.doctordeploy.com/wenn-tt-files-b-majorupgrade-nicht-neu-geschrieben-werden-t419.html
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