IBM 51 Network Router User Manual


 
4. Make sure that the common agent has write
permission to the relative_path target directory. This
path is relative to the common agent installation
directory.
After you correct the problem, start the upgrade again.
BTC5053E The upgrade bundle cannot look up the
deployer service.
Explanation: The deployer service is used to copy the
image to the common agent. Because the deployer
service was not found, the upgrade cannot continue.
System action: The upgrade of the common agent
stopped and the version of the common agent has not
been changed.
Administrator Response: Collect the common agent
logs and contact customer support.
BTC5054E The upgrade bundle cannot create the
URL for the agent manager context root.
The common agent configuration for the
agent manager contains the agent
manager host value of AM_host and the
agent manager public port number
AM_public_port. One or both of these
values is incorrect.
Explanation: The upgrade bundle constructs an HTTP
URL in the form of http://AM_host:AM_public_port/
AgentMgr/...
to download the needed information
from the agent manager. This error indicates that the
URL cannot be created because one of the AM_host or
AM_public_port values is null.
System action: The upgrade of the common agent
stopped and the version of the common agent has not
been changed.
Administrator Response: Verify that the
endpoint.properties file has valid values for the
AgentManagerQuery.host and ARS.port.public keys.
If the values are correct, collect the common agent logs
and properties files, and then contact customer support.
BTC5055E The upgrade bundle cannot invoke the
system_command system command. Look
in the logs/upgradeAgentTrace.log and
logs/upgradeAgentMessage.log files for
information about the exception:
exception
Explanation: A system command that is required for
the upgrade failed with the exception exception.
System action: The upgrade of the common agent
stops and the version of the common agent is
unchanged.
Administrator Response: Collect the common agent
logs and contact customer support.
BTC5057I This error code indicates that a specific
key was not found in the
CAUpgrade.properties file. Look for the
previously logged message BTC5049E in
the logs/upgradeAgentMessage.log file
in the logs directory for more
information about the key that could
not be found.
Explanation: You are checking the status of the
upgrade after it failed, recovered from the error, and
restarted, so this command does not have access to the
complete context of the error. To get the details of the
error, such as the specific key that was incorrect, look
in the logs for the message that was recorded when the
error occurred.
BTC5058I This error code indicates that the
upgrade response file could not be
created. The response file is used to
drive the upgrade portion of the
common agent installation. Look for the
previously logged message BTC5050E in
the logs/upgradeAgentMessage.log file
in the logs directory for more
information about the error that
occurred.
Explanation: You are checking the status of the
upgrade after it failed, recovered from the error, and
restarted, so this command does not have access to the
complete context of the error. To get the details of the
error, such as the specific exception, look in the logs for
the message that was recorded when the error
occurred.
BTC5059I This error code indicates that a system
command failed. Look for the
previously logged message BTC5055E in
the logs/upgradeAgentMessage.log file
in the logs directory for more
information about the error that
occurred.
Explanation: You are checking the status of the
upgrade after it failed, recovered from the error, and
restarted, so this command does not have access to the
complete context of the error. To get the details of the
error, such as the specific system command that failed,
look in the logs for the message that was recorded
when the error occurred.
BTC5060I This error code indicates that there was
an error unpacking an image file. The
image is either the common agent
installation image or the JRE image.
Look for the previously logged message
BTC5051E in the logs/
upgradeAgentMessage.log
file in the
logs directory for more information
200 Tivoli Intelligent Orchestrator Problem Determination and Troubleshooting Guide