This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Revenera Community
- :
- InstallShield
- :
- InstallShield Forum
- :
- Re: Major Upgrade Issue???
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Mar 24, 2011
06:02 PM
Major Upgrade Issue???
We have not had issues with our installs performing Major Upgrades over previous versions when we update the version number and the Product code, but I seem to be running into that now.
According to the log it finds the previous version:
InstallShield 16:47:24: UpgradeCode: {6C72A6DB-5E47-4B2D-B398-A5CB8C3E1FB7} MinVersion: MaxVersion: 10.8.126.0 Language: Attributes: 256
InstallShield 16:47:24: SMART Product Drivers {4CE6C6E8-0DAD-4757-86ED-7FB4035BA98B} 0 10.7.182.1 ***Related***
And it does set the major upgrade property:
Action start 16:47:25: FindRelatedProducts.
MSI (s) (C0:38) [16:47:25:575]: Using cached product context: machine assigned for product: 8E6C6EC4DAD0757468DEF74B30B59AB8
MSI (s) (C0:38) [16:47:25:575]: Using cached product context: machine assigned for product: 8E6C6EC4DAD0757468DEF74B30B59AB8
MSI (s) (C0:38) [16:47:25:575]: Using cached product context: machine assigned for product: 8E6C6EC4DAD0757468DEF74B30B59AB8
MSI (s) (C0:38) [16:47:25:591]: PROPERTY CHANGE: Adding DETECTMAJORUPGRADE property. Its value is '{4CE6C6E8-0DAD-4757-86ED-7FB4035BA98B}'.MSI (s) (C0:38) [16:47:25:591]: Using cached product context: machine assigned for product: 8E6C6EC4DAD0757468DEF74B30B59AB8
MSI (s) (C0:38) [16:47:25:591]: Using cached product context: machine assigned for product: 8E6C6EC4DAD0757468DEF74B30B59AB8
MSI (s) (C0:38) [16:47:25:591]: Using cached product context: machine assigned for product: 8E6C6EC4DAD0757468DEF74B30B59AB8
Action ended 16:47:25: FindRelatedProducts. Return value 1.
But then when it gets to the RemoveExistingProducts it has the following:
MSI (s) (C0:38) [16:47:25:888]: Doing action: RemoveExistingProducts
Action start 16:47:25: RemoveExistingProducts.
MSI (s) (C0:38) [16:47:25:888]: Skipping RemoveExistingProducts action: current configuration is maintenance mode or an uninstallAction ended 16:47:25: RemoveExistingProducts. Return value 0.
What would be causing the install to think that it can skip this action as it thinks that it is now a maintenance or uninstall mode?
any help would be appreciated.
According to the log it finds the previous version:
InstallShield 16:47:24: UpgradeCode: {6C72A6DB-5E47-4B2D-B398-A5CB8C3E1FB7} MinVersion: MaxVersion: 10.8.126.0 Language: Attributes: 256
InstallShield 16:47:24: SMART Product Drivers {4CE6C6E8-0DAD-4757-86ED-7FB4035BA98B} 0 10.7.182.1 ***Related***
And it does set the major upgrade property:
Action start 16:47:25: FindRelatedProducts.
MSI (s) (C0:38) [16:47:25:575]: Using cached product context: machine assigned for product: 8E6C6EC4DAD0757468DEF74B30B59AB8
MSI (s) (C0:38) [16:47:25:575]: Using cached product context: machine assigned for product: 8E6C6EC4DAD0757468DEF74B30B59AB8
MSI (s) (C0:38) [16:47:25:575]: Using cached product context: machine assigned for product: 8E6C6EC4DAD0757468DEF74B30B59AB8
MSI (s) (C0:38) [16:47:25:591]: PROPERTY CHANGE: Adding DETECTMAJORUPGRADE property. Its value is '{4CE6C6E8-0DAD-4757-86ED-7FB4035BA98B}'.MSI (s) (C0:38) [16:47:25:591]: Using cached product context: machine assigned for product: 8E6C6EC4DAD0757468DEF74B30B59AB8
MSI (s) (C0:38) [16:47:25:591]: Using cached product context: machine assigned for product: 8E6C6EC4DAD0757468DEF74B30B59AB8
MSI (s) (C0:38) [16:47:25:591]: Using cached product context: machine assigned for product: 8E6C6EC4DAD0757468DEF74B30B59AB8
Action ended 16:47:25: FindRelatedProducts. Return value 1.
But then when it gets to the RemoveExistingProducts it has the following:
MSI (s) (C0:38) [16:47:25:888]: Doing action: RemoveExistingProducts
Action start 16:47:25: RemoveExistingProducts.
MSI (s) (C0:38) [16:47:25:888]: Skipping RemoveExistingProducts action: current configuration is maintenance mode or an uninstallAction ended 16:47:25: RemoveExistingProducts. Return value 0.
What would be causing the install to think that it can skip this action as it thinks that it is now a maintenance or uninstall mode?
any help would be appreciated.
(3) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Mar 25, 2011
03:07 AM
Do you use 'Detect Only' setting in upgrade view?
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Mar 25, 2011
06:37 AM
Nope, that has not been changed it is still set to No.
Could there have been a action in the sequence table that is out of place? This particual install project had it's RemoveExistingProducts action move to just after the CostInitialize action. So I am just wondering if something got moved that was not suppose to have been moved and therefore causing this issue?
Could there have been a action in the sequence table that is out of place? This particual install project had it's RemoveExistingProducts action move to just after the CostInitialize action. So I am just wondering if something got moved that was not suppose to have been moved and therefore causing this issue?
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Mar 25, 2011
05:01 PM
Maintenance mode is indicated by the presence of a product code and package code registered with Windows Installer on a target machine (product version is then associated with this). If the product code/package code combination for the MSI that you are running is registered on the target machine you are running on, the installation will run in maintenance mode. Maintenance mode can typically also be seen in a log indications like the following:
A first time install log (as is the case in a major upgrade) would have information similar to the following:
Having the RemoveExistingProducts action sequenced out of place, while not necessarily working correctly, shouldn't cause the log line that you are seeing.
Note another thing to ensure has changed is the package code for the MSI that is running. If the product code changes but the package code does not, for whatever reason, MSI operates in a rather strange first time install/maintenance state that does not run the installation correctly.
MSI (c) (68:48) [16:54:10:374]: Product registered: entering maintenance mode
MSI (c) (68:48) [16:54:10:374]: Determined that existing product (either this product or the product being upgraded with a patch) is installed per-machine.
MSI (c) (68:48) [16:54:10:374]: PROPERTY CHANGE: Adding ProductState property. Its value is '5'.
...
MSI (c) (68:48) [16:54:10:389]: PROPERTY CHANGE: Adding Installed property. Its value is '2011/03/25 11:53:34'
A first time install log (as is the case in a major upgrade) would have information similar to the following:
MSI (c) (60:48) [16:53:41:170]: Product not registered: beginning first-time install
MSI (c) (60:48) [16:53:41:170]: PROPERTY CHANGE: Adding ProductState property. Its value is '-1'.
Having the RemoveExistingProducts action sequenced out of place, while not necessarily working correctly, shouldn't cause the log line that you are seeing.
Note another thing to ensure has changed is the package code for the MSI that is running. If the product code changes but the package code does not, for whatever reason, MSI operates in a rather strange first time install/maintenance state that does not run the installation correctly.
