I have a package that is an upgrade to a previous version. I'm using the upgrade table to uninstall the older package, and even though my package has all the neccesary files needed for a successful installation it still does repair on first launch. The first thing I did was check the Event viewer to see what component was missing from my package and I was able to see that the same file that is missing is also within my package. So then I thought my deleting the component from my package and re-adding it would fix the problem, but it wasn’t going to be that easy because I still have that problem. Now, the funny thing is that if I just install my new package without having a older version on my pc, I get no repair on first launch, so why would my new package not install the font file when it has to uninstall an older package?

Any thoughts or ideas on how to fix this issue or some details on why this may occur when there is an uninstall that needs to be done?

Thanks!
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Answers

0
Hi Justin,
check where the 'RemoveExistingProducts' action is located in the 'InstallExecuteSequence' table.
Regards, Nick
Answered 09/06/2007 by: nheim
Tenth Degree Black Belt

Please log in to comment
0
in addition to Nicks comments have you sync'd the components between the two versions of the apps. if the Remove action is late in the sequences you can have issues if this is not done.
Answered 09/06/2007 by: jmcfadyen
Fifth Degree Black Belt

Please log in to comment
0
I moved the "RemoveExistingProducts" in between InstallValidate and InstallInitalize. So, if I understand this correctly, my package will remove the older package before installing the new version right?
Answered 09/07/2007 by: justinSingh
Blue Belt

Please log in to comment
0
how can i sync the components in both of my packages?
Answered 09/10/2007 by: justinSingh
Blue Belt

Please log in to comment
0
Depending on the packaging tool you're using there should exist a tool for syncing between two MSIs. Wise has the UpgradeSync tool for this. If not then you could use a simple vbscript to go through each component as set the component GUID (ComponentId column) to the same for both.
Answered 09/10/2007 by: AngelD
Red Belt

Please log in to comment
Answer this question or Comment on this question for clarity