Tivoli®Intelligent OrchestratorProblem Determination and Troubleshooting Guide Version 5.1 SC32-2216-00
Explains how to install and upgrade Tivoli Intelligent Orchestrator software. This guide also provides information about troubleshootin
v The wrong resource manager registration user or password was used when installing the resource manager. v Agent manager configu
assign a different port to the administrative console. You can do this when you install WebSphere Application Server or afterwards.
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
v Proper contact information - your IBM Passport Advantage® or Tivoli Customer ID, appropriate phone number or e-mail address, your
Prerequisites This utility assumes that you have set the JAVA_HOME and WAS_HOME environment variable appropriately. For example: Windows
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 mor
Explanation: An error occurred when the workflow received as the input parameter a software resource ID that does not contain a v
COPCOM016E The directory VALUE_0 does not exist. Explanation: An error occurred when the directory that contains the scripts that
v The Tivoli Software Library provides a variety of Tivoli publications such as white papers, datasheets, demonstrations, redbooks,
COPCOM037E A shell command error occurred and the system cannot create the InputStreamHelper for the error stream. Explanation: No
COPCOM053E The system cannot allocate VALUE_0 shares of resource VALUE_1 from the VALUE_2 host platform. Explanation: No additional
COPCOM071E The system cannot find the load balancer: VALUE_0. Explanation: No additional information is available for this message.
COPCOM088E The system cannot find the VALUE_0 software product. 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. COP
COPCOM134E The password that you are trying to update cannot be null or empty for username VALUE_0. Explanation: No additional in
COPCOM157E The system cannot find the VALUE_0 software product category. Explanation: No additional information is available for thi
COPCOM178E The system cannot find the volume container settings VALUE_0 with volume manager VALUE_1 and spare pool VALUE_2. Explanatio
COPCOM196E The system cannot find the VALUE_0 volume container. 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:
Tivoli software training For Tivoli software training information, refer to the IBM Tivoli Education Web site: http://www.ibm.com/softwa
COPCOM236E The system cannot find the supported requirement type: VALUE_0. Explanation: No additional information is available for t
Facility to determine the problem. To activate logging, set the TraceFileName variable in the Tivoli Enterprise Console configuration
COPCOM278E The system cannot find the VALUE_0 storage manager. Explanation: No additional information is available for this message.
COPCOM299E The system cannot delete the application deployment template VALUE_0 because it is used by at least one application deplo
COPCOM316E The system cannot find the VALUE_0 boot server type. Explanation: No additional information is available for this messag
Explanation: No additional information is available for this message. COPCOM337E The subscription with ID VALUE_0 cannot be re-subsc
COPCOM355E The scheduled task type VALUE_0 is not valid. Explanation: No additional information is available for this message. COPCO
COPCOM374E The system cannot find the service instance by subscription with ID VALUE_0. Explanation: No additional information is a
COPCOM392E The system cannot find the TCM object for the Hostname: VALUE_0, Type: VALUE_1, Object Label: VALUE_2 Explanation: The
COPCOM405E The Profile Manager is VALUE_0. Explanation: The Profile Manager specified is not valid. Operator response: Ensure that
Chapter 1. Introduction to troubleshooting Problem determination, or troubleshooting, is a process of determining why a product is not
COPCOM430E The instance permission VALUE_0 is unknown. Explanation: No additional information is available for this message. COPCOM431
Administrator Response: Verify that the RIM object is valid. This can be done by running the command wrimtest -l inv at the IBM T
COPCOM459E No software module was found in the data center model to install the Common Agent for the "VALUE_0" operating
COPCOM477E The alternate gateway port is not correct. Explanation: No additional information is available for this message. COPCOM478
COPCOM497E Error copying file "VALUE_0" to endpoint using RXA: VALUE_1. Explanation: No additional information is available
COPCOM520E Unable to parse attribute: VALUE_0 from xml config file: VALUE_1. Explanation: No additional information is available for
COPCOM539E Task "VALUE_0" (Task Id: "VALUE_1") failed. Explanation: The TPM task failed. COPCOM540E Task "VA
COPDEX001E The system cannot get a JNDI context. Explanation: No additional information is available for this message. COPDEX002E
COPDEX019E The condition VALUE_0 is not valid. Explanation: No additional information is available for this message. COPDEX020E Th
COPDEX038E A database error occurred: VALUE_0. Explanation: No additional information is available for this message. COPDEX039E A
v Each asset is represented by a data center object. When you make a change to an asset with Tivoli Intelligent Orchestrator, t
COPDEX060E A workflow XML parser error "VALUE_0" occurred. Explanation: No additional information is available for this mes
COPDEX081E The system cannot specify an input file. Explanation: No additional information is available for this message. COPDEX082E
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
COPDEX110E An internal error occurred when the system tried to generate the name of the Tivoli Enterprise Console (TEC) configuratio
COPDEX132E The system is running a workflow VALUE_0. No modifications can be made to the workflow while the workflow is running. Ex
COPDEX149E No such parameter "VALUE_0". Explanation: No additional information is available for this message. COPDEX150E U
COPDEX170E The "VALUE_0" Java plug-in does not exist. Explanation: No additional information is available for this message.
COPDEX189E The tc-driver.xml in VALUE_0 refers to a workflow VALUE_1 that does not exist. Explanation: No additional information i
you are using to manage users in your LDAP database does not have the support for customizable roles. You can either specify a di
COPJEE027E The system cannot copy credentials ID "VALUE_0" specified in stack VALUE_1 and service access point VALUE_2. Explan
Product architecture Tivoli Intelligent Orchestrator includes the following main components: EJB(EJB Container)WebSphereApplication ServerWebS
COPJEE043E The system cannot add server "VALUE_0" to application tier "VALUE_1" because the application tier already
COPJEE060E Server: "VALUE_0" was not removed from the spare resource pool "VALUE_1". Explanation: A server can be
(and usually happens when the user is updating some data). The most likely reason for it is a constraint violation or a miscellane
COPJEE101E A user interface error occurred VALUE_0 Explanation: Please consult the j2ee/console.log file for more information. Operator
COPJEE154E Not enough servers are available to complete this task. Explanation: No additional information is available for this messa
COPJEE205E A software requirement occurred. Verify the requirement name, type, and value. Explanation: No additional information is a
COPJEE235E No additional servers are available in the application tier ID: "VALUE_0". Explanation: No additional information
COPJEE281E The system cannot delete the resource pool with ID: "VALUE_0" because it is associated with the following data ce
COPJEE304E The LUN VALUE_0 in fibre channel port VALUE_1 is not available. Explanation: No additional information is available for t
COPJEE326E The system failed to delete deployment request. Explanation: No additional information is available for this message. COPJEE
from each managed application environment in the data center. It captures and filters data from the application, operating system, an
COPJEE345E Multiple Password credentials were returned. Explanation: The system contains multiple Password credentials that have the sa
COPJEE364E The report was not created when using report creator. Report: VALUE_0. Explanation: The database transaction failed. COPJEE
COPJEE381E A user interface error occurred. The configuration is incorrect for: action="VALUE_0", objectType="VALUE_1". E
COPPEZ041E A generic data acquisition configuration error occurred. Operator response: Validate the configuration of the acquisition
COPPEZ071E An SNMP error (Error code=VALUE_0 occurred in response to Error name=VALUE_1). Explanation: No additional information is
COPPEZ113E An error occurred. The Tivoli Management Region orb object is null. Explanation: No additional information is available
COPTCA009E Error copying Subagent jar VALUE_0 to the endpoint. Explanation: For more information, check the logs/msgAgent.log file o
COPTDM001E The system does not support the VALUE_0 operating system running Kula. Explanation: No additional information is availabl
COPTDM023E The system cannot find the virtual IP address VALUE_0. Explanation: No additional information is available for this mess
COPTDM044E The argument is not valid. The RuntimeParameters value is null. Explanation: No additional information is available for
WebSphere Application Server WebSphere Application Server hosts management interfaces and coordinates interaction between other system co
COPTDM070E The system cannot find the service access point for device ID "VALUE_0" with protocol "VALUE_1" and co
COPTDM085E The system cannot find the credentials for device ID "VALUE_0" and the SAP ID "VALUE_1" with the crede
the transitions and then try again. COPTDM102E The system cannot stop the monitoring resource "VALUE_0" using the "VALU
COPTDM119E No device is associated with SAP ID: "VALUE_0". Explanation: No additional information is available for this me
COPTDM148E The system cannot create the new device model "VALUE_0" because it already exists. Explanation: No additional i
Explanation: No additional information is available for this message. COPTDM172E An error occurred while the system uninstalled the
COPTDM185E The file VALUE_0 is already used by TCDriver VALUE_1. Explanation: TCDriver file cannot be overwritten by a file from
COPUTL009E Usage: IDSCoexistMigration Migration-path root-userName password hostname port SSL(true/false) source-baseDN target-baseDN Explana
Compliance Messages COPDSE001E The system cannot update the given guest access desired state element because it is not stored in DC
Explanation: No additional information is available for this message. COPDSE015E The DSE setting value to be validated cannot be n
You might want to consider the following general recommendations for backing up your Tivoli Intelligent Orchestrator system: v Perfo
COPDSE103E Each permission character in the input permission string VALUE_0 must be one of "-", "r", "w"
determined by a database query. It is not possible to add members to a dynamic group. COPGRP009E Cannot remove the object "V
Explanation: No additional information is available for this message. COPNET014E The system cannot find VLAN: VALUE_0. Explanation:
RXA Messages CTGRI0000E Could not establish a connection to the target machine with the authorization credentials that were provided. E
administrator enable remote registry access and verify that the credentials your application is submitting have sufficient privileges o
CTGRI0024E Access to Resource is denied. Explanation: The operation failed because access to a resource has been denied. This could
Operator response: In the package definition file, specify the section name. DISSP6009W File file name not found in directory nam
v The OS/400® Preparation Site was installed correctly on the system. v The software package contains valid objects. v The user
DISSP6030W The configuration file file name was not found Explanation: You specified a configuration file that does not exist. Mess
Operator response: Enter the path to a valid directory. DISSP6044E Enter a value in the suggested range. Explanation: You have e
Chapter 2. Problem determination essentials for Tivoli Intelligent Orchestrator This chapter describes how to approach troubleshooting i
password are defined in Tivoli Provisioning Manager WebUI. 178 Tivoli Intelligent Orchestrator Problem Determination and Troubleshooting
Chapter 11. Tivoli Common Agent Services messages This chapter lists the available Tivoli Common Agent Services messages. Common Agent
common agent will send a notification to the agent recovery service. Administrator Response: Check the agent manager logs to find i
BTC1026I The common agent credentials are valid. The common agent has determined that it does not need to register for security cred
BTC1041I command to register the common agent with the agent registration service Explanation: No additional information is available
BTC1048E The common agent failed to renew its certificate revocation list. Explanation: The common agent failed to renew its certifi
If resetting the GUID failed, or the problem persists, contact customer support. BTC1050I true Explanation: No additional information
BTC2200I The system is restarting the common agent. Explanation: No additional information is available for this message. BTC2201E The
BTC2209I The common agent is being initialized. Explanation: No additional information is available for this message. BTC2210E The sh
BTC2411I The locale was successfully set to language_code and region_code. Explanation: No additional information is available for thi
v What was the first symptom of the problem? Have you noticed other symptoms occurring simultaneously? v Does the problem affect
BTC3009E The bundle_name bundle cannot be deleted because system cannot be found in the OSGi storage. Explanation: The specified bun
System action: The bundle was not installed. Administrator Response: Verify that the specified bundle is the one you intended to
BTC3117E The preupdate of the bundle, bundle_name failed. Explanation: The preUpdate logic specified in the bundle LifecycleActivator
BTC3135I command to create a directory in the common agent base directory Explanation: No additional information is available for th
BTC3154I The system failed to create the directory_name directory because the specified directory name is not valid. Explanation: No
System action: The bundle was not started. Administrator Response: Verify that the bundle is in the OSGi storage and that it ha
BTC4008I The common agent is reducing the service tracker cache size. Explanation: No additional information is available for this m
BTC4027I command to restart the common agent Explanation: No additional information is available for this message. BTC4028I unknown p
BTC4043E The command-line interface command failed. A communication error occurred. Verify that the common agent is registered and acti
BTC5007I The process_name status collection process is ending. Explanation: No additional information is available for this message. BT
searching the available IBM technotes for your product and the available knowledge bases to determine whether the resolution to your
BTC5027I Status has been sent. Explanation: No additional information is available for this message. BTC5028I The status report for
v Using a Web browser, access the URL, url.4. Start the upgrade again. 5. If the common agent upgraded continues to fail, co
4. Make sure that the common agent has write permission to the relative_path target directory. This path is relative to the commo
about the error that occurred. Explanation: You are checking the status of the upgrade after it failed, recovered from the error,
BTC5068I The upgrade of the common agent failed. Look in the common agent installation log at logs/agentInstall.log for more informati
not turned on, you might have to turn tracing on and restart the application server. If the exception indicates an I/O error (IOE
Programmer response: If the exception indicates that the class was not found (ClassNotFoundException), make sure that the name of t
Administrator Response: Contact IBM Customer Support. CTGEM0010E The agent manager cannot open the root private key associated with
CTGEM0016E The parameter_name parameter cannot be NULL. Explanation: A client program specified NULL for the parameter_name paramete
CTGEM0023E The agent manager cannot store information about the agent with the operating system GUID "operating_system_GUID"
The following stages are described to the Tivoli Intelligent Orchestrator problem determination process: 1. “Troubleshooting the prer
Administrator Response: Check the WebSphere application server log and trace files. Look at the log information that is generated w
v The client program uses the agent manager ID to verify that it is talking to the same agent manager as in previous requests,
CTGEM0042I The agent manager successfully revoked one or more certificates assigned to the component with managed element GUID GUID.
4. Ensure that the AgentManager.properties file contains an encrypted string for the value of the Registration.Agent.Access.Password p
property. The AgentManager.properties file is in the WEB-INF/classes/resources directory of the AgentManager.war file. 2. Use the Encry
WEB-INF/classes/resources directory of the AgentManager.war file and that the file is readable by the current user. 2. Ensure that t
CTGEM0058E The AuthXMLRemoveUser command received incorrect input arguments. This command takes a single argument, which is the ID o
CTGEM0062E The AuthXMLRemoveAuthType command received incorrect input arguments. This command takes a single argument, which is the I
application server for the recovery service. CTGEM0155I The recovery service started successfully. Explanation: No additional informa
accepted by this script. To find out which script failed, read the text of message CTGEM2100I, which occurs earlier in this message
v On Windows, launch Task Manager and check the Processes window. v On UNIX, run the following command to list all DB2 Univer
Application Server. Because the configuration script cannot read the properties file, the configuration cannot be performed and the ag
vvrrmm is the version information. The name of the file for the agent recovery service application is CTGEMRECvvrrmm.sys. If the fil
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
v GUID v SysInfo (Host Name, IP addr, OS Arch, OS Name, OS Ve r, Java Ver, Java VM, Java VM Ve r, CA Install Dir) v comm
Table 14. Files included in the CASservice.zip file (continued) File name File path All files from logs directory: msgAgent.log nonstop
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 kno
4. Click the name of a fix to read the description and optionally download the fix.To receive weekly e-mail notifications about
2. Describe your problem and gather background information. 3. Submit your problem to IBM Software Support.Determine the business
Use the Windows Services panel, or issue the ibmdiradm command on UNIX to verify if the service is running. IBM Directory Administ
For more information about problem resolution, see Searching knowledge bases and Obtaining fixes. 228 Tivoli Intelligent Orchestrator
Appendix C. Notices This information was developed for products and services offered in the U.S.A. IBM may not offer the products,
IBM Canada Ltd. Office of the Lab Director 8200 Warden Avenue Markham, Ontario L6G 1C7 CanadaSuch information may be available, subject
Index Aagent managerconfiguring WAS console to use a different port 88 determining version 83 disabling tracing 85 enabling tracing 85 i
Mmanualssee publications vii, ix message elementsaction 36 explanation 36 ID 36 text 36 message logs 35 messagescommon agent subsystem mes
troubleshooting (continued)manually associating discovered software resources with software definitions 75 Microsoft Active Directory instal
234 Tivoli Intelligent Orchestrator Problem Determination and Troubleshooting Guide
Printed in USA SC32-2216-00
7. Search the knowledge bases and, if necessary, contact Support. For more information, refer to Appendix B, “Support information,”
administrative console, security can be disabled in this file by changing the value of the enabled parameter in the second line fr
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
ResourceMgrIm I WSVR0049I: Binding Default_CF as eis/DefaultDatasource_CMP ResourceMgrIm I WSVR0049I: Binding AgentRegistry as jdbc/AgentReg
HttpTransport A SRVE0171I: Transport https is listening on port 9,043. HttpTransport A SRVE0171I: Transport https is listening on por
Tivoli®Intelligent OrchestratorProblem Determination and Troubleshooting Guide Version 5.1 SC32-2216-00
v Starts the WebSphere Application Server. v Configures the WebSphere Application Server, including: – WebSphere Application Serve
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
The output should return the following entries: tioldap, tiointernal, and tioappadmin. c. Confirm that a particular user or group h
c. If the ldapsearch search returns a connection error, start a Telnet session and try to connect to the IBM Tivoli Directory S
Constraints are listed in the $TIO_HOME/sql/db2/dbschema.sql file as foreign keys and primary keys. 2. Identify the type of constrai
8. Search the knowledge bases and, if necessary, contact Support. For more information, refer to Appendix B, “Support information,”
3. If the IBM Tivoli Directory Server is started, check the SystemOut.log file for the following types of exceptions. For more i
2005-05-02 10:24:11,123 ERROR [Servlet.Engine.Transports : 2] (Location.java:506) webui.Location: Error Code = COPCOM093EdcmSqlException ERR
ssh -l username IP ’command’ 4. If running the command using the command line interface works, it is an environment issue. In yo
Note: The command line tools can be found on TIO_HOME/tools Table 1. Tivoli Intelligent Orchestrator command line tools Name Locatio
Note: Before using this information and the product it supports, read the information in Appendix C, “Notices,” on page 229.First E
Table 1. Tivoli Intelligent Orchestrator command line tools (continued) Name Location Description Syntax dcmExport.cmd dcmExport.sh v On
Table 1. Tivoli Intelligent Orchestrator command line tools (continued) Name Location Description Syntax retrieveDetails.cmd retrieveDetail
Table 1. Tivoli Intelligent Orchestrator command line tools (continued) Name Location Description Syntax siregister.cmd siregister.sh v
Table 1. Tivoli Intelligent Orchestrator command line tools (continued) Name Location Description Syntax tc-driver-manager.cmd tc-driver-ma
Table 1. Tivoli Intelligent Orchestrator command line tools (continued) Name Location Description Syntax xmlImport.cmd xmlImport.sh v On
Table 2. WebSphere Application Server command line tools (continued) Name Location Description Syntax backupConfig restoreConfig v On Wi
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
v ### is 3-digit unique serial or message number. v Z is the severity code indicator, including the following indicators: Seve
Action title Description Administrator Response Describes what response a system administrator might be able to take. Programmer Response D
Contents Preface . . . . . . . . . . . . . . vii Who should read this book . . . . . . . . . vii Publications . . .
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 Co
Logging levels This section details the behavior of Tivoli Intelligent Orchestrator logs based on how the logging levels are defined.
# module is meant for messages written module specific files # output.normal=%d{ISO8601} %-5p [%t] (%13F:%L) %c{2}: %m%n output.error=%
#log4j.appender.datacentermodel.layout=org.apache.log4j.PatternLayout #log4j.appender.datacentermodel.layout.ConversionPattern=${output.module} #log4j
The Tivoli Intelligent Orchestrator application server automatically reloads the log4j configurations 60 seconds after you save the pr
44 Tivoli Intelligent Orchestrator Problem Determination and Troubleshooting Guide
Chapter 5. Tivoli Intelligent Orchestrator log files This chapter describes the directory locations for the following log files: v
UNIX or Linux $TIO_LOGS/uninstallLog files for starting and stopping the server Log files for starting and stopping the Tivoli Intell
Log files for the Web interface Log files for the Web interface and data center model changes, and other operations associated with
The silent installation program for Tivoli Intelligent Orchestrator exits before the installation is completed . . . . . . . . .5
Table 7. Deployment engine logs (continued) File name Location Description cbe.log Windows %TIO_LOGS%\deploymentengineUNIX or Linux $TIO_LOG
Logs for data collection and decision making Log files for the policy engine component (data acquisition engine, application controlle
Table 9. Automation package logs (continued) File name Location Description trace.log Windows %TIO_LOGS%\tcdrivermanagerUNIX or Linux $TIO_L
Chapter 6. Middleware prerequisite log files This chapter describes the directory locations for the following log files: v “Installa
Directory Server The log files for the IBM Tivoli Directory Server are: v ldap.stderr v ldap.stdout v ldapinst.logRuntime logs fo
WebSphere Application Server is the last service to stop when you shut down Tivoli Intelligent Orchestrator, so this log file is u
v db2diag.log v ibmds_config.log v ibmds_config_err.logTivoli Agent Manager Trace logs for the agent manager are stored in the Ag
Chapter 7. Common problems and known limitations in Tivoli Intelligent Orchestrator This chapter describes how to recover from the fo
In Linux, the tioadmin user creation fails if the tioadmin group already exists before you install. No exception is thrown, so the
Solution Use the DB2 Universal Database Administration Client, Version 8.1 for Windows operating systems on 32–bit systems CD instead.
Common agent subsystem messages . . . . . 153 TC driver manager subsystem messages . . . . 154 Utilities subsystem messages . .
3. Import the schema.ldif and ldap.ldif files into the Microsoft Active Directory server. Instructions for this step are found in
The installation of IBM Tivoli NetView on Windows fails if the password for creating a user account does not meet the system requi
v Do not uninstall the agent manager until all products that use it have been uninstalled. v Do not clean the agent manager t
Agent_Manager_install_dir/bin/RunInDbEnv.sh RemoveCASTables.sh database_password Replace database_password with the DB2 database password.–
Reinstalling Tivoli Intelligent Orchestrator: Retry the Tivoli Intelligent Orchestrator installation. The Tivoli Intelligent Orchestrato
Solution 2 Run the Tivoli Directory Server Web Administration tool to check the status of the LDAP server.Note: This solution is p
6. Change your password again based on the specified password syntax.Problems with workflows This section includes troubleshooting s
Cause The workflow variable values are limited to 4000 bytes. When a scriptlet or Java plug-in returns a value longer than 4000 by
This command line utility exports the workflow execution logs into an XML file. The tool simplifies the process of sending workflow
Log content structure: workflow –> deployment request –> workflow execution log –> workflow execution log detail Example wor
vi Tivoli Intelligent Orchestrator Problem Determination and Troubleshooting Guide
Cannot run workflows if the PS1 environment variable is altered Cause When running scriptlets in Tivoli Intelligent Orchestrator, the
v “Common agents unable to communicate with the agent manager” on page 75 v “Limitations when trying to manually associate a d
privacy settings for the Tivoli Intelligent Orchestrator Web address so that they no longer interfere with the Tivoli Intelligent Or
DB2 Universal Database does not work properly with terminal server Cause The Tivoli Intelligent Orchestrator installation fails with DB
Solution From the Microsoft Visual C++ 6.0 Support Web site available at http://support.microsoft.com/default.aspx?scid=kb;en-us;259403&
For more information, refer to the DB2 product documentation available at http://www.ibm.com/software/data/db2/udb/support/manualsv8.html.Fo
native2ascii -encoding UTF-8 <Report_name>.csv | native2ascii -reverse -encoding <Language_Code> > <Report_name>_output.
Cause The Distinguished Name (DN) syntax supported by the directory server does not support special characters. This is a known prob
v When you look at the properties of the software stack, no software modules are displayed. v Compliance checking also incorrect
Agent receives an HTTP Unauthorized (401) response code Agent can receive an Unauthorized (401) response code for a number of reaso
Preface This guide describes how to identify and resolve problems that might occur when you use Tivoli® Intelligent Orchestrator or T
78 Tivoli Intelligent Orchestrator Problem Determination and Troubleshooting Guide
Chapter 8. Troubleshooting the agent manager This chapter contains the following sections to help you resolve problems with the agent
Table 10. Agent manager installation log files Log file name Description AMReturnValues.log Summary of return values of the steps of
Table 10. Agent manager installation log files (continued) Log file name Description jacl/appServer_out.log jacl/appServer_err.log Standard
Table 12. Remote registry database installation log files Log File Description datastore.out A log of the SQL statements that are ru
Determining the version of agent manager To determine the version of the agent manager, use the GetAMInfo command, which is located
Verifying the installation of WebSphere Application Server To verify the installation of WebSphere Application Server, use the firstst
3. Click Apply to list the JDBC providers for the agent manager application server. 4. In the list of providers, click AgentJDB
2. Click Servers –> Application Servers –> app_server_name –> Logging and Tracing –> Diagnostic Trace. Replace app_server
h. In the Save to Master Configuration area , click Save again to exit the Master Configuration window.5. Optionally, clean up
Comments to this Manuals