Filter
Top Products
CTGEM0016E The parameter_name parameter cannot
be NULL.
Explanation: A client program specified NULL for the
parameter_name parameter. This parameter must have a
non-NULL value.
System action: In addition to logging this message in
the agent manager message and trace files, the agent
manager throws an exception to notify the calling
program about the problem.
Administrator Response: Make sure that the agent
configuration file (AgentManager.properties) lists the
correct port numbers for each agent manager request
type. If the configuration file is correct, collect the
message and trace files and contact IBM Customer
Support.
CTGEM0017E Client authentication is required to
process the request.
Explanation: A client program issued a request to
perform an action that requires authentication, but did
not supply a certificate with the request. This can
indicate that the agent is not correctly configured or
that the program is sending the request to the wrong
TCP/IP port.
System action: In addition to logging this message in
the agent manager message and trace files, the agent
manager throws an exception to notify the calling
program about the problem.
Administrator Response: Collect the message and
trace files and contact IBM Customer Support.
CTGEM0018E An internal HTTP or application
server error prevented a request from
being fulfilled.
Explanation: An internal HTTP or application server
error prevented the request from being fulfilled. Look
at the exception information in the agent manager trace
log to determine the problem.
Administrator Response: Check the agent manager
message and trace files. If a solution to the problem is
not apparent, contact IBM Customer Support.
CTGEM0019E The agent with the operating system
GUID "operating_system_GUID" and
component ID "component_ID" is already
registered, but duplicate registration is
not enabled. The registration is not
allowed.
Explanation: An agent with the same identification is
already registered, but the agent manager is configured
to prevent duplicate registration.
The component ID component_ID identifies the specific
instance of the agent on a computer system by using
the root configuration directory, or installation
directory, of the agent.
System action: In addition to logging this message in
the agent manager message and trace files, the agent
manager throws an exception to notify the calling
program about the problem.
Administrator Response: If you want to allow
duplicate registration, change the value of the
Registration.Agent.Reregistration.Policy property in the
agent manager configuration file,
AgentManager.properties. To allow a specific agent to
reregister, delete the certificates for that agent from the
registry. If the Registration.Agent.Reregistration.Policy
setting allows reregistration, delete the certificates for
all agents running the same operating system on the
target agent.
CTGEM0020E An agent registration request from
IP_address was rejected because the
password is not correct. The password
that was specified is password.
Explanation: Agent registration was blocked because
the password submitted is incorrect.
Administrator Response: Configure the agent to
provide the correct password.
CTGEM0021E The agent manager instance cannot
be retrieved.
Explanation: An error occurred while running the
agent manager getInstance() method to retrieve the
instance of the agent manager, which is class
AgentManager. To determine the original point of
failure, examine the trace log file to see the series of
exception traces for this failure.
System action: The agent manager is not operational.
Administrator Response: Collect the message and
trace files and contact IBM Customer Support.
CTGEM0022E The agent manager cannot connect to
the agent registry.
Explanation: A database error occurred while
connecting to the agent registry.
System action: Information gathered by the agent
manager will not be written to the agent registry.
However, the agent manager continues to run.
Administrator Response: Verify that the agent registry
database is operational. If it is not running locally,
make sure that you can connect to it from the agent
manager server. Turn on tracing (if it is not already on),
and restart the agent manager. If the problem
continues, contact IBM Customer Support.
206 Tivoli Intelligent Orchestrator Problem Determination and Troubleshooting Guide