upgrading with msi throwing error
Posted 12 November 2010 - 05:34
I installed my application setup.exe.Now am trying to upgrade it via .msi.
But it is throwing an error( 1638:Another version of this product is already installed. Installation of this version cannot continue. To configure or remove the existing version of this product, use Add/Remove Programs on the Control Panel).
But using setup.exe am able to upgrade my application.
Similarly if installed using .msi the application is succesfully upgraded using .msi and .exe.
What may be the problem in this??
Posted 12 November 2010 - 09:25
Alternatively you can change the ProductCode to make it a Major Upgrade and author an entry in the Upgrade table. Then you can upgrade by simply running the msi.
Another option would be a minor update, but not shipped as full msi file but as msp patch.
Posted 12 November 2010 - 11:30
This is a minor upgrade as no change in product code.I was trying vth these parameters.But still it is throwing the same error.
Any other solution.
Posted 15 November 2010 - 05:47
I installed the lower version of the application with .exe and tried to upgrade it via .msi pf higher version.Then the error shown is attached below.
I was using below command line parametrs
msiexec.exe /i "xyz.msi" REINSTALLMODE=vomus REINSTALL=ALL
Thanks & Regards
Posted 15 November 2010 - 05:53
Posted 15 November 2010 - 12:22
Posted 27 January 2011 - 15:03
Are you sure the msiexec was executed with REINSTALLMODE=vomus, especially 'v', if that is missing you will get the error attached.
I have a question, is there a way to set REINSTALLMODE & REINSTALL within msi based on some condition. So that msi can be double clicked and work in either case of fresh & minor upgrade.
Posted 27 January 2011 - 16:42
Typically a setup.exe is used to detect whether it's an update and set the v accordingly.
Posted 28 January 2011 - 08:49
Why I raised this question is because, we have a deployment structure which is only aware of MSI and we thought of doing fresh, minor & major upgrades using single msi instead of msi & msp/exe.
126.96.36.199 version of msi is for
a. fresh installation
b. 188.8.131.52 -> 184.108.40.206 as minor upgrade
c. 220.127.116.11 -> 18.104.22.168 as major upgrade
I made changes within msi to achieve a & c, where b is where I got struck for deployment with REINSTALLMODE=vomus.
I thought, instead of doing major change in my deployment structure to make it aware of exe, change within msi will be considerably simple.
After looking at MSDN article about ReinstallMode Control Event (http://msdn.microsof...a371183(v=vs.85).aspx), I thought it is possible.
If I understand correctly, except option 'v' for REINSTALLMODE rest can be set using the Control Event or through CA within msi, is it so?
Posted 02 February 2011 - 11:02
Your options would be to use Major Upgrades also for case b. or use patches (.msp) for minor updates.