BkSetupDev
Level 4

ISInstallPrerequisites ends with 1603

On some systems our setups ends with 1603 in CA ISInstallPrerequisites. We got some logs from our custumers:

 

InstallShield 18:25:08: *** Launching prerequisites (): C:\Users\Hans Juerg Eggimann\Desktop\TC31-FULL-Setup.3.1.4024.0.exe /embed"{3809E5BF-FB49-46C5-8013-DD20378517B6}" /hide_splash /hide_progress /runprerequisites"XAR64,TC3ADS64,TC3IO64,TC3CPP64,TC3MC64,TC3MC64Setup,TC3PLC64,TCADSAPI,XAE,VSIntegration,XAESetups,XAEUserFiles,XARCOMMON,XARUserFiles" /l1033
MSI (c) (6C!CC) [18:25:08:248]: Closing MSIHANDLE (2818) of type 790531 for thread 16332
MSI (c) (6C!CC) [18:25:08:923]: Creating MSIHANDLE (2819) of type 790531 for thread 16332
InstallShield 18:25:08: *** Prerequisites complete; return code -858993460
MSI (c) (6C!CC) [18:25:08:923]: Closing MSIHANDLE (2819) of type 790531 for thread 16332
MSI (c) (6C!CC) [18:25:08:923]: Creating MSIHANDLE (2820) of type 790531 for thread 16332
InstallShield 18:25:08: Destroyed Window {3809E5BF-FB49-46C5-8013-DD20378517B6}
MSI (c) (6C!CC) [18:25:08:923]: Closing MSIHANDLE (2820) of type 790531 for thread 16332
CustomAction ISInstallPrerequisites returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)
MSI (c) (6C:50) [18:25:08:923]: Closing MSIHANDLE (150) of type 790542 for thread 12244
Action ended 18:25:08: ISInstallPrerequisites. Return value 3.

 

InstallShield 11:15:22: *** Launching prerequisites (): E:\Tools\!Industrie\Beckhoff\TwinCAT_SETUP\TwinCAT_3\Software\TE-Engineering\TC31-FULL-Setup.3.1.4024.7.exe /embed"{07011ED2-4FA6-481E-933D-A71426552319}" /hide_splash /hide_progress /runprerequisites"XAR64,TC3ADS64,TC3IO64,TC3CPP64,TC3MC64,TC3MC64Setup,TC3PLC64,TCADSAPI,XAE,TcXAE.Shell,VSIntegration,XAESetups,XAEUserFiles,XARCOMMON,XARUserFiles" /l1033
MSI (c) (34!F8) [11:15:22:946]: Closing MSIHANDLE (2714) of type 790531 for thread 6136
MSI (c) (34!F8) [11:15:23:740]: Creating MSIHANDLE (2715) of type 790531 for thread 6136
InstallShield 11:15:23: *** Prerequisites complete; return code -858993460
MSI (c) (34!F8) [11:15:23:740]: Closing MSIHANDLE (2715) of type 790531 for thread 6136
MSI (c) (34!F8) [11:15:23:740]: Creating MSIHANDLE (2716) of type 790531 for thread 6136
InstallShield 11:15:23: Destroyed Window {07011ED2-4FA6-481E-933D-A71426552319}
MSI (c) (34!F8) [11:15:23:741]: Closing MSIHANDLE (2716) of type 790531 for thread 6136
CustomAction ISInstallPrerequisites returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)
MSI (c) (34:60) [11:15:23:743]: Closing MSIHANDLE (150) of type 790542 for thread 13068
Action ended 11:15:23: ISInstallPrerequisites. Return value 3.

 

InstallShield 14:15:27: *** Launching prerequisites (): C:\Users\Varshini KILLIVALAVA\Desktop\TC31-FULL-Setup.3.1.4024.7.exe /embed"{A908E7E4-452A-496D-A128-272E577FAA6F}" /hide_splash /hide_progress /runprerequisites"XAR64,TC3ADS64,TC3IO64,TC3CPP64,TC3MC64,TC3MC64Setup,TC3PLC64,TCADSAPI,XAE,TcXAE.Shell,VSIntegration,XAESetups,XAEUserFiles,XARCOMMON,XARUserFiles" /l1033
MSI (c) (88!BC) [14:15:27:535]: Closing MSIHANDLE (2801) of type 790531 for thread 15804
MSI (c) (88!BC) [14:15:47:804]: Creating MSIHANDLE (2802) of type 790531 for thread 15804
InstallShield 14:15:47: *** Prerequisites complete; return code -858993460
MSI (c) (88!BC) [14:15:47:805]: Closing MSIHANDLE (2802) of type 790531 for thread 15804
MSI (c) (88!BC) [14:15:47:806]: Creating MSIHANDLE (2803) of type 790531 for thread 15804
InstallShield 14:15:47: Destroyed Window {A908E7E4-452A-496D-A128-272E577FAA6F}
MSI (c) (88!BC) [14:15:47:807]: Closing MSIHANDLE (2803) of type 790531 for thread 15804
CustomAction ISInstallPrerequisites returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)
MSI (c) (88:30) [14:15:47:812]: Closing MSIHANDLE (237) of type 790542 for thread 15468
Action ended 14:15:47: ISInstallPrerequisites. Return value 3.

 
Is there any way to detect, which prerequisite setup is failing? Eventlog does not help 😞 

Labels (1)
0 Kudos
2 Replies
Jenifer
Flexera Alumni

Hi @BkSetupDev ,

  • Error code 1603 is a Windows installer's generic error code when custom action throws any error/exception. Windows installer does not show actual error/exception in installer logs.
  • To verify actual error/exception we have to debug the custom action.Please verify if custom action is throwing any error/exception.
  • As well were you able to install the above mentioned pre-requisite independently?

Thanks,

Jenifer

0 Kudos

There are a lot of (feature) prerequisites we are installing (depending on the system up to 15). Is there a way to detect, which of this prerequisite setups is failing?

0 Kudos