Table of Contents
Advertisement
v "Common agents unable to communicate with the agent manager" on page 75
v "Limitations when trying to manually associate a discovered software resource
with a software definition" on page 75
v "Some patch installations might fail when trying to perform a multiple patch
installation" on page 76
v "Running lightweight management server with DB2 Universal Database
generates exceptions" on page 76
v "Agent receives an HTTP Unauthorized (401) response code" on page 77
v "There is a maximum size for returnResult parameter storage" on page 76
On Windows, Tivoli Intelligent Orchestrator does not start
Tivoli Intelligent Orchestrator does not start, and a message appears in the
WebSphere Application Server log (%WAS_HOME%\logs\server1\SystemOut.log)
similar to:
3c450cad LdapRegistryI E SECJ0352E: Could not get the users
matching the pattern wasadmin because of the following exception
javax.naming.AuthenticationException:
[LDAP: error code 49 - Invalid Credentials]
Cause
In this configuration, IBM Tivoli Directory Server might treat DB2 Universal
Database as if it has started, even though it may not be completely started.
Solution
Try stopping and starting your IBM Tivoli Directory Server service, and then try
starting Tivoli Intelligent Orchestrator again.
To prevent this problem from occurring each time you reboot:
1. Go to Start –> Settings –> Control Panel –> Administrative Tools –> Services
2. Right-click the IBM Tivoli Directory Server service and select Properties.
3. In the Start type list, select Manual.
Problems occur when administering Tivoli Intelligent
Orchestrator from the Web interface while a local firewall is
enabled
When you try to perform administrative tasks from the Tivoli Intelligent
Orchestrator Web interface while firewall applications are running on the client
machine, certain features of the desktop firewall might interfere with the user
interface functions, leading to unexpected errors.
Cause
Some desktop firewall applications that are running locally on the client machine,
such as Zone Labs Integrity Client, can remove the HTTP Referer field from the
header of the HTTP request. In Zone Labs Integrity Client, this feature is enabled
through the Remove private header information setting. When enabled, this
setting automatically replaces the value of the HTTP Referer field with the
XXXXXXX string. As a result, a number of functions in the Tivoli Intelligent
Orchestrator Web interface will not work. The errors that occur are not descriptive.
Solution
Before logging in to Tivoli Intelligent Orchestrator, ensure that the HTTP Referal
field removal does not apply to the Tivoli Intelligent Orchestrator Web site. The
following are Zone Labs Integrity Desktop-specific instructions to customize the
Chapter 7. Common problems and known limitations in Tivoli Intelligent Orchestrator
69
Advertisement
Table of Contents
Troubleshooting
