Errors during installation
Errors that you must correct can occur during installation. Many error messages contain enough information to correct the situation that caused the error. However, some error conditions require more information.
- Silent installation might exit with no error message displayed, but errors do exist in the log file.
- If silent installation exits with a zero return code, also check the log file for error messages.
- Windows
-
\<IM_DATA_DIR>\logs - Linux or AIX
-
/<IM_DATA_DIR>/logs
- If you get an error message about a disk or file system not having enough disk space available:
- Remove files to free up space, or add storage to the system to
expand the size of the file system.
Do not correct the problem while the installation program is running. Exit the installation program before you make the corrections, and restart the program after the corrections are made.
See Hardware requirements for information about disk space and other hardware requirements.
- If you install IBM Security Key Lifecycle Manager using an Exceed X Server on a local machine while exporting the display from a Linux system to the local machine, do not decline the license agreement.
- If you decline the license agreement, the installation program can be rendered unresponsive. Accept the license agreement, or use a Cygwin X Server or a Virtual Network Connection instead.
- Removing the
sklmdb31administrator using Windows user and group management tool requires removing the previous sklmdb301 subdirectory before reinstalling IBM Security Key Lifecycle Manager and DB2®. - During IBM Security Key Lifecycle Manager installation, you might
encounter a problem if you used the Windows user and group management tool to previously delete the
sklmdb31user ID as the Db2 administrator. Reinstalling IBM Security Key Lifecycle Manager then fails to install Db2.To fix the problem, take these steps:- Change to the appropriate subdirectory:
- Windows Server 2012: drive:\Users
- Remove the sklmdb301 subdirectory.
- Reinstall IBM Security Key Lifecycle Manager. The sklmdb301 subdirectory is not automatically removed when you use the Windows user and group management tool to delete the user account sklmdb301.
- Change to the appropriate subdirectory: