We deployed the corporate msi 11.4 version in our environment. Now we wish to deploy the corporate msi 11.5 Looking at the upgrade table in Orca it is empty and checking the two packages shows that the product code is identical. Even if I change the product code in the new version and populate the upgrade table and add the securecustomproperty I still get an Modify/Repair/Remove when installing the new version. Damn Adobe again. What am I missing?
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
I would assume they're treating this as a minor upgrade (hence the product code being the same).

You'd be best off running the new MSI (11.5) with the command line REINSTALL=ALL REINSTALLMODE=vomus which would result in the application updating the new version.

If you don't want to do down this route and still modify the new version........Is the package code the same ? What does it say in your logging ?
Answered 07/08/2009 by: michaelnowell
Second Degree Blue Belt

Please log in to comment
0
That would be too simple. Unfortunately it does not upgrade the files but does change the entry name in add/remove programs. Also when you uninstall it does not remove the files.

Here is an excerpt from the attempted upgrade install log.

MSI (c) (C4:E4) [09:58:40:093]: APPCOMPAT: looking for appcompat database entry with ProductCode '{AD72CFB4-C2BF-424E-9DF0-C7BAD1F30A11}'.
MSI (c) (C4:E4) [09:58:40:093]: APPCOMPAT: no matching ProductCode found in database.
MSI (c) (C4:E4) [09:58:40:093]: MSCOREE not loaded loading copy from system32
MSI (c) (C4:E4) [09:58:40:093]: Machine policy value 'DisablePatch' is 0
MSI (c) (C4:E4) [09:58:40:093]: Machine policy value 'AllowLockdownPatch' is 0
MSI (c) (C4:E4) [09:58:40:093]: Machine policy value 'DisableLUAPatching' is 0
MSI (c) (C4:E4) [09:58:40:093]: Machine policy value 'DisableFlyWeightPatching' is 0
MSI (c) (C4:E4) [09:58:40:093]: APPCOMPAT: looking for appcompat database entry with ProductCode '{AD72CFB4-C2BF-424E-9DF0-C7BAD1F30A11}'.
MSI (c) (C4:E4) [09:58:40:093]: APPCOMPAT: no matching ProductCode found in database.
MSI (c) (C4:E4) [09:58:40:093]: Transforms are not secure.

MSI (c) (C4:E4) [09:58:40:093]: PROPERTY CHANGE: Adding PackageCode property. Its value is '{525016AD-E3AC-4C8A-8ABB-C934C10AE996}'.
MSI (c) (C4:E4) [09:58:40:093]: Product Code passed to Engine.Initialize: '{AD72CFB4-C2BF-424E-9DF0-C7BAD1F30A11}'
MSI (c) (C4:E4) [09:58:40:093]: Product Code from property table before transforms: '{AD72CFB4-C2BF-424E-9DF0-C7BAD1F30A11}'
MSI (c) (C4:E4) [09:58:40:093]: Product Code from property table after transforms: '{AD72CFB4-C2BF-424E-9DF0-C7BAD1F30A11}'
MSI (c) (C4:E4) [09:58:40:093]: Product registered: entering maintenance mode
MSI (c) (C4:E4) [09:58:40:093]: PROPERTY CHANGE: Adding ProductState property. Its value is '5'.
MSI (c) (C4:E4) [09:58:40:093]: PROPERTY CHANGE: Adding ProductToBeRegistered property. Its value is '1'.
MSI (c) (C4:E4) [09:58:40:140]: Entering CMsiConfigurationManager::SetLastUsedSource.
MSI (c) (C4:E4) [09:58:40:140]: Specifed source is already in a list.
MSI (c) (C4:E4) [09:58:40:140]: User policy value 'SearchOrder' is 'nmu'
MSI (c) (C4:E4) [09:58:40:140]: Machine policy value 'DisableBrowse' is 0
MSI (c) (C4:E4) [09:58:40:140]: Machine policy value 'AllowLockdownBrowse' is 0
MSI (c) (C4:E4) [09:58:40:140]: Adding new sources is allowed.
MSI (c) (C4:E4) [09:58:40:140]: Package name retrieved from configuration data: 'ShockWavePlyr11.msi'
MSI (c) (C4:E4) [09:58:40:140]: Determined that existing product (either this product or the product being upgraded with a patch) is installed per-machine.
MSI (c) (C4:E4) [09:58:40:140]: Note: 1: 2262 2: AdminProperties 3: -2147287038
MSI (c) (C4:E4) [09:58:40:140]: Machine policy value 'DisableMsi' is 0
MSI (c) (C4:E4) [09:58:40:140]: Machine policy value 'AlwaysInstallElevated' is 0
MSI (c) (C4:E4) [09:58:40:140]: User policy value 'AlwaysInstallElevated' is 0
MSI (c) (C4:E4) [09:58:40:140]: Product {AD72CFB4-C2BF-424E-9DF0-C7BAD1F30A11} is admin assigned: LocalSystem owns the publish key.
MSI (c) (C4:E4) [09:58:40:140]: Product {AD72CFB4-C2BF-424E-9DF0-C7BAD1F30A11} is managed.
MSI (c) (C4:E4) [09:58:40:140]: Running product '{AD72CFB4-C2BF-424E-9DF0-C7BAD1F30A11}' with elevated privileges: Product is assigned.


