Table of Contents
Advertisement
accepted by this script. To find out which script failed,
read the text of message CTGEM2100I, which occurs
earlier in this message file (msg_EPM_Install.log).
Administrator Response: Save the message and trace
files (msg_EPM_Install.log and trace_EPM_Install.log),
and then contact IBM Customer Support.
CTGEM2105E
The installation program cannot get
the ID for the object specified by the
search string search_string.
Explanation: The internal identifier for the WebSphere
configuration object specified by the search string
search_string was not found. This typically happens
when you provide incorrect input to the installation
program, for example, if you misspell the name of the
WebSphere cell.
Administrator Response: Start the installation again,
providing the correct data in all input fields.
CTGEM2106I
The object of type object_type and ID
object_ID was created.
Explanation: No additional information is available
for this message.
CTGEM2107I
The object of type object_type and ID
object_ID was deleted.
Explanation: No additional information is available
for this message.
The object with ID object_ID and
CTGEM2108I
attribute name attribute_name was
modified.
Explanation: No additional information is available
for this message.
CTGEM2109I
The environment variable
variable_name was modified.
The original value was original_value.
The new value is new_value.
Explanation: No additional information is available
for this message.
CTGEM2110E
The installation program cannot load
the resource bundle resource_bundle for
the current locale, current_locale.
Explanation: The installation program cannot locate
the resource bundle resource_bundle in the current
locale, current_locale. This indicates a problem in the
files used by the installation program.
You do not get this error if you start the installation in
a locale that is not supported by the agent manager
component. In that situation, the installation uses the
resource bundle for the default locale.
Administrator Response: If possible, obtain a new
copy of the installation media and start the installation
again. If you get the same message again, save the
message and trace files (msg_EPM_Install.log and
trace_EPM_Install.log), and then contact IBM Customer
Support.
Programmer response: This error can be caused by
one of the following problems:
The install.jar file is not in the correct directory
v
The -wsadmin_classpath parameter does not point
v
to the location of the install.jar file.
Make sure that the installation image contains the jar
file in the correct directory, and that the program
passes the correct value for the -wsadmin_classpath
parameter.
CTGEM2111I
The WebSphere application
application_name was installed.
Explanation: No additional information is available
for this message.
CTGEM2112I
The WebSphere application
application_name was uninstalled.
Explanation: No additional information is available
for this message.
CTGEM2113E
A WebSphere configuration script
cannot complete because the properties
file properties_file_name was not found.
Explanation: The installation program creates the
properties file to pass configuration information to the
scripts that configure the agent manager in WebSphere
Application Server. Because the configuration script
cannot locate the properties file, the configuration
cannot be performed and the agent manager
installation cannot complete.
To find out which script failed, read the text of message
CTGEM2100I, which occurs earlier in this message file
(msg_EPM_Install.log).
Administrator Response: This message typically
indicates a problem in the installation program. Save
the message and trace files (msg_EPM_Install.log and
trace_EPM_Install.log), and then contact IBM Customer
Support.
CTGEM2114E
A WebSphere configuration script
cannot complete because it cannot read
the installation properties file
properties_file_name. Error information:
error_information
Explanation: The installation program creates the
properties file to pass configuration information to the
scripts that configure the agent manager in WebSphere
Page 217
Advertisement
Table of Contents
Troubleshooting
