Major Upgrade Not Working...

[Superfreak3]

Hi all,

I'm working on our new product install which will the version 10.0 family. We are coming from 8.6 and earlier. When I run the upgrade from 8.6.x to 10.0.1 all works as planned. Old version detected and removed and the latest is put in place.

I thought I would look ahead and ensure a Major Upgrade in our new version family worked as expected. When I try moving from 10.0.1 to 10.0.257, the old is not removed and I see two instances in Add Remove Programs.

I can't for the life of me figure out what is wrong. I bumped the ProductVersion, obviously. Changed the ProductCode and PackageCode and changed the MaxVersion field value in the Upgrade Table.

All I see in the Log is Not Related and I don't see the ISFOUNDCURRENT property set in the second log. I've attached the 8x to 10 log and log from the 10.0.257 upgrade. I've also attached images of the Upgrade table settings.

I even tried changing the Upgrade Code and creating a separate Upgrade table entry for the v10 family, but that didn't work either. On this new entry I tried including the MinVer, but to no avail.

I just can figure this out. It almost seems there is a problem using 10 versions at this point, but that's absurd.

Any help in this would be greatly appreciated!

Thanks MUCH in advance!!

[Superfreak3]

If you look at the logs, it appears that there is a problem with the language selection or that field in the Upgrade table.

It's pulled from the Upgrade showing 1033, but is being evaluated as related to the upgrade as 0. ?? Anyway, I read that if there are no language restrictions, leave that field in the table blank, which does appear to work. After removing that attribute or blanking that field value in the .msi, the Major upgrade proceeded as expected.

The only problem is that it does not appear that this can be blanked in the Upgrades view. If I blank that field in the IDE and switch views, when I return, the default English value, 1033, appears.

I guess I'll try populating that entry with our two supported language values to see what happens. I'm currently only testing English so I would have guessed it should have worked as is.

[Superfreak3]

Tried populating the Language with 1033,1036. Same unsuccessful results. I have no idea what to do next. It does appear that I can blank the Language field in the Upgrade Table via the Direct Editor.

Something is definitely amiss with this multi-language install. I may have to hit support up with this one.

[Reureu]

Hi there,

The funny thing in your log is that the custom action that logs your previous product as "not related" is ISSetAllUsers.

The Upgrade table is actually used by FindRelatedProducts which seems to do nothing if I believe your logfiles.

In your successful upgrade log:

MSI (c) (28:14) [09:34:53:734]: Doing action: FindRelatedProducts
Action 9:34:53: FindRelatedProducts. Searching for related applications
Action start 9:34:53: FindRelatedProducts.
FindRelatedProducts: Found application: {8E482393-8EBB-4C31-AD13-9EAF9873EC56}
MSI (c) (28:14) [09:34:53:734]: PROPERTY CHANGE: Adding ISFOUNDCURRENT property. Its value is '{8E482393-8EBB-4C31-AD13-9EAF9873EC56}'.
Action ended 9:34:53: FindRelatedProducts. Return value 1.

In your failed upgrade log:

MSI (c) (F8:CC) [09:48:56:875]: Doing action: FindRelatedProducts
Action 9:48:56: FindRelatedProducts. Searching for related applications
Action start 9:48:56: FindRelatedProducts.
Action ended 9:48:56: FindRelatedProducts. Return value 1.

So if I were you, I would try to understand why the FindRelatedProducts action does not work.

Could you have installed 10.0.1 using the per-user installation context?

[Superfreak3]

Could you have installed 10.0.1 using the per-user installation context?

I don't believe so. The only difference between the 10.0.1 and 10.0.257 installs was the changing of codes, etc to prep the later as a Major Upgrade.

ALLUSERS is authored into the Property Table with a value of 1 and the user for this install testing is an Admin so it should be executed in Machine context in all instances.

I still think it has something to do with the Language setting in the Upgrade table. If this is blanked the 10.0.1 to 10.0.257 upgrade works as expected. I will set up that test now and post the logs in a bit.