I have an application A. My current application B is uninstalling App A and then installing App B. App B is an patch upgrade to App A.

After I install the Application B, when I launch the app, it goes through a self repair.
This only happens once. The next time I open the app, it opens fine.

I checked the eventvwr and it points to a location under Detection of product {GUID} feature 'Complete'. Component '{GUID coresposing to the filename.dll} failed. The resource 'C:\Program Files\ApplicationName\dirA\dirB\dirC\dirD\dirE\dirF\filename.dll does not exist.

I checked my package (compiled with the files), I checked the file section and the file exists. I also installed the package on a test machine and the file (filename.dll) exists fine. So then why the error?

I checked the old version of the app, and it has a different version of the filename.dll file. Could it be that the file is not getting overwritten due to some issue?

This does not seem to a HKEY_Curent User issue.

Any thoughts to try?
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
Probably down to the location of the RemoveExistingProducts action... have a look at this post http://itninja.com/question/real-player-package-initiates-repair-after-an-upgrade

Cheers,
Rob.
Answered 06/24/2008 by: MSIPackager
Third Degree Black Belt

Please log in to comment
0
also check your REINSTALLMODE property and determine if your file versions are changing etc
Answered 06/24/2008 by: jmcfadyen
Fifth Degree Black Belt

Please log in to comment
0
I followed the steps on the other post and it seems like it is working. I changed the RemoveExistingProduct to sequence 480 [right before CCP Search].

Now, the app doesn't cause self repair on the 1st launch.
So, I know that the issue is resolved for now.

Question: I know for a fact that the new file versions (in App B) are different. All the other files (of app A) are getting updated, why then would I have an issue for one specific dll file? If I would not have changed the sequence property, what else would I have looked for in the ReinstallMode, or MigrateFeature etc?

Thanks for all your advise and help.
Answered 06/25/2008 by: aek
Purple Belt

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