Server installation and uninstallation return codes
If the server installation or uninstallation fails, check the return code to learn about the reason of the problem and possible solutions.
| Return code | Possible cause and solutions |
|---|---|
| 0 | The server was installed successfully. |
| 5 | An unexpected error occurred. |
| 6 | An unexpected exception occurred. |
| 7 | An internal error occurred. The installer failed to save the file with information that was collected or generated during the preinstallation stage. |
| 8 | The installation was canceled. |
| 9 | A post-installation step was terminated before it was finished. Problems with resuming the installation might occur. |
| 11 | Validation of the communication ports failed. Either the same port is specified for more than one parameter or the specified port is in use. If you want to specify a port that is temporarily used but will be available later, set the RSP_DISABLE_COMMUNICATION_WARNINGS parameter to true. For more information, see: Server installation response file. |
| 13 | Validation of the license agreement, or the file path failed. Either the
license agreement was not accepted, the path to the installation response file is not absolute, or
the command is too long. To accept the license agreement, set the
RSP_LICENSE_ACCEPTED parameter to true. If the problem persists, ensure that you provided an absolute path to the response file, or move the files to a different directory to shorten the command, for example /root/BFI or C:\BFI. |
| 14 | There is not enough space for the installation. To check how much free disk space is required to proceed with the installation, see the following installation log: installation_dir/BFI_9.2_timestamp_logs.tar.gz. |
| 18 | Validation of the installation path failed. The specified path is incorrect or the installation directory is read-only. |
| 20 | An unknown response file parameter was specified. Remove the parameter from the installation response file. |
| 21 | The response file was not found. It is either empty or contains Windows™ line endings instead of UNIX™ ones. |
| 23 | The command-line interface or another application from the BigFix Inventory installation path is still running. End the process manually or set the RSP_AUTO_CLOSE_PROCESSES parameter to true. |
| 26 | An internal error occurred. Creation of the log directory failed. |
| 27 | It was impossible to recognize the environment, for example, installed products. |
| 28 | The upgrading scenario is not supported. |
| 29 | A part of BigFix Inventory that is already installed, is corrupted. |
| 30 | The uninstallation wizard could not find product information in registries. BigFix Inventory was already uninstalled. |
| 31 | The host name was not obtained. To verify the host name, in the command-line
interface, enter the following command:
|
| 32 | An exception was detected while reading the setup.ini file. |
| 33 | An attempt of creating a log directory in the installation path failed because a file called BFI9.2 already exists. To proceed with the installation, delete the file. |
| 34 | The log directory is read-only. |
| 35 | The system TEMP environment variable does not point to a
valid directory. |
| 36 | Installation in console mode is not supported. Use interactive or silent mode. |
| 37 | The required resources could not be extracted from the installation image. |
| 38 | The required resources could not be found inside the installation image. |
| 41 | The post-installation failed. Tip: If the issue occurs when upgrading BigFix Inventory
server using a fixlet, and the fixlet is no longer relevant, resume the installation in
interactive mode. One of possible causes of this problem is that a folder or a log file
from BigFix Inventory installation folder is open in an external application or there is a
command line running, which locks the resource and prevents the upgrade
operation.
|
| 42 | Another instance of the installer is already running. |
| 46 | The post-installation was interrupted. |
| 50 | Resuming a failed installation in silent mode is not supported. |
| 55 | All elements of the infrastructure are already installed. |
| 59 | An internal error occurred. Contact IBM® support. |
| 74 | The previous installation or upgrade has not been finished successfully. |
| 208 | The installation could not finish because of the NOEXEC on
the tmp directory. If all installation steps are completed, no further action
is required. Otherwise, remove NOEXEC from the tmp directory
or specify a new tmp directory in the following environment variable:
IATEMPDIR. For example, mkdir /root/Install_tmp; export
IATEMPDIR=/root/Install_tmp. Next, repeat the installation. |
| 214 | The uninstallation process could not connect to the X server. Verify that the
DISPLAY variable is properly set and points to a working X server. |