Filter
Top Products
The silent installation program for Tivoli
Intelligent Orchestrator exits before the
installation is completed . . . . . . . . .58
Environment variables not set for user tioadmin 58
The installation of IBM Tivoli NetView on
Windows fails if the password for creating a user
account does not meet the system requirements .59
The agent manager installation fails during the
Tivoli Intelligent Orchestrator installation . . .59
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 . . . . . . . . . . . . . . .62
Problems with logging in . . . . . . . . . .62
You cannot log in . . . . . . . . . . .62
You cannot change your password . . . . .63
Problems with workflows . . . . . . . . .64
DB2 Universal Database errors occur when you
deploy resources . . . . . . . . . . . .64
DB2 Universal Database creates a database state
error . . . . . . . . . . . . . . . .64
DB2 Universal Database deadlocks occur when
the system runs a logical operation . . . . .65
Shell command error: Resource temporarily
unavailable . . . . . . . . . . . . .65
Shell command error: Exit value=1, Error
stream=", Result stream="no bash in ..." . . . .65
IBM Tivoli Software Support personnel have
requested a copy of a workflow . . . . . .65
A workflow does not install . . . . . . . .67
Cannot run workflows if the PS1 environment
variable is altered . . . . . . . . . . .68
Other common problems . . . . . . . . . .68
On Windows, Tivoli Intelligent Orchestrator does
not start . . . . . . . . . . . . . .69
Problems occur when administering Tivoli
Intelligent Orchestrator from the Web interface
while a local firewall is enabled . . . . . .69
Incorrect SOAP parameters generate detailed
Java exception messages . . . . . . . . .70
XML import does not work properly . . . . .70
DB2 Universal Database does not work properly
with terminal server . . . . . . . . . .71
On UNIX, Tivoli Intelligent Orchestrator logs fill
up the file system . . . . . . . . . . .71
On Windows 2000, the embedded messaging
feature does not work . . . . . . . . . .71
WebSphere Application Server on Linux remains
paused when you try to stop the JMS pub sub
broker . . . . . . . . . . . . . . .72
On Windows, the remote connection to the
database hangs when the database server is on a
multiprocessor machine . . . . . . . . .72
For languages other than English, the text in CSV
reports imported in Microsoft Excel is garbled . .73
An error occurs if you use special characters to
create a new user or security role . . . . . .74
Common agents unable to communicate with the
agent manager . . . . . . . . . . . .75
Limitations when trying to manually associate a
discovered software resource with a software
definition . . . . . . . . . . . . . .75
Some patch installations might fail when trying
to perform a multiple patch installation . . . .76
There is a maximum size for returnResult
parameter storage . . . . . . . . . . .76
Device Manager limitations . . . . . . . . .76
Running lightweight management server with
DB2 Universal Database generates exceptions . .76
Agent receives an HTTP Unauthorized (401)
response code . . . . . . . . . . . .77
Known report limitations . . . . . . . . . .77
Running any report with too many objects
selected fails . . . . . . . . . . . . .77
Chapter 8. Troubleshooting the agent
manager . . . . . . . . . . . . . .79
Log files for the agent manager . . . . . . . .79
Packaging the log files . . . . . . . . . .79
Locating the installation log files . . . . . .79
Locating the uninstallation log files . . . . .81
Locating the remote registry logs . . . . . .81
Locating the runtime log files . . . . . . .82
Locating the DB2 Universal Database runtime
logs . . . . . . . . . . . . . . . .82
Determining the version of agent manager . . . .83
Installation and uninstallation verifications . . . .83
Verifying that the agent manager service is
running . . . . . . . . . . . . . . .83
Verifying the installation of WebSphere
Application Server . . . . . . . . . . .84
Verifying the installation of DB2 Universal
Database Enterprise Server Edition (ESE) . . .84
Errors starting the agent manager application
server . . . . . . . . . . . . . . .84
Errors starting the agent manager application . .84
Verifying the connection to the registry . . . .84
Enabling and disabling tracing . . . . . . .85
Recovering from an incomplete uninstallation of
the agent manager . . . . . . . . . . .86
Common problems . . . . . . . . . . . .87
Registration and communication failures . . .87
Problems using the WebSphere Administrative
Console . . . . . . . . . . . . . . .88
Chapter 9. Contacting IBM Tivoli
Software Support . . . . . . . . . .91
General data to collect for Tivoli Support . . . .91
packageLog ZIP tool . . . . . . . . . .92
Level Reporting tool for the WebSphere
Application Server platform . . . . . . . .92
Chapter 10. Tivoli Intelligent
Orchestrator messages . . . . . . .95
Common subsystem messages . . . . . . . .95
Deployment engine subsystem messages . . . . 124
Job Distribution Service (JDS) subsystem messages 135
J2ee subsystem messages . . . . . . . . . 135
Policy engines subsystem messages . . . . . . 150
iv Tivoli Intelligent Orchestrator Problem Determination and Troubleshooting Guide