cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
hirosea
Level 3

Behavior of the SdFinishReboot function in the nstallShield 2020 R3 InstallScript project.

I created the following script in the InstallScript project of InstallShield 2020 R3 to create the installer.

When I start the installer, select Reboot in the dialog displayed by the SdFinishReboot function, and end the installer,
When I log in after restarting the OS, the upgrade installation will start automatically.

In previous versions of InstallShield (2016), the installation did not start when logging in after restarting the OS.

1. Is this behavior a bug in InstallShield 2020 R3? Is it a specification change?
2. If it is a specification change, what kind of change is required to make it work with the previous version of InstallShield 2016?

 

 

//===========================================================================
//
// FileName: Setup.rul
//
//===========================================================================

#include "ifx.h"


//---------------------------------------------------------------------------
// OnFirstUIAfter
//
// First Install UI Sequence - After Move Data
//
// The OnFirstUIAfter event called by OnShowUI after the file transfer
// of the setup when the setup is running in first install mode. By default
// this event displays UI that informs the end user that the setup has been
// completed successfully.
//
// Note: This event will not be called automatically in a
// program...endprogram style setup.
//---------------------------------------------------------------------------
function OnFirstUIAfter()
STRING szTitle, szMsg1, szMsg2, szOpt1, szOpt2;
NUMBER bvOpt1, bvOpt2;
begin

ShowObjWizardPages(NEXT);

szTitle = "";
szMsg1 = "";
szMsg2 = "";
szOpt1 = "";
szOpt2 = "";
bvOpt1 = FALSE;
bvOpt2 = FALSE;

SdFinishReboot ( szTitle , szMsg1 , SYS_BOOTMACHINE , szMsg2 , 0 );
end;

//---------------------------------------------------------------------------
// OnMaintUIAfter
//
// The OnMaintUIAfter event called by OnShowUI after the file transfer
// of the setup when the setup is running in maintenance mode. By default
// this event displays UI that informs the end user that the maintenance setup
// has been completed successfully.
//
// Note: This event will not be called automatically in a
// program...endprogram style setup.
//---------------------------------------------------------------------------
function OnMaintUIAfter()
STRING szTitle, szMsg1, szMsg2, szOpt1, szOpt2;
NUMBER bvOpt1, bvOpt2;
begin

ShowObjWizardPages(NEXT);

// Added - Version 9.5 - Use appropriate strings for complete
// uninstall.
if( REMOVEALLMODE ) then
szTitle = SdLoadString(IFX_SDFINISH_REMOVE_TITLE);
szMsg1 = SdLoadString(IFX_SDFINISH_REMOVE_MSG1);
else
szTitle = SdLoadString(IFX_SDFINISH_MAINT_TITLE);
szMsg1 = SdLoadString(IFX_SDFINISH_MAINT_MSG1);
endif;

szMsg2 = "";
szOpt1 = "";
szOpt2 = "";
bvOpt1 = FALSE;
bvOpt2 = FALSE;

SdFinishReboot ( szTitle , szMsg1 , SYS_BOOTMACHINE , szMsg2 , 0 );
end;

Labels (1)
(4) Replies
nsanderson
Level 3

Hi,

We're suffering from the same problem, though we're only upgrading from 2019 to 2020 R3.

The installer produced by 2020 R3 has a strange issue where it, after a reboot & post a successful install, relaunches itself immediately into maintenance mode after the user logs back in.

The same .ism file used in 2019 does not display this odd behaviour.  I also wonder if the SdFinishReboot function is not working as it should.

SpiderLily1
Level 6

Hello,

I have the same problem. Multiple users reported this issue today.

0 Kudos
varul
Revenera Moderator Revenera Moderator
Revenera Moderator

Hi,

 The issue has been already reported and it will be fixed in our next release IS2021,  

As a work around you use "BATCH_INSTALL = TRUE" in your script  and it will  fix launch the setup.exe in maintenance mode after reboot.

 

 

0 Kudos

Hi SpiderLily1,

We've dropped back to using InstallShield 2019 (had to modify the 2019 script again) and had to forgo the Server 2019 OS check (thankfully it still identifies itself as a Windows 10 variant) as the BATCH_INSTALL = TRUE didn't seem to sort our issue.

Looking forward to trying IS2021 whenever it drops.

0 Kudos