IBM Security Identity Manager : Troubleshooting and support

Troubleshooting installation and configuration problems

This section describes solutions for installation and configuration problems.

Before you install IBM® Security Identity Manager Server:

• Read the troubleshooting tips in the "Installation Guide" and the "Configuration Guide".
• Review the known problems and solutions in the IBM Security Identity Manager Information Center. Some of the topics in the "Installation Guide" and the "Configuration Guide" are repeated in this section.
• Configure IBM Tivoli® Common Reporting to run on non-default ports if it is installed on the same system as IBM Security Identity Manager version 6.0 prerequisites. The default ports of IBM Tivoli Common Reporting are likely to conflict with ports of the installed products, which causes the IBM Tivoli Common Reporting installation to fail.

• Firewalls can block the IBM Security Identity Manager Server installation
  Stop all firewalls before initiating the product installation and configuration to prevent problems.

• User IDs must be in the administrator group to start an installation
  The DB2 Universal Database™ configuration can fail due to restrictions on the privileges of and the characters in the user ID.

• Microsoft Windows Terminal Server License server prevents an IBM Security Identity Manager installation
  Do not install the product with a DB2 Universal Database on a workstation with a Microsoft Windows Terminal Server License server installation.

• Middleware configuration utility fails to catalog LDAP database instance node
  If the middleware configuration utility fails to configure the LDAP instance for IBM Security Identity Manager, check the error messages in the cfg_itim_mw.log file.

• Entries in the services file prevent reinstalling the DB2 Universal Database
  When you uninstall DB2 Universal Database, some port entries are not deleted. If you attempt to reinstall the database, the installation fails.

• LDAP port value is already in use for an initial installation of IBM Security Identity Manager
  IBM Tivoli Directory Server uses the default port value 389.

• Backspace key deletes characters (SUSE Linux only)
  The Backspace key might work like a Delete key on SUSE Linux systems when you use the user interface for installation, uninstallation, or middleware configuration tasks.

• Error messages do not display when using an emulator program to install IBM Security Identity Manager
  If you use an emulator program such as the X Window System server or Virtual network computing (VNC) to access a remote computer to perform a separate installation of middleware or IBM Security Identity Manager Server, you might not see all the error messages that an installation problem can generate.

• tzmappings: illegal format at near line 11 error message
  The tzmappings: Illegal format at near line 11 message might be displayed during installation and configuration. You can ignore it.

• Messaging engines do not start after installation
  On systems that run DB2 Universal Database, the IBM Security Identity Manager messaging engines might not start.

• The temp directory is not deleted after installation (Microsoft Windows only)
  The temp directory is not deleted after the installation. You must manually delete it.

• A java.lang exception occurs in a cluster environment
  A java.lang exception occurs during installation in a cluster environment. You can ignore the exception. It does not affect the IBM Security Identity Manager installation or operation.

• Cannot uninstall interim fixes or fix packs
  IBM Security Identity Manager cannot uninstall interim fixes or fix packs.

• Cannot log on to the IBM Security Identity Manager Console
  You cannot log on to the IBM Security Identity Manager Console. This problem occurs if you rerun the runConfig utility on IBM Security Identity Manager that is configured to access LDAP server with SSL.