/bundles/itninjaweb/img/Breadcrumb_cap_w.png
Hi @ll,

We are having the following problem:

With the help of Windows Installer 3.0 and WPS 5.6 we built around 300 applications.
None of these 300 applications can be repaired with the help of msiexec /fa.
For example, if I exchange a file and then perform a msiexec /fa the old file still remains.

If I build this application with the WPS 5.6 and the Windows Installer, this procedure works just fine.
That means, I can exchange files and update/repair them via msiexec /fa.

My question would be: How come that this operation is possible with only the newly constructed applications and not with the “old” ones.

Thanks
0 Comments   [ - ] Hide 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.
Answer this question or Comment on this question for clarity

Answers

0
Hmmm - check your existing MSI against your new one for the REINSTALL and REINSTALLMODE properties and compare them to see if you get any pointers..

Cheers,
Rob.
Answered 12/16/2005 by: MSIPackager
Third Degree Black Belt

Please log in to comment
0
Hello MSIPackager,

we have compared both msi- files... but we do not have found any Differences. :-(

Any Idea?
Answered 12/20/2005 by: private
Senior Yellow Belt

Please log in to comment
0
Have a look for the following properties in the Property table:

ReinstallFileOlderVersion
ReinstallFileVersion
ReinstallRepair
etc
etc
etc
Answered 12/20/2005 by: brenthunter2005
Fifth Degree Brown Belt

Please log in to comment