1. Manuals
  2. Brands
  3. IBM Manuals
  4. Network Router
  5. 51
  6. Troubleshooting manual

IBM 51 Troubleshooting Manual

Ibm troubleshooting guide
Hide thumbs
Table of Contents

Advertisement

Quick Links

Download this manual
T ivo l i
Intelligent Orchestrator
®
Version 5.1
Problem Determination and Troubleshooting Guide
SC32-2216-00

Advertisement

Table of Contents
loading

Related Manuals for IBM 51

Summary of Contents for IBM 51

  • Page 1 T ivo l i Intelligent Orchestrator ® Version 5.1 Problem Determination and Troubleshooting Guide SC32-2216-00...
  • Page 3 T ivo l i Intelligent Orchestrator ® Version 5.1 Problem Determination and Troubleshooting Guide SC32-2216-00...
  • Page 4 Before using this information and the product it supports, read the information in Appendix C, “Notices,” on page 229. First Edition, July 2006 © Copyright International Business Machines Corporation 2003, 2006. All rights reserved. US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

  • Page 5: Table Of Contents

    Logs for data collection and decision making . Automation package logs . Chapter 6. Middleware prerequisite log files ....51 Installation log files for prerequisites . Installation logs for individual prerequisites Runtime logs for prerequisites .
  • Page 6 Intelligent Orchestrator exits before the installation is completed . Environment variables not set for user tioadmin The installation of IBM Tivoli NetView on Windows fails if the password for creating a user account does not meet the system requirements . 59 The agent manager installation fails during the Tivoli Intelligent Orchestrator installation .
  • Page 7 Determine the business impact of your problem 227 Describe your problem and gather background information . . 179 Submit your problem to IBM Software Support . 202 Appendix C. Notices ..229 Trademarks .
  • Page 8 Tivoli Intelligent Orchestrator Problem Determination and Troubleshooting Guide...

  • Page 9: Preface

    Tivoli Intelligent Orchestrator library The publications in the Tivoli Intelligent Orchestrator library are: Tivoli Intelligent Orchestrator Installation Guide © Copyright IBM Corp. 2003, 2006 ® Intelligent Orchestrator or Tivoli Provisioning Manager. ® 2000 Server or Windows Server 2003 ®...

  • Page 10: Prerequisite Publications

    Information related to Tivoli Intelligent Orchestrator is available in the following locations: v The IBM Orchestration and Provisioning Automation Library is available online at: http://catalog.lotus.com/wps/portal/tpm. The IBM Orchestration and Provisioning Automation Library delivers the tools that you need to build your business around on demand automation.

  • Page 11: Accessing Publications Online

    File → Print). In addition to accessing the PDF publications, you can also access the online help which is shipped with Tivoli Intelligent Orchestrator. The online help is available at the external IBM Tivoli Information Center, located at: http:// publib.boulder.ibm.com/infocenter/tivihelp/index.jsp. Ordering publications You can order many Tivoli publications online at the following Web site: http://www.elink.ibmlink.ibm.com/public/applications/ publications/cgibin/...

  • Page 12: Tivoli Software Training

    Support information If you have a problem with your IBM software, you want to resolve it quickly. IBM provides the following ways for you to obtain the support you need: v Searching knowledge bases: You can search across a large collection of known problems and workarounds, Technotes, and other information.

  • Page 13: Chapter 1. Introduction To Troubleshooting

    Modeling your data center assets Tivoli Intelligent Orchestrator manages a virtual representation of your data center in a data center model. Virtualization exists on several levels to provide flexible configuration in different contexts: © Copyright IBM Corp. 2003, 2006...

  • Page 14: Product Comparison

    v Each asset is represented by a data center object. When you make a v For some data center assets, the data center model stores data about the v You can create templates that define standard configurations. For v You can define application topologies that describe requirements for an Orchestrating provisioning You can configure Tivoli Intelligent Orchestrator to dynamically allocate resources to applications based on demand or priority.

  • Page 15: Product Architecture

    Product architecture Tivoli Intelligent Orchestrator includes the following main components: Device-specific protocols (For ex., SNMP) WebSphere Application Server Soap Service (Web Container) Tivoli Intelligent Orchestrator components data center model The data center model is an abstract representation of all physical and logical assets in a data center that Tivoli Intelligent Orchestrator manages, and their relationships.

  • Page 16: Prerequisites Installed With Tivoli Intelligent Orchestrator

    objective analyzer global resource manager deployment engine The deployment engine is responsible for automated provisioning. It creates, stores, and runs workflows and communicates their success or failure in performing an operation. Workflows can be triggered by commands from an administrator, by external tools that send SOAP commands to Tivoli Intelligent Orchestrator, or by recommendations from the policy engine.

  • Page 17: Built-In Troubleshooting Features

    WebSphere Application Server WebSphere Application Server hosts management interfaces and coordinates interaction between other system components. Database server The database server stores the data center model and report and audit data. Directory server The directory server manages user accounts and user authentication. Built-in troubleshooting features Tivoli Intelligent Orchestrator records system activity and events in message logs, trace logs, and Common Base Event logs.

  • Page 18: Performing Periodic Checks And Maintenance

    Use the information in this guide to identify and resolve potential problems. If you cannot correct the problem, gather the relevant diagnostic information as described in this guide and then use the information in Chapter 9, “Contacting IBM Tivoli Software Support,” on page 91 to get further assistance.

  • Page 19: Chapter 2. Problem Determination Essentials For Tivoli Intelligent Orchestrator

    – Were you installing Tivoli Intelligent Orchestrator? If yes, was this the first installation? – Were you performing post-installation configurations? – Were you performing a runtime task? v Have you previously performed the same procedure without getting errors? What was done differently this time? © Copyright IBM Corp. 2003, 2006...

  • Page 20: Identifying The Cause Of The Problem

    Tivoli Support team, who will be able to pinpoint the cause of the problem and recommend ways to recover from specific situations. For more information on how to contact the IBM Tivoli Software Support, refer to Chapter 9, “Contacting IBM Tivoli Software Support,” on page 91.

  • Page 21: Fixing The Problem

    IBM technotes for your product and the available knowledge bases to determine whether the resolution to your problem is already documented. Analyzing the actions that led up to the problem and generating an action plan The approach that you should take must make use of all the available resources and tools.

  • Page 22: Troubleshooting The Prerequisite Installation

    WebSphere Application Server, Version 6.0, Fix Pack 2. 3. After the prerequisite installation, you might want to follow these steps: v Ensure that the configuration of the IBM Tivoli Directory Server database was successful. If not, refer to the “IBM Tivoli Directory Server verification”...
  • Page 23 IBM Tivoli Directory Server verification The verification requires these steps: 1. Ensure that the IBM Tivoli Directory Server database was successfully created. Check the ldapcfg.stat file to see the syntax used at the time of the database creation. The file is located in the following directory:...
  • Page 24 4. Verify whether the DB2 database is successfully started. For more information, refer to “DB2 Universal Database verification” on page 10. 5. Check the runtime IBM Tivoli Directory Server log files for errors. The logs are stored in the following directory: v Windows: <LDAP_Install_Directory>\var\...
  • Page 25 7. Search the knowledge bases and, if necessary, contact Support. For more information, refer to Appendix B, “Support information,” on page 225. WebSphere Application Server verification The verification requires the following steps: 1. Perform a WebSphere Application Server installation verification test, by running the following script: v On Windows: %WAS_HOME%\bin\ivt.bat v On UNIX: $WAS_HOME/bin/ivt.sh...
  • Page 26 Server.xml Java.security Sas.client.props 4. Check the runtime WebSphere Application Server log files for errors. The logs are stored in the following directory: v On Windows: %WAS_HOME%\logs\<server-name> v On UNIX: $WAS_HOME/logs/<server-name> where <server-name> is by default server1. The runtime WebSphere Application Server log files include: SystemOut.log SystemErr.log startServer.log...
  • Page 27 SecurityCompo I SECJ0212I: WCCM JAAS configuration information successfully pushed to login provider class. SecurityCompo I SECJ0240I: Security service initialization completed successfully SASRas A JSAS0001I: Security configuration initialized. SASRas A JSAS0002I: Authentication protocol: CSIV2/IBM SASRas A JSAS0003I: Authentication mechanism: LTPA SASRas A JSAS0004I: Principal name: todaix05.think.lab.austin.- ibm.com:389/wasadmin SASRas A JSAS0005I: SecurityCurrent registered.
  • Page 28 ResourceMgrIm I WSVR0049I: Binding Default_CF as eis/DefaultDatasource_CMP ResourceMgrIm I WSVR0049I: Binding AgentRegistry as jdbc/AgentRegistry Simple Object Access Protocol ( SOAP) JMXSoapAdapte A ADMC0013I: SOAP connector available at port 8880 Applications ApplicationMg A WSVR0200I: Starting application: DefaultApplication EJBContainerI I WSVR0207I: Preparing to start EJB jar: Increment.jar EJBContainerI I WSVR0037I: Starting EJB jar: Increment.jar .

  • Page 29: Tivoli Intelligent Orchestrator Installation And Subcomponent Configuration Verification

    On Windows, it creates Tivoli Intelligent Orchestrator start and stop desktop icons. v Generates the agent manager response file template. v Sets up the DB2 database. v Configures the IBM Tivoli Directory Server. Chapter 2. Problem determination essentials for Tivoli Intelligent Orchestrator...
  • Page 30 Verifying Tivoli Intelligent Orchestrator’s connection to DB2 Universal Database. See “DB2 Universal Databaseconfiguration verification.” v Verifying the IBM Tivoli Directory Server configuration. See “IBM Tivoli Directory Server configuration verification” on page 19. v Verifying Tivoli Intelligent Orchestrator’s connection to IBM Tivoli Directory Server.
  • Page 31 For more information, see “IBM Tivoli Directory Server verification” on page 11. 2. If the IBM Tivoli Directory Server was successfully started, check the IBM Tivoli Directory Server’s basic functionality, using the ldapsearch command line utility: ldapsearch -h <ldapserver>...
  • Page 32 -v -h <ldapserver> -p 389 -D cn=root -w <password> -b "" -s base objectclass=* b. If the ldapsearch search returns a command not found, install the IBM Tivoli Directory Server Client, following the instructions provided in the Tivoli Intelligent Orchestrator Installation Guide.

  • Page 33: Tivoli Intelligent Orchestrator Runtime Problem Determination

    If the ldapsearch search returns a connection error, start a Telnet session and try to connect to the IBM Tivoli Directory Server using the port number 389. d. If communication can be established with a Telnet session between the IBM Tivoli Directory Server and Tivoli Intelligent Orchestrator, check the IBM Tivoli Directory Server administrative password.
  • Page 34 -v -h < ldapserver > -p 389 -D "cn=root" -w <password> -b "dc=ibm,dc=com" cn=wasadmin If it is a connection problem, refer to “IBM Tivoli Directory Server connection verification” on page 20. 2. Check the IBM Tivoli Directory Server for wasadmin authentication: ldapsearch -v -h <...
  • Page 35 Universal Database verification” on page 10. 2. If DB2 Universal Database is started, check whether the IBM Tivoli Directory Server is started. If the IBM Tivoli Directory Server is not started, start it. For more information, refer to “IBM Tivoli Directory Server verification” on page...
  • Page 36 3. If the IBM Tivoli Directory Server is started, check the SystemOut.log file for the following types of exceptions. For more information on the SystemOut.log file, refer to “Problem determination using SystemOut.log” on page 14: a. If authentication exceptions are found in the log file, go to “IBM Tivoli Directory Server authentication problem determination”...
  • Page 37 4. If a solution is still not found, try matching the error with the following keywords: LTPA, LDAP, authentication, credential, token. If a match is found, go to “IBM Tivoli Directory Server authentication problem determination” on page 22. 5. If no match is found, try matching the error with the following keywords: constraint, DB2, SQL, relationship, row, table.

  • Page 38: Accessing The Knowledge Bases

    “Tivoli Intelligent Orchestrator command line tools” v “WebSphere Application Server command line tools” on page 32 v “IBM Tivoli Directory Server command line tools” on page 33 Tivoli Intelligent Orchestrator command line tools The following table lists a number of command line tools that can be used during...
  • Page 39 Note: The command line tools can be found on TIO_HOME/tools Table 1. Tivoli Intelligent Orchestrator command line tools Name Location applyNewEncryptKey.cmd v On applyNewEncryptKey.sh Windows: %TIO_HOME%\ tools v On UNIX: $TIO_HOME/ tools cancel-all-in- v On progress.cmd Windows: cancel-all-in- %TIO_HOME%\ progress.sh tools v On UNIX: $TIO_HOME/...
  • Page 40 Table 1. Tivoli Intelligent Orchestrator command line tools (continued) Name dcmExport.cmd dcmExport.sh dcmQueryCommand.cmd dcmQueryCommand.sh engineStatus.cmd engineStatus.sh init.cmd init.sh packageLogs.cmd packageLogs.sh reinit.cmd reinit.sh Tivoli Intelligent Orchestrator Problem Determination and Troubleshooting Guide Location Description Example: v On dcmExport.cmd Windows: c:/myDirectory/ %TIO_HOME%\ myOutput.xml If tools outputFilename is not v On UNIX:...
  • Page 41 Table 1. Tivoli Intelligent Orchestrator command line tools (continued) Name Location retrieveDetails.cmd v On retrieveDetails.sh Windows: %TIO_HOME%\ tools v On UNIX: $TIO_HOME/ tools Chapter 2. Problem determination essentials for Tivoli Intelligent Orchestrator Description Syntax Retrieves and retrieveDetails.cmd displays a data center -i<deviceId>...
  • Page 42 Table 1. Tivoli Intelligent Orchestrator command line tools (continued) Name siregister.cmd siregister.sh Tivoli Intelligent Orchestrator Problem Determination and Troubleshooting Guide Location Description Extracts installable v On files from Windows: Macrovision Solution %TIO_HOME%\ Installation packages tools and adds them to the v On UNIX: Tivoli Intelligent $TIO_HOME/...
  • Page 43 Table 1. Tivoli Intelligent Orchestrator command line tools (continued) Name Location tc-driver- v On manager.cmd Windows: tc-driver-manager.sh %TIO_HOME%\ tools v On UNIX: $TIO_HOME/ tools tio.cmd v On tio.sh Windows: %TIO_HOME%\ tools v On UNIX: $TIO_HOME/ tools tioStatus.cmd v On tioStatus.sh Windows: %TIO_HOME%\ tools...
  • Page 44 Table 1. Tivoli Intelligent Orchestrator command line tools (continued) Name xmlImport.cmd xmlImport.sh WebSphere Application Server command line tools The following table lists command line tools that can be used during the WebSphere Application Server problem determination process: Table 2. WebSphere Application Server command line tools Name setupCmdLine.bat setupCmdLine.sh...
  • Page 45 On UNIX: $TIO_HOME/ IBM Tivoli Directory Server command line tools The following table lists command line tools that can be used during the IBM Tivoli Directory Server problem determination process: Table 3. IBM Tivoli Directory Server command line tools...
  • Page 46 Tivoli Intelligent Orchestrator Problem Determination and Troubleshooting Guide...

  • Page 47: Chapter 3. Log File Types

    Message logs Message logs record Tivoli Intelligent Orchestrator system events as text messages so they can be reviewed later by customers or by IBM Tivoli Software Support. Typically, messages are used to provide information about how the system or application is performing, and to alert the system administrator to exceptional conditions when they occur.

  • Page 48: Message Elements

    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 Message ID String of 10 alphanumeric characters that uniquely identifies the message.

  • Page 49: Trace Logs

    Tivoli Intelligent Orchestrator provides configurable tracing capabilities that can help you determine the cause of a problem. Trace logs and first-failure data capture (FFDC) are built into the software to assist the IBM Customer Support for Tivoli software personnel in gathering information to determine why a problem is occurring, and might be requested as part of diagnosing a reported problem.
  • Page 50 Tivoli Intelligent Orchestrator Problem Determination and Troubleshooting Guide...

  • Page 51: Chapter 4. Locating And Configuring Log Files

    Stores the globalized event messages so the user can understand a problem and take action to try and resolve the problem. trace.log Stores errors that are reviewed by IBM Tivoli Support. cbe.log Stores all error messages in Common Base Event format.

  • Page 52: Logging Levels

    Logging levels This section details the behavior of Tivoli Intelligent Orchestrator logs based on how the logging levels are defined. The logging level hierarchy for Tivoli Intelligent Orchestrator is shown in the following table: Logging level msg_error#com.thinkdynamics.kanaha. util.logging.MessageLevel msg_warn#com.thinkdynamics.kanaha. util.logging.MessageLevel msg_info#com.thinkdynamics.kanaha.
  • Page 53 # module is meant for messages written module specific files output.normal=%d{ISO8601} %-5p [%t] (%13F:%L) %c{2}: %m%n output.error=%d{ISO8601} %-5p [%t] (%13F:%L): %m%n output.module=%d{ISO8601} %-5p [%t] (%13F:%L): %m%n # configure root category # note that this configuration is inherited by all other categories (see # example below if you want to suppress this behaviour) log4j.rootCategory=DEBUG, consolefile, errorfile, messagefile # everything goes to console.log...

  • Page 54: Log Level Defaults

    #log4j.appender.datacentermodel.layout=org.apache.log4j.PatternLayout #log4j.appender.datacentermodel.layout.ConversionPattern=${output.module} #log4j.appender.datacentermodel.append=false Log level defaults The initial log4j log level configuration for each log file is set to info. As defined in the log4j.prop file above, each log file is set to a unique log level for Tivoli Intelligent Orchestrator using the log4j.appender.filename.threshold= parameter.

  • Page 55: Preparing Log Files For Review By Ibm Tivoli Support

    2. Change the default log4j.appender.file.append=false to log4j.appender.file.append=true. 3. Save the file. Preparing log files for review by IBM Tivoli Support Tivoli Intelligent Orchestrator includes packageLog, a log management tool that simplifies the problem determination process. For more information, see “packageLog ZIP tool” on page 92.
  • Page 56 Tivoli Intelligent Orchestrator Problem Determination and Troubleshooting Guide...

  • Page 57: Chapter 5. Tivoli Intelligent Orchestrator Log Files

    When you uninstall Tivoli Intelligent Orchestrator, the log files for the uninstall process follow the Tivoli Common Directory standard, and are located in the following directory: Windows %TIO_LOGS%\uninstall © Copyright IBM Corp. 2003, 2006 Location Windows %TIO_LOGS% Default value for %TIO_LOGS%:...

  • Page 58: Log Files For Starting And Stopping The Server

    UNIX or Linux $TIO_LOGS/uninstall Log files for starting and stopping the server Log files for starting and stopping the Tivoli Intelligent Orchestrator server are stored in the %TIO_LOGS% directory. Log files specific to WebSphere Application Server are located in the %WAS_HOME%\logs\server1 directory, where %WAS_HOME% is the default WebSphere Application Server home directory.

  • Page 59: Log Files For The Web Interface

    Log files for the Web interface Log files for the Web interface and data center model changes, and other operations associated with the Web interface are stored in the %TIO_LOGS%\j2ee directory. Table 6. Web interface logs File name console.log msg.log trace.log cbe.log Deployment engine log files...

  • Page 60: Workflow Logs

    Table 7. Deployment engine logs (continued) File name cbe.log deploymentengine_start.log Workflow logs If you want to determine why a particular workflow has failed, you can use the Web interface to display the run history for that workflow. You can also export the log files of your workflow history using the workflowLogExport command, as described below.

  • Page 61: Logs For Data Collection And Decision Making

    Logs for data collection and decision making Log files for the policy engine component (data acquisition engine, application controllers, global resource manager) are stored in the %TIO_LOGS%\policyengine directory. Table 8. Policy engine logs File name console.log msg.log trace.log cbe.log policyengine_start.log Automation package logs Log files for orchestration packages are stored in the %TIO_LOGS%\tcdrivermanager directory.
  • Page 62 Table 9. Automation package logs (continued) File name trace.log cbe.log Tivoli Intelligent Orchestrator Problem Determination and Troubleshooting Guide Location Windows %TIO_LOGS%\tcdrivermanager UNIX or Linux $TIO_LOGS/tcdrivermanager Windows %TIO_LOGS%\tcdrivermanager UNIX or Linux $TIO_LOGS/tcdrivermanager Description This log file stores error messages that can be reviewed by Tivoli Software Support.

  • Page 63: Chapter 6. Middleware Prerequisite Log Files

    The WebSphere Application Server logs are: v base.log v websphere.stdout v websphere.stderr v websphereFixPack.stdout v websphereFixPack.stdout DB2 Universal Database The log files for IBM DB2 Universal Database Enterprise Edition 8.2 are: v db2server.log v db2server.trace v db2Server.stderr v db2Server.stdout v db2ServerHotfix.stderr v db2ServerHotfix.stdout v db2client.log...

  • Page 64: Runtime Logs For Prerequisites

    Directory Server The log files for the IBM Tivoli Directory Server are: v ldap.stderr v ldap.stdout v ldapinst.log Runtime logs for prerequisites For additional information on errors that do not pertain to Tivoli Intelligent Orchestrator, you might want to consult the error and trace logs for the middleware prerequisites.

  • Page 65: Db2 Universal Database

    WebSphere Application Server is the last service to stop when you shut down Tivoli Intelligent Orchestrator, so this log file is useful for verifying whether the shutdown completed. It is located in the %WAS_HOME%\logs\ server1 directory on Windows systems ($WAS_HOME/logs/server1 on UNIX or Linux).

  • Page 66: Tivoli Agent Manager

    v db2diag.log v ibmds_config.log v ibmds_config_err.log Tivoli Agent Manager Trace logs for the agent manager are stored in the Agent_Manager_install_dir\ logs directory, where Agent_Manager_install_dir is the installation directory for the agent manager. The log files for the Tivoli Intelligent Orchestrator installed on a managed server are stored in the installation directory on the target server.

  • Page 67: Chapter 7. Common Problems And Known Limitations In Tivoli Intelligent Orchestrator

    This section includes troubleshooting scenarios for the following problems: v “In Linux, you cannot create the user tioadmin” v “The system cannot connect to the IBM Tivoli Directory Server during the Tivoli Intelligent Orchestrator installation” on page 56 v “The installation of the DB2 Universal Database Client on Windows 2003 system fails”...

  • Page 68: The System Cannot Connect To The Ibm Tivoli Directory Server During The Tivoli Intelligent Orchestrator Installation

    Cause During the Tivoli Intelligent Orchestrator installation, the system might indicate that it cannot connect to the IBM Tivoli Directory Server. This error occurred because the directory server was not started before running the installer. The directory server must be started before you install Tivoli Intelligent Orchestrator, so the installer can connect to it.

  • Page 69: Installing The Common Agent And The Agent Manager Is Not Supported

    Solution Use the DB2 Universal Database Administration Client, Version 8.1 for Windows operating systems on 32–bit systems CD instead. Installing the common agent and the agent manager is not supported Cause Installing the common agent on the Tivoli Intelligent Orchestrator server, where the agent manager is also installed, is not supported.

  • Page 70: The Microsoft Active Directory Installation Fails With Invalid Certificate Value

    3. Import the schema.ldif and ldap.ldif files into the Microsoft Active Directory server. Instructions for this step are found in Tivoli Intelligent Orchestrator Installation Guide Version 5.1. 4. Run the reinit command. The Microsoft Active Directory installation fails with invalid certificate value Cause The Microsoft Active Directory certificate is missing but the user enters a value for...

  • Page 71: The Installation Of Ibm Tivoli Netview On Windows Fails If The Password For Creating A User Account Does Not Meet The System Requirements

    Cause When installing IBM Tivoli NetView on Windows, the NetView installer creates a user account on your system for the NetView service. If the password that you are prompted to enter for creating this user account does not conform with the password policy of your system, the NetView installation fails.
  • Page 72 Microsoft Management Console to stop the service with the following name: IBM WebSphere Application Server V5 - Tivoli Agent Manager v On Windows but not as a service: To stop the agent manager server if it is not a Windows service: a.
  • Page 73 By default, this is the following directory: v On Windows systems: C:\Program Files\IBM\AgentManager v On AIX, Linux, and Solaris systems: /opt/IBM/AgentManager Note: On a Windows system, you might have to restart the system before you can delete the agent manager installation directory.

  • Page 74: An Error Occurs When Running The Rpm -Qa

    Tivoli Intelligent Orchestrator is already installed, and will install only agent manager. An error occurs when running the rpm -qa command after the DB2 Universal Database, IBM Tivoli Directory Server, and WebSphere Application Server prerequisites are installed on Linux After successfully installing the Tivoli Intelligent Orchestrator prerequisites on Linux, the following error might occur when running the rpm -qa command.

  • Page 75: You Cannot Change Your Password

    5. Click Start or Stop or Restart to change the status of the server. For more information on scenarios that can affect login, see the Tivoli Intelligent Orchestrator support Web site: http://www.ibm.com/software/sysmgmt/ products/support/IBMTivoliIntelligentOrchestrator.html In the Choose a Product list, select Tivoli Intelligent Orchestrator.

  • Page 76: Problems With Workflows

    “DB2 Universal Database deadlocks occur when the system runs a logical operation” on page 65 v “Shell command error: Resource temporarily unavailable” on page 65 v “IBM Tivoli Software Support personnel have requested a copy of a workflow” on page 65 v “A workflow does not install” on page 67 v “Cannot run workflows if the PS1 environment variable is altered”...

  • Page 77: Db2 Universal Database Deadlocks Occur When The System Runs A Logical Operation

    /nmlprod/common/bin /opt/seos/bin". Solution The automation package that you are running requires bash on the endpoint. IBM Tivoli Software Support personnel have requested a copy of a workflow Solution: workflowLogExport tool This command line utility exports the run history of one or more specified workflows to a log file that can be either in XML format (the default option) or in any other file format of your choice.
  • Page 78 This command line utility exports the workflow execution logs into an XML file. The tool simplifies the process of sending workflows to the Software Support team so they can access the log information that they need to diagnose a workflow problem without accessing your computer remotely.

  • Page 79: A Workflow Does Not Install

    Log content structure: workflow –> deployment request –> workflow execution log –> workflow execution log detail Example workflow log export: <?xml version="1.0" encoding="UTF-8"?> <workflow-execution-history> <workflow id="21" name="Test Workflow 99999"> <deployment-requestid="10020"> <execution-log id="21" date="Mar 10, 2005 11:48:54 AM" position="1" call-stack-level="1" lo <log-details position="2"...

  • Page 80: Cannot Run Workflows If The Ps1 Environment Variable Is Altered

    Cannot run workflows if the PS1 environment variable is altered Cause When running scriptlets in Tivoli Intelligent Orchestrator, the system will expect that the command prompt ends in $ or #. The PS1 environment variable governs what your prompt looks like. If you change this variable on your managed-to or managed-from system, you might run into problems running workflows.

  • Page 81: On Windows, Tivoli Intelligent Orchestrator Does Not Start

    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.

  • Page 82: Incorrect Soap Parameters Generate Detailed Java Exception Messages

    privacy settings for the Tivoli Intelligent Orchestrator Web address so that they no longer interfere with the Tivoli Intelligent Orchestrator user interface. To customize the privacy settings for the Tivoli Intelligent Orchestrator URL in the Zone Labs Integrity Desktop, perform the following steps: 1.

  • Page 83: Db2 Universal Database Does Not Work Properly With Terminal Server

    DB2 Universal Database does not work properly with terminal server Cause The Tivoli Intelligent Orchestrator installation fails with DB2 Universal Database when terminal server is enabled. There is an db2.exe application error. The DB2 Universal Database command will not work. Solution Disable the terminal server and reboot before trying to install again.

  • Page 84: Websphere Application Server On Linux Remains Paused When You Try To Stop The Jms Pub Sub Broker

    Solution From the Microsoft Visual C++ 6.0 Support Web site available at http://support.microsoft.com/default.aspx?scid=kb;en-us;259403&Product=vc6, follow the instructions to download the Vcredist.exe installer. The installer will place the msvcp60.dll file at the correct location on your computer. WebSphere Application Server on Linux remains paused when you try to stop the JMS pub sub broker The last line in the log is: 1b2ddb28 JMSEmbeddedPr A MSGS0054I: Stopping the Broker...

  • Page 85: For Languages Other Than English, The Text In Csv Reports Imported In Microsoft Excel Is Garbled

    For more information, refer to the DB2 product documentation available at http://www.ibm.com/software/data/db2/udb/support/manualsv8.html. For languages other than English, the text in CSV reports imported in Microsoft Excel is garbled Tivoli Intelligent Orchestrator reports that are exported to Comma Separated Values (CSV) file format can be afterwards imported in spreadsheet applications such as Microsoft Excel.

  • Page 86: An Error Occurs If You Use Special Characters To Create A New User Or Security Role

    3. Open the <Report_name>_output.csv file in Excel. All characters are properly displayed. Instead of running the above command more than once for converting more CSV files, you might want to create a script file that uses the command in step 2 and specifies the names of all the CSV files that require conversion.

  • Page 87: Common Agents Unable To Communicate With The Agent Manager

    Cause The Distinguished Name (DN) syntax supported by the directory server does not support special characters. This is a known problem with the IBM Tivoli Directory Server and is described in detail in the Tivoli Directory Server Administration Guide that is available at http://publib.boulder.ibm.com/tividd/td/ IBMDirectoryServer5.2.html.

  • Page 88: Some Patch Installations Might Fail When Trying To Perform A Multiple Patch Installation

    v When you look at the properties of the software stack, no software modules are displayed. v Compliance checking also incorrectly defines the software stack as missing when the software stack is included in the server template. Cause You can associate a discovered software resource with a software product, patch, or operating system software definition only.

  • Page 89: Agent Receives An Http Unauthorized (401) Response Code

    Agent receives an HTTP Unauthorized (401) response code Agent can receive an Unauthorized (401) response code for a number of reasons, such as: v The agent did not provide a client certificate as part of the SSL handshake, which can be caused by the agent connecting in on the wrong port. The agent must connect in on the port which is configured for SSL client authentication.
  • Page 90 Tivoli Intelligent Orchestrator Problem Determination and Troubleshooting Guide...

  • Page 91: Chapter 8. Troubleshooting The Agent Manager

    If you contact IBM Customer Support, you must provide this package. To package the logs and configuration information into a compressed, or zipped, file for IBM Customer Support, use the log collection tool that is available in the toolkit subdirectory of the agent manager installation directory (Agent_Manager_install_dir).
  • Page 92 Table 10. Agent manager installation log files Log file name AMReturnValues.log am_install.log am_upgrade.log auth_stdout.log auth_stderr.log certGen_stdout.log certGen_stderr.log datastore_stdout.log datastore_stderr.log db_stdout.log db_stderr.log encrypt_stdout.log encrypt_stderr.log guid_install.log guid_stdout.log guid_stderr.log msg_EPM_Install.log trace_EPM_Install.log startserver_stdout.log startserver_stderr.log jacl/amApp_out.log jacl/amApp_err.log Tivoli Intelligent Orchestrator Problem Determination and Troubleshooting Guide Description Summary of return values of the steps of the agent manager installation.

  • Page 93: Locating The Uninstallation Log Files

    Table 10. Agent manager installation log files (continued) Log file name jacl/appServer_out.log jacl/appServer_err.log jacl/checkcell_out.log jacl/checkcell_err.log jacl/checknode_out.log jacl/checknode_err.log jacl/jdbc_out.log jacl/jdbc_err.log jacl/ssl_out.log jacl/ssl_err.log jacl/virHost_out.log jacl/virHost_err.log Locating the uninstallation log files The log files generated when you uninstall the agent manager are located in the Agent_Manager_install_dir\logs directory.

  • Page 94: Locating The Runtime Log Files

    Table 12. Remote registry database installation log files Log File datastore.out ds_install.log db_stdout.log db_stderr.log Locating the runtime log files The runtime logs for the agent manager are located in the was_install_dir\logs\ app_server_name directory, where app_server_name is the name of the application server.

  • Page 95: Determining The Version Of Agent Manager

    Determining the version of agent manager To determine the version of the agent manager, use the GetAMInfo command, which is located in the Agent_Manager_install_dir/bin directory. On Windows systems, it has the .cmd extension (GetAMInfo.cmd). On AIX, Linux, and Solaris systems, is has the .sh extension (GetAMInfo.sh). To display the version of the agent manager and agent recovery service applications, run the following command.

  • Page 96: Verifying The Installation Of Websphere Application Server

    Verifying the installation of WebSphere Application Server To verify the installation of WebSphere Application Server, use the firststeps tool, located in the WAS_install_dir/firststeps directory. Run the program for your operating system: v Windows: firststeps.bat v AIX, Linux, or Solaris: firststeps.sh Verifying the installation of DB2 Universal Database Enterprise Server Edition (ESE) If the registry is in a DB2 database and the agent manager server does not install...

  • Page 97: Enabling And Disabling Tracing

    3. Click Apply to list the JDBC providers for the agent manager application server. 4. In the list of providers, click AgentJDBCProvider. 5. In the Additional Properties area at the bottom of the Configuration page of the JDBC provider, click Data Sources. 6.

  • Page 98: Recovering From An Incomplete Uninstallation Of The Agent Manager

    Remove the entry that starts the agent manager server. This entry is added on all systems. am:2345:once:/opt/IBM/WebSphere/AppServer/bin/rc.am >/dev/console 2>&1 In this example, WebSphere Application Server is installed in the /opt/IBM/WebSphere/AppServer directory. v If the registry is in a local DB2 database, remove the entry that starts the DB2 server.

  • Page 99: Common Problems

    If an agent is in a network that cannot resolve the short host name to the fully qualified host name, it cannot access the agent manager services.

  • Page 100: Problems Using The Websphere Administrative Console

    Services window or the Services folder in the Microsoft Management Console to start the service with the following name: IBM WebSphere Application Server V5 - server1 To start the WebSphere using a Windows command: 1. Open a command prompt window.
  • Page 101 Target field of the shortcut properties. If this chapter did not help you resolve your problem, you can get additional assistance from the IBM Software Support Web site at the following Web address: http://www.ibm.com/software/support/ Chapter 8. Troubleshooting the agent manager...
  • Page 102 Tivoli Intelligent Orchestrator Problem Determination and Troubleshooting Guide...

  • Page 103: Chapter 9. Contacting Ibm Tivoli Software Support

    The site also contains presentations, fixes, fix packs, and white papers. Go to http://www-306.ibm.com/software/sysmgmt/products/support/, and under Product support pages A to Z click I, and then select IBM Tivoli Intelligent Orchestrator to open the Tivoli Intelligent Orchestrator Support Web site.

  • Page 104: Packagelog Zip Tool

    ZIP tool The packageLog tool is a command line utility that packages Tivoli Intelligent Orchestrator logs into a single ZIP file that you can send to the IBM Tivoli Software Support team. The ZIP file includes the log information that Tivoli Support representatives need to access so they can help diagnose a problem.
  • Page 105 Returned file The returned report file is located in the current directory. For additional options that can be used to obtain support for IBM products, refer to Appendix B, “Support information,” on page 225. Chapter 9. Contacting IBM Tivoli Software Support...
  • Page 106 Tivoli Intelligent Orchestrator Problem Determination and Troubleshooting Guide...

  • Page 107: Chapter 10. Tivoli Intelligent Orchestrator Messages

    Explanation: The uninstall process failed when the provided software module did not have the required third party software package. The third party software © Copyright IBM Corp. 2003, 2006 package is required to provide the name and version of the IBM Tivoli Configuration Manager Software Package.
  • Page 108 Explanation: An error occurred in the workflow because the server specified has a locale value that is null. The locale value is required to specify the locale value of the items that will be imported into the IBM database. Administrator Response: Verify that the server object does not have null locale value.
  • Page 109 COPCOM016E The directory V ALUE_0 does not exist. Explanation: An error occurred when the directory that contains the scripts that interact with IBM Tivoli Configuration Manager was not found. This directory contains the required scripts itcmDist.sh, tmeCkDt.sh, and others. This directory is usually $TIO_HOME/repository/tivoli/itcm.
  • Page 110 COPCOM037E A shell command error occurred and the system cannot create the InputStreamHelper for the error stream. Explanation: No additional information is available for this message. COPCOM038E A shell command error occurred and the system cannot create a BufferedWriter for the input stream. Explanation: No additional information is available for this message.
  • Page 111 COPCOM053E The system cannot allocate V ALUE_0 shares of resource V ALUE_1 from the V ALUE_2 host platform. Explanation: No additional information is available for this message. COPCOM054E The system cannot delete the "V ALUE_0" (V ALUE_1) software fix pack because it is part of the "V ALUE_2"...
  • Page 112 COPCOM071E The system cannot find the load balancer: V ALUE_0. Explanation: No additional information is available for this message. COPCOM072E The system cannot find the monitoring application: V ALUE_0. Explanation: While it imported monitoring application information from an XML file, the system looked in the data center model but did not find the monitoring application being associated.
  • Page 113 COPCOM088E The system cannot find the V ALUE_0 software product. Explanation: No additional information is available for this message. COPCOM089E The system cannot find the V ALUE_0 software stack entry. Explanation: No additional information is available for this message. COPCOM090E The system cannot find the V ALUE_0 software stack.
  • Page 114 Operator response: Detach the license pool from the stack definition before you attempt to delete it. COPCOM128E The system cannot delete all roles from a user with IBM Directory Server. At least one role is required. The first group found that would become empty is: V ALUE_0.
  • Page 115 COPCOM134E The password that you are trying to update cannot be null or empty for username V ALUE_0. Explanation: No additional information is available for this message. COPCOM135E The username that you are trying to update cannot be null or empty. Explanation: No additional information is available for this message.
  • Page 116 COPCOM157E The system cannot find the V ALUE_0 software product category. Explanation: No additional information is available for this message. COPCOM158E The system cannot find the V ALUE_0 interface card. Explanation: No additional information is available for this message. COPCOM159E The system cannot find the V ALUE_0 access rule.
  • Page 117 COPCOM178E The system cannot find the volume container settings V ALUE_0 with volume manager V ALUE_1 and spare pool V ALUE_2. Explanation: No additional information is available for this message. COPCOM179E The system cannot find the volume container settings V ALUE_0 with volume manager V ALUE_1 and application tier V ALUE_2.
  • Page 118 COPCOM196E The system cannot find the V ALUE_0 volume container. Explanation: No additional information is available for this message. COPCOM197E The system cannot find the V ALUE_0 logical volume. Explanation: No additional information is available for this message. COPCOM198E The system cannot find the V ALUE_0 file system.
  • Page 119 COPCOM216E No file system settings are defined in the logical volume settings V ALUE_0 of the V ALUE_1 storage template. Explanation: No additional information is available for this message. COPCOM217E The system cannot create the output file V ALUE_0. Explanation: No additional information is available for this message.
  • Page 120 COPCOM236E The system cannot find the supported requirement type: V ALUE_0. Explanation: No additional information is available for this message. COPCOM237E The system cannot find the V ALUE_0 software module. Explanation: No additional information is available for this message. COPCOM238E The system cannot find the V ALUE_0 resource allocation.
  • Page 121 Facility to determine the problem. To activate logging, set the TraceFileName variable in the Tivoli Enterprise Console configuration file. COPCOM264E The system cannot generate the Tivoli Enterprise Console (TEC) event because no event class name was specified. Explanation: The Send TEC Event Java plug-in uses the Tivoli Enterprise Console TECAgent code base to send TEC events to the Tivoli Enterprise Console (TEC) server.
  • Page 122 COPCOM278E The system cannot find the V ALUE_0 storage manager. Explanation: No additional information is available for this message. COPCOM279E The active zone set already exists in the V ALUE_0 storage area network fabric. Explanation: No additional information is available for this message.
  • Page 123 Ensure that the correct discovery object was used. Administrator Response: A software distribution application construct should be created for the IBM Tivoli Configuration Management server if one does not exist. Explanation: No additional information is available for this message.
  • Page 124 COPCOM316E The system cannot find the V ALUE_0 boot server type. Explanation: No additional information is available for this message. COPCOM317E The system cannot find the V ALUE_0 image type. Explanation: No additional information is available for this message. COPCOM321E The system cannot find the V ALUE_0 image.
  • Page 125 Explanation: Dictionary entries must be unique and duplicate ID values or names are not allowed. Operator response: This is an internal error. Contact your IBM service representative for assistance. COPCOM348E The system cannot create the offering, because an offering V ALUE_0 already exists.
  • Page 126 COPCOM355E The scheduled task type V ALUE_0 is not valid. Explanation: No additional information is available for this message. COPCOM356E Cannot create the scheduled task. Check the scheduled time and scheduled task type for valid input. Explanation: No additional information is available for this message.
  • Page 127 COPCOM374E The system cannot find the service instance by subscription with ID V ALUE_0. Explanation: No additional information is available for this message. COPCOM375E The system cannot create the Constraint with constraint type V ALUE_0. Explanation: The system does not recognize the type of the Constraint to be created.
  • Page 128 COPCOM392E The system cannot find the TCM object for the Hostname: V ALUE_0, Type: V ALUE_1, Object Label: V ALUE_2 Explanation: The object lookup failed for the given Object Label. Operator response: Ensure that the Object Label exists in the TCM database. COPCOM393E The lookup results were ambiguous for TCM object Hostname: V ALUE_0, Type: V ALUE_1, Object Label: V ALUE_2...
  • Page 129 COPCOM405E The Profile Manager is V ALUE_0. Explanation: The Profile Manager specified is not valid. Operator response: Ensure that the Profile Manager exists in the TCM environment. COPCOM407E Profile V ALUE_0 is not a managed profile. Explanation: The creation of the profile failed because it is not a managed profile.
  • Page 130 IBM Tivoli Configuration Manager server, etc. Operator response: Verify that the hostname of the IBM Tivoli Configuration Manager is correct and that a connection to the server can be established. Administrator Response: Verify that the RIM object is valid.
  • Page 131 IBM Tivoli Configuration Manager server are not valid or do not exist. Explanation: The username password combination that is specified in the SAP credentials for the IBM Tivoli Configuration Manager values is incorrect or was not specified. Operator response: Verify that the credentials for the data center model object V ALUE_0 are correct.
  • Page 132 COPCOM459E No software module was found in the data center model to install the Common Agent for the "V ALUE_0" operating system and the "V ALUE_1" platform. Explanation: The system searched the software modules that can install the Tivoli Common Agent specific to the server operating system and hardware platform, but did not find one.
  • Page 133 COPCOM477E The alternate gateway port is not correct. Explanation: No additional information is available for this message. COPCOM478E The endpoint port is not correct. Explanation: No additional information is available for this message. COPCOM479E The alternate endpoint port is not correct.
  • Page 134 COPCOM497E Error copying file "V ALUE_0" to endpoint using RXA: V ALUE_1. Explanation: No additional information is available for this message. COPCOM498E Error copying file "V ALUE_0" from endpoint using RXA: V ALUE_1. Explanation: No additional information is available for this message. COPCOM499E Error copying file using RXA: V ALUE_0.
  • Page 135 COPCOM520E Unable to parse attribute: V ALUE_0 from xml config file: V ALUE_1. Explanation: No additional information is available for this message. COPCOM521E Unable to read xml config file: V ALUE_0. Explanation: No additional information is available for this message. COPCOM522E Incorrect MAC address: V ALUE_0.

  • Page 136: Deployment Engine Subsystem Messages

    COPCOM539E Task "V ALUE_0" (Task Id: "V ALUE_1") failed. Explanation: The TPM task failed. COPCOM540E Task "V ALUE_0" (Task Id: "V ALUE_1") failed". Here is the error: V ALUE_2. Explanation: The TPM task failed, with an error log appended COPCOM541E The system cannot delete the "V ALUE_0"...
  • Page 137 COPDEX001E The system cannot get a JNDI context. Explanation: No additional information is available for this message. COPDEX002E The system cannot use the "V ALUE_0" JMS destination. Explanation: No additional information is available for this message. COPDEX003E The system cannot perform the type conversion for V ALUE_0 because the type information that was set has an incorrect value.
  • Page 138 COPDEX019E The condition V ALUE_0 is not valid. Explanation: No additional information is available for this message. COPDEX020E The system requires the V ALUE_0 attribute. Explanation: No additional information is available for this message. COPDEX021E The system cannot find the field name for the attribute: V ALUE_0.
  • Page 139 COPDEX038E A database error occurred: V ALUE_0. Explanation: No additional information is available for this message. COPDEX039E A configuration error occurred. Explanation: No additional information is available for this message. COPDEX040E A deployment engine exception occurred: V ALUE_0. Explanation: No additional information is available for this message.
  • Page 140 COPDEX060E A workflow XML parser error "V ALUE_0" occurred. Explanation: No additional information is available for this message. COPDEX061E The system expected a single value, but it received multiple values. Explanation: No additional information is available for this message. COPDEX062E A data insert error: "V ALUE_0" occurred.
  • Page 141 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 system encountered a problem when the name of the profile XML file was an empty string.
  • Page 142 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.
  • Page 143 Operator response: This is an internal error. Contact your IBM service representative. COPDEX111E An internal error occurred when the system tried to open the V ALUE_0 Tivoli Enterprise Console (TEC) configuration file.
  • Page 144 COPDEX132E The system is running a workflow V ALUE_0. No modifications can be made to the workflow while the workflow is running. Explanation: No additional information is available for this message. COPDEX134E A logical operation must have at least one parameter. Explanation: No additional information is available for this message.
  • Page 145 COPDEX149E No such parameter "V ALUE_0". Explanation: No additional information is available for this message. COPDEX150E Unknown instance permission "V ALUE_0". Explanation: No additional information is available for this message. COPDEX151E Duplicate permission "V ALUE_0" for parameter "V ALUE_1". Explanation: No additional information is available for this message.
  • Page 146 COPDEX170E The "V ALUE_0" Java plug-in does not exist. Explanation: No additional information is available for this message. COPDEX171E The system cannot update the Service Instance of ID V ALUE_0 with status V ALUE_1. Explanation: There might be a problem when connecting to the database.

  • Page 147: Job Distribution Service (Jds) Subsystem Messages

    COPDEX189E The tc-driver.xml in V ALUE_0 refers to a workflow V ALUE_1 that does not exist. Explanation: No additional information is available for this message. COPDEX190E The index "V ALUE_0" for array "V ALUE_1" is out of bounds. Explanation: No additional information is available for this message.
  • Page 148 you are using to manage users in your LDAP database does not have the support for customizable roles. You can either specify a different factory class name in user-factory.xml or continue using pre-defined roles. COPJEE007E The destination for a network configuration item cannot be null.
  • Page 149 COPJEE027E The system cannot copy credentials ID "V ALUE_0" specified in stack V ALUE_1 and service access point V ALUE_2. Explanation: No additional information is available for this message. COPJEE028E The system cannot identify credentials ID "V ALUE_0" specified in V ALUE_1 and service access point V ALUE_2.
  • Page 150 COPJEE043E The system cannot add server "V ALUE_0" to application tier "V ALUE_1" because the application tier already includes the server. Explanation: No additional information is available for this message. COPJEE044E The system cannot allocate a new IP address for subnetwork "V ALUE_0" and for the NIC ID "V ALUE_1".
  • Page 151 COPJEE060E Server: "V ALUE_0" was not removed from the spare resource pool "V ALUE_1". Explanation: A server can be dedicated to a designated application tier, or it can be a part of the resource pool. To remove a server from the spare resource pool, the server must be dedicated to an application tier or to another resource pool.
  • Page 152 (and usually happens when the user is updating some data). The most likely reason for it is a constraint violation or a miscellaneous database error. Inspecting the logs should help to localize the problem. COPJEE080E A record with this name already exists. A record name must be unique.
  • Page 153 COPJEE101E A user interface error occurred V ALUE_0 Explanation: Please consult the j2ee/console.log file for more information. Operator response: This is a generic error message that’s used when the UI does not have enough information about the error. Checking the error logs should help in localizing the problem.
  • Page 154 COPJEE154E Not enough servers are available to complete this task. Explanation: No additional information is available for this message. COPJEE160E The system cannot delete the power unit. Power outlets for this unit are still being used by devices. Explanation: Power outlets for this unit are still being used by devices.
  • Page 155 COPJEE205E A software requirement occurred. Verify the requirement name, type, and value. Explanation: No additional information is available for this message. COPJEE206E The system cannot find the Tivoli Data Warehouse report.properties file in the config subdirectory. Explanation: In this instance, either the system cannot find the Tivoli Data Warehouse report.properties file in the config subdirectory or the file is not configured correctly.
  • Page 156 Explanation: No additional information is available for this message. COPJEE236W WARNING: Do not modify these settings unless you have been instructed to do so by IBM Tivoli Software Support. Explanation: No additional information is available for this message. COPJEE240E The system cannot create the deployment plan.
  • Page 157 COPJEE281E The system cannot delete the resource pool with ID: "V ALUE_0" because it is associated with the following data center fragment IDs: "V ALUE_1". Explanation: No additional information is available for this message. COPJEE282E The system cannot delete the server with ID: "V ALUE_0"...
  • Page 158 COPJEE304E The LUN V ALUE_0 in fibre channel port V ALUE_1 is not available. Explanation: No additional information is available for this message. COPJEE305E Storage volume V ALUE_0 in storage subsystem V ALUE_1 already exists. Explanation: No additional information is available for this message.
  • Page 159 COPJEE326E The system failed to delete deployment request. Explanation: No additional information is available for this message. COPJEE327E Fibre adapter port, with port ID "V ALUE_0", does not belong to "V ALUE_1" storage subsystem. Explanation: No additional information is available for this message.
  • Page 160 COPJEE345E Multiple Password credentials were returned. Explanation: The system contains multiple Password credentials that have the same search key. Operator response: Contact your system administrator. COPJEE347E The operation V ALUE_0 is not implemented. Explanation: No additional information is available for this message. COPJEE348E The system cannot complete the database operation.
  • Page 161 COPJEE364E The report was not created when using report creator. Report: V ALUE_0. Explanation: The database transaction failed. COPJEE365E The report name is required to create the user’s report definition. Explanation: The required input, report name, is not passed in. COPJEE366E The user’s report definition was not created.

  • Page 162: Policy Engines Subsystem Messages

    COPJEE381E A user interface error occurred. The configuration is incorrect for: action="V ALUE_0", objectType="V ALUE_1". Explanation: No additional information is available for this message. COPJEE382E The system can not find the VLAN in the switch port with ID: "V ALUE_0". Explanation: No additional information is available for this message.
  • Page 163 COPPEZ041E A generic data acquisition configuration error occurred. Operator response: Validate the configuration of the acquisition engine. COPPEZ042E V ALUE_0" is not a valid device type. Operator response: Validate the configuration of the acquisition engine. COPPEZ043E The management IP address "V ALUE_0"...
  • Page 164 COPPEZ071E An SNMP error (Error code=V ALUE_0 occurred in response to Error name=V ALUE_1). Explanation: No additional information is available for this message. COPPEZ072E The SNMP GET request cannot return any results. Explanation: No additional information is available for this message. COPPEZ073E An SNMP IO error occurred.

  • Page 165: Common Agent Subsystem Messages

    COPPEZ116E The endpoint label is null or empty. Explanation: No additional information is available for this message. COPPEZ117E The credentials for the IBM Tivoli Monitoring server are not configured properly. Explanation: No additional information is available for this message.

  • Page 166: Tc Driver Manager Subsystem Messages

    COPTCA009E Error copying Subagent jar V ALUE_0 to the endpoint. Explanation: For more information, check the logs/msgAgent.log file on the endpoint in the agent install directory. COPTCA010E Error during Agent operation: V ALUE_0. Explanation: No additional information is available for this message. COPTCA011E Error during WGet from the CopyFile subagent.
  • Page 167 COPTDM001E The system does not support the V ALUE_0 operating system running Kula. Explanation: No additional information is available for this message. COPTDM003E The application is not specified. Explanation: No additional information is available for this message. COPTDM004E Authentication is required, but the system cannot find the credentials for SAP ID "V ALUE_0"...
  • Page 168 COPTDM023E The system cannot find the virtual IP address V ALUE_0. Explanation: No additional information is available for this message. COPTDM024E The system cannot install the "V ALUE_0" software product. Review the execution logs for more details. Explanation: No additional information is available for this message.
  • Page 169 COPTDM044E The argument is not valid. The RuntimeParameters value is null. Explanation: No additional information is available for this message. COPTDM045E The argument is not valid because the RuntimeParameters value cannot be null. Explanation: No additional information is available for this message. COPTDM051E The system cannot find the V ALUE_0 software stack within V ALUE_1.
  • Page 170 COPTDM070E The system cannot find the service access point for device ID "V ALUE_0" with protocol "V ALUE_1" and context "V ALUE_2". Explanation: No additional information is available for this message. COPTDM071E The system cannot find a service access point for device ID "V ALUE_0" with protocol "V ALUE_1"...
  • Page 171 COPTDM085E The system cannot find the credentials for device ID "V ALUE_0" and the SAP ID "V ALUE_1" with the credentials key "V ALUE_2". Explanation: No additional information is available for this message. COPTDM087E The system cannot find the software product ID "V ALUE_0".
  • Page 172 the transitions and then try again. COPTDM102E The system cannot stop the monitoring resource "V ALUE_0" using the "V ALUE_1" monitoring application. Request ID "V ALUE_2". Explanation: The system cannot stop monitoring the resource. Operator response: Search the workflow execution history for errors that use the request ID.
  • Page 173 COPTDM119E No device is associated with SAP ID: "V ALUE_0". Explanation: No additional information is available for this message. COPTDM120E The system cannot reach IP address "V ALUE_0" by SNMP. Explanation: No additional information is available for this message. COPTDM121E A driver error occurred. Explanation: No additional information is available for this message.
  • Page 174 COPTDM148E The system cannot create the new device model "V ALUE_0" because it already exists. Explanation: No additional information is available for this message. COPTDM150E An error occurred while the system installed the driver "V ALUE_0". Explanation: No additional information is available for this message.
  • Page 175 Explanation: No additional information is available for this message. COPTDM172E An error occurred while the system uninstalled the "V ALUE_0"driver because the driver status must be V ALUE_1. Explanation: No additional information is available for this message. COPTDM173E The configuration directory must be specified in the tcdrivermanager.xml file.

  • Page 176: Utilities Subsystem Messages

    COPTDM185E The file V ALUE_0 is already used by TCDriver V ALUE_1. Explanation: TCDriver file cannot be overwritten by a file from another tcdriver. COPTDM186E The TCDriver object V ALUE_0: V ALUE_1 is still used by other DCM objects. Explanation: Remove all references to the TCDriver and try again.
  • Page 177 Explanation: No additional information is available for this message. COPUTL013E Usage: MSADMigration migration_homePath hostname principalFullDN(e.g. cn=hosting,cn=Users,dc=ibm,dc=com) password port ssl(true/false) baseDN(e.g. OU=TIO,DC=IBM,DC=com) Explanation: No additional information is available for this message. COPUTL014E Cannot create a JDOM document object from the xml file V ALUE_0.

  • Page 178: Compliance Messages

    Compliance Messages COPDSE001E The system cannot update the given guest access desired state element because it is not stored in DCM. Its SecurityDesiredStateElementId is V ALUE_0, its UserAccountDesiredStateElmentId is V ALUE_1. Explanation: No additional information is available for this message. COPDSE002E The system cannot update the given root remote login desired state element because it is not stored in DCM.
  • Page 179 Explanation: No additional information is available for this message. COPDSE015E The DSE setting value to be validated cannot be null. Explanation: No additional information is available for this message. COPDSE016E The system cannot validate the non-supported DSE setting type: V ALUE_0. Explanation: No additional information is available for this message.

  • Page 180: Group Messages

    COPDSE103E Each permission character in the input permission string V ALUE_0 must be one of "-", "r", "w", "x", or "s". Explanation: No additional information is available for this message. COPDSE104E The input desired state name V ALUE_0 should be no longer than 256 characters. Explanation: No additional information is available for this message.

  • Page 181: Networking Messages

    determined by a database query. It is not possible to add members to a dynamic group. COPGRP009E Cannot remove the object "V ALUE_0" from the group "V ALUE_1" because it is a dynamic group. Explanation: The members of a dynamic group are determined by a database query.
  • Page 182 Explanation: No additional information is available for this message. COPNET014E The system cannot find VLAN: V ALUE_0. Explanation: No additional information is available for this message. COPNET015E The switch endpoint mode V ALUE_0 is not valid. Explanation: No additional information is available for this message.

  • Page 183: Rxa Messages

    RXA Messages CTGRI0000E Could not establish a connection to the target machine with the authorization credentials that were provided. Explanation: A connection to the target machine was denied. This is probably due to improper authorization credentials being specified. Programmer response: Verify that the login name and password are valid for the target machine.
  • Page 184 Windows binary, which is used to run remote applications, anywhere in the classpath. Programmer response: The trisvc.exe binary, which is normally located in an IBM Tivoli Remote Execution and Access JAR file, cannot be located. Verify that the TRIsvc.exe file is in the JAR file.

  • Page 185: Software Distribution Messages

    CTGRI0024E Access to Resource is denied. Explanation: The operation failed because access to a resource has been denied. This could be due to a permission problem or a sharing violation. Programmer response: Verify that the user has sufficient authority to perform the operation and that the resource being accessed is not locked.
  • Page 186 Operator response: In the package definition file, specify the section name. DISSP6009W File file name not found in directory name Would you correct it? Explanation: The name of the file you specified does not exist in the specified directory. Message Variables: where file name The name of the file.
  • Page 187 ® v The OS/400 Preparation Site was installed correctly on the system. v The software package contains valid objects. v The user is authorized to perform the operation. DISSP6020E Failed to export file name Explanation: An error occurred while the file was being exported.
  • Page 188 DISSP6030W The configuration file file name was not found Explanation: You specified a configuration file that does not exist. Message Variables: where file name The name of the file. System action: The operation is not performed. Operator response: Specify the correct file name and try the operation again.
  • Page 189 Operator response: Enter the path to a valid directory. DISSP6044E Enter a value in the suggested range. Explanation: You have entered a value which is outside the supported range. The correct range is displayed in the GUI by the relevant text field. System action: The operation is not performed.
  • Page 190 password are defined in Tivoli Provisioning Manager WebUI. Tivoli Intelligent Orchestrator Problem Determination and Troubleshooting Guide...

  • Page 191: Chapter 11. Tivoli Common Agent Services Messages

    Explanation: The common agent registration service was unable to register the common agent because the © Copyright IBM Corp. 2003, 2006 necessary properties could not be accessed. The endpoint.properties file might be corrupted or missing. System action: If the common agent cannot register, it will not be able to communicate with the agent manager.
  • Page 192 common agent will send a notification to the agent recovery service. Administrator Response: Check the agent manager logs to find information that might help you diagnose the problem. Security issues should be resolved as soon as possible. BTC1011E A failure occurred while accessing the key store.
  • Page 193 BTC1026I The common agent credentials are valid. The common agent has determined that it does not need to register for security credentials at this time. Explanation: No additional information is available for this message. BTC1027E The common agent failed to renew client credentials with the common agent registration service name at port number.
  • Page 194 BTC1041I command to register the common agent with the agent registration service Explanation: No additional information is available for this message. BTC1042I command to renew the certificate revocation list Explanation: No additional information is available for this message. BTC1043I command to renew the certificate of the common agent Explanation: No additional information is available for this message.
  • Page 195 BTC1048E The common agent failed to renew its certificate revocation list. Explanation: The common agent failed to renew its certificate revocation list with the certificate authority of the agent manager. One of the following reasons might be the cause of the failure: v The certificate revocation list port of the agent manager cannot be reached, either because the agent manager is not active, an error exists in the network...
  • Page 196 If resetting the GUID failed, or the problem persists, contact customer support. BTC1050I true Explanation: No additional information is available for this message. BTC1051I false Explanation: No additional information is available for this message. BTC1052I The common agent successfully renewed its security credentials. Explanation: No additional information is available for this message.
  • Page 197 BTC2200I The system is restarting the common agent. Explanation: No additional information is available for this message. BTC2201E The system encountered an error while reading the common agent configuration properties. Verify that the file_name file exists in the config directory on the common agent.
  • Page 198 BTC2209I The common agent is being initialized. Explanation: No additional information is available for this message. BTC2210E The shutdown worker failed to sleep while restarting the common agent. Negligible stack traces might have been thrown. Explanation: The shutdown worker failed to sleep while restarting the common agent.
  • Page 199 BTC2411I The locale was successfully set to language_code and region_code. Explanation: No additional information is available for this message. BTC2412I The locale was not set. The default locale is language_code_ region_code. Explanation: No additional information is available for this message. BTC3001E The system encountered an error while creating the file_name file.
  • Page 200 BTC3009E The bundle_name bundle cannot be deleted because system cannot be found in the OSGi storage. Explanation: The specified bundle was not found in the OSGi storage. The bundle might be missing, inaccessible, corrupted, or it might not be installed. System action: The specified bundle was not deleted.
  • Page 201 System action: The bundle was not installed. Administrator Response: Verify that the specified bundle is the one you intended to install. If you want to replace this bundle you must first uninstall it, then install the bundle again, or try updating it. BTC3106I The system is retrieving a LifecycleActivator from the bundle_name...
  • Page 202 BTC3117E The preupdate of the bundle, bundle_name failed. Explanation: The preUpdate logic specified in the bundle LifecycleActivator failed. System action: The preUpdate logic was not completed successfully. The bundle might not be updated correctly. Administrator Response: If you continue to experience problems with the bundle, try uninstalling and reinstalling the bundle.
  • Page 203 BTC3135I command to create a directory in the common agent base directory Explanation: No additional information is available for this message. BTC3136I command to delete a directory from the common agent base directory Explanation: No additional information is available for this message. BTC3137I command to copy the file from the URL to the directory in the common agent...
  • Page 204 BTC3154I The system failed to create the directory_name directory because the specified directory name is not valid. Explanation: No additional information is available for this message. BTC3155I The system encountered an error while attempting to delete the directory_name directory. Explanation: No additional information is available for this message.
  • Page 205 System action: The bundle was not started. Administrator Response: Verify that the bundle is in the OSGi storage and that it has all of the necessary components. If necessary, update the bundle in the OSGi storage. BTC3174E The deployer service failed to save the installation status.
  • Page 206 BTC4008I The common agent is reducing the service tracker cache size. Explanation: No additional information is available for this message. BTC4009E The connector cannot list the OSGi services properly. Explanation: The connector cannot list the OSGi services. This might be caused by a problem that occurred when the connector attempted to obtain information from the OSGi container.
  • Page 207 BTC4027I command to restart the common agent Explanation: No additional information is available for this message. BTC4028I unknown parameter Explanation: No additional information is available for this message. BTC4029I command to get the ID of the machine that the common agent is running on Explanation: No additional information is available for this message.
  • Page 208 BTC4043E The command-line interface command failed. A communication error occurred. Verify that the common agent is registered and active on port port_number. Explanation: This message is displayed when command-line interface command invocation fails due to a communication problem with the common agent. The communication failure might be caused by one of the following reasons: v The common agent is not active.
  • Page 209 BTC5007I The process_name status collection process is ending. Explanation: No additional information is available for this message. BTC5015I A new subagent bundle status report has been created for the subagent_name subagent bundle. Explanation: No additional information is available for this message. BTC5018I The status report for host host_name, URI URI_name, and port number port_number...
  • Page 210 BTC5027I Status has been sent. Explanation: No additional information is available for this message. BTC5028I The status report for host host_name, URI URI_name, and port port_number was not delivered. Explanation: The specified status report was not delivered. System action: The common agent will continue to run, but the agent manager will not know the common agent status.
  • Page 211 v Using a Web browser, access the URL, url. 4. Start the upgrade again. 5. If the common agent upgraded continues to fail, collect the common agent logs and contact customer support. BTC5049E The upgrade bundle cannot retrieve the value for the key key from CAUpgrade.properties file.
  • Page 212 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.
  • Page 213 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 name of the file being unpacked and the specific exception that resulted, you must look in the logs for the message that was recorded when the...

  • Page 214: Agent Manager Messages

    Administrator Response: Make sure that the agent manager configuration file (AgentManager.properties) is in the correct location, and then restart the agent manager. If the problem continues, contact IBM Customer Support. Tivoli Intelligent Orchestrator Problem Determination and Troubleshooting Guide System action: The common agent will continue to run but cannot report status to the agent manager.
  • Page 215 If the problem continues, there might be either a problem with the file system permissions or a disk failure. For other errors, contact IBM Customer Support. Programmer response: If the exception indicates that the class was not found (ClassNotFoundException), make sure that the name of the class is spelled correctly in the Registration.Listeners.Agent.Request property of...
  • Page 216 If the problem continues, there might be either a problem with the file system permissions or a disk failure. For other errors, contact IBM Customer Support. Programmer response: If the exception indicates that the class was not found (ClassNotFoundException), make sure that the name of the class is spelled correctly in the Config.Listener.Agent and...
  • Page 217 SQL error associated with this problem for additional information about the problem. Turn tracing on, if it is not already on, and restart the agent manager. If the problem continues, contact IBM Customer Support. CTGEM0013E The following Web Services Description Language (WSDL) file was not found: file_name.
  • Page 218 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.
  • Page 219 System action: The certificate authority is not initialized. Certificate generation and renewal cannot occur, so registration requests cannot be processed. Administrator Response: Collect the agent manager and trace files and contact IBM Customer Support. CTGEM0028E The identification information in the certificate request is incomplete. Both the operating system GUID and the component ID must be specified.
  • Page 220 Administrator Response: This error might be caused by an error in the configuration file. Verify that the syntax of the file is correct and then restart the agent manager. If the problem continues, contact IBM Customer Support. CTGEM0034W The agent manager cannot write the agent manager ID to the file_name file.
  • Page 221 After making sure that everything is in order, restart the agent manager. If the problem continues, contact IBM Customer Support. CTGEM0035E An agent registration was rejected...
  • Page 222 Gather the log files and contact IBM Customer Support. Programmer response: A query may consist of SQL provided by the Agent Manager itself, or written by a Resource Manager using the Agent Manager.
  • Page 223 Instructions for regenerating the keystore file are located in the agent manager documentation. 7. If the problem continues after regenerating the keystore file, contact IBM Customer Support. CTGEM0048E The agent registration password cannot be updated in the agent manager configuration file (AgentManager.properties) because the...
  • Page 224 Authorization.xml file, relative to the ARS.directory location. 5. When the files and properties are correct, retry the operation that failed. 6. If the problem continues, contact IBM Customer Support. CTGEM0053E The UpdatePW program encountered an error. It was called by the command command.
  • Page 225 Instructions for regenerating the keystore file are located in the agent manager documentation. 8. If the problem continues after regenerating the keystore file, contact IBM Customer Support. CTGEM0054E The UpdatePW program received incorrect input arguments.
  • Page 226 Instructions for regenerating the keystore file are located in the agent manager documentation. 6. If the problem continues after regenerating the keystore file, contact IBM Customer Support. CTGEM0060E An error occurred while attempting to encrypt the resource manager registration password.
  • Page 227 Authorization.xml file, relative to the ARS.directory location. 5. When the files and properties are correct, retry the operation that failed. 6. If the problem continues, contact IBM Customer Support. CTGEM0150I Initializing the recovery service ... Explanation: No additional information is available for this message.
  • Page 228 The message bundle was found but does not contain the specified message key v The message bundle is in the wrong directory Administrator Response: Collect the message and trace files and contact IBM Customer Support. CTGEM2100I The WebSphere configuration script script_name started. The action taken is action_code.
  • Page 229 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.
  • Page 230 (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. CTGEM2115E The value of the property property in the properties file is incorrect. The value...
  • Page 231 GetAMInfo command again. If the problem persists, either the file system or the version information file is damaged. Locate the version information file if possible and then contact IBM Customer Support. CTGEM2123I The wrong number of parameters was specified.
  • Page 232 Tivoli Intelligent Orchestrator Problem Determination and Troubleshooting Guide...

  • Page 233: Appendix A. Common Agent Serviceability Tool

    IBM Customer Support for analysis in the event of problems with the common agent. The archive includes an HTML compilation of the information gathered.
  • Page 234 v GUID v SysInfo (Host Name, IP addr, OS Arch, OS Name, OS Ver, Java Ver, Java VM, Java VM Ver, CA Install Dir) v common agent version number v ipconfig /all (″ifconfig -a″ on UNIX or Linux) v netstat -a v Listing of following directories: –...
  • Page 235 Table 14. Files included in the CASservice.zip file (continued) File name All files from logs directory: msgAgent.log nonstop.log smfnonstop.log SystemErr.log SystemOut.log traceAgent.log All files from logs\install directory: ep_install.err ep_install.log epInstallStatus.log guid_install.err guid_install.log trace_ep_install.err trace_ep_install.log File path <basedir>\logs\ <basedir>\logs\ <basedir>\logs\ <basedir>\logs\ <basedir>\logs\ <basedir>\logs\ <basedir>\logs\install\...
  • Page 236 Tivoli Intelligent Orchestrator Problem Determination and Troubleshooting Guide...

  • Page 237: Appendix B. Support Information

    “Contacting IBM Software Support” on page 226 Searching knowledge bases If you have a problem with your IBM software, you want it resolved quickly. Begin by searching the available knowledge bases to determine whether the resolution to your problem is already documented.

  • Page 238: Contacting Ibm Software Support

    – Online: Go to the Passport Advantage Web page (http://www-306.ibm.com/software/howtobuy/passportadvantage/) and click How to Enroll – By phone: For the phone number to call in your country, go to the IBM Software Support Web site (http://techsupport.services.ibm.com/guides/ contacts.html) and click the name of your geographic region.

  • Page 239: Determine The Business Impact Of Your Problem

    3. Submit your problem to IBM Software Support. Determine the business impact of your problem When you report a problem to IBM, you are asked to supply a severity level. Therefore, you need to understand and assess the business impact of the problem you are reporting.
  • Page 240 For more information about problem resolution, see Searching knowledge bases and Obtaining fixes. Tivoli Intelligent Orchestrator Problem Determination and Troubleshooting Guide...

  • Page 241: Appendix C. Notices

    Web sites. The materials at those Web sites are not part of the materials for this IBM product and use of those Web sites is at your own risk.

  • Page 242: Trademarks

    The licensed program described in this document and all licensed material available for it are provided by IBM under terms of the IBM Customer Agreement, IBM International Program License Agreement or any equivalent agreement between us.

  • Page 243: Index

    Common Agent messages listing 179 Common Base Event logs 37 configuring logs 40 conventions typeface x © Copyright IBM Corp. 2003, 2006 customer support see Software Support x, 226 problems 84 troubleshooting 84 creating a database state error in a...
  • Page 244 91 contacting 91 Level Reporting tool for the WebSphere Application Server platform 92 ZIP tool for sending logs to IBM for review 92 trace logs 37 training, Tivoli software x troubleshooting application does not start on...
  • Page 245 troubleshooting (continued) manually associating discovered software resources with software definitions 75 Microsoft Active Directory installation fails 57, 58 password for creating NetView user account does not meet requirements 59 patch install fails 76 problems occur when administering the product from the Web interface 69 remote connection to the database hangs on Windows 72...
  • Page 246 Tivoli Intelligent Orchestrator Problem Determination and Troubleshooting Guide...
  • Page 248 Printed in USA SC32-2216-00...

Table of Contents