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
- :
- Major Upgrade patch from IS8 to IS2008 failling
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
‎Aug 28, 2008
08:11 AM
Major Upgrade patch from IS8 to IS2008 failling
Hi, I am having issue with my project upgrades.I even tried on a dummy project and it's doesnt work either. Here is the detail:
Project A: Created in IS8, version 1.0000
Project B: Copied project A and upgrade it to IS2008, Version 1.1000, also modified the only component ( add one file and update one)
I have changed the Project B's product code and keep the upgrade code as same as Project A. Created a Major Upgrade Item and a patch configuration. I believe this is the correct step to do the Major upgrade.
However, the build of the patch failed, error saying "Since MSI 3.0 will block installation of major upgrade patches with sequencing information, creation of such patches is blocked.", I then disabled the option ( Use default patch sequencing) in the Sequence tab in patch configuration, the build worked
When I trying to apply the patch( update.exe) to the target machine, it failed after the initialization, error 1628: Failed to complete installation.
Also, I tried run the setup.exe in Project B and it will show the same UI as clean install and do the major upgrade.
So, my question is, is there any way I can get the updates.exe( the patch) working?
Thank you in advance 🙂
Project A: Created in IS8, version 1.0000
Project B: Copied project A and upgrade it to IS2008, Version 1.1000, also modified the only component ( add one file and update one)
I have changed the Project B's product code and keep the upgrade code as same as Project A. Created a Major Upgrade Item and a patch configuration. I believe this is the correct step to do the Major upgrade.
However, the build of the patch failed, error saying "Since MSI 3.0 will block installation of major upgrade patches with sequencing information, creation of such patches is blocked.", I then disabled the option ( Use default patch sequencing) in the Sequence tab in patch configuration, the build worked
When I trying to apply the patch( update.exe) to the target machine, it failed after the initialization, error 1628: Failed to complete installation.
Also, I tried run the setup.exe in Project B and it will show the same UI as clean install and do the major upgrade.
So, my question is, is there any way I can get the updates.exe( the patch) working?
Thank you in advance 🙂
(3) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Aug 28, 2008
03:00 PM
Performing a major upgrade through a patch is generally not recommended (please see http://msdn.microsoft.com/en-us/library/aa369786.aspx) and should typically be applied with a full installation package.
In addition, it looks like you are using an InstallScript MSI project (based on the 1628 error). Due to additional complexity inherent in InstallScript MSI projects, and the change in InstallShield versions used to build the different product versions (starting with InstallShield 12, the InstallScript engine was re-architected away from how it worked in pre-12 versions to increase stability), a full major upgrade should be used to ensure the product upgrades successfully. A full upgrade provides for an installation with fewer possible points of failure.
In addition, it looks like you are using an InstallScript MSI project (based on the 1628 error). Due to additional complexity inherent in InstallScript MSI projects, and the change in InstallShield versions used to build the different product versions (starting with InstallShield 12, the InstallScript engine was re-architected away from how it worked in pre-12 versions to increase stability), a full major upgrade should be used to ensure the product upgrades successfully. A full upgrade provides for an installation with fewer possible points of failure.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Aug 28, 2008
05:41 PM
Thank you very much for you reply, I have persuaded my boss to go for the setup.exe and using the clean install screen. However, there still some problem, the uninstall will leave some file untouched and also it will create two entried in the Add/Remove Progam with same name.
Could you please advise about that? Thank you
Could you please advise about that? Thank you
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Aug 29, 2008
09:45 AM
Never mind the above issue, I have solved them now. By deleting them using the script
However, i still trying to make some improvement of the major upgrade, like automatically detect the feature installed on previous version and install the same of the new version. Eg, project Old have three option, client, server, complete. and the installation was server, how can the major upgrade using setup.exe to not show the feature selection screen but only auto-reinstall the server but not other option.
Hope that is clear....
However, i still trying to make some improvement of the major upgrade, like automatically detect the feature installed on previous version and install the same of the new version. Eg, project Old have three option, client, server, complete. and the installation was server, how can the major upgrade using setup.exe to not show the feature selection screen but only auto-reinstall the server but not other option.
Hope that is clear....