why does my package repair?
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!
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
Answers (5)
Please log in to answer
Posted by:
nheim
17 years ago
Hi Justin,
check where the 'RemoveExistingProducts' action is located in the 'InstallExecuteSequence' table.
Regards, Nick
check where the 'RemoveExistingProducts' action is located in the 'InstallExecuteSequence' table.
Regards, Nick
Posted by:
jmcfadyen
17 years ago
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.
Posted by:
justinSingh
17 years ago
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?
Posted by:
AngelD
17 years ago
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.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.