Tivoli Intelligent Orchestrator ® Version 5.
Tivoli Intelligent Orchestrator ® Version 5.
Note: 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.
Contents Preface . . . . . . . . . . . . . . vii Who should read this book . . . . . . . . . vii Publications . . . . . . . . . . . . . . vii Tivoli Intelligent Orchestrator library . . . . . vii Prerequisite publications . . . . . . . . . viii Related publications and resources . . . . . viii Accessing publications online . . . . . . . ix Ordering publications . . . . . . . . . . . ix Accessibility . . . . . . . . . . . . . . ix Tivoli software training . . . . . . . . . . . x Support information . . . . .
The silent installation program for Tivoli 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 . The agent manager installation fails during the Tivoli Intelligent Orchestrator installation . . .
Common agent subsystem messages . TC driver manager subsystem messages Utilities subsystem messages . . . . Compliance Messages . . . . . . Group Messages . . . . . . . . Networking Messages . . . . . . RXA Messages . . . . . . . . . Software Distribution Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153 154 164 166 168 169 171 173 Chapter 11. Tivoli Common Agent Services messages . . . . . . . . . 179 Common Agent messages . Agent Manager messages . . . . . . . .
vi Tivoli Intelligent Orchestrator Problem Determination and Troubleshooting Guide
Preface This guide describes how to identify and resolve problems that might occur when you use Tivoli® Intelligent Orchestrator or Tivoli Provisioning Manager. The instructions in this book apply to both Tivoli Intelligent Orchestrator and Tivoli Provisioning Manager and will clearly identify any information or tasks that apply only to one application or the other.
Explains how to install and upgrade Tivoli Intelligent Orchestrator software. This guide also provides information about troubleshooting installation problems. v Tivoli Intelligent Orchestrator Migration Guide This book describes the steps to migrate from a previous version of Tivoli Intelligent Orchestrator. v Tivoli Intelligent Orchestrator Release Notes® These release notes describe last minute product changes and known problems in the Tivoli Intelligent Orchestrator product release.
v The Tivoli Software Library provides a variety of Tivoli publications such as white papers, datasheets, demonstrations, redbooks, and announcement letters. The Tivoli Software Library is available on the Web at: http:// publib.boulder.ibm.com/tividd/td/tdprodlist.html v The Tivoli Software Glossary includes definitions for many of the technical terms related to Tivoli software. The Tivoli Software Glossary is available at http://publib.boulder.ibm.com/tividd/glossary/tivoliglossarymst.
Tivoli software training For Tivoli software training information, refer to the IBM Tivoli Education Web site: http://www.ibm.com/software/tivoli/education. 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.
Chapter 1. Introduction to troubleshooting Problem determination, or troubleshooting, is a process of determining why a product is not functioning in the expected manner. This guide provides information to help you identify and resolve problems that you encounter when using Tivoli Intelligent Orchestrator. Product and system overview Tivoli Intelligent Orchestrator is an automated resource management solution for corporate and Internet data centers.
v Each asset is represented by a data center object. When you make a change to an asset with Tivoli Intelligent Orchestrator, the data center object is updated in the data center model. If a change is made outside of Tivoli Intelligent Orchestrator, the external change can be identified by comparing it with the data center object in the data center model.
Product architecture Tivoli Intelligent Orchestrator includes the following main components: Device-specific protocols (For ex.
from each managed application environment in the data center. It captures and filters data from the application, operating system, and infrastructure layers and communicates the data to other components. objective analyzer This component determines the resource requirements of each application, and identifies trends and peaks in resource use. Each managed application environment has an associated objective analyzer.
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.
You might want to consider the following general recommendations for backing up your Tivoli Intelligent Orchestrator system: v Perform a full backup of your existing DB2 Universal Database or Oracle database. General guidelines for backing up DB2 Universal Database and Oracle9i Database data are provided in the Tivoli Intelligent Orchestrator Version 5.1 Migration Guide. For more details, refer to the DB2 Universal Database information center available at http://publib.boulder.ibm.
Chapter 2. Problem determination essentials for Tivoli Intelligent Orchestrator This chapter describes how to approach troubleshooting in Tivoli Intelligent Orchestrator. Providing methodologies and troubleshooting methods for identifying problems in Tivoli Intelligent Orchestrator will help you to reduce the time spent finding resolutions to these problems.
v What was the first symptom of the problem? Have you noticed other symptoms occurring simultaneously? v Does the problem affect only one system or multiple systems? v Did you receive an error message indicating what the problem is? v If the problem can be reproduced, what are the steps that you need to perform to recreate it? Identifying the cause of the problem The information you gathered during the previous phase helped you to correctly identify the problem and describe the context that triggered it.
searching the available 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. You should start by verifying whether all the hardware and software prerequisites have been met.
The following stages are described to the Tivoli Intelligent Orchestrator problem determination process: 1. “Troubleshooting the prerequisite installation” 2. “Tivoli Intelligent Orchestrator installation and subcomponent configuration verification” on page 17 3. “Tivoli Intelligent Orchestrator runtime problem determination” on page 21 4. “Accessing the knowledge bases” on page 26 5.
v On Windows, launch Task Manager and check the Processes window. v On UNIX, run the following command to list all DB2 Universal Databaseprocesses: db2_local_ps The required DB2 Universal Database processes include: v db2fmd v Db2resync v db2dasrrm v db2srvlst v db2fmcd v db2agent (LDAP) v db2wdog v db2fmp v db2sysc v db2agent (TIOINTER) v db2ckpwd v db2loggr (TC) v db2gds v v db2syslog v db2dlock (TC) v db2ipccm v db2pfchr v db2tcpcm v db2pclnr db2loggw (TC) v db2event 4.
Use the Windows Services panel, or issue the ibmdiradm command on UNIX to verify if the service is running. IBM Directory Administrator uses the port number 3538 for requests. You can also start and stop IBM Tivoli Directory Server using the ibmdirctl command: v Starting the IBM Tivoli Directory Server: ibmdirctl -D cn=root -w start v Stopping the IBM Tivoli Directory Server: ibmdirctl -D cn=root -w stop 3.
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 Check the ivt.log file for errors.
administrative console, security can be disabled in this file by changing the value of the enabled parameter in the second line from true to false. By default, represents the host name. Server.xml This file contains server-specific configuration information, and is located in the $WAS_HOME/config/cells/| /nodes//servers/ server1 directory. Java.security This file contains security properties used by the java.security classes. It is located in the $WAS_HOME/java/jre/lib/security directory. | |
v If no error can be found, look for other symptoms in the log file. 2. Find the first occurrence of the error in the log file. You will either see an error message or an error exception with a stack trace. 3. Review the proper error message. It will be either from WebSphere Application Server or from the application that caught and properly handled the exception. Review the message and investigate. 4.
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 EJBContainerI EJBContainerI . . . ApplicationMg A WSVR0200I: Starting application: DefaultApplication I WSVR0207I: Preparing to start EJB jar: Increment.jar I WSVR0037I: Starting EJB jar: Increment.
HttpTransport HttpTransport HttpTransport HttpTransport A A A A SRVE0171I: SRVE0171I: SRVE0171I: SRVE0171I: Transport Transport Transport Transport https is listening on port 9,043. https is listening on port 9,511. https is listening on port 9,512. http is listening on port 9,513.
v Starts the WebSphere Application Server. v Configures the WebSphere Application Server, including: – WebSphere Application Server configuration – WebSphere Application Server deployment – WebSphere Application Server setup on UNIX, to run as user configuration v Enables security for the WebSphere Application Server. v On Windows, it creates the Windows Service. v On Windows, it creates keys in Windows registry. v Reinitializes the database.
Verify if the DCM_OBJECT table is listed. If not, determine what user ID is required to connect to see the DCM_OBJECT table, and update the dcm.xml file and the kula user appropriately. If the table list is successfully created, verify the DB2 Universal Database connection information in the dcm.xml file. 2. If you cannot connect manually to the database, check if the database is started successfully. See “DB2 Universal Database verification” on page 10.
The output should return the following entries: tioldap, tiointernal, and tioappadmin. c. Confirm that a particular user or group has been imported: ldapsearch -v -h < ldapserver > -D cn=root -w -p 389 -b "dc=ibm,dc=com" cn= This should return the full output of the specified user. d.
c. 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. 4. Search the knowledge bases and, if necessary, contact Support. For more information, refer to Appendix B, “Support information,” on page 225.
Constraints are listed in the $TIO_HOME/sql/db2/dbschema.sql file as foreign keys and primary keys. 2. Identify the type of constraint, by specifying whether it is an object addition or an object removal. 3. In the dbschema.sql file, search the ALTER TABLE constraint for the table that interests you. Use the table name from the error message and the type of constraint identified. 4.
8. Search the knowledge bases and, if necessary, contact Support. For more information, refer to Appendix B, “Support information,” on page 225. WebSphere Application Server error problem determination: If you have encountered a WebSphere Application Server error, use SystemOut.log and follow these steps: 1. In the SystemOut.log file, find the last startup section by going to the end of the file and then searching upwards for "End Display". If you cannot find it, start the WebSphere Application Server.
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” on page 22. b. If XA connection exceptions are found, go to “DB2 Universal Database error problem determination” on page 21. c.
2005-05-02 10:24:11,123 ERROR [Servlet.Engine.Transports : 2] (Location.java:506) webui.Location: Error Code = COPCOM093EdcmSqlException ERROR MESSAGE = COPCOM093E The JDBC driver caused an SQL exception. 1. NESTED EXCEPTION: MESSAGE = [IBM][CLI Driver][DB2/6000] SQL0532N A parent row cannot be deleted because the relationship "DB2INST1.RECOMMENDATION_REQUEST.SQL050324085328960" restricts the deletion. SQLSTATE=23504 DETAILS: DB2INST1.RECOMMENDATION_REQUEST(POOL_ID) -> DB2INST1.SPARE_POOL(POOL_ID) IP = 9.3.
ssh -l username IP ’command’ 4. If running the command using the command line interface works, it is an environment issue. In your workflow source, check your .profile first. 5. If running the command using the command line interface fails, run the command directly on the managed server. 6. If running the command on the managed server works, debug the SSH configuration issue. For more information on SSH configurations, refer to the Security section of the Tivoli Intelligent Orchestrator information center.
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 Description Syntax Migrates all of the existing credentials from the TIO database tables based on a new encryption key.
Table 1. Tivoli Intelligent Orchestrator command line tools (continued) Name Location Description Syntax dcmExport.cmd dcmExport.sh v On Windows: %TIO_HOME%\ tools Example: dcmExport.cmd c:/myDirectory/ myOutput.xml If outputFilename is not specified, the default output file name is dcmExport.xml in the current directory). Use of option [-d] outputs protected data in clear text (default is encrypted). dcmExport.cmd [-d] [outputFilename] dcmExport.
Table 1. Tivoli Intelligent Orchestrator command line tools (continued) Name Location Description Syntax retrieveDetails.cmd retrieveDetails.sh v On Windows: %TIO_HOME%\ tools Retrieves and displays a data center model object based on the specified identifier. retrieveDetails.cmd -i [-i]* retrieveDetails.sh -i [-i]* v On UNIX: $TIO_HOME/ tools Chapter 2.
Table 1. Tivoli Intelligent Orchestrator command line tools (continued) Name Location Description siregister.cmd siregister.sh v On Windows: %TIO_HOME%\ tools Extracts installable files from Macrovision Solution Installation packages and adds them to the Tivoli Intelligent Orchestrator software catalog. v On UNIX: $TIO_HOME/ tools Syntax siregister.cmd [package_location] [repository_name] [repository_mount_point] [mount_path] [repository_host_name] [user_name] siregister.
Table 1. Tivoli Intelligent Orchestrator command line tools (continued) Name Location Description Syntax tc-drivermanager.cmd tc-driver-manager.sh v On Windows: %TIO_HOME%\ tools Installs, uninstalls, gets information, and gets the device model for the specified automation package. Available commands are: tc-driver-manager.cmd [command] tc-driver-manager.
Table 1. Tivoli Intelligent Orchestrator command line tools (continued) Name Location Description xmlImport.cmd xmlImport.sh v On Windows: %TIO_HOME%\ tools Imports objects from xmlImport.cmd file_URL a specified XML file [file_URL] xmlImport.sh into the data center file_URL [file_URL] model. The XML source file must be validated against the xmlimport.dtd file (located in the $TIO_HOME/xml directory), that defines the legal building blocks of the XML document.
Table 2. WebSphere Application Server command line tools (continued) Name Location Description backupConfig restoreConfig v On Windows: %WAS_HOME%\ bin Archives the contents of the %WAS_HOME%\config directory and subdirectories to a specified ZIP file, or toWebSphereConfig_.zip, created in the same directory in which the command is run. v On UNIX: $WAS_HOME/ bin was_security.bat was_security.
34 Tivoli Intelligent Orchestrator Problem Determination and Troubleshooting Guide
Chapter 3. Log file types Tivoli Intelligent Orchestrator produces message logs, trace logs, and Common Base Event logs that can be configured dynamically. 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.
v ### is 3-digit unique serial or message number. v Z is the severity code indicator, including the following indicators: Severity code Description I Informational message. The message provides information or feedback about normal events that have occurred or are occurring, but do not require you to take action. The message might also request that you provide information in instances where the outcome of the information you provide will not be negative. W Warning message.
Action title Description Administrator Response Describes what response a system administrator might be able to take. Programmer Response Describes what response a system programmer might be able to take. In the example, the action follows the label Operator Response. Trace logs Tivoli Intelligent Orchestrator provides configurable tracing capabilities that can help you determine the cause of a problem.
38 Tivoli Intelligent Orchestrator Problem Determination and Troubleshooting Guide
Chapter 4. Locating and configuring log files This release of Tivoli Intelligent Orchestrator produces logs that follow the Tivoli Common Directory standard. Log locations To provide a consistent mechanism for locating serviceability information, Tivoli products and applications have implemented the Tivoli Common Directory. The Tivoli Common Directory represents a central location on systems running Tivoli software for storing serviceability-related files.
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 Description msg_error#com.thinkdynamics.kanaha. util.logging.MessageLevel Extended for message logs msg_warn#com.thinkdynamics.kanaha. util.logging.MessageLevel Extended for message logs msg_info#com.thinkdynamics.kanaha. util.logging.
# 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 # rolling by log size.
#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.
The Tivoli Intelligent Orchestrator application server automatically reloads the log4j configurations 60 seconds after you save the properties file. You do not need to restart the Tivoli Intelligent Orchestrator server. The updated log4j configuration will implement after 60 seconds. Example: To enable the TC driver manager to append to its log file located in the %TIO_LOGS%\tcdrivermanager directory, complete these steps: 1. Open log4j-util.prop in a text editor. 2. Change the default log4j.appender.file.
44 Tivoli Intelligent Orchestrator Problem Determination and Troubleshooting Guide
Chapter 5.
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. Table 5. Server startup and shutdown logs File name tio_start.
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 Location Description Windows %TIO_LOGS%\j2ee This log file stores all event logs for the Web interface including messages, traces, and debugging information. UNIX or Linux $TIO_LOGS/j2ee msg.
Table 7. Deployment engine logs (continued) File name cbe.log Location Windows %TIO_LOGS%\deploymentengine UNIX or Linux $TIO_LOGS/deploymentengine deploymentengine_start.log Windows %TIO_LOGS%\deploymentengine UNIX or Linux $TIO_LOGS/deploymentengine Description This log file stores all event logs for the deployment engine component in Common Base Event standard format. This is the log file of the most recent startup of the deployment engine.
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 Location console.log Description Windows %TIO_LOGS%\policyengine UNIX or Linux $TIO_LOGS/policyengine msg.log Windows %TIO_LOGS%\policyengine UNIX or Linux $TIO_LOGS/policyengine trace.
Table 9. Automation package logs (continued) File name trace.log Location Windows %TIO_LOGS%\tcdrivermanager UNIX or Linux $TIO_LOGS/tcdrivermanager cbe.log Windows %TIO_LOGS%\tcdrivermanager UNIX or Linux $TIO_LOGS/tcdrivermanager 50 Tivoli Intelligent Orchestrator Problem Determination and Troubleshooting Guide Description This log file stores error messages that can be reviewed by Tivoli Software Support.
Chapter 6.
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. The names and the locations of these log files are provided below.
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). Look for Server stop completed for a successful shutdown of the WebSphere Application Server. SystemErr.
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.
Chapter 7.
In Linux, the tioadmin user creation fails if the tioadmin group already exists before you install. No exception is thrown, so the installer cannot detect that the user creation operation has failed, and the system cannot return to a previous stage of the installation. Solution Reinstall Tivoli Intelligent Orchestrator. However, before you start the installation, ensure that the tioadmin user and tioadmin group either both exist or both do not exist.
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. Solution Manually uninstall the common agent.
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 the certificate location during the install.
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.
v Do not uninstall the agent manager until all products that use it have been uninstalled. v Do not clean the agent manager tables from the registry or drop the registry database until all products that use the registry are uninstalled. To uninstall the agent manager, follow these steps: 1.
Agent_Manager_install_dir/bin/ RunInDbEnv.sh RemoveCASTables.sh database_password Replace database_password with the DB2 database password. – Oracle a. In a command line window, change to the Agent_Manager_install_dir/db/oracle directory. b. Run the following command: - On Windows ./RemoveCASTables.bat database_password - On AIX, Linux, and Solaris ./RemoveCASTables.sh database_password Replace database_password with the Oracle database password. 3.
Reinstalling Tivoli Intelligent Orchestrator: Retry the Tivoli Intelligent Orchestrator installation. The Tivoli Intelligent Orchestrator installer will detect that Tivoli Intelligent Orchestrator is already installed, and will install only agent manager.
Solution 2 Run the Tivoli Directory Server Web Administration tool to check the status of the LDAP server. Note: This solution is provided for a two-node directory server installation. 1. From LDAP_Install\appsrv\bin, run: v startServer.sh in UNIX v startServer.bat in Windows and use the following syntax: startServer server1 2. In a Web browser, go to http://hostname:9080/IDSWebApp/IDSjsp/Login.jsp 3. Log in with the appropriate user name and password.
6. Change your password again based on the specified password syntax.
Cause The workflow variable values are limited to 4000 bytes. When a scriptlet or Java plug-in returns a value longer than 4000 bytes, DB2 Universal Database will throw an exception. Solution Keep the length of your workflow variables to less than 4000 bytes. DB2 Universal Database deadlocks occur when the system runs a logical operation Cause The DB2 database configuration parameter (lock list) value is not large enough. Solution Adjust the size of the lock list value from 50 to 2000.
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. The user can export the run history of individual workflows, or the run history of more logs into a log file whose name, file format, and location you can specify.
Log content structure: workflow –> deployment request –> workflow execution log –> workflow execution log detail Example workflow log export:
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.
v “Common agents unable to communicate with the agent manager” on page 75 v “Limitations when trying to manually associate a discovered software resource with a software definition” on page 75 v “Some patch installations might fail when trying to perform a multiple patch installation” on page 76 v “Running lightweight management server with DB2 Universal Database generates exceptions” on page 76 v “Agent receives an HTTP Unauthorized (401) response code” on page 77 v “There is a maximum size for returnResul
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. Open the Zone Labs Integrity Desktop. 2. Click Privacy. The Main tab is displayed. Click the Site List tab. 3. Click Add. The Add Site window is displayed. 4.
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.
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.
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.
native2ascii -encoding UTF-8 .csv | native2ascii -reverse -encoding > _output.csv where is the locale code for the language that you are interested in. For example, GB2312 is the code for simplified Chinese. 3. Open the _output.csv file in Excel. All characters are properly displayed.
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. Solution Escape these special characters or other characters in an attribute value in a distinguished name string by preceding it with a backslash (\).
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. Associations with a software stack or distributed application are not supported.
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. v The client certificate provided as part of the SSL handshake revoked.
78 Tivoli Intelligent Orchestrator Problem Determination and Troubleshooting Guide
Chapter 8.
Table 10. Agent manager installation log files Log file name Description AMReturnValues.log Summary of return values of the steps of the agent manager installation. If the agent manager was installed silently, check this log for the results of each step of the installation. If you installed using the agent manager installation wizard, this information is displayed automatically. If you are performing a silent installation, check this log for a step-by-step summary of the installation’s results.
Table 10. Agent manager installation log files (continued) Log file name Description jacl/appServer_out.log Standard output and standard error logs generated while installing the application server for the agent manager. These logs are generated by the EPMAppServer.jacl script 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.
Table 12. Remote registry database installation log files Log File Description datastore.out A log of the SQL statements that are run to create the registry database and its tables. ds_install.log An ISMP log for installing the files necessary to create the registry database. db_stdout.log Standard output and standard error logs for creating the registry database. Check db_stdout.log first to see if the registry was created successfully. db_stderr.
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.
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.
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. In the Data Sources page, check the box next to AgentRegistry and then click Test Connection. 7. Review the status message at the top of the Data Sources panel.
2. Click Servers –> Application Servers –> app_server_name –> Logging and Tracing –> Diagnostic Trace. Replace app_server_name with the name of the application server where the agent manager applications are installed, for example, AgentManager. 3. Ensure that Enable Trace is not checked. 4. Click OK.
h. In the Save to Master Configuration area , click Save again to exit the Master Configuration window. 5. Optionally, clean up the agent manager objects in the database. Important: Remove the agent manager tables from the database or drop the registry database only if all products that use the registry are uninstalled. a. Remove the agent manager tables from the registry database by running the following command: v On Windows systems: Agent_Manager_install_dir\db\database_type\RemoveCASTables.
v The wrong resource manager registration user or password was used when installing the resource manager. v Agent manager configuration files, such as AgentManager.properties or Authorization.xml, are missing or have been altered. v Security credentials are invalid, expired, or revoked. v An agent is attempting to re-register, but duplicate registration is disabled.
assign a different port to the administrative console. You can do this when you install WebSphere Application Server or afterwards. To change the port used by the WebSphere Administrative Console after WebSphere Application Server is installed, complete the following steps. In this example, the WebSphere Administrative Console runs under the application server named server1 and the Web browser is running on the same system as WebSphere Application Server: 1.
90 Tivoli Intelligent Orchestrator Problem Determination and Troubleshooting Guide
Chapter 9. Contacting IBM Tivoli Software Support If you encounter a problem with the Tivoli Intelligent Orchestrator product, first look for help at the Tivoli Intelligent Orchestrator Support Web site. This site contains a searchable database of Technotes and frequently asked questions relating to current issues. The site also contains presentations, fixes, fix packs, and white papers. Go to http://www-306.ibm.
v Proper contact information - your IBM Passport Advantage® or Tivoli Customer ID, appropriate phone number or e-mail address, your preference of return correspondence: by phone or e-mail, alternate phone numbers (if possible), and if not responding to you, the name and contact information for the person Tivoli Customer Support needs to contact.
Prerequisites This utility assumes that you have set the JAVA_HOME and WAS_HOME environment variable appropriately.
94 Tivoli Intelligent Orchestrator Problem Determination and Troubleshooting Guide
Chapter 10. Tivoli Intelligent Orchestrator messages This chapter lists the available Tivoli Intelligent Orchestrator messages. For more information on the conventions used to create these messages, see the section “Message logs” on page 35. Note: Variables in a message are represented by variable_n where n is a unique value within the message.
Explanation: An error occurred when the workflow received as the input parameter a software resource ID that does not contain a valid software module ID. A valid software module ID is required to identify which package will be uninstalled from the specified system. Operator response: Verify that the provided software resource references the correct software module. Verify that the package was installed on the specified system using a workflow that implements SoftwareInstallable.Install.
COPCOM016E The directory VALUE_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. Administrator Response: Verify that script repository directory exists.
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. COPCOM039E A shell command error occurred and the system cannot create the InputStreamHelper for the output/result stream.
COPCOM053E The system cannot allocate VALUE_0 shares of resource VALUE_1 from the VALUE_2 host platform. Explanation: No additional information is available for this message. COPCOM054E The system cannot delete the "VALUE_0" (VALUE_1) software fix pack because it is part of the "VALUE_2" stack. Explanation: No additional information is available for this message. COPCOM055E The system cannot delete the "VALUE_0" (VALUE_1) software fix pack because it is installed on the "VALUE_2" device.
COPCOM071E The system cannot find the load balancer: VALUE_0. COPCOM079E The system cannot find the requested data center model object: VALUE_0. Explanation: No additional information is available for this message. Explanation: No additional information is available for this message. COPCOM072E The system cannot find the monitoring application: VALUE_0. COPCOM080E The system cannot find the required data center model object.
COPCOM088E The system cannot find the VALUE_0 software product. COPCOM099E The system cannot find the virtual IP: VALUE_0. Explanation: No additional information is available for this message. Explanation: No additional information is available for this message. COPCOM089E The system cannot find the VALUE_0 software stack entry. COPCOM100E The system cannot find VLAN VALUE_0. Explanation: No additional information is available for this message.
COPCOM115E There is not enough data to complete the task. Explanation: No additional information is available for this message. COPCOM124E A Telnet error occurred. Explanation: No additional information is available for this message. COPCOM125E A Telnet error occurred. COPCOM116E The operation timed out. Explanation: No additional information is available for this message. COPCOM117E The system cannot decrypt a string that is empty or null.
COPCOM134E The password that you are trying to update cannot be null or empty for username VALUE_0. COPCOM148E The system does not support an Insert action for the DCM object: "VALUE_0". Explanation: No additional information is available for this message. Explanation: No additional information is available for this message. COPCOM135E The username that you are trying to update cannot be null or empty. COPCOM149E The system does not support update for the "VALUE_0" attribute.
COPCOM157E The system cannot find the VALUE_0 software product category. COPCOM167E The system cannot find the VALUE_0 network interface. Explanation: No additional information is available for this message. Explanation: No additional information is available for this message. COPCOM158E The system cannot find the VALUE_0 interface card. COPCOM168E The update function is not supported for the DCM object "VALUE_0". Explanation: No additional information is available for this message.
COPCOM178E The system cannot find the volume container settings VALUE_0 with volume manager VALUE_1 and spare pool VALUE_2. Explanation: No additional information is available for this message. COPCOM179E The system cannot find the volume container settings VALUE_0 with volume manager VALUE_1 and application tier VALUE_2. Explanation: No additional information is available for this message. COPCOM180E The system cannot find the VALUE_0 storage policy settings.
COPCOM196E The system cannot find the VALUE_0 volume container. COPCOM206E The system cannot find the VALUE_0 zone membership data. Explanation: No additional information is available for this message. Explanation: No additional information is available for this message. COPCOM197E The system cannot find the VALUE_0 logical volume. COPCOM207E A worldwide name is not defined for the VALUE_0 fibre channel port. Explanation: No additional information is available for this message.
COPCOM216E No file system settings are defined in the logical volume settings VALUE_0 of the VALUE_1 storage template. Explanation: No additional information is available for this message. COPCOM226E The VALUE_0 server template is not valid. Explanation: No additional information is available for this message. COPCOM217E The system cannot create the output file VALUE_0. COPCOM228E The system cannot delete the VALUE_0 host platform because it includes virtual servers.
COPCOM236E The system cannot find the supported requirement type: VALUE_0. COPCOM246E The system cannot find the VALUE_0 default protocol endpoint. Explanation: No additional information is available for this message. Explanation: No additional information is available for this message. COPCOM237E The system cannot find the VALUE_0 software module. COPCOM250E The system cannot find the VALUE_0 access control list network interface. Explanation: No additional information is available for this message.
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.
COPCOM278E The system cannot find the VALUE_0 storage manager. COPCOM290E The system cannot find the VALUE_0 storage subsystem template. Explanation: No additional information is available for this message. Explanation: No additional information is available for this message. COPCOM279E The active zone set already exists in the VALUE_0 storage area network fabric. COPCOM291E The system cannot find the VALUE_0 storage fibre adapter template.
COPCOM299E The system cannot delete the application deployment template VALUE_0 because it is used by at least one application deployment. Explanation: No additional information is available for this message. COPCOM300E The input XML file VALUE_0 is not encoded with UTF-8 encoding. Re-create the input XML file with proper encoding and try again. Explanation: No additional information is available for this message. COPCOM302E Port number VALUE_0 is not unique.
COPCOM316E The system cannot find the VALUE_0 boot server type. COPCOM329E The system cannot find the VALUE_0 storage template. Explanation: No additional information is available for this message. Explanation: No additional information is available for this message. COPCOM317E The system cannot find the VALUE_0 image type. COPCOM330E The principal VALUE_0 does not have VALUE_1 permission on the object with ID VALUE_2. Explanation: No additional information is available for this message.
Explanation: No additional information is available for this message. COPCOM337E The subscription with ID VALUE_0 cannot be re-subscribed, because it is not in the failed state. Explanation: No additional information is available for this message. COPCOM338E The subscription with ID VALUE_0 cannot be terminated, because the unprovision schedule task ID cannot be found in its service instance with ID VALUE_1. Explanation: No additional information is available for this message.
COPCOM355E The scheduled task type VALUE_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. COPCOM357E The Order of ID VALUE_0 cannot be found. Explanation: No additional information is available for this message. COPCOM358E The service with name VALUE_0 cannot be found.
COPCOM374E The system cannot find the service instance by subscription with ID VALUE_0. Explanation: No additional information is available for this message. COPCOM375E The system cannot create the Constraint with constraint type VALUE_0. Explanation: The system does not recognize the type of the Constraint to be created. The constraint creation failed. Operator response: Verify the correct type of the new Constraint to be created.
COPCOM392E The system cannot find the TCM object for the Hostname: VALUE_0, Type: VALUE_1, Object Label: VALUE_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: VALUE_0, Type: VALUE_1, Object Label: VALUE_2 Explanation: The object lookup results are ambiguous for the Object Label.
COPCOM405E The Profile Manager is VALUE_0. Explanation: The Profile Manager specified is not valid. Operator response: Ensure that the Profile Manager exists in the TCM environment. COPCOM407E Profile VALUE_0 is not a managed profile. Explanation: The creation of the profile failed because it is not a managed profile. Operator response: Ensure that the profile being created for the software package is a managed profile. COPCOM408E The Endpoint subscriber: VALUE_0 does not exist.
COPCOM430E The instance permission VALUE_0 is unknown. Explanation: No additional information is available for this message. COPCOM431E The instance access role VALUE_0 is unknown. Explanation: No additional information is available for this message. COPCOM432E The access domain VALUE_0 is unknown. Explanation: No additional information is available for this message. COPCOM433E The domain role VALUE_0 is unknown. Explanation: No additional information is available for this message.
Administrator Response: Verify that the RIM object is valid. This can be done by running the command wrimtest -l inv at the IBM Tivoli Configuration Server. COPCOM442E The type VALUE_0 is not a valid filter type. COPCOM451E The system failed to update the password for VALUE_0. Explanation: No additional information is available for this message. Explanation: The only valid hardware filter types are Gateway and Subscribers. COPCOM452E The wasadmin password is not valid.
COPCOM459E No software module was found in the data center model to install the Common Agent for the "VALUE_0" operating system and the "VALUE_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. Operator response: Check the software catalog and ensure that there is a software module that can install Tivoli Common Agent on the specified operating system and platform.
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. COPCOM489E The system cannot delete "VALUE_0" access group because users "VALUE_1" are using it as the default access group. Operator response: Make sure no user is using the selected access group as default access group, and then try again.
COPCOM497E Error copying file "VALUE_0" to endpoint using RXA: VALUE_1. COPCOM511E Circular inheritance relationship is not permitted. VALUE_0. Explanation: No additional information is available for this message. Explanation: No additional information is available for this message. COPCOM498E Error copying file "VALUE_0" from endpoint using RXA: VALUE_1. COPCOM512E DCM type VALUE_0 is not recognized for the access group inheritance relationship.
COPCOM520E Unable to parse attribute: VALUE_0 from xml config file: VALUE_1. Explanation: No additional information is available for this message. COPCOM521E Unable to read xml config file: VALUE_0. Explanation: No additional information is available for this message. COPCOM522E Incorrect MAC address: VALUE_0. A MAC address must have 12 hex digits. Explanation: No additional information is available for this message. COPCOM523E The template does not indicate the software definition.
COPCOM539E Task "VALUE_0" (Task Id: "VALUE_1") failed. Explanation: The TPM task failed. COPCOM540E Task "VALUE_0" (Task Id: "VALUE_1") failed". Here is the error: VALUE_2. Explanation: The TPM task failed, with an error log appended COPCOM541E The system cannot delete the "VALUE_0" device driver because one or more devices are using it. Explanation: No additional information is available for this message. COPCOM542E Task "VALUE_0" (Task Id: "VALUE_1") failed on the following targets: VALUE_2.
COPDEX001E The system cannot get a JNDI context. Explanation: No additional information is available for this message. COPDEX002E The system cannot use the "VALUE_0" JMS destination. Explanation: No additional information is available for this message. COPDEX003E The system cannot perform the type conversion for VALUE_0 because the type information that was set has an incorrect value. (Field argument type is VALUE_1.) Explanation: No additional information is available for this message.
COPDEX019E The condition VALUE_0 is not valid. Explanation: No additional information is available for this message. COPDEX020E The system requires the VALUE_0 attribute. Explanation: No additional information is available for this message. COPDEX021E The system cannot find the field name for the attribute: VALUE_0. COPDEX029E The system cannot continue a deployment request from a previous deployment engine VM session. Explanation: No additional information is available for this message.
COPDEX038E A database error occurred: VALUE_0. Explanation: No additional information is available for this message. COPDEX049E The "VALUE_0" operand does not exist for instruction ID: VALUE_1. 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: VALUE_0. Explanation: No additional information is available for this message.
COPDEX060E A workflow XML parser error "VALUE_0" occurred. COPDEX070E The variable name "VALUE_0" is not valid. Explanation: No additional information is available for this message. Explanation: No additional information is available for this message. COPDEX061E The system expected a single value, but it received multiple values. COPDEX071E The system requires an object here: "VALUE_0". Explanation: No additional information is available for this message.
COPDEX081E The system cannot specify an input file. Explanation: No additional information is available for this message. COPDEX082E The system cannot find the input file VALUE_0. Explanation: No additional information is available for this message. COPDEX083E The input file VALUE_0 is empty. Explanation: No additional information is available for this message. COPDEX084E The operation type VALUE_0 is not identified. Explanation: No additional information is available for this message.
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.
COPDEX110E An internal error occurred when the system tried to generate the name of the Tivoli Enterprise Console (TEC) configuration file. 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 receives configuration information from a TEC configuration file. In this event, the system did not produce that internal file name. Operator response: This is an internal error.
COPDEX132E The system is running a workflow VALUE_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. COPDEX135E "InvokeImplementation" can be called only from a logical operation. Explanation: No additional information is available for this message.
COPDEX149E No such parameter "VALUE_0". Explanation: No additional information is available for this message. COPDEX150E Unknown instance permission "VALUE_0". Explanation: No additional information is available for this message. COPDEX151E Duplicate permission "VALUE_0" for parameter "VALUE_1". Explanation: No additional information is available for this message. COPDEX152E The system cannot specify the permission for the output only parameter "VALUE_0".
COPDEX170E The "VALUE_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 VALUE_0 with status VALUE_1. Explanation: There might be a problem when connecting to the database. Check the SQLException message for further details about the problem. COPDEX172E The VALUE_0 variable is a single value variable, cannot assign an array value to it.
COPDEX189E The tc-driver.xml in VALUE_0 refers to a workflow VALUE_1 that does not exist. Explanation: No additional information is available for this message. COPDEX190E The index "VALUE_0" for array "VALUE_1" is out of bounds. Explanation: No additional information is available for this message. COPDEX191E The index "VALUE_0" for array "VALUE_1" is not valid. Explanation: No additional information is available for this message. COPDEX192E The method VALUE_0 with VALUE_1 parameters is not found.
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. Explanation: No additional information is available for this message. COPJEE008E The source for a network configuration item cannot be null. Explanation: No additional information is available for this message.
COPJEE027E The system cannot copy credentials ID "VALUE_0" specified in stack VALUE_1 and service access point VALUE_2. Explanation: No additional information is available for this message. COPJEE028E The system cannot identify credentials ID "VALUE_0" specified in VALUE_1 and service access point VALUE_2. Explanation: No additional information is available for this message. COPJEE029E The relationship between the network interface ID "VALUE_0" and the router ID: "VALUE_1" is not valid.
COPJEE043E The system cannot add server "VALUE_0" to application tier "VALUE_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 "VALUE_0" and for the NIC ID "VALUE_1". Explanation: No additional information is available for this message.
COPJEE060E Server: "VALUE_0" was not removed from the spare resource pool "VALUE_1". COPJEE070E The recommendation "VALUE_0" is obsolete and has been replaced. 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. Explanation: No additional information is available for this message.
(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. Explanation: No additional information is available for this message. COPJEE081E The system was unable to invoke EJB. Ask your system administrator if the EJB server is available.
COPJEE101E A user interface error occurred VALUE_0 COPJEE112E A power outlet already exists. Explanation: Please consult the j2ee/console.log file for more information. Explanation: No additional information is available for this message. 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.
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. COPJEE163E Service access points and/or credentials are associated with this device. Explanation: No additional information is available for this message.
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. The report.
COPJEE235E No additional servers are available in the application tier ID: "VALUE_0". 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. Explanation: No additional information is available for this message.
COPJEE281E The system cannot delete the resource pool with ID: "VALUE_0" because it is associated with the following data center fragment IDs: "VALUE_1". Explanation: No additional information is available for this message. COPJEE282E The system cannot delete the server with ID: "VALUE_0" because is is associated with the following data center fragment IDs: "VALUE_1". Explanation: No additional information is available for this message. COPJEE289E The deployment request ID VALUE_0 does not exist.
COPJEE304E The LUN VALUE_0 in fibre channel port VALUE_1 is not available. Explanation: No additional information is available for this message. COPJEE305E Storage volume VALUE_0 in storage subsystem VALUE_1 already exists. Explanation: No additional information is available for this message. COPJEE308E The HBA port or FA Port with ID VALUE_0 does not have a WWN defined. Explanation: No additional information is available for this message.
COPJEE326E The system failed to delete deployment request. COPJEE337E Required inputs, VALUE_0, for report, VALUE_1 is missing. Explanation: No additional information is available for this message. Explanation: No additional information is available for this message. COPJEE327E Fibre adapter port, with port ID "VALUE_0", does not belong to "VALUE_1" storage subsystem. COPJEE338E The request to decrypt the database password from dcm.xml failed.
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. COPJEE355E The requested resource "VALUE_0" is not locked, or the resource is locked but the wrong key is specified. Explanation: No additional information is available for this message. COPJEE356E A system error VALUE_0 occurred. COPJEE347E The operation VALUE_0 is not implemented.
COPJEE364E The report was not created when using report creator. Report: VALUE_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. Report: VALUE_0. COPJEE373E The VALUE_0 from the configuration file, report.xml, is not configured properly or is not loaded properly.
COPJEE381E A user interface error occurred. The configuration is incorrect for: action="VALUE_0", objectType="VALUE_1". COPJEE387E The system cannot create the credential since its search key VALUE_0 is already used by other credential of this access point. Explanation: No additional information is available for this message. Explanation: No additional information is available for this message. COPJEE382E The system can not find the VLAN in the switch port with ID: "VALUE_0".
COPPEZ041E A generic data acquisition configuration error occurred. Operator response: Validate the configuration of the acquisition engine. COPPEZ051E VALUE_0" is not a valid device type. Explanation: This error can be triggered by a tier/application configuration problem: all tiers and active/online (instead of "not in maintenance") applications must be configured for data acquisition. COPPEZ042E VALUE_0" is not a valid device type.
COPPEZ071E An SNMP error (Error code=VALUE_0 occurred in response to Error name=VALUE_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. COPPEZ097E No LoadObject exists for the VALUE_0 application. Explanation: No additional information is available for this message. COPPEZ098E A resource broker error occurred. It is missing the VALUE_0 object.
COPPEZ113E An error occurred. The Tivoli Management Region orb object is null. Explanation: No additional information is available for this message. COPPEZ114E The system cannot obtain an application tier properties instance. Explanation: No additional information is available for this message. COPPEZ115E The system cannot obtain a application tier ID. Explanation: No additional information is available for this message. COPPEZ116E The endpoint label is null or empty.
COPTCA009E Error copying Subagent jar VALUE_0 to the endpoint. COPTCA018E Error executing command on endpoint: output is null Explanation: For more information, check the logs/msgAgent.log file on the endpoint in the agent install directory. Explanation: For more information, check the logs/tioExecuteCommandTrace.log file on the endpoint in the agent install directory. COPTCA010E Error during Agent operation: VALUE_0. COPTCA019E Error converting path VALUE_0 to DOS style path.
COPTDM001E The system does not support the VALUE_0 operating system running Kula. COPTDM013E The system cannot associate the "VALUE_0" stack with object ID VALUE_1. Explanation: No additional information is available for this message. Explanation: No additional information is available for this message. COPTDM003E The application is not specified. COPTDM014E The system cannot deactivate the server on the load balancer. Explanation: No additional information is available for this message.
COPTDM023E The system cannot find the virtual IP address VALUE_0. Explanation: No additional information is available for this message. COPTDM033E The system cannot uninstall the "VALUE_0" software stack. Review the execution logs for more details. Explanation: No additional information is available for this message. COPTDM024E The system cannot install the "VALUE_0" software product. Review the execution logs for more details. COPTDM034E The system cannot update the status for the "VALUE_0" software.
COPTDM044E The argument is not valid. The RuntimeParameters value is null. COPTDM062E The system cannot allocate the IP address. Explanation: No additional information is available for this message. Explanation: No additional information is available for this message. COPTDM045E The argument is not valid because the RuntimeParameters value cannot be null. COPTDM063E The system cannot allocate the server. Explanation: No additional information is available for this message.
COPTDM070E The system cannot find the service access point for device ID "VALUE_0" with protocol "VALUE_1" and context "VALUE_2". Explanation: No additional information is available for this message. COPTDM071E The system cannot find a service access point for device ID "VALUE_0" with protocol "VALUE_1" and credentials key "VALUE_2". Explanation: No additional information is available for this message.
COPTDM085E The system cannot find the credentials for device ID "VALUE_0" and the SAP ID "VALUE_1" with the credentials key "VALUE_2". Explanation: No additional information is available for this message. COPTDM087E The system cannot find the software product ID "VALUE_0". Explanation: No additional information is available for this message. COPTDM088E The subnetwork ID is not specified and the system cannot derive the subnetwork ID from the IP address.
the transitions and then try again. COPTDM102E The system cannot stop the monitoring resource "VALUE_0" using the "VALUE_1" monitoring application. Request ID "VALUE_2". Explanation: The system cannot stop monitoring the resource. Operator response: Search the workflow execution history for errors that use the request ID. Review all the transitions and then try again. COPTDM103E The system cannot uninstall the application on VALUE_0. Explanation: No additional information is available for this message.
COPTDM119E No device is associated with SAP ID: "VALUE_0". Explanation: No additional information is available for this message. COPTDM120E The system cannot reach IP address "VALUE_0" by SNMP. Explanation: No additional information is available for this message. COPTDM132E For this operation, the credentials ID "VALUE_0" must be password credentials or RSA credentials. Explanation: No additional information is available for this message. COPTDM133E The timeout value VALUE_0=VALUE_1 is not valid.
COPTDM148E The system cannot create the new device model "VALUE_0" because it already exists. Explanation: No additional information is available for this message. COPTDM150E An error occurred while the system installed the driver "VALUE_0". Explanation: No additional information is available for this message. COPTDM151E The format for the TC Driver item "VALUE_0" is not valid. Explanation: No additional information is available for this message.
Explanation: No additional information is available for this message. COPTDM172E An error occurred while the system uninstalled the "VALUE_0"driver because the driver status must be VALUE_1. Explanation: No additional information is available for this message. COPTDM173E The configuration directory must be specified in the tcdrivermanager.xml file. Explanation: No additional information is available for this message. COPTDM174E The driver directory must be specified in the "-Dkanaha.drivers=" VM property.
COPTDM185E The file VALUE_0 is already used by TCDriver VALUE_1. COPTDM193E Multiple default values were set for template property VALUE_0. Explanation: TCDriver file cannot be overwritten by a file from another tcdriver. Explanation: No additional information is available for this message. COPTDM186E The TCDriver object VALUE_0: VALUE_1 is still used by other DCM objects. COPTDM194E No license is found for TCDriver VALUE_0. Explanation: Remove all references to the TCDriver and try again.
COPUTL009E Usage: IDSCoexistMigration Migration-path root-userName password hostname port SSL(true/false) source-baseDN target-baseDN Explanation: No additional information is available for this message. COPUTL010E Usage: IDSPostCoexist Migration-root userName password hostname port SSL(true/false) source-baseDN target-baseDN Explanation: No additional information is available for this message.
Compliance Messages COPDSE001E The system cannot update the given guest access desired state element because it is not stored in DCM. Its SecurityDesiredStateElementId is VALUE_0, its UserAccountDesiredStateElmentId is VALUE_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. Its SecurityDesiredStateElementId is VALUE_0.
Explanation: No additional information is available for this message. Explanation: No additional information is available for this message. COPDSE015E The DSE setting value to be validated cannot be null. COPDSE023E The system cannot update the given customized desired state element because it is not stored in the data center model. Its DesiredStateElementId is VALUE_0. Explanation: No additional information is available for this message.
COPDSE103E Each permission character in the input permission string VALUE_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 VALUE_0 should be no longer than 256 characters. Explanation: No additional information is available for this message. COPDSE105E The input desired state description VALUE_0 should be no longer than 2000 characters.
determined by a database query. It is not possible to add members to a dynamic group. COPGRP009E Cannot remove the object "VALUE_0" from the group "VALUE_1" because it is a dynamic group. Explanation: The members of a dynamic group are determined by a database query. It is not possible to remove individual members from a dynamic group. COPGRP010E Cannot remove all the members from the group "VALUE_0" because it is a dynamic group.
Explanation: No additional information is available for this message. COPNET014E The system cannot find VLAN: VALUE_0. Explanation: No additional information is available for this message. COPNET015E The switch endpoint mode VALUE_0 is not valid. Explanation: No additional information is available for this message. COPNET016E The switch endpoint encapsulation VALUE_0 is not valid. Explanation: No additional information is available for this message.
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. For SSH logins, also verify that the key store name and passphrase are correctly specified. Retry the connection.
administrator enable remote registry access and verify that the credentials your application is submitting have sufficient privileges on the target to perform remote registry operations. CTGRI0012E The requested registry key does not exist on the target machine. CTGRI0017E An error occurred in RCP communication. Explanation: A remote copy (rcp) operation failed. Programmer response: Ensure that the rsh/rexec remote protocols are enabled on the target.
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. CTGRI0025E The file File is not a valid SSH key. Explanation: The format of the specified SSH key file is not valid or not supported. SSH key and that the format is supported.
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. directory name The name of the directory. DISSP6014W file name file not found. Please verify the correct file name was given Explanation: The system does not recognize the file name you specified.
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. Message Variables: where file name The name of the file. System action: The operation is not performed. Operator response: Check that the package contains no incorrect values. Verify that all the libraries are present on the system.
DISSP6030W The configuration file file name was not found DISSP6037W The configuration file specified is not valid Explanation: You specified a configuration file that does not exist. Explanation: You specified an invalid configuration file. Message Variables: where file name The name of the file. System action: The operation is not performed. Operator response: Specify a valid file. System action: The operation is not performed.
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. Operator response: Enter a value in the suggested range. DISSP6044E Enter a value in the suggested range. Explanation: You have entered a value which is outside the supported range.
password are defined in Tivoli Provisioning Manager WebUI.
Chapter 11. Tivoli Common Agent Services messages This chapter lists the available Tivoli Common Agent Services messages. Common Agent messages BTC0006I The common agent has stopped. Explanation: No additional information is available for this message. BTC0007I The common agent MBeanServer has started. Explanation: No additional information is available for this message. BTC0008I The common agent is ready for autonomic on demand e-business.
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. The common agent was unable to store the certificate on the local machine. Explanation: The common agent registration service was unable to store the security certificate on the common agent machine.
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. Explanation: If existing credential are not valid, this is an unrecoverable error.
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.
BTC1048E The common agent failed to renew its certificate revocation list. configuration, or the service location information stored in the common agent properties file is incorrect. Explanation: The common agent failed to renew its certificate revocation list with the certificate authority of the agent manager.
If resetting the GUID failed, or the problem persists, contact customer support. Explanation: The validation dates for the certificate are set using the agent manager clock, but the clock on the common agent has one of the following problems: BTC1050I v It is earlier than the not valid before date in the certificate. true Explanation: No additional information is available for this message. BTC1051I false Explanation: No additional information is available for this message.
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. Explanation: A required properties file does not exist. System action: The common agent will be unable to register or contact the agent manager.
BTC2209I The common agent is being initialized. BTC2403E 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. The system encountered a problem while saving the logging property information to persistent storage. Explanation: The logging property information could not be saved. System action: The logging property information was not saved.
BTC2411I The locale was successfully set to language_code and region_code. BTC3005E The update source file, bundle_name, was not found. Explanation: No additional information is available for this message. Explanation: The source file for the update operation was not found. The file might be missing, inaccessible, or corrupted. BTC2412I System action: The bundle was not updated. The locale was not set. The default locale is language_code_ region_code.
BTC3009E The bundle_name bundle cannot be deleted because system cannot be found in the OSGi storage. running and is not corrupted. BTC3014E An error occurred while uninstalling the bundle_name bundle. Explanation: The specified bundle was not found in the OSGi storage. The bundle might be missing, inaccessible, corrupted, or it might not be installed. Explanation: An error occurred while uninstalling the bundle. Verify that the bundle is installed. System action: The specified bundle was not deleted.
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 bundle. not exist or the user account that runs the common agent does not have the correct file permissions.
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. BTC3118I command to install a bundle from the specified URL Explanation: No additional information is available for this message.
BTC3135I command to create a directory in the common agent base directory BTC3144I The bundle_name bundle was uninstalled successfully. Explanation: No additional information is available for this message. Explanation: No additional information is available for this message. BTC3136I BTC3145I command to delete a directory from the common agent base directory The uninstallation of the bundle_name bundle failed. cause. Explanation: No additional information is available for this message.
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. BTC3156I The directory_name directory has been created. Explanation: No additional information is available for this message.
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. Explanation: The deployer service encountered a problem while saving its properties to the local file system. There might be a problem with the file system.
BTC4008I The common agent is reducing the service tracker cache size. Explanation: No additional information is available for this message. BTC4017I Explanation: No additional information is available for this message. BTC4018I 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.
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. BTC4036E Explanation: The component that attempted to connect and invoke an operation on the common agent is not a valid component.
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. v The common agent does not have valid security credentials.
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 was delivered successfully. Explanation: No additional information is available for this message.
BTC5027I Status has been sent. BTC5047E 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. Administrator Response: The credentials on the common agent are not valid.
v Using a Web browser, access the URL, url. 4. Start the upgrade again. BTC5051E 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. Explanation: The CAUpgrade.properties file contains key/value pairs that provide platform-specific information that is needed to upgrade the common agent. The value for the required key was not found in the file.
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. BTC5057I After you correct the problem, start the upgrade again. BTC5053E The upgrade bundle cannot look up the deployer service. Explanation: The deployer service is used to copy the image to the common agent. Because the deployer service was not found, the upgrade cannot continue.
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 error occurred.
BTC5068I The upgrade of the common agent failed. Look in the common agent installation log at logs/agentInstall.log for more information. Explanation: No additional information is available for this message. System action: The common agent will continue to run but cannot report status to the agent manager. Administrator Response: Verify that the common agent is registered, and that it has valid security credentials. BTC5072E BTC5069E The upgrade status retrieved from the logs/install/epInstallStatus.
not turned on, you might have to turn tracing on and restart the application server. If the exception indicates an I/O error (IOException), try to restart the application server. 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.Issue property of the agent manager configuration file (AgentManager.properties). If the name of the class is correct, make sure that the class is in the class path of the agent manager.
Administrator Response: Contact IBM Customer Support. CTGEM0010E The agent manager cannot open the root private key associated with the certificate authority. Explanation: The root private key of the certificate authority cannot be opened. This means that one or both of the key store or password stash file are missing or damaged. System action: The certificate authority is not initialized. The certificate authority cannot generate and renew certificates, so registration requests cannot be processed.
CTGEM0016E The parameter_name parameter cannot be NULL. Explanation: A client program specified NULL for the parameter_name parameter. This parameter must have a non-NULL value. System action: In addition to logging this message in the agent manager message and trace files, the agent manager throws an exception to notify the calling program about the problem. Administrator Response: Make sure that the agent configuration file (AgentManager.
CTGEM0023E The agent manager cannot store information about the agent with the operating system GUID "operating_system_GUID" and component ID "component_ID" in the agent registry. Explanation: The agent manager cannot store information about the specified agent in the agent registry. This indicates a possible problem with the database or a problem in the agent manager. The agent or resource manager that called the agent manager is not affected by this problem.
Administrator Response: Check the WebSphere application server log and trace files. Look at the log information that is generated with this error to determine the name of the exception. The name of the exception typically indicates the problem. If tracing is not turned on, turn it on and restart the application server. If the exception indicates an I/O error (IOException), try to restart the application server.
v The client program uses the agent manager ID to verify that it is talking to the same agent manager as in previous requests, and therefore compares the new agent manager ID to a saved copy of the original ID. Administrator Response: Make sure that the directory to which the agent manager ID file was to be written exists. If the directory exists, verify that the base directory specified by the ARS.directory property in the agent manager configuration file (AgentManager.properties) is correct.
CTGEM0042I The agent manager successfully revoked one or more certificates assigned to the component with managed element GUID GUID. Explanation: The agent manager successfully revoked the registration of a certificate for a component identified by GUID, which is a type 3 GUID. CTGEM0043E The agent manager received the exception exception while attempting to run the query query with a desired Detail Level of detail. Explanation: An error occurred while running a query against the registry.
4. Ensure that the AgentManager.properties file contains an encrypted string for the value of the Registration.Agent.Access.Password property. 5. When the files and properties are correct, retry the operation that failed. 6. If the problem continues, regenerate the registration encryption keystore file and retry the operation that failed. Instructions for regenerating the keystore file are located in the agent manager documentation. 7.
property. The AgentManager.properties file is in the WEB-INF/classes/resources directory of the AgentManager.war file. 2. Use the EncryptPW command to encrypt the password for each user in the Authorization.xml file. The EncryptPW command writes the encrypted password to standard output. Copy and paste the output string into the password= attribute of the element. 3. Save the file. If you cannot encrypt the passwords using the EncryptPW command, contact IBM Customer Support.
WEB-INF/classes/resources directory of the AgentManager.war file and that the file is readable by the current user. 2. Ensure that the directory pointed to by the ARS.directory property in the AgentManager.properties file exists and is readable. agent manager configuration file (AgentManager.properties) with the encrypted form of the specified password. v Creates a resource manager user ID in the Authorization.
CTGEM0058E The AuthXMLRemoveUser command received incorrect input arguments. This command takes a single argument, which is the ID of the resource manager user ID that you want to remove. Explanation: No additional information is available for this message. CTGEM0059E An error occurred while attempting to retrieve the key used to encrypt resource manager passwords.
CTGEM0062E The AuthXMLRemoveAuthType command received incorrect input arguments. This command takes a single argument, which is the ID of the resource manager user ID that you want to remove. Explanation: No additional information is available for this message. CTGEM0063E A resource manager authorization type cannot removed from the Authorization.
application server for the recovery service. CTGEM0155I The recovery service started successfully. Explanation: No additional information is available for this message. CTGEM0156I The registration server was missing Explanation: No additional information is available for this message. CTGEM0157I Registration server trust failure CTGEM2000E The agent manager cannot find the requested message. The message key is message_key. The message bundle is message_bundle.
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.
Application Server. Because the configuration script cannot read 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.
vvrrmm is the version information. The name of the file for the agent recovery service application is CTGEMRECvvrrmm.sys. If the file exists and the user has permission to read the file, retry the 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.
220 Tivoli Intelligent Orchestrator Problem Determination and Troubleshooting Guide
Appendix A. Common Agent serviceability tool This section describes the serviceability tool that captures information about the common agent and the machine the agent is running on. The serviceability tool is a script that can be run from the common agent installation directory, also referred to as the base directory.
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: – base directory – cert directory – config directory – installableBundles directory and subdirectories – installedBundles directory and subdirectories – jre directory – lib directory – logs directory and subdirectories – subagents directory and subdirectories 2.
Table 14. Files included in the CASservice.zip file (continued) File name File path All files from logs directory: msgAgent.log \logs\ nonstop.log \logs\ smfnonstop.log \logs\ SystemErr.log \logs\ SystemOut.log \logs\ traceAgent.log \logs\ All files from logs\install directory: ep_install.err \logs\install\ ep_install.log \logs\install\ epInstallStatus.log \logs\install\ guid_install.
224 Tivoli Intelligent Orchestrator Problem Determination and Troubleshooting Guide
Appendix B. Support information This section describes the following options for obtaining support for IBM products: v “Searching knowledge bases” v “Obtaining fixes” v “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.
4. Click the name of a fix to read the description and optionally download the fix. To receive weekly e-mail notifications about fixes and other news about IBM products, follow these steps: 1. From the support page for any IBM product, click My support in the upper-right corner of the page. 2. If you have already registered, skip to the next step. If you have not registered, click register in the upper-right corner of the support page to establish your user ID and password. 3. Sign in to My support. 4.
2. Describe your problem and gather background information. 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. Use the following criteria: Severity 1 Critical business impact: You are unable to use the program, resulting in a critical impact on operations.
For more information about problem resolution, see Searching knowledge bases and Obtaining fixes.
Appendix C. Notices This information was developed for products and services offered in the U.S.A. IBM may not offer the products, services, or features discussed in this document in other countries. Consult your local IBM representative for information on the products and services currently available in your area. Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM product, program, or service may be used.
IBM Canada Ltd. Office of the Lab Director 8200 Warden Avenue Markham, Ontario L6G 1C7 Canada Such information may be available, subject to appropriate terms and conditions, including in some cases, payment of a fee. 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.
Index A agent manager configuring WAS console to use a different port 88 determining version 83 disabling tracing 85 enabling tracing 85 installation and uninstallation verifications 83 log files 79 problems 79, 81, 82, 83, 84, 86, 88 recovering from incomplete uninstallation 86 registration failures 87 tracing 85 troubleshooting 79, 81, 82, 83, 84, 86, 88 verifying connection to registry 84 verifying the agent manager service is running 83 agent manager application errors starting the agent manager applica
M manuals see publications vii, ix message elements action 36 explanation 36 ID 36 text 36 message logs 35 messages common agent subsystem messages 153 common subsystem messages 95 compliance subsystem messages 166 deployment engine subsystem messages 125 elements 36 group subsystem messages 168 ID format 35 j2ee subsystem messages 135 JDS subsystem messages 135 listing 95 networking subsystem messages 169 policy engines subsystem messages 150 rxa 171 software distribution subsystem messages 173 tc driver m
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 returnResult 76 shell command error in a workflow 65 silent installation exits before it is completed 58 the agent manager instal
234 Tivoli Intelligent Orchestrator Problem Determination and Troubleshooting Guide
Printed in USA SC32-2216-00
