Unable to install APM EM - disk space check fails
Article ID: 197260
Updated On:
Products
Issue/Introduction
It is not clear why the disk check is failing in the middle of the installation since the logs show sufficient space at the beginning of the process.
From install log, in this example:
...
Space needed to complete the self-extraction: 8124110 blocks
Available space: 226369536 blocks
Available blocks: 226369536 Needed blocks: 8124110 (block = 512 bytes)
Cause
The disk space check is a check that InstallAnywhere does at the beginning, and also during the installation depending on certain criteria, however, this specific issue is related to a defect in Flexera or InstallAnywhere:
https://community.flexera.com/t5/InstallAnywhere-Knowledge-Base/Disk-Space-Check/ta-p/3452
Environment
Release : 10.7
Resolution
Workaround:
Set the environment variable CHECK_DISK_SPACE=OFF before launching the installer to avoid this issue.
From https://community.flexera.com/t5/InstallAnywhere-Knowledge-Base/Disk-Space-Check/ta-p/3452
- On MacOS, since there is no equivalent to an environment variable the PropertyManager method is ignored. The only way to control the action is through the IA Designer by setting the InstallAnywhere variable.
-
On Windows the simplest way to utilize the Environment Variable method is to open a Command Prompt and type the following:
C:\> set CHECK_DISK_SPACE=OFF
(or "ON", as needed). Then the installer should be run from this window (i.e. in the same "scope"). -
On UNIX in csh/tcsh set the variable this way:
% setenv CHECK_DISK_SPACE OFF
(or ON, as needed) and run the installer within that shell. -
On UNIX in sh/ksh/bash set the variable this way:
$ export CHECK_DISK_SPACE=OFF
(or ON, as needed) and run the installer within that shell.
Additional Information
Other similar InstallAnyhere issues:
Installer cannot launch in localized environment (e.g. LANG=ja_JP.UTF-8)
https://knowledge.broadcom.com/external/article/36503/installer-cannot-launch-in-localized-env.html
Feedback
