cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
unnic_arcanane
Level 4

BUG : InstallShield 2019 R2 Dev IDE crashes during Build, when low disk space!

BUG : InstallShield 2019 R2 Dev IDE crashes during Build, when low disk space!

When the disk-space is low in the drive where InstallShield Dev IDE is installed, the  Dev IDE crashes when build is triggered from the menu.

No log files generated, no warning messages on low diskspace and No alerts.

Had two Webex sessions with support professional, who couldn't find the root cause in the absence of Logs, warnings.

Please find the attached screenshots.

Another Issue:

InstallShield 2019 R2 and R3 Installers also getting 'interrupted' and fails to upgrade/repair when diskspace is low. No warnings, No logs!

We developers use the the InstallScript function, GetDiskInfo(). By the by, do you know what is it for?

https://docs.flexera.com/installshield25helplib/installshield25helplib.htm#Subsystems/LangRef/helplibrary/LangrefGetDiskInfo.htm?Highlight=GetDiskInfo

 

Labels (1)
0 Kudos
(3) Replies
banna_k
Revenera
Revenera

For Systems Running InstallShield

InstallShield runs on the latest versions of these operating systems, fully updated with the most recent patches and service packs.

Item

Description

Processor

Pentium III-class PC (500 MHz or higher recommended)

RAM

256 MB of RAM (512 MB preferred)

Hard Disk

750 MB free space

Display

Designed for XGA resolution at 1024 × 768 or higher

 

https://docs.flexera.com/installshield25helplib/rn/ReleaseNotes.htm#sysreq

 
0 Kudos

Hi banna_k

Crash from the application is not the right way to behave. The tool should warn / throw error message/ log which are the graceful ways to report in such situations.

Otherwise user will break his head troubleshooting.

For e.g. InstallShield Support staff was clueless on this crash after Webex sessions.

Thanks.
0 Kudos

Hi @unnic_arcanane,

We have a case reported on this issue, and it will be addressed in the future releases.

You can track the issue using the IOJ-1720983

  

0 Kudos