Video Screencast Help
Search Video Help Close Back
to help
Not able to make it to Vision this year? Get a sampling in the Best of Vision on Demand group.

Upgrade Sync Errors

Updated: 22 May 2010 | 6 comments
kgandy's picture
+1 1 Vote
Login to vote
This issue has been solved. See solution.

When I run upgrade sync I get the following message for several files:
File 'emancipatedstudent.aspx.cdcab7d2.compiled' is a new resource that needs to be added to a new component and assigned to a new subfeature.

However when I go to check the components I see the files there, and if I try to add them I get messages saying that the files already exist, and if I try to add it as a new component I only get <none> in the keypath dropdown, however if I go ahead and add it anyway I still get the error.  My installation only has one feature, so I shouldn't have to explicitly assign the new component to the feature, but I've tried it both ways and the messages do not go away.

After running the upgrade the files are not on the destination machine, but they install fine for a full install.

What else should I be looking at?

Discussion Filed Under:

Comments

EdT's picture
26
Jun
2009
1 Vote +1
Login to vote

Upgradesync

The purpose of upgradesync is to compare your original MSI and your updated MSI to ensure that components with identical content continue to have the same component GUID.
New resources need to be assigned to a new component - I remain unconvinced for the need to use a new subfeature.

However, assuming you are creating a major upgrade rather than a patch, what I would suggest is that you re-sequence your RemoveExistingProducts custom action so that it is between InstallValidate and InstallInitialize, rather than at its default location near the end of the InstallExecute sequence. Look up RemoveExistingProducts in the help file MSI.CHM for a full explanation of the different positions it can be placed in, and their consequences.

Using the above placement also ensures that old files are removed before any new files are installed, thus avoiding any file versioning issues you may be encountering with files that don't have an internal version resource, and are thus compared using Create and Modify date/time stamps.

Finally, why not enable verbose logging of the install of your upgrade - the log will give you information on why files are installed (or not installed)

If your issue has been solved, please use the "Mark as Solution" link on the most relevant thread.

kgandy's picture
26
Jun
2009
0 Votes 0
Login to vote

UpgradeSync

Thanks for the response.

Where do I find msi.chm?  I've seen it mentioned here frequently and my attempts to google for it just send me in circles, and the windows installer sdk doesn't seem to have installed it on my local drive.

I'm using wise installation studio 7.3, I checked, and the verbose log of the upgrade shows that the installer checks the file, and verifies that there are not any changes, so it rightly indicates that it will not upgrade it.  But at the very end of the installation it removes some files that it should leave as it is removing the files that are no longer needed. 

After I resequenced the custom actions all of the files were there, but it did not upgrade all of the files that it should have. 

I went back to square 1 and tried to add a new component, but the Wise Studio crashes every time I try to add files that already exist in the instalation to the component.

kgandy's picture
26
Jun
2009
0 Votes 0
Login to vote

Upgrade Working

I ended up getting the upgrade to work by setting the upgrade to not uninstall the previous version and I commented out the RemoveExistingProducts custom action, and that seems to have done the trick.

I tried to just set the flag to not uninstall the previous version but that just got me an Internal error 2762, but that went away as soon as I commented out the CA.

The interesting thing is that UpgradeSync seems to be perfectly happy now.

EdT's picture
29
Jun
2009
0 Votes 0
Login to vote

MSI.CHM

A copy of this file is installed by the Wise product. Look for it in the Wise installation folders.

If your issue has been solved, please use the "Mark as Solution" link on the most relevant thread.

kgandy's picture
29
Jun
2009
0 Votes 0
Login to vote

Got it.  Thanks!

Got it.  Thanks!

EdT's picture
29
Jun
2009
1 Vote +1
Login to vote

Please click "mark as solution"....

---once your questions have been answered

If your issue has been solved, please use the "Mark as Solution" link on the most relevant thread.