ORIGINAL: michaelnowell

You'd be best off running the new MSI (11.5) with the command line REINSTALL=ALL REINSTALLMODE=vomus which would result in the application updating the new version.

Answered 07/08/2009 by: joedown
Second Degree Brown Belt

Please log in to comment
0
Find a file that you know should be upgraded, but isn't. Find out what component it's in and then look at the upgrade log file to see what action the component is taking (e.g. Null/Local). That should get you going on the right track

Also try REINSTALLMODE=vamus (note the a instead of the o) as this will reinstall all file regardless of version.

PS. Where did you get the msi for shockwave that has 11.5 as the version, I can only seem to download 11.0 from teh adobe website ?
Answered 07/08/2009 by: michaelnowell
Second Degree Blue Belt

Please log in to comment
0
The upgrade log for all the components during reinstall shows Local and Null for the Request and Action even when using vamus. Another problem is that even though I'm using the new msi during the reinstall it is looking for the old MSI and if it's not available it dies. Renaming the new msi the same as the old allows it to run but it does not upgrade the files. Too bad I can't bill Adobe for my wasted time on this.

The msi I downloaded is from the Adobe Shockwave Player distribution license site. The version listed in the MSI is 11.0 but the files that get distributed to C:\Windows\System32\Adobe\Shockwave 11 show 11.5.

ORIGINAL: michaelnowell

Find a file that you know should be upgraded, but isn't.  Find out what component it's in and then look at the upgrade log file to see what action the component is taking (e.g. Null/Local).  That should get you going on the right track

Also try REINSTALLMODE=vamus (note the a instead of the o) as this will reinstall all file regardless of version.

PS.  Where did you get the msi for shockwave that has 11.5 as the version, I can only seem to download 11.0 from teh adobe website ?
Answered 07/09/2009 by: joedown
Second Degree Brown Belt

Please log in to comment
0
It's not the greatest way of doing it and considering that a REINSTALL=ALL REINSTALLMODE=vomus does work, I was able to upgrade by doing the following.

Change Product Code
Change Package Code
Change Product version
Add upgrade information.

Voila !
Answered 07/10/2009 by: michaelnowell
Second Degree Blue Belt

Please log in to comment
0
I have never had to change the Package Code before for a package. Looking at what needs to be done to make this work makes sense but why should I have had to? [:'(] Anyway, doing the steps below works great to upgrade from 11.4 to 11.5

Thanks


ORIGINAL: michaelnowell

It's not the greatest way of doing it and considering that a REINSTALL=ALL REINSTALLMODE=vomus does work, I was able to upgrade by doing the following.

Change Product Code
Change Package Code
Change Product version
Add upgrade information.

Voila !
Answered 07/10/2009 by: joedown
Second Degree Brown Belt

Please log in to comment
0
Glad that it worked for you.

Quite simply it's the PackageCode that marks the msi as being unique. You can have different msi's that can have the same ProductCode (for minor changes etc...), but the PackageCode must never be the same.

You'll find that some msi's (particulary ones that are generated as a client install after a server upgrade) will always be compiled with matching Package/Product Codes.

In this case it just down to Adobe not doing things correctly. Maybe you should send them the following link...... http://msdn.microsoft.com/en-us/library/aa370568(VS.85).aspx

......as if they'd even bat an eye at it. ;o)
Answered 07/10/2009 by: michaelnowell
Second Degree Blue Belt

Please log in to comment
0
The Adobe MSIs are always a head ache. That's why we switched to the exe installer from Adobe enterprise deployment website.
Answered 07/13/2009 by: app.packager
Senior Yellow Belt

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