I have an installation which is chaining 3 msi files, using the Windows Installer 4.5 chaining feature, in InstallShield 2010.
Each of the msi files were created in Visual Studio setup projects. One of these installers, when run manually, is stating that it requires a reboot, and asks the user whether they want to do it or not.
The problem: ========================== The master installer is running the chained msi files in basic UI mode, so the above request is never seen.
This seems to be causing a problem, in that the installer runs, no apparent errors appear, then the final window of the master installer is showing the following text:
InstallShield Wizard Completed
The wizard was interrupted before B2c Software Suite could be completely installed.
Your system has not been modified. To complete installation at another time, please run setup again.
Click Finish to exit the wizard.
======================
Is there any way to detect that this might be the case, alert the user, or take the result code as an indication that the master installer must ask the user to reboot?
The current way InstallShield handles it (a) appears as though everything went OK if you just read the bold heading, and (b) doesn't give any clue as to why the installation was interrupted.
Reboots and chaining don't get along, and cause a rollback (resulting in the generic setup interrupted message). Perhaps you could pass in a REBOOT=Suppress or REBOOT=ReallySuppress to this chained msi to prevent this?
