Real Player package initiates repair after an upgrade
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
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
Answers (9)
Please log in to answer
Posted by:
jmcfadyen
16 years ago
where is the removeRelatedProducts action in relation to the upgrade.
Posted by:
timmsie
16 years ago
Do you mean: Where is the RemoveExistingProducts action in the InstallExecuteSequence table?
Posted by:
PackageExpert
16 years ago
jmcfadyen
Hi
Posted by:
anonymous_9363
16 years ago
ORIGINAL: harjindThat would be because it repaired the component the first time.
This only happens on the 1st launch. Subsequent launch doesn't self-repair.
ORIGINAL: harjindOur 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.
it's in between Install Validate and Install Initialize
Posted by:
MSIPackager
16 years ago
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?
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?
Posted by:
PackageExpert
16 years ago
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.
Posted by:
jmcfadyen
16 years ago
sounds like an issue with MigrateFeatureStates or something.
probably not worth investigating now you have a workaround.
probably not worth investigating now you have a workaround.
Posted by:
PackageExpert
16 years ago
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
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.