Hi Folks,

Appreciate any help. I'm creating a package for Real Player 11 and if i install without upgrading, package installs without issues. However if there is a previous version, 10, MSI has an upgrade code and hence it removes version 10 and install 11. When i launch the shorcut, application initiates repair. These are 2 components that cause that.

Detection of product '{AB5CCF73-E37D-4504-A62D-86FB339059F9}', feature 'RealPlayer11.0ENR1B1NewFeature',
component '{4BE6086A-C2DF-4C2B-9224-EA7E403A9886}' failed. The resource 'C:\Program Files\Common Files\Real\Codecs\atrc.dll' does not exist.

and

Detection of product '{AB5CCF73-E37D-4504-A62D-86FB339059F9}', feature 'RealPlayer11.0ENR1B1NewFeature' failed during request for component '{10839368-CF8D-4F70-8092-D4BF3FECE756}'

This only happens on the 1st launch. Subsequent launch doesn't self-repair. Appreciate any help. 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
where is the removeRelatedProducts action in relation to the upgrade.
Answered 05/20/2008 by: jmcfadyen
Fifth Degree Black Belt

Please log in to comment
0
Do you mean: Where is the RemoveExistingProducts action in the InstallExecuteSequence table?
Answered 05/20/2008 by: timmsie
Fourth Degree Brown Belt

Please log in to comment
0
lol yeah.. i always mix those two up dunno why.
Answered 05/20/2008 by: jmcfadyen
Fifth Degree Black Belt

Please log in to comment
0
jmcfadyen

Hi jmcfadyen..it's in between Install Validate and Install Initialize.... 1410....i been using this without any issues....
Answered 05/20/2008 by: PackageExpert
Blue Belt

Please log in to comment
0
ORIGINAL: harjind
This only happens on the 1st launch. Subsequent launch doesn't self-repair.
That would be because it repaired the component the first time.

ORIGINAL: harjind
it's in between Install Validate and Install Initialize
Our templates ALL have RemoveExistingProduct as the LAST CA in ExecuteImediate. I may be wrong - it's a long time since I did any upgrades, as most clients I work for these days seem to want complete removal of version x.x before version y.y gets installed but IIRC, MS guidelines state that upgrades should do as little work as possible. That is to say, if an upgrade will, for example, replace a bunch of files, there's no point in having RemoveExistingProduct remove them first, only for the new version to be copy the new versions of those files anyway.
Answered 05/21/2008 by: VBScab
Red Belt

Please log in to comment
0
Interesting one.

You say that a clean install works 1st time. What happens if you manually remove the previous version (via ARP) then install your new package? Does it still cause a self repair on 1st run?
Answered 05/21/2008 by: MSIPackager
Third Degree Black Belt

Please log in to comment
0
If i manually remove the 1st application and then install the new one, its fine. Anyway I've found the solution by placing RemoveExistingProduct to sequence 480 which is before CCP Search. As long as it removes previous version and doesn't cause self repair on the 1st launch I'm happy. Thanks for the support. Appreicate it very much.
Answered 05/21/2008 by: PackageExpert
Blue Belt

Please log in to comment
0
sounds like an issue with MigrateFeatureStates or something.

probably not worth investigating now you have a workaround.
Answered 05/22/2008 by: jmcfadyen
Fifth Degree Black Belt

Please log in to comment
0
yes mate...i suspected that. that is why i moved RemoveExistingProduct before MigrateFeatureState...im not sure its a good practice but i leave it there as long as no other issues comes by....thanks
Answered 05/22/2008 by: PackageExpert
Blue Belt

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