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: Installation does not go into maintenance mode
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
‎Dec 01, 2008
04:45 PM
Installation does not go into maintenance mode
Hello,
I am having a problem with my installation packages that I have upgraded to IS 2009. In situations where I expect the install to go into maintenance mode, I am instead prompted with "another version of this product is already installed..." and am instructed to first remove the previous install using Add/Remove programs.
It is my understanding that this is because the Product Code remains the same, and the Package Code has been changed. However, these both remain unchanged in my setup. What does change is the version number.
Can someone please suggest how I can suppress this prompt, and allow the install to go into maintenance mode?
Thanks very much...
I am having a problem with my installation packages that I have upgraded to IS 2009. In situations where I expect the install to go into maintenance mode, I am instead prompted with "another version of this product is already installed..." and am instructed to first remove the previous install using Add/Remove programs.
It is my understanding that this is because the Product Code remains the same, and the Package Code has been changed. However, these both remain unchanged in my setup. What does change is the version number.
Can someone please suggest how I can suppress this prompt, and allow the install to go into maintenance mode?
Thanks very much...
(2) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Dec 02, 2008
05:55 PM
If you look in Media > Releases > product config name, the Generate Package Code setting is normally set to Yes, which generates a new package code GUID during every build, which overrides the hard-coded value in General Information > Product Properties.
As a rule, the package code should be different for any two different MSI databases, including just a version-number change. Perhaps a small update or minor upgrade is what you want?
As a rule, the package code should be different for any two different MSI databases, including just a version-number change. Perhaps a small update or minor upgrade is what you want?
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Dec 02, 2008
06:58 PM
Thanks, Robert. Yes, I may need to re-configure the installation packages to account for minor upgrades, but I'll need to coordinate that with documentation folks. 🙂
![](/skins/images/8CE4FAD0DE6F3A6F9D0567434D2D2DAE/responsive_peak/images/icon_anonymous_message.png)