IBM 51 - Manual (Page 142)

Typically this error is caused by the condition of the
XML file. The XML file might be damaged, or it might
not be valid, or it might include a character that is not
valid.
Operator response: Verify that the wdmlseng
command is working properly from the command line
at the IBM Tivoli Monitoring server.
COPDEX101E A security exception occurred while
the system parsed the profile XML file.
Explanation: The ITM Obtain OS Profiles workflow
generates an XML file that contains the list of profiles
installed in Tivoli Management Agent. This profile
XML file is copied to the IBM Tivoli Provisioning
Manager and then it is parsed by the Profile XML
Parser. The XML parser cannot read the profile XML
file because a security error occurred. This is a file
permissions issue. Either the parent directory of the
profile XML file is missising appropriate file
permissions, or the profile XML file is missing the
appropriate file permissions.
Operator response: Verify that the login user is
assigned read and write access to the parent directory
of the ProfileXMLParser.
COPDEX102E An error occurred when the DOM
parser returned an empty document.
Explanation: The XML parser did not produce a
parsed XML document. The jdom.jar file might be
damaged, or the XML file that contains the list of
profiles was not transferred or generated correctly.
Operator response: Verify that the system successfully
processed the jdom.jar file, the XML data produced by
the wdmlseng command at the ITM server, and the file
transfer from the IBM Tivoli Monitoring server to the
server.
COPDEX103E An error occurred when the DOM
parser returned an empty root XML
element.
Explanation: The XML parser did not produce a
parsed XML document. The jdom.jar file might be
damaged, or the XML file that contains the list of
profiles was not transferred or generated correctly.
Operator response: Verify that the system successfully
processed the jdom.jar file, the XML data produced by
the wdmlseng command at the ITM server, and the file
transfer from the IBM Tivoli Monitoring server to the
server.
COPDEX104E An IO error occurred while the system
tried to verify the profile XML file.
Explanation: The ITM Obtain OS Profiles workflow
generates an XML file that contains the list of profiles
that are installed in Tivoli Management Agent. This
profile XML file is copied to the IBM Tivoli
Provisioning Manager and then it is parsed by the
Profile XML Parser. The system verifies the consistency
of the file before it parses the file. An error occurred,
and then the system threw an IOException when it
tried to verify the profile XML file.
Operator response: Verify that no other process is
trying to access this XML file. Also verify that the
profile XML file on the local system is valid.
COPDEX106E An error occurred when the system
did not find the VALUE_0 Tivoli
Enterprise Console (TEC) configuration
file.
Explanation: The Send TEC Event Java plug-in obtains
its configuration information from a fully configured
TEC configuration file. This file must be
TIO_HOME/config/tivoli.send.conf.
Operator response: Verify that the TEC configuration
file exists, and verify that the file is fully configured.
Refer to the Tivoli Enterprise Console product manual
for more information.
COPDEX107E An error occurred while the system
initialized the Tivoli Enterprise Console
(TEC).
Explanation: The Send TEC Event Java plug-in uses
the Tivoli Enterprise Console TECAgent code base to
transmit TEC events to the Tivoli Enterprise Console
server. The TECAgent obtains its configuration
information from the TEC configuration file:
TIO_HOME/config/tivoli.send.conf. The TECAgent did
not initialize correctly when it tried to send a TEC
event.
Operator response: Verify that the TEC configuration
file exists, and verify that it is fully configured. Refer to
the Tivoli Enterprise Console product manual for more
information.
COPDEX109E The Tivoli Enterprise Console (TEC)
cannot use VALUE_0 as the event class
name.
Explanation: The Send TEC Event Java plug-in uses
the Tivoli Enterprise Console TECAgent code base to
transmit TEC events to the Tivoli Enterprise Console
server. All TEC events sent by the Send TEC Event Java
plug-in must conform to the Tivoli Enterprise Console
standards. In this event, the TEC event class name did
not conform to these standards.
Operator response: Verify that the TEC event name
contains only alphanumeric characters and does not
contain any white space. Refer to the Tivoli Enterprise
Console product manual for more information.
130 Tivoli Intelligent Orchestrator Problem Determination and Troubleshooting Guide