IBM 51 - Manual (Page 67)

Chapter 7. Common problems and known limitations in Tivoli
Intelligent Orchestrator
This chapter describes how to recover from the following types of Tivoli Intelligent
Orchestrator problems, and describes a number of known limitations for the Tivoli
Intelligent Orchestrator reports:
v “Problems with installation”
v “Problems with logging in” on page 62
v “Problems with workflows” on page 64
v “Other common problems” on page 68
v “Known report limitations” on page 77
Problems with installation
This section includes troubleshooting scenarios for the following problems:
v “In Linux, you cannot create the user tioadmin”
v “The system cannot connect to the IBM Tivoli Directory Server during the Tivoli
Intelligent Orchestrator installation” on page 56
v “The installation of the DB2 Universal Database Client on Windows 2003 system
fails” on page 56
v “Installing the common agent and the agent manager is not supported” on page
57
v “The system cannot connect to the database server during the Tivoli Intelligent
Orchestrator installation” on page 57
v “The Microsoft Active Directory installation fails” on page 57
v “The Microsoft Active Directory installation fails with invalid certificate value”
on page 58
v “The silent installation program for Tivoli Intelligent Orchestrator exits before
the installation is completed” on page 58
v “Environment variables not set for user tioadmin” on page 58
v “The installation of IBM Tivoli NetView on Windows fails if the password for
creating a user account does not meet the system requirements” on page 59
v “The agent manager installation fails during the Tivoli Intelligent Orchestrator
installation” on page 59
v “An error occurs when running the rpm -qa command after the DB2 Universal
Database, IBM Tivoli Directory Server, and WebSphere Application Server
prerequisites are installed on Linux” on page 62
In Linux, you cannot create the user tioadmin
The installation appears to proceed successfully to completion, but when you check
to find the user tioadmin , it has not been created.
Cause
This is a known InstallShield Multi-Platform issue. Because the user tioadmin is
not created, the server environment is unstable. Various elements of the installation
expect tioadmin and require it to exist. For example, because WebSphere
Application Server is configured to start with tioadmin , WebSphere Application
Server cannot start.
© Copyright IBM Corp. 2003, 2006 55