Professional Documents
Culture Documents
TPM PD Guide
TPM PD Guide
TPM PD Guide
Version 7.1.1
Provisioning Manager
Version 7.1.1
Note
Before using this information and the product it supports, read the information in Notices on page 553.
Contents
Chapter 1. Introduction . . . . . . . . 1
Support information . . . . . . . . . . . . 1
Searching knowledge bases . . . . . . . . 2
Obtaining fixes . . . . . . . . . . . . 4
Contacting IBM Software Support . . . . . . 5
General data to collect for IBM Software Support 7
Problem classification . . . . . . . . . . . 11
Product maintenance . . . . . . . . . . 11
Using log files for troubleshooting . . . . . . . 12
Setting up IBM Support Assistant and the Tivoli
Provisioning Manager data collector . . . . . 12
Collecting data with IBM Support Assistant . . 13
Trace logs . . . . . . . . . . . . . . 15
Log locations . . . . . . . . . . . . . 15
Installation directories and other paths . . . . . 32
35
40
45
48
49
49
50
50
50
50
51
52
52
52
53
54
54
54
55
55
55
56
57
58
59
59
59
60
61
61
62
63
64
66
66
67
67
69
70
71
72
74
75
75
77
77
77
78
79
79
80
80
81
81
82
56
iii
85
86
82
83
83
84
84
84
88
89
92
92
93
93
94
94
. 99
.
.
.
. 99
. 100
. 101
.
.
.
. 102
. 103
. 103
105
105
106
107
107
108
109
. . . . 111
iv
105
.
.
. 111
. 111
. 112
113
113
114
114
114
115
115
116
117
118
118
119
119
119
120
120
121
121
123
123
124
124
125
125
126
127
127
128
128
129
. 129
. 130
. 130
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
. 130
. 131
132
. 133
. 133
134
134
135
135
135
136
136
136
137
137
138
138
139
139
139
140
140
140
141
. 149
133
143
143
144
145
145
146
146
147
147
147
148
149
149
. 151
.
.
.
.
151
152
152
153
. 153
. 154
. 154
. 154
. 155
. 155
157
157
158
158
158
159
159
159
160
161
161
162
162
163
163
163
164
164
165
165
166
166
166
167
169
. 170
. 170
. 171
. 171
. 172
. 172
. 172
196
. 173
. 175
. 175
. 176
. 176
. 177
. 178
vi
.
.
.
.
.
.
.
.
179
181
181
182
182
183
184
185
. 185
. 186
. 186
. 187
. 188
. 188
. 189
. 190
. 190
. 190
. 191
. 191
195
197
197
198
198
199
. 199
. 199
. 199
200
. 200
. 201
. 201
. 201
201
. 202
. 202
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
205
205
206
206
207
207
208
208
208
209
210
210
211
211
212
212
212
213
213
214
214
214
. 217
.
.
.
.
217
218
218
218
219
219
220
221
222
223
224
224
225
226
226
227
228
229
231
231
232
232
232
235
235
235
236
238
238
240
241
241
242
242
243
243
244
244
245
245
245
246
247
247
248
248
249
250
250
251
251
251
252
252
253
253
254
.
.
.
.
.
.
.
255
255
256
256
257
257
258
261
. 262
. 262
. 263
Contents
vii
. 262
239
239
265
. 265
. 265
. 266
. 266
.
.
.
.
.
.
.
.
266
267
267
268
269
269
270
271
272
. 272
277
280
280
281
281
viii
283
283
283
284
284
285
285
286
286
287
287
288
. 289
289
. 290
. 290
. 291
. 291
292
. 292
. 292
. 293
. 293
293
. 294
. 294
. 295
. 296
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
297
297
298
299
299
353
355
387
395
396
409
410
414
414
435
437
439
441
442
445
448
450
458
463
468
472
472
473
479
485
488
489
499
503
CTGDEQ .
CTGDES .
CTGEM .
CTGRI .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
506
511
515
550
Notices . . . . . . . . . . . . . . 553
Contents
ix
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
Chapter 1. Introduction
Identify and resolve problems that might occur when you are using the product.
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 Provisioning Manager.
There are a number of options available for problem determination, and they are described in this
section. The options include:
v Obtaining support to help identify your problem.
v Consulting the overall product overview.
v Using the log files for troubleshooting.
Support information
If you encounter a problem with the product, first look for help at the Tivoli Provisioning Manager
Support Web site. This site contains a searchable database of Technotes and frequently asked questions
relating to current issues.
This site also contains presentations, fixes, fix packs, and white papers. Access the Web site, at the
following address:
http://www-306.ibm.com/software/sysmgmt/products/support/
In addition, 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.
v Obtaining fixes: You can locate the latest fixes that are already available for your product.
v Contacting IBM Software Support: If you still cannot solve your problem, and you need to work with
someone from IBM, you can use a variety of ways to contact IBM Software Support.
Troubleshooting
Troubleshooting is the process of finding and eliminating the cause of a problem. Whenever you have a
problem with your IBM software, the troubleshooting process begins as soon as you ask yourself what
happened? A basic troubleshooting strategy at a high level involves:
v Recording the symptoms.
v Recreating the problem.
v Eliminating possible causes.
If you cannot identify the cause of a problem, you might want to seek the assistance of the IBM Tivoli
Support team, who will be able to pinpoint the cause of the problem and suggest ways to recover from
specific situations. For more information about how to contact the IBM Tivoli Software Support, refer to
Contacting IBM Software Support on page 5.
Recording the symptoms of the problem
Depending on the type of problem you have, whether it be with your application, your computer, or
your tools, you might receive a message that indicates something is wrong. Always record the error
message that you see. As simple as this sounds, error messages often contain codes that make more sense
Copyright IBM Corp. 2003, 2011
as you investigate your problem further. You might also receive multiple error messages that look similar,
but have subtle differences. By recording the details of each one you can learn more about where your
problem exists. Sources of error messages:
v
v
v
v
Web interface
Command-line interface
Log files
Error dialog boxes
: %WAS_HOME%\logs\<server-name>
: $WAS_HOME/logs/<server-name>
v Isolate the root error using the proposed troubleshooting methods to find a resolution.
v Take screen shots of specific steps and errors received along the way.
UNIX
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
Search tips
The following resources describe how to optimize your search results:
v Searching the IBM Support Web site
v Using the Google search engine
v Search the information center for more information about error messages that you encounter while
using the product.
Obtaining fixes
A product fix might be available to resolve your problem. To determine what fixes and other updates are
available, search for downloads on the IBM Software Support Web site.
Support for Tivoli Provisioning Manager
When you find a fix that you are interested in, click the name of the fix to read its description and to
optionally download the fix.
Procedure
1.
2.
3. If you are already registered for the My Support feature, sign in and skip to the next step. If you are
not registered, click Register now. Complete the registration form using your e-mail address as your
IBM ID and click Submit.
4. Click the Edit profile tab.
5. In the Products list, select Software. A second list is displayed.
6. Select a product subsegment, for example, Systems and Asset Management. A third list is displayed.
7. Select a product subsegment, for example, Change & Configuration. A list of applicable products is
displayed.
8. Select the products for which you want to receive updates, for example, Tivoli Provisioning Manager.
9. Click Add products.
10. After selecting all products that are of interest to you, click Subscribe to e-mail.
11. Update your e-mail address as needed.
12. In the list, select Software.
13. Select the types of documents for which you want to receive information.
14. Click Update.
Results
If you experience problems with the My support feature, request help in one of the following ways:
Online
Send an e-mail message to erchelp@ca.ibm.com, describing your problem.
By phone
Call 1-800-IBM-4You (1-800-426-4968).
For information about types of fixes, see the IBM Software Support Handbook at http://
techsupport.services.ibm.com/guides/contacts.html.
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
Chapter 1. Introduction
Severity 4
The problem has minimal business impact: The problem causes little impact on operations or a
reasonable circumvention to the problem was implemented.
v
v
v
v
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
ISA has a new Tool workbench that provides you with the problem determination tools that IBM Support
uses to resolve issues.
Included in ISA, is a Service feature with an automated system and symptom based collector. The system
collector gathers general information from your operating system, registry, and other important locations.
The system based collection provides the unique ability to collect specific information relating to a
particular problem that you are having.
You can also use ISA to enter your entitlement information once and have it saved for future sessions.
This enables you to create a problem report for IBM and attach the collector file at the same time.
Chapter 1. Introduction
For the most current version information, see the document called Collect troubleshooting data for Tivoli
Provisioning Manager: http://www-01.ibm.com/support/docview.wss?rs=1015&context=SS2GNX
&uid=swg27011981.
Use the configuration examiner as described in Built-in troubleshooting features to collect the following
information and make it available to IBM Software Support so that they can solve the problem as quickly
as possible:
v A brief description of the class of problem, such as installation, configuration, audit, system failure, or
performance.
v Language or locale information.
v Server information for these servers: Tivoli Provisioning Manager, LDAP, DB2, IBM Tivoli Directory
Server, WebSphere Application Server. The information must include the systems on which they are
located, network connectivity to these systems, and the version number (including fix packs) of the
servers.
v Time frame in which the problem occurred (in relation to the log entries).
v Proper contact information - your IBM Passport Advantage or Tivoli Customer ID, appropriate
telephone number or e-mail address, your preference of return correspondence: by phone or e-mail,
alternate phone number (if possible), and if not responding to you, the name and contact information
for the person Tivoli Customer Support needs to contact.
Tool location
v If theTivoli Provisioning Manager installation failed, you can find the configuration examiner in the
TPMConfigUtil folder, where TPM_V711_Install_Win.zip or TPM_V711_Install_Unix.zip was extracted.
v If you successfully installed Tivoli Provisioning Manager, you can find the configuration examiner in
$TIO_HOME/tools/TPMConfigUtil.
Windows
2000
ExamineTPM.cmd
UNIX
2000
Linux
./ExamineTPM.sh
v For archived configuration files and logs, run:
Windows
2000
UNIX
Where:
archive-file is the path of the archived file
extract-location is the folder where the archived files are to be extracted to. If this option is not
specified, the files are loaded in the memory. If this option is specified, the files are saved for future
use.
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
v To package installation or runtime logs together with system properties and Tivoli Provisioning
Manager product information, go to File > Archive All or File > Archive Install or File > Archive
Runtime.
To archive logs for a given time period, set the log start and finish date under Logs > Archive - Log
start time and Logs > Archive - Log finish time.
v To switch the log level between info and debug, go to Logs > Set Log Level > info or Logs > Set Log
Level > debug.
%TIO_HOME%\tools
Where %TIO_HOME% is the Tivoli Provisioning Manager home directory.
UNIX
$TIO_HOME/tools
Where$TIO_HOME in the Tivoli Provisioning Manager home directory.
Syntax:
Windows
2000
packageLogs.cmd
The packageLogs tools automatically determines the default location of the logs.
UNIX
packageLogs.sh
The packageLogs tool automatically determines the default location of the logs.
Returned file: The tool produces a compressed file LogPackagetimestamp.zip, located in the current
directory, where timestamp is a time stamp assigned by the system when the packageLog tool completes
the compressed file.
C:\Windows\swdis.ini
Chapter 1. Introduction
UNIX
/etc/Tivoli/swdis.ini
2. In the MOBILE section of the file, find the property trace_level. Set the property to trace_level=5.
3. Note the value of the property prodcut_dir. The default value is the following directory:
Windows
2000
C:\swdis
UNIX
/.swdis
4. Run the software package block installation again to reproduce the problem.
5. Find the value of the property prodcut_dir. Collect the content of the directory that product_dir now
specifies.
The data you collect can be sent to the IBM Tivoli Software Support team for troubleshooting assistance.
Windows
2000
%TIO_HOME%\eclipse\tpmconfig
Where %TIO_HOME% is the Tivoli Provisioning Manager home directory.
UNIX
$TIO_HOME/eclipse/tpmconfig
Where $TIO_HOME in the Tivoli Provisioning Manager home directory.
set JAVA_HOME=C:\IBM\WebSphere\AppServer\java
set WAS_HOME=C:\IBM\WebSphere\AppServer
UNIX
2000
Linux
export JAVA_HOME=/opt/WebSphere/AppServer/java
export WAS_HOME=/opt/WebSphere/AppServer
AIX
export JAVA_HOME=/usr/WebSphere/AppServer/java
export WAS_HOME=/usr/WebSphere/AppServer
Location:
Windows
2000
%TIO_HOME%\tools
Where %TIO_HOME% is the Tivoli Provisioning Manager home directory.
10
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
UNIX
$TIO_HOME/tools
Where $TIO_HOME is the Tivoli Provisioning Manager home directory.
Syntax:
Windows
2000
Problem classification
This guide provides information about Tivoli Provisioning Manager tools, resources, and techniques that
can help you identify and resolve the following types of problems:
v
v
v
v
v
Installation problems
Login problems
Provisioning workflow problems
Other common problems
Problems with the distribution infrastructure
Product maintenance
Problems can often be avoided with planning and preparation before you deploy Tivoli Provisioning
Manager. Before you install the software, review the Tivoli Provisioning Manager Release Notes, the Tivoli
Provisioning Manager Installation Guide, and the Tivoli Provisioning Manager Coexistence and Migration Guide.
These documents contain the following important information:
v Supported operating system levels
v
v
v
v
v
v
11
your system, you must back up your system in accordance with the documentation that is provided with
your operating system or with any specialized backup and restore software that you use.
You might want to consider the following general recommendations for backing up your Tivoli
Provisioning Manager system:
v Back up your existing DB2 or Oracle database. For more information, see theDB2 documentation and
the Oracle documentation for your database version.
v Back up your directory server database. For more information, see the documentation provided for
your directory server.
v Back up your automation packages (.tcdriver files) using any of the standard backup and restore
tools that you are using. For more information, see the Provisioning Workflows Guide.
Procedure
1. Installing ISA on the Tivoli Provisioning Manager computer is recommended to make it easier for the
tool to collect system and product logs. Download and install the latest version from
http://www.ibm.com/software/support/isa/. You will need to log in using your IBM Web identity;
if you do not already have one, you can complete the free registration process to obtain one.
Uncompress the downloaded archive file and follow the instructions included in the archive to install
ISA. You only require the ISA workbench, not the ISA agent.
12
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
Click the IBM Support Assistant on the Windows desktop or from the Start menu under
Start > All Programs > IBM Support Assistant.
2000
Linux
Click IBM Support Assistant "Other" group of the Application Browser or run the
following command:
Windows
2000
installation_directory/rcp/rcplauncher
AIX
installation_directory/rcp/rcplauncher
What to do next
IBM Support Assistant is now configured to collect data for Tivoli Provisioning Manager. If you need
assistance with problem determination, you can use the data collector to gather log files into a single
archive that you can submit to IBM Software Support.
Procedure
1. If you want to collect logs for a managed computer, you can run a provisioning workflow to collect
the logs and store them on the provisioning server. You can then package these logs with other logs
on the provisioning server using ISA. You can only collect logs from a computer where the IBM
Tivoli Common Agent is installed.
a. Log on to Tivoli Provisioning Manager.
b. From the Start Center, find the data model ID of the computer.
c. Click Go To > Administration > Provisioning > Provisioning Workflows.
d. Search for the provisioning workflow called TCA_Collect_Logs and run it.
e. When the provisioning workflow is complete, the log is stored in the provisioning server in the
TIO_LOGS/tivolicommonagent directory. The log can now be included with other logs collected
by ISA.
2. If you want to collect logs for base services, use a compression tool to add the following log files to
an archive.
a. On the computer where the base services is installed:
v c:\ibm\smp\logs, where c:\ibm is the default installation location.
v c:\ibm\smp\solutions\logs
v c:\ibm\smp\maximo\tools\logs
v c:\program files\ibm\common\acsi\logs
v If your problem occurred during installation validation, logs can also be located under
C:\Documents and Settings\Administrator\Configurable Fields.
Chapter 1. Introduction
13
Click the IBM Support Assistant on the Windows desktop or from the Start menu under
Start > All Programs > IBM Support Assistant.
2000
Linux
Click IBM Support Assistant "Other" group of the Application Browser or run the
following command:
Windows
2000
installation_directory/rcp/rcplauncher
AIX
installation_directory/rcp/rcplauncher
Windows
2000
C:\Program Files\IBM\tivoli\common\COP\logs
UNIX
2000
Linux
/usr/ibm/tivoli/common/COP/logs
v
10. When prompted, enter the WebSphere Application Server profile directory.
11.
12.
13.
14.
Note: You will not be prompted for the WebSphere Application Server profile directory if you have
WebSphere Application Server installed in the default location.
Click Proceed to Data Collection, and click OK in the next window to confirm your selection.
When prompted, enter information for the base services and click OK.
a. Specify the user name and password that you use to log on to the Tivoli Provisioning Manager
interface.
a. Specify the host name of the computer where base services is installed.
a. Specify the HTTP port of the base services computer. The default is 80.
In the window that confirms the location of the resulting log package, click OK
When prompted for feedback, click Yes and type your feedback, or click No to skip this step.
15. Check the status of the data collection on the Analyze Problem > Collect Data > Current Status tab.
16. View the resulting log package by clicking the link next to Collected Result in the Current Status
tab.
What to do next
The logs are now saved you can click the name of the log to open the package or you can submit it to
IBM Software Support.
14
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
Trace logs
Tivoli Provisioning Manager provides configurable tracing capabilities that can help you determine the
cause of a problem. Trace logs and first-failure data capture (FFDC) are built into the software to assist
the IBM Customer Support for Tivoli software personnel in gathering information to determine why a
problem is occurring, and might be requested as part of diagnosing a reported problem.
v Trace logs capture operating environment details, including the starting and stopping of processes, data
transfer between software components, activity that occurs while the software is running, and errors
that occur when the code fails to operate as intended.
v First-failure data capture captures and stores the tracing information preceding an error message.
Trace logs are used to determine the causes of Tivoli Provisioning Manager problems and to debug
errors. Error messages can include information about the cause of the error and possible resolutions for
the error. Trace logs are intended to be used by Tivoli Customer Support service engineers or developers.
If you encounter an issue, Support representatives might ask you to obtain information from trace logs so
that they can review the details.
Trace logs have the file name trace.log, and are stored in the subfolder for each software component.
Trace logs are in English only, multicultural support is not provided for trace entries. By default, tracing
is enabled at the minimal level that is required for FFDC, and can be changed as required.
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.
The location of the message logs and trace logs for Tivoli Provisioning Manager follow the Tivoli
Common Directory standard. The log locations are shown in the table.
Directory name
Description
Path
J2EE
WebSphere JVM
v %WAS_HOME%\profiles\ctgAppSrv01\
logs\MXServer
v %TIO_LOGS%\j2ee
deploymentengine
%TIO_LOGS%\console.log
install
Installation
uninstall
Uninstall process
%TIO_LOGS%\uninstall
activityplan
Activity plan
%TIO_LOGS%\console.log
jvm
%TIO_LOGS%\jvm
Chapter 1. Introduction
15
Directory name
Description
Path
Windows
2000
UNIX
C:\Program Files\IBM\tivoli\common\COP\logs
/usr/ibm/tivoli/common/COP/logs
Windows
2000
UNIX
C:\Program Files\IBM\WebSphere\AppServer
/opt/IBM/WebSphere/AppServer
The log files that are generated by all the utility scripts, such as %TIO_LOGS%\tools\cancel-all-in-progress.cmd,
%TIO_LOGS%\tools\changepassword.cmd, are located in the %TIO_LOGS% directory on Windows systems ($TIO_LOGS
on UNIX or Linux).
Installation logs
Tivoli Provisioning Manager installation logs:
Because multiple components are installed during installation, there are several log files that you might
need to check to resolve an installation error. If you need to troubleshoot the installation of a specific
component, check the log file associated with the component. Ensure that you check any referenced log
files for additional information. For example, the log file for component that failed during installation
might point to a log for more information. The WebSphere Application Server might reveal an incorrect
WebSphere Application Server setting that caused the component installation to fail.
The listed log files are located on the Tivoli Provisioning Manager computer. If you installed Tivoli
Directory Server on a separate computer, the log files for Tivoli Directory Server are located on that
computer.
16
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
Log files
Middleware
Windows
2000
v %MWI_workspace%\mwi.log
v %MWI_workspace%\mwi.err
UNIX
v $MWI_workspace/mwi.log
v $MWI_workspace/mwi.err
2000
Linux
v $MWI_workspace/mwi.log
v $MWI_workspace/mwi.err
Deployment engine log files
UNIX
v $MWI_workspace/hostname/deploymentPlan/logs/
[INSTALL_timestamp]
DB2
v $MWI_workspace/hostname/deploymentplan/
MachinePlan_hostname/00004_DB2_9.1/install/01_BASE/
[INSTALL_timestamp]/logs/
v $MWI_workspace/hostname/deploymentPlan/
MachinePlan_hostname/00004_DB2_9/logs
Windows
2000
v %MWI_workspace%\hostname\deploymentplan\
MachinePlan_hostname\00009_WAS_ND_6.1\install\01_BASE\
[INSTALL_timestamp]\logs
v %MWI_workspace%\hostname\deploymentPlan\
MachinePlan_hostname\00009_WAS_ND_6.1\logs
v C:\Program Files\IBM\WebSphere\AppServer\logs\install\
UNIX
v $MWI_workspace/hostname/deploymentplan/
MachinePlan_hostname/00009_WAS_ND_6.1/install/01_BASE/
[INSTALL_timestamp]/logs/
v /usr/IBM/WebSphere/AppServer/logs/install/
2000
Linux
v $MWI_workspace/hostname/deploymentplan/
MachinePlan_hostname/00009_WAS_ND_6.1/install/01_BASE/
[INSTALL_timestamp]/logs
v /opt/IBM/WebSphere/AppServer/logs/install/
Tivoli Directory Server
v $MWI_workspace/deploymentplan/MachinePlan_hostname/
00007_ITDS_6.1/install/02_BASE/[INSTALL_timestamp]/logs/
v $MWI_workspace/hostname/deploymentPlan/
MachinePlan_hostname/00006_ITDS_DB2_CCMDB/logs
v $MWI_workspace/hostname/deploymentPlan/
MachinePlan_hostname/00008_ITDS_Configuration/logs
Chapter 1. Introduction
17
Log files
Base services
Windows
2000
v C:\ibm\SMP\logs\si_inst.log
v C:\ibm\SMP\logs\CCMDB_install.log
v C:\ibm\SMP\logs
UNIX
2000
Linux
v /opt/IBM/SMP/logs/si_inst.log
v /opt/IBM/SMP/logs/CCMDB_install.log
v /opt/IBM/SMP/logs
Cygwin
v C:\cygwin\var\log\
v %TEMP%\tclog_wrapper\downloadCygwinSetup.log
v %TEMP%\tclog_wrapper\downloadCygwinRep.log
v %TEMP%\tclog_wrapper\instCygwin.log
v %TEMP%\tclog_wrapper\cygwin_ssh_config.log
v %TEMP%\tclog_wrapper\cygwin_ssh_config.err
v $TEMP\tclog_wrapper\tcinstall.log
v $TEMP/tclog_wrapper/nonUI_install.log
v $TEMP/tclog_wrapper/nonUI_install_err.log
v $TEMP/tclog
Windows
2000
v %TEMP%\tclog_wrapper\amtrace.log
v %TEMP%\tclog_wrapper\amtrace.err
v C:\Program Files\IBM\AgentManager\logs
UNIX
2000
Linux
v $TEMP/tclog_wrapper/amtrace.log
v $TEMP/tclog_wrapper/amtrace.err
v /opt/IBM/AgentManager/logs
Dynamic Content Delivery Management
Center
Device manager federator
v $TEMP/tclog_wrapper/CDSinstall-stdout.log
v $TEMP/tclog_wrapper/CDSinstall-stderr.log
Windows
2000
v %TEMP%\tclog_wrapper\dmsinstalltrace.log
v %TEMP%\tclog_wrapper\dmsinstalltrace.err
v C:\Program Files\IBM\DeviceManager\log
UNIX
2000
Linux
v $TEMP/tclog_wrapper/dmsinstalltrace.log
v $TEMP/tclog_wrapper/dmsinstalltrace.err
v /opt/IBM/DeviceManager/log
Tivoli Provisioning Manager for OS
Deployment
v $TEMP/tclog_wrapper/tpmfosd.log
v $TEMP/tclog_wrapper/tpmfosd.err
v $TEMP/tclog_wrapper/tpmfosd-installation.log
18
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
Log files
v $TEMP/tclog_wrapper/itmtrace.log
v $TEMP/tclog_wrapper/itmtrace.err
v $TEMP/tclog_wrapper/itmInstall.log
Windows
2000
v %TEMP%\tclog_wrapper\psi_tpm.log
v C:\ibm\SMP\solutions\logs
UNIX
2000
Linux
v $TEMP/tclog_wrapper/psi_tpm.log
v /opt/IBM/SMP/solutions/logs
TEMP is
v %TEMP% - the Windows temporary directory.
v $TEMP - the Unix temporary directory.
MWI_workspace
v %MWI_workspace% - the Windows directory path whose default value is C:\ibm\tivoli\mwi\
workspace
v $MWI_workspace - the Unix directory path whose default value is /root/ibm/tivoli/mwi/workspace
For more information about path variables, see Path Variables
Tivoli Provisioning Manager uninstallation logs:
When you uninstall Tivoli Provisioning Manager, the log files are located in
Windows
2000
%TEMP%\tclog
UNIX
/tmp/tclog
C:\Program Files\ibm\tivoli\common\
Chapter 1. Introduction
19
UNIX
/opt/ibm/tivoli/common
/var/IBM/tivoli/common
%TIO_HOME%\tools
Where %TIO_HOME% is the Tivoli Provisioning Manager home directory.
UNIX
$TIO_HOME/tools
Where $TIO_HOME is the Tivoli Provisioning Manager home directory.
Syntax:
Windows
2000
Windows
2000
%TIO_LOGS%\packageFipsConfig\FipsConfigPackagepackage.zip.
UNIX
$TIO_LOGS/packageFipsConfig/FipsConfigPackagepackage.zip.
Component logs
Tivoli Provisioning Manager start and stop log:
When you start Tivoli Provisioning Manager, the application creates a log file, tio_start.log. The
tio_start.log file is located in:
Windows
2000
%TIO_LOGS%
UNIX
$TIO_LOGS
When you stop Tivoli Provisioning Manager, the application creates a log file, tio_stop.log. The
tio_stop.log file is located in:
Windows
2000
%TIO_LOGS%
20
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
UNIX
$TIO_LOGS
Location
Description
Windows
%TIO_LOGS%\j2ee
UNIX or Linux
$TIO_LOGS/j2ee
msg.log
Windows
%TIO_LOGS%\j2ee
UNIX or Linux
$TIO_LOGS/j2ee
trace.log
Windows
%TIO_LOGS%\j2ee
UNIX or Linux
$TIO_LOGS/j2ee
Maximo Logs
web interface events are also included within Maximo logs. These logs are stored in
Windows
%WAS_HOME%\profiles\ctgAppSrv01\logs\MXServer
UNIX or Linux
$WAS_HOME/profiles/ctgAppSrv01/logs/MXServer
Table 3. Maximo web interface logs
File name
Description
startServer.log
stopServer.log
SystemErr.log
SystemOut.log
v DMSMsg.log
v native_stderr.log
v native_stdout.log
v serverStatus.log
v TraceDMS.log
Chapter 1. Introduction
21
where <datadir> is the Tivoli Provisioning Manager for OS Deployment data directory specified during
the Tivoli Provisioning Manager for OS Deployment installation.
Table 4. Tivoli Provisioning Manager for OS Deployment logs
File name
Description
boot.log
This log file stores all information about the PXE Proxy
service, the PXE Boot Discovery service and the MTFTP
service.
file.log
http.log
jobs.log
nbp.log
tcp.log
vm.log
Description
tivhscan.xml
22
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
Description
cit_software.xml
cit_signature.xml
traceCIT.log
The input files for the Common Inventory Technology scan can be found in the following location:
<system_temp_dir>/SoftwareSignatureInput<discoveryId><deviceId>
<profileTypeId>.xml
Table 6. Output files of the Tivoli Common Agent
File name
Description
../tivoli/ep/conf/org.eclipse.osgi/
bundles/<bundle_number>/data/
cit_<computername>
<date_and_time>.xml.archive
The XML file that converts the scan output into the
Tivoli Provisioning Manager database schema.
../tivoli/ep/logs/*
Location
Windows
%TIO_LOGS%
UNIX or Linux
$TIO_LOGS/
msg.log
Windows
%TIO_LOGS%\
Description
This log file stores all event logs for
workflow and deployment requests
including messages, traces, and
debugging information.
This log file stores the globalized
event messages for the deployment
engine component.
UNIX or Linux
$TIO_LOGS/
trace.log
Windows
%TIO_LOGS%\
UNIX or Linux
$TIO_LOGS/
heartbeat.log
Windows
%TIO_LOGS%\
UNIX or Linux
$TIO_LOGS/
Chapter 1. Introduction
23
Workflow logs:
If you want to determine why a particular provisioning workflow has failed, you can use the Web
interface to display the run history for that provisioning workflow. You can also export the log files of
your provisioning workflow history using the workflowLogExport command, as described in
workflowLogExport command.
Automation package files:
Users can run the tcdrivermanager utility if they have installation and uninstallation issues and look in
the %TIO_HOME%\tcdrivermanager.log for details. Messages and errors for provisioning workflows that
have run are logged in the deployment engine logs files in TIO_LOGS\console.log.
C:\Program Files\IBM\WebSphere\AppServer
AIX
/usr/IBM/WebSphere/AppServer
2000
Linux
Solaris
2000
/opt/IBM/WebSphere/AppServer
Check the following log files for errors:
v SystemOut.log
v startServer.log
v stopServer.log
v SystemErr.log
SystemOut.log
This is the log file for WebSphere output. It contains messages that are generated when the
applications running inside the WebSphere Application Server are being started or stopped. You
might want to refer to this file when WebSphere does not start. You can find the log files in the
following locations:
v
Windows
2000
UNIX
%WAS_HOME%\profiles\ctgAppSrv01\logs\MXServer\SystemOut.log
2000
Linux
$WAS_HOME/profiles/ctgAppSrv01/logs/MXServer/SystemOut.log on UNIX
or Linux
After the provisioning server is started, use the tail -f SystemOut.log command to monitor this
log file for any problems that might occur.
startServer.log
24
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
This is the log file for the startup of the WebSphere Application Server, located in the following
locations:
v
Windows
2000
UNIX
%WAS_HOME%\logs\server1
2000
Linux
$WAS_HOME/logs/server1
Look for Open for e-business for a successful startup of the WebSphere Application Server.
stopServer.log
This is the log file for the shutdown of the WebSphere Application Server. WebSphere Application
Server is the last service to stop when you shut down the provisioning server, so this log file is
useful for verifying whether the shutdown completed. You can find the log files in the following
locations:
2000
%WAS_HOME%\logs\server1
v Windows
v $WAS_HOME/logs/server1
Look for Server <server-name> stop completed for a successful shutdown of the WebSphere
Application Server.
SystemErr.log
This is the log file that contains Java exceptions and stack traces caused by the enterprise
applications. You can find the log files in the following locations:
2000
%WAS_HOME%\logs\server1
v Windows
v $WAS_HOME/logs/server1
25
26
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
v ibmdiradm.log: The administration daemon error log. View status and errors encountered by the
administrative daemon.
v adminaudit.log: The administration daemon audit log. Use the records in the log to check for
suspicious patterns of activity in an attempt to detect security violations.
v audit.log: Audit logging is used to improve the security of the directory server.
v bulkload.log: The idsbulkload log command is used to load entries. The bulkload log allows you to
view status and errors related to bulkload.
v idstools.log: The configuration tools log contains status and error messages related to the
configuration tools.
v db2cli.log: This log records database errors that occur as a result of LDAP operations.
v lostandfound.log: This log archives entries that were replaced due to replication and conflict
resolution. The log allows you to recover the data in the replaced entries, if necessary.
v ibmslapd.log: The server error log contains status and error messages related to the server.
For more information about the IBM Tivoli Directory Server Version 6.0 logging utilities, see
http://publib.boulder.ibm.com/infocenter/tivihelp/v2r1/index.jsp?topic=/com.ibm.IBMDS.doc/
PDGuide05.htm
Log configuration
Logging levels:
This section details the behavior of Tivoli Provisioning Manager logs based on how the logging levels are
defined.
The logging level hierarchy for Tivoli Provisioning Manager is shown in the following table:
Logging level
Description
msg_error#com.thinkdynamics.kanaha.
util.logging.MessageLevel
msg_warn#com.thinkdynamics.kanaha.
util.logging.MessageLevel
msg_info#com.thinkdynamics.kanaha.
util.logging.MessageLevel
error
warn
info
debug
The extended logging levels are the highest levels in the logging hierarchy. These levels are set
exclusively for the messages, which are globalized and distinct from the trace logs. Trace logs are
available only in English.
Configuring logs with log4j:
Log data in Tivoli Provisioning Manager is managed by log4j, an open source logging tool. This section
details the default log4j settings, the customized Tivoli Provisioning Manager settings, and how you can
modify settings dynamically. For complete log4j documentation, go to http://logging.apache.org/log4j/
docs/documentation.html.
The data from the console.log, msg.log, trace.log, and cbe.log files are recorded based on the default
logging levels and configuration parameters set in the log4j.prop file or in the log4j-util.prop. Use the
Chapter 1. Introduction
27
log4j-util.prop file to configure the logging for all scripts located in the %TIO_HOME%\tools directory.
Some scripts in automation packages also use the logging settings in log4j-util.prop.
Configuring log4j dynamically:
The log4j files are in the following locations:
v
Windows
2000
UNIX
%TIO_HOME%\config
2000
Linux
$TIO_HOME/config
It is possible to change the INFO variable into WARNING, ERROR, or DEBUG, depending on the type
of logging information needed. For example, DEBUG has a higher threshold than INFO.
3. Save the file.
The provisioning server automatically reloads the log4j configurations 60 seconds after you save the
properties file. You need to restart the provisioning server for the changes to take effect. The updated
log4j configuration will implement after 60 seconds.
To enable the automation package 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.append=false to log4j.appender.file.append=true.
3. Save the file.
Configuring logging levels within the web interface:
You are able to change the logging level of any of the loggers from within the web interface.
Before you begin
You can discover the definitions of each logging level within the topic Logging Levels.
Logging levels can be set for each logger within the web interface. In order to change the logging level of
a logger:
Procedure
1. Click Go To > System Configuration -> Platform Configuration -> Logging.
2. Within the Log Level column, click the Select Value button for the logger to be configured. A dialog
for selecting the log level is displayed.
3. Within the Select Value dialog, select the logging level to use for the logger.
4. Click the Save Logger button within the action menu bar.
Results
The logger is now configured to produce logs at the selected level.
Note: This change will not occur immediately; see Configuring log4j dynamically for further information.
28
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
%TIO_HOME%\config
UNIX
2000
Linux
$TIO_HOME/config
# output directory. Can be overwritten with -Dkanaha.logs=<directory>
#
kanaha.logs=logs
# message formats
# normal used to write to console.log
# error used to format error messages (prints location of a problem)
# 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
#Do not configure the root category - that is configured
by the Maximo framework
#
log4j.category.com.thinkdynamics=INFO, consolefile, errorfile
log4j.category.com.ibm.tivoli=INFO, consolefile, errorfile
#
#everything goes to console.log
#rolling by log size. For other rolling options, see
http://logging.apache.org/log4j/docs/index.html
#
log4j.appender.consolefile=org.apache.log4j.RollingFileAppender
log4j.appender.consolefile.MaxFileSize=100MB
log4j.appender.consolefile.MaxBackupIndex=10
log4j.appender.consolefile.File=${kanaha.logs}/console.log
log4j.appender.consolefile.layout=org.apache.log4j.PatternLayout
log4j.appender.consolefile.layout.ConversionPattern=${output.normal}
log4j.appender.consolefile.threshold=info
log4j.appender.consolefile.append=true
#errors to trace log file, for FFDC
#rolling by log size
#
log4j.appender.errorfile=org.apache.log4j.RollingFileAppender
log4j.appender.errorfile.MaxFileSize=10MB
log4j.appender.errorfile.MaxBackupIndex=10
log4j.appender.errorfile.File=${kanaha.logs}/trace.log
log4j.appender.errorfile.layout=org.apache.log4j.PatternLayout
log4j.appender.errorfile.layout.ConversionPattern=${output.error}
log4j.appender.errorfile.threshold=error
log4j.appender.errorfile.append=true
#globalized message log to msg.log (user log)
#rolling by log size
#
log4j.appender.messagefile=org.apache.log4j.RollingFileAppender
log4j.appender.messagefile.MaxFileSize=10MB
log4j.appender.messagefile.MaxBackupIndex=10
log4j.appender.messagefile.File=${kanaha.logs}/msg.log
log4j.appender.messagefile.layout=org.apache.log4j.PatternLayout
Chapter 1. Introduction
29
log4j.appender.messagefile.layout.ConversionPattern=${output.normal}
log4j.appender.messagefile.threshold=MSG_INFO#com.thinkdynamics.kanaha.
util.logging.MessageLevel
log4j.appender.messagefile.append=true
#suppress annoying messages from datacentermodel
#
log4j.category.com.thinkdynamics.kanaha.datacentermodel=INFO
#suppress annoying messages from dataaquisition
#
log4j.category.com.thinkdynamics.kanaha.dataaquisitionengine=INFO
#suppress annoying messages from org.apache
#
log4j.category.org.apache=INFO
#write heart beat messages to heartbeat.log only (not console.log)
where the possible values for <value> are FINE, FINER, and FINEST.
2. Restart the agent service or run the following command:
CA_HOME/bin/lwilog.sh[bat] -refresh
3. Use the trace command on the managed server. The following is the syntax for this command:
agentcli.bat trace <command> <level>
30
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
console.log
info
If you want more log information for troubleshooting purposes, set the log level to debug.
trace.log
error
msg.log
MSG_INFO#com.thinkdynamics.kanaha.util.logging.MessageLevel
cbe.log
off
RollingFileAppender defaults:
The RollingFileAppender defines the autoarchiving behavior of the log4j tool. As defined in the
log4j.prop file above, the default settings for each Tivoli Provisioning Manager log file are:
console.log
v Maximum number of archived log files: 10
v Maximum log file size: 100MB
trace.log
v Maximum number of archived log files: 10
v Maximum log file size: 10MB
msg.log
v Maximum number of archived log files: 10
v Maximum log file size: 10MB
cbe.log
v Maximum number of archived log files: 10
v Maximum log file size: 10MB
Enabling expect tracing:
There are two methods to enable Expect tracing for Tivoli Provisioning Manager.
1. Change the file on the provisioning server:
Windows
2000
%TIO_HOME%\scriplets
UNIX
$TIO_HOME/scriplets
Edit header.expect, or header.expect_local if it is a local Expect scriplet, launch.bash_local, and
launch.ksh_local by changing:
log_user 0
exp_internal 0
to
log_user 1
exp_internal -f <filename> 1
For example, the change for a UNIX file might look like the following:
Chapter 1. Introduction
31
log_user 1
exp_internal -f /tmp/expect.log 1
to
log_user 1
exp_internal -f <filename> 1
Adding these statements to the scriptlet code will enable logging to the specified file name.
Component
Default directory
AM_HOME
Windows
2000
UNIX
APDE_HOME
Automation Package
Developer
Environment
DB2_HOME
DB2
C:\Program Files\IBM\AgentManager
2000
Linux
/opt/IBM/AgentManager
TIO_HOME/eclipse
Windows
2000
AIX
2000
Linux
/opt/ibm/db2/V9.5
2000
Linux
SystemDrive:\Program Files\IBM\SQLLIB
Solaris
2000
/opt/IBM/db2/V9.5
Windows
2000
Eclipse
HTTP_HOME
Windows
2000
AIX
Solaris
2000
JAVA_HOME
Java Runtime
Environment
C:\Program Files\IBM\HTTPServer
/usr/IBM/HTTPServer
2000
Linux
/opt/IBM/HTTPServer
32
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
Component
Default directory
MAXIMO_HOME
base services
Windows
2000
UNIX
Windows
2000
UNIX
MWI_workspace
ORACLE_HOME
Middleware installer
directory
Oracle Database
C:\ibm\SMP
2000
Linux
/opt/IBM/SMP
C:\ibm\tivoli\mwi\workspace
2000
Linux
/root/ibm/tivoli/mwi/workspace
$ORACLE_BASE/product/version/db_1
The value of $ORACLE_BASE is the directory in which all Oracle
Database software is installed.
v
UNIX
2000
Linux
/u01/app/oracle/product/10.2.0/db_1
UNIX
2000
Linux
/u01/app/oracle/product/11.1.0/db_1
TDS_HOME
TIO_HOME
TIO_LOGS
common agent
Tivoli Provisioning
Manager
Windows
2000
AIX
2000
Linux
Windows
2000
UNIX
Windows
2000
UNIX
Tivoli Provisioning
Manager runtime logs v
v
Windows
2000
UNIX
C:\Program Files\tivoli\ep
/usr/tivoli/ep
/opt/tivoli/ep
C:\Program Files\IBM\LDAP\V6.2
2000
Linux
/opt/IBM/ldap/V6.2
C:\Program Files\IBM\tivoli\tpm
2000
Linux
/opt/IBM/tivoli/tpm
C:\Program Files\IBM\tivoli\common\COP\logs
2000
Linux
/usr/ibm/tivoli/common/COP/logs
%TEMP%
WAS_HOME
WebSphere
Application Server
Windows
2000
AIX
Solaris
2000
C:\Program Files\IBM\WebSphere\AppServer
/usr/IBM/WebSphere/AppServer
2000
Linux
/opt/IBM/WebSphere/AppServer
Chapter 1. Introduction
33
34
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
For information about uninstalling components, see Uninstalling Tivoli Provisioning Manager.
Log files
Step during installation where the
problem occurs
v TEMP/tclog_wrapper/
extractDB2Client.log
v TEMP/tclog_wrapper/
extractDB2Client_err.log
v TEMP/tclog_wrapper/db2installstdout.log
v TEMP/tclog_wrapper/db2installstderr.log
v TEMP/tclog_wrapper/
DBbackupafterMBS-stdout.log
v TEMP/tclog_wrapper/
DBbackupafterMBS-stderr.log
35
Log files
Step during installation where the
problem occurs
v TEMP/tclog_wrapper/
call_was_config.log
v TEMP/tclog_wrapper/
call_was_config_fips.log
v TEMP/tclog_wrapper/
nonUI_install.log
v TEMP/tclog_wrapper/
nonUI_install_err.log
v TEMP/tclog
v TEMP/tclog_wrapper/
create_wasprofile.log
v WAS_HOME/AppServer/profiles/
casprofile/logs/
AboutThisProfile.txt
36
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
Log files
Step during installation where the
problem occurs
Agent Manager installation, actual
installation
v TEMP/tclog_wrapper/
preparePingAM.log
v TEMP/tclog_wrapper/
preparePingAM.err
v TEMP/tclog_wrapper/
call_pingam.log
v TEMP/tclog_wrapper/
call_pingam_err.log
v TEMP/tclog_wrapper/
config_ssl.log
v TEMP/tclog_wrapper/
config_ssl.err
v TEMP/tclog_wrapper/soapsslconfig.log
v TEMP/tclog_wrapper/soapsslconfig.err
v TEMP/tclog_wrapper/
getAMPass4CDS.log
v TEMP/tclog_wrapper/
getAMPass4CDS.err
v TEMP/tclog_wrapper/CDSinstallstdout.log
v TEMP/tclog_wrapper/CDSinstallstderr.log
v CDS_HOME/log
v TEMP/tclog_wrapper/
dmsinstalltrace.log
v TEMP/tclog_wrapper/
dmsinstalltrace.err
37
Log files
Step during installation where the
problem occurs
v TEMP/tclog_wrapper/
dmsconfigtrace.log
v TEMP/tclog_wrapper/
dmsconfigtrace.err
v DMS_HOME/logs/
dms_config_trace.log
v DMS_HOME/logs/dms_config.log
v TEMP/tclog_wrapper/
dms_getpass.log
v TEMP/tclog_wrapper/
dms_getpass_err.log
v TEMP/tclog_wrapper/tpmfosd.log
v TEMP/tclog_wrapper/
call_importXML4OSD.log
v TEMP/tclog_wrapper/tpmfosd.err
v TEMP/tclog_wrapper/
call_importXML4OSD.err
Windows
2000
v %TEMP%\tclog_wrapper\
itmtrace.log
v %TEMP%\tclog_wrapper\
itmtrace.err
v ITM_HOME\InstallITM/IBM
Tivoli Monitoring for
Provisioning<timestamp>.log
UNIX
2000
Linux
v $TEMP/tclog_wrapper/ITMconfigstdout.log
v $TEMP/tclog_wrapper/ITMconfigstderr.log
v ITM_HOME/InstallITM/IBM
Tivoli Monitoring for
Provisioning<timestamp>.log
38
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
Log files
Step during installation where the
problem occurs
Configure WAS to run as tioadmin
v TEMP/tclog_wrapper/
cas_runastioadmin.log
v TEMP/tclog_wrapper/
cas_runastioadmin.err
v TEMP/tclog_wrapper/
stop_CASServer_root.log
v TEMP/tclog_wrapper/
stop_CASServer_root.err
v TEMP/tclog_wrapper/
changePermission_cas.log
v TEMP/tclog_wrapper/
changePermission_cas.err
v TEMP/tclog_wrapper/
start_CASServer_tioadmin.log
v TEMP/tclog_wrapper/
start_CASServer_tioadmin.err
v TEMP/tclog_wrapper/
wasND_runastioadmin.log
v TEMP/tclog_wrapper/
wasND_runastioadmin.err
v TEMP/tclog_wrapper/
stop_MXServer_root.log
v TEMP/tclog_wrapper/
stop_MXServer_root.err
v TEMP/tclog_wrapper/
stop_nodedmgr_root.log
v TEMP/tclog_wrapper/
stop_nodedmgr_root.err
v TEMP/tclog_wrapper/
changePermission_was.log
v TEMP/tclog_wrapper/
changePermission_was.err
v TEMP/tclog_wrapper/
start_nodedmgr_tioadmin.log
v TEMP/tclog_wrapper/
start_nodedmgr_tioadmin.err
Database backup
v TEMP/tclog_wrapper/
call_db2_restart.log
v TEMP/tclog_wrapper/
call_db2_restart.err
v TEMP/tclog_wrapper/
DBbackupafterTPMCore-stdout.log
v TEMP/tclog_wrapper/
DBbackupafterTPMCore-stderr.log
39
Log files
Step during installation where the
problem occurs
WAS backup
For information about uninstalling components, see Uninstalling Tivoli Provisioning Manager.
Step during installation where the
problem occurs
Log files
v C:\cygwin\var\log\
v %TEMP%\tclog_wrapper\
downloadCygwinSetup.log
v %TEMP%\tclog_wrapper\
downloadCygwinRep.log
v %TEMP%\tclog_wrapper\
instCygwin.log
v %TEMP%\tclog_wrapper\
cygwin_ssh_config.log
v %TEMP%\tclog_wrapper\
cygwin_ssh_config.err
40
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
Log files
v C:\ibm\tivoli\mwi\workspace\
mwi.log
v C:\ibm\tivoli\mwi\workspace\
mwi.err
3. Remove the failed component and
then try again.
Deployment engine log files
2. Resolve the cause of the problem.
v MWI_workspace\hostname\
deploymentPlan\logs\
INSTALL_<timestamp>
DB2 log files
v MWI_workspace\hostname\
deploymentplan\
MachinePlan_hostname\
00004_DB2_9.5\install\01_BASE\
INSTALL_<timestamp>\logs
v MWI_workspace\hostname\
deploymentPlan\
MachinePlan_wind\
00004_DB2_9\logs
WAS log files
v MWI_workspace\hostname\
deploymentplan\
MachinePlan_hostname\
00009_WAS_ND_6.1\install\
01_BASE\INSTALL_<timestamp>\
logs
v MWI_workspace\hostname\
deploymentPlan\
MachinePlan_hostname\
00009_WAS_ND_6.1\logs
v C:\Program Files\IBM\
WebSphere\AppServer\logs\
install\
ITDS log files
v MWI_workspace\hostname\
deploymentplan\
MachinePlan_hostname\
00007_ITDS_6.1\install\02_BASE\
INSTALL_<timestamp>\logs\
v MWI_workspace\hostname\
deploymentPlan\
MachinePlan_hostname\
00006_ITDS_DB2_CCMDB\logs
v MWI_workspace\hostname\
deploymentPlan\
MachinePlan_hostname\
00008_ITDS_Configuration\logs
41
Log files
Windows
2000
MAXIMO_HOME\scripts\
LogZipper.bat
UNIX
MAXIMO_HOME\
scripts\LogZipper.sh
v %TEMP%\tclog_wrapper\
MBSBackupB4TPM-stdout.log
v %TEMP%\tclog_wrapper\
MBSBackupB4TPM-stderr.log
v %TEMP%\tclog_wrapper\
DBbackupafterMBS-stdout.log
v %TEMP%\tclog_wrapper\
DBbackupafterMBS-stderr.log
v %TEMP%\tclog_wrapper\
WASbackupctgDmgr01-afterMBSstdout.log
v %TEMP%\tclog_wrapper\
WASbackupctgDmgr01-afterMBSstderr.log
v %TEMP%\tclog_wrapper\
WASbackupAppSrv01-afterMBSstdout.log
v %TEMP%\tclog_wrapper\
WASbackupAppSrv01-afterMBSstderr.log
v %TEMP%\tclog_wrapper\
call_was_config.log
v %TEMP%\tclog_wrapper\
call_was_config_fips.log
42
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
Log files
v %TEMP%\tclog_wrapper\
nonUI_install.log
v %TEMP%\tclog_wrapper\
nonUI_install_err.log
v %TEMP%\tclog
v %TEMP%\tclog_wrapper\
create_wasprofile.log
v WAS_HOME\AppServer\profiles\
casprofile\logs\
AboutThisProfile.txt
v %TEMP%\tclog_wrapper\
preparePingAM.log
v %TEMP%\tclog_wrapper\
preparePingAM.err
v %TEMP%\tclog_wrapper\
call_pingam.log
v %TEMP%\tclog_wrapper\
call_pingam_err.log
v %TEMP%\tclog_wrapper\
config_ssl.log
v %TEMP%\tclog_wrapper\
config_ssl.err
v %TEMP%\tclog_wrapper\soapsslconfig.log
v %TEMP%\tclog_wrapper\soapsslconfig.err
43
Log files
v %TEMP%\tclog_wrapper\
getAMPass4CDS.log
v %TEMP%\tclog_wrapper\
getAMPass4CDS.err
v %TEMP%\tclog_wrapper\
CDSinstall-stdout.log
v %TEMP%\tclog_wrapper\
CDSinstall-stderr.log
v CDS_HOME\log
v %TEMP%\tclog_wrapper\
dmsinstalltrace.log
v %TEMP%\tclog_wrapper\
dmsinstalltrace.err
v %TEMP%\tclog_wrapper\
dmsconfigtrace.log
v %TEMP%\tclog_wrapper\
dmsconfigtrace.err
v DMS_HOME\logs\
dms_config_trace.log
v DMS_HOME\logs\dms_config.log
v %TEMP%\tclog_wrapper\
dms_getpass.log
v %TEMP%\tclog_wrapper\
dms_getpass_err.log
v %TEMP%\tclog_wrapper\
tpmfosd.log
v %TEMP%\tclog_wrapper\
tpmfosd.err
v %TEMP%\tclog_wrapper\
call_importXML4OSD.log
v %TEMP%\tclog_wrapper\
call_importXML4OSD.err
v %TEMP%\tclog_wrapper\
itmtrace.log
v %TEMP%\tclog_wrapper\
itmtrace.err
v %TEMP%\tclog_wrapper\
call_db2_restart.log
v %TEMP%\tclog_wrapper\
call_db2_restart.err
44
v ITM_HOME\InstallITM/IBM
Tivoli Monitoring for
Provisioning<timestamp>.log
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
WAS backup
Log files
v %TEMP%\tclog_wrapper\
DBbackupafterTPMCore-stdout.log
v %TEMP%\tclog_wrapper\
DBbackupafterTPMCore-stderr.log
v %TEMP%\tclog_wrapper\
WASbackupctgDmgr01afterTPMCore-stdout.log
v %TEMP%\tclog_wrapper\
WASbackupctgDmgr01afterTPMCore-stderr.log
v %TEMP%\tclog_wrapper\
WASbackupAppSrv01afterTPMCore-stdout.log
v %TEMP%\tclog_wrapper\
WASbackupAppSrv01afterTPMCore-stderr.log
v %TEMP%\tclog_wrapper\
psi_tpm.log
v MAXIMO_HOME\solutions\logs\
TPM_PMP
Log files
TIO_LOGS/fixpack/
1. Remove /tmp/CAS_Update or
%tmp%/CAS_Update.
TIO_LOGS/fixpack/
*Upgrade_<timestamp>.log
TIO_LOGS/fixpack/
*Upgrade_<timestamp>.log
45
Log files
TIO_LOGS/fixpack/
*Upgrade_<timestamp>.log
TIO_LOGS/fixpack/
*Upgrade_<timestamp>.log
TIO_LOGS/fixpack/
*Upgrade_<timestamp>.log
TIO_LOGS/fixpack/
<timestamp>_tpm71_fp1_*.log
3. Restore permissions:
Windows
2000
Use Cygwin to
restore permissions
UNIX
2000
Linux
User and
group is tioadmin. Mode is 755.
TIO_LOGS/fixpack/
postinstall_<timestamp>.log
TIO_LOGS/fixpack/
postinstall_<timestamp>.log
TIO_LOGS/migration
TIO_LOGS/
importSoftwareSignature.log
TIO_LOGS/fixpack/
postinstall_<timestamp>.log
46
DMS_HOME/log
TIO_LOGS/fixpack
If trace is enabled, also see the
TraceDMS*.logs
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
Log files
Windows
2000
%ProgramFiles%\IBM\
tivoli\common\ctgde\logs\
UNIX
2000
Linux
/var/IBM/tivoli/common/ctgde/
logs/
TIO_LOGS/fixpack/
tpmfosdUpgrade_<timestamp>.log
1.
v
Windows
2000
2000
Linux
Extract
the binary file from the
fp_temp/TPMFOSD folder to the
installation directory for Tivoli
Provisioning Manager for OS
Deployment. The fp_temp
directory is where you
extracted the core component
upgrade package files.
TIO_LOGS/fixpack/itmagentStop.log
TIO_LOGS/fixpack/
itmagentUpgrade_<timestamp>
ITM_HOME/logs
TIO_LOGS/fixpack/
itmagentUpgrade_<timestamp>
ITM_HOME/logs
47
Log files
TIO_LOGS/fixpack/itmagentStart.log
1. Start WAS.
2. Check the
_master_tcdriver_update
workflow execution log and
determine which migration
workflow failed.
TIO_LOGS/fixpack/
*Upgrade_<timestamp>.log
TIO_LOGS/runmastertcdriverupdate.log
Symptoms
The upgrade of the agent manager fails during the Tivoli Provisioning Manager upgrade from version 7.1
to version 7.1.1.
Windows
2000
AIX
2000
Linux
%CommonProgramFiles%\InstallShield\Universal\common\Gen2\_vpddb\vpd.script
/usr/lib/objrepos/InstallShield/Universal/common/Gen2/_vpddb/vpd.script
/root/InstallShield/Universal/common/Gen2/_vpddb/vpd.script
48
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
INSERT
INSERT
INSERT
INSERT
INSERT
INTO
INTO
INTO
INTO
INTO
DATABASE_META VALUES(2)
LOCAL_PERSISTED_VARIABLES_TABLE
LOCAL_PERSISTED_VARIABLES_TABLE
LOCAL_PERSISTED_VARIABLES_TABLE
LOCAL_PERSISTED_VARIABLES_TABLE
VALUES(1,WAS_PASS,,NULL,false)
VALUES(1,CONTAINER_WAS,true,NULL,false)
VALUES(1,CONTAINER_EWAS,,NULL,false)
VALUES(1,WAS_USER,,NULL,false)
2. Install the agent manager again using the agent manager image file:
a. Extract the agent manager image <fp_temp>/CAS/AM_V142_PLATFORMS.[zip|tar] into a location on
your computer.
b. Run the setupPLATFORM.[exe|bin] file.
c. Select Custom for the installation type and click Next.
d. Select the agent manager installation directory.
e. Select the Install from relocation image check box.
f. Select the backup file in the Relocation Image File Name field.
g. Select an empty temporary folder in the Relocation Temporary Storage Directory Name field.
3. Perform the rest of the steps in the wizard to complete the installation.
4. Run the following command:
MigrationClosureTool -close force
Symptoms
NFS mounted images are used and the checksum validation is slow.
DB2 transaction log error during the base services upgrade of Tivoli
Provisioning Manager
See the following information to recover from problems during the base services upgrade.
Symptoms
DB2 transaction log error causes a failure of the base services upgrade.
Causes
The upgrade of the base services fails due to transaction log for the database is full during the Tivoli
Provisioning Manager upgrade from version 7.1 to version 7.1.1.
49
Symptoms
AIX
On AIX, the middleware installer reports that you have insufficient disk space.
1.
2. The solution installer is included with some IBM products. If the middleware installer detects an
existing installation and the service is not started, an error is displayed.
50
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
2. If the solution installer was previously installed by another product, you must start it manually before
running the middleware installer.
a. Check for an existing installation of solution installer. The default installation location is:
v
Windows
2000
C:\Program Files\IBM\Common\acsi
UNIX
/usr/ibm/common/acsi
v
b. If an installation exists, check that the deployment engine is working:
1)
Windows
2000
Windows
2000
listIU.cmd
UNIX
./listIU.sh
If the deployment engine installed correctly, you receive output similar to the following :
IU
UUID: DDCE934782398B3E81431666515AC8B5 Name: DE Extensions
Interfaces CLI IU
Version: 1.3.1
IU
UUID: C37109911C8A11D98E1700061BDE7AEA Name: Deployment
Engine IU
Version: 1.3.1
IU
RootIU UUID: D94240D11C8B11D99F2D00061BDE7AEA
Name:
Install IU
Version: 1.3.1
Check the Services control panel. If the IBM ADE service is not running, start it.
UNIX
2000
Linux
Symptoms
DB2 installation stops halfway when the configured node name is different from the configured host
name.
Causes
The DB2 installation uses the uname -n command to obtain the node name of the computer. Typically, the
node name is the same as the host name that is returned with the hostname command. Tivoli Provisioning
Manager installation requires that the host name and the node name of the computer are identical.
51
a. Log on as root.
b. Change the node name to match the host name. For example, to change the node name to
myserver, run the following command:
uname -S myserver
Symptoms
v You receive this error during installation.
SQL1390C The environment variable DB2INSTANCE is not defined or is
invalid.
v The following message appears in the DB2 installation log called db2inst.log:
1: WARNING:A minor error occurred while installing "DB2 Enterprise Server
Edition" on this computer. Some features may not function correctly.
Causes
This is a known issue. This error occurs because Tivoli Provisioning Manager is initially deployed
without any DB2 instances. The DB2INSTANCE variable is defined later in the installation process.
Symptoms
While attempting to extract the DB2 package on Solaris 10, the workflow might generate the following
error:
tar: ././@LongLink: typeflag L not recognized, converting file.
Causes
This problem is caused by a limitation of the tar utility, which prevents extracting very long paths.
Symptoms
During the Tivoli Provisioning Manager installation, the system might indicate that it cannot connect to
the IBM Tivoli Directory Server.
52
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
Causes
This error occurs because Tivoli Directory Server was not started before running the installer. Tivoli
Directory Server must be started before you install Tivoli Provisioning Manager so that the installer can
connect to it.
Windows
2000
UNIX
: C:\IBM\LDAP\ldapinst.log
2000
Linux
: /usr/ldap/ldapinst.log
After the installation of the directory server is complete, an LDAP database must be created within
DB2. For more information, refer to the Installation Guide for Tivoli Provisioning Manager 7.1.1.
The ldapcfg.stat file shows the syntax that was used at the time of the database creation:
C:\IBM\ldap\bin\ldapcfg -n -a db2inst1 -w password -d LDAP -l
C: -c -f C:\IBM\ldap\tmp\ldapcfg.dat
Windows
2000
: C:\IBM\ldap\tmp\ldapcfg.stat
UNIX
2000
Linux
: /usr/ldap/tmp/ldapcfg.stat
v
2. Verify the status of the directory server, using the ibmdirctl tool, located in the C:\IBM\ldap\bin
2000
UNIX
2000
Linux
, or in the /usr/ldap/bin directory on
. Type the following
directory on Windows
command to check the directory server status:
3. If the directory server is not started, start it by using the following command:
start: ibmdirctl -D cn=root -w <password> status
Symptoms
During the installation, the system indicates that it cannot connect to the database.
Causes
This error occurred because the database was not started before running the installer. The database server
must be started before you install Tivoli Provisioning Manager, so that the installer can connect to it.
Windows
2000
UNIX
: DB2 - <instance_name>
: $db2start
If the database server was successfully started, you can see the following output:
db2start 12-21-2004 14:44:01 0 0 SQL1063N
DB2START processing was successful. SQL1063N
DB2START processing was successful
53
Symptoms
Installing the DB2 client on Windows 2003 fails.
Causes
The CD used for installing the DB2 client, DB2 Administration Client, Version 8.1 on 64bit systems, is
not supported on Windows 2003 operating systems.
Symptoms
During the Tivoli Management Agent installation, the Tivoli Directory Server installation step fails. The
log file /tmp/itds60/idsicrt.log has an error message similar to the following:
GLPICR058E: The specified directory, /home/ldapinst,
is not a valid directory, does not exist, or is not writable.
Causes
The LDAP instance user was manually created but the associated home directory does not exist. This
causes the Tivoli Directory Server instance creation to fail because it cannot write files to the home
directory of the LDAP instance user.
Symptoms
The Microsoft Active Directory configuration fails.
Causes
54
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
The Microsoft Active Directory SSL certificate is missing. If you run the Tivoli Provisioning Manager
installer without the SSL certificate, the Microsoft Active Directory configuration will fail.
Symptoms
File corruption leads to missing XML files.
Causes
Older versions of Winzip causes an incompatibility problem.
Symptoms
The Tivoli Provisioning Manager installation exits with error 1005.
Causes
The Microsoft Active Directory certificate is missing but the user enters a value for the certificate location
during the install. If the file does not exist, then the error occurs. There is no other information available
with this error code.
Symptoms
Chapter 2. Installation and upgrade problems
55
When starting Tivoli Provisioning Manager using a login window manager such as the Common Desktop
Environment (CDE), a message informs you that WAS_HOME is not set.
Causes
The login window manager might have bypassed the required user profile file.
The tioadmin user uses the bash shell as the login shell, which is supported for a line-mode login (for
example, using telnet). If you use a login window manager, it might bypass the .profile file for
tioadmin. When the profile file is bypassed, the system cannot create a complete login environment.
Base services installation does not accept LDAP names with spaces
Add quotation marks (" ") around the LDAP distinguished names if you need to include spaces.
Symptoms
Manually entering the User base entry and Group base entry LDAP information during the base services
installation causes the LDAP validation to fail.
Causes
Spaces in the LDAP distinguished names are not supported.
Symptoms
The Tivoli middleware installer fails on Red Hat Enterprise Linux. Systems with SELinux enabled display
an error message stating that the Java Runtime Environment (JRE) was not found on the system.
56
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
v Edit the /etc/selinux/config file and set SELINUX to either permissive or disabled. This solution,
however, affects the level of security for the entire system.
Procedure
1. First check de_processreq.log for failures related to VerifyLogsInInstallLogs Action. The
de_processreq.log file can be found at:
<workspace>\<machine name>\deploymentPlan\MachinePlan_<computer shortname>
\00009_WAS_ND_6.1\install\01_BASE/[INSTALL_<processing.req.id>]/logs/de_processreq.log
So, for example, if the workspace is located at: C:\ibm\tivoli\workspace, the computer name is
mycomputer, and the processing.req.id is created as a date_timestamp, then the de_processreq.log
would be located in:
C:\ibm\tivoli\mwi\workspace\mymachine.ibm.com\deploymentPlan\MachinePlan_mymachine\
00009_WAS_ND_6.1\install\01_BASE\[INSTALL_1130_06.54]\logs
2. Next, check for any stale WebSphere Application Server Network Deployment entries:
a. Extract the native image of WebSphere Application Server Network Deployment:
Windows
WAS-ND_WindowsIA32_Custom_v61023
LINUX
WAS-ND_LinuxIA32_Custom_v61023.tar.gz
AIX
WAS-ND_AIXppc64_Custom_v61023.tar.gz
57
b. Edit the vpd.properties file, remove any WebSphere Application Server Network Deployment
entries, and then save the file. The file is located in the installation directory of the operating
system:
Windows
C:\WINNT directory or C:\windows directory
UNIX /usr/lib/objrepos/
4. After cleaning the registry, run the middleware installation program again and Restart the plan.
WebSphere Application Server Network Deployment will now be successfully installed in the default
location, for example, C:\Program Files\IBM\WebSphere\AppServer for Windows.
Procedure
1. For UNIX systems, complete the following steps:
a. List Java processes.
ps -ef | grep -i java
b. Locate the process-id of the Java thread: <WebSphere Install Location>/java/bin/java and then
kill the process.
kill -9 <process-id>
58
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
Symptoms
Installation failed during the base services installation with the error message Failed to install IBM
Tivoli Provisioning Manager base services.
Windows
2000
2000
Linux
Windows
2000
59
2000
Linux
Windows
2000
2000
Linux
3. Log on to the database server as the database instance owner and recover the database. The following
instructions are for DB2. For Oracle database recovery, see your Oracle documentation.
a.
Windows
2000
set DB2INSTANCE=CTGINST1
db2cmd
b. Run the command to restore the database. Enter the command on a single line.
db2 restore database MAXDB71 user ctginst1 using <instance owner password> from <DB2_BACKUP_DIR>
with 3 buffers buffer 1000 without rolling forward without prompting
4. If you are using the base services for other products that are installed in the same environment as
Provisioning Manager, restore the deployment engine database to the state before installing the base
services. For more information, see ../com.ibm.tivoli.tpm.ins.doc/install/t_ccmdb_restorede.dita.
5. Log on to the computer where WebSphere Application Server is installed and start WebSphere
Application Server.
Windows
2000
WAS_HOME\profiles\ctgDmgr01\bin\startManager.bat
WAS_HOME\profiles\ctgAppSrv01\bin\startNode.bat
WAS_HOME\profiles\ctgAppSrv01\bin\startServer.bat MXServer
UNIX
2000
Linux
WAS_HOME/profiles/ctgDmgr01/bin/startManager.sh
WAS_HOME/profiles/ctgAppSrv01/bin/startNode.sh
WAS_HOME/profiles/ctgAppSrv01/bin/startServer.sh MXServer
6.
Restart the base services installation. For more information, see Installing the base services.
Symptoms
The base services WebSphere Application Server trace logs indicate that there was a file transfer error for
MAXIMO.ear.
Causes
The port settings might not be properly set up.
60
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
Verify the port settings on both the provisioning server and on the Windows computer where the base
services are installed. On both computers, ensure that the port speed settings for the network interface
card and for the port switch match. Setting the port speed to bidirectional communication on both the
network interface card and on the port switch is recommended.
Symptoms
At the end of base services installation, the following error is displayed:
CTGIN2252I: Can not access to base services web application.
Causes
At the end of the base services installation, the installer tries to connect to the Web application. The
connection might fail if the Web application is not yet running on the application server.
Symptoms
One of the following error messages can occur either in an installation panel, or the
CTGInstallTrace00.log file:
CTGIN2381E: Maximo Database upgrade command failed. Command: Database Upgrade command validation failed.
CTGIN2381E: Maximo updatedb utility would fail.
Causes
This message indicates that there were changes made in your environment that need to be committed in
the database before new products can be added into the database.
61
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
Symptoms
The following message is displayed at the end of the base services installation:
The installation is finished, but some serious errors occurred during the install.
The error message tells you to check the file CTGInstallTrace00.log. The log file contains an error similar
to the following example:
** ERROR: Autonomic Deployment Engine installation/upgrade failure.
Return code: 3
Failure: DE in use or general failure
See the CCMDB si_inst.log and DE logs for additional information.
If you continue with Web components installation on the same computer, the installation fails.
Causes
There are several possible causes for this error.
C:\Program Files\IBM\Common\acsi
Windows
2000
/usr/ibm/common/acsi
2. Clean up any existing .lck files.
v
UNIX
Note: If you created images after completing stages of the Tivoli Provisioning Manager installation,
the lock files might have been present in an image of the computer that you recovered before running
the Web components installer.
3. Verify that the deployment engine is running. Check the Services control panel. If the IBM ADE
service is not running, start it.
4.
Windows
2000
setenv.cmd
Windows
2000
listIU.cmd
62
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
UNIX
./listIU.sh
If the deployment engine engine installed correctly, you receive output similar to the following
example:
IU
UUID: DDCE934782398B3E81431666515AC8B5 Name: DE Extensions
Interfaces CLI IU
Version: 1.3.1
IU
UUID: C37109911C8A11D98E1700061BDE7AEA Name: Deployment
Engine IU
Version: 1.3.1
IU
RootIU UUID: D94240D11C8B11D99F2D00061BDE7AEA
Name:
Install IU
Version: 1.3.1
Windows
2000
UNIX
C:\ibm\SMP
2000
Linux
/opt/IBM/SMP
Windows
2000
si_inst.bat
UNIX
./si_inst.sh
8. Continue the base services installation. In the Maximo_HOME\scripts directory, run the following
2000
command: Windows
taskRunner.bat CONTINUE STOPONERROR
UNIX
Causes
Middleware installed on different computers, with multiple middleware installer workspaces contain
fragments of the middleware configuration information. When you run the base services installation, it
fails because it does not have the complete set of data.
63
Symptoms
During language pack installation, the installation fails to remove PortalLogTraceAnalyzer.war. The
following log files indicate this error. The Maximo_HOME directory is the default installation directory for
the base services. The default location of Maximo_HOME is:
v
Windows
2000
C:\Program Files\IBM\Common\acsi
UNIX
/usr/ibm/common/acsi
v
v Maximo_HOME\solutions\logs\LTA_WAR_Package\Lang_Pack_Remove_Portal_LTA_WAR.err
This file indicates that PortalLogTraceAnalyzer.war was not found. Example error:
v Maximo_HOME\solutions\logs\LTA_WAR_Package\Lang_Pack_Remove_Portal_LTA_War.out
This file indicates that PortalLogTraceAnalyzer.war was not removed. Example error:
Removing old WAR Install directory:
/usr/IBM/WebSphere/AppServer/systemApps/isclite.ear/PortalLogTraceAnalyzer.war
Checking for success of removal operation...
Failure: old WAR Install directory "/usr/IBM/WebSphere/AppServer/systemApps/
isclite.ear/PortalLogTraceAnalyzer.war" still exists.
ERRORLEVEL was 1 from command.
d. In the same directory, delete the directories for the corresponding .war deployment that failed.
e. Navigate further down to the /isclite.war/WEB-INF directory.
f. Open the components.xml file and remove the entries for your deployed WAR files. Remove
everything between <registry:component> and </registry:component>. Save and close. Example:
<registry:component contextRoot="cells\ctgCell01\applications
\isclite.ear\deployments\isclite\PortalLogTraceAnalyzer.war
\WEB-INF" id="com.ibm.ac.lta.web.ui.WebClientPortlet" version="4.2.2.1">
<registry:title>
<base:nls-ref key="javax.portlet.title"
64
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
locationName="classes/WebClient/nl/app_properties"/>
</registry:title>
<registry:about-page>
com.ibm.ac.lta.web.ui.layoutElement.D</registry:about-page>
<registry:portletApplication id="com.ibm.ac.lta.web.ui.WebClientPortlet"
name="PortalLogTraceAnalyzer.war"/>
</registry:component>
g. Open the navigation.xml file and remove the entries for your deployed WAR files. Remove
everything between <navigation:nav-element> and </navigation:nav-element>. Save and close.
Example:
<navigation:nav-element isWscNode="false"
layout-element-ref="com.ibm.ac.lta.web.ui.layoutElement.A"
moduleID="com.ibm.ac.lta.web.ui.WebClientPortlet" nodeType="page"
uniqueName="com.ibm.ac.lta.web.ui.WebClientPortlet-SPSVScom.ibm.ac.lta.web.ui.LogAnalyzer" wscRole="Maximo Administrator,
administrator">
<navigation:title>
<base:nls-ref key="javax.portlet.title"
locationName="classes/WebClient/nl/app_properties"/>
</navigation:title>
<navigation:parentTree ordinal="100"
parentTreeRef="com.ibm.isc.commontasks.node.problem.84a3d05711"/>
</navigation:nav-element>
h. Open the portletEntities.xml file and remove the entries for your deployed WAR files. Remove
everything between <portletentities:application-definition> and
</portletentities:application-definition>. Save and close. Example:
<portletentities:portlet-entity uniqueName=
"com.ibm.ac.lta.web.ui.About_Log_And_Trace_Analyzer.appElement.D">
<portletentities:title>
<base:nls-ref ey="about_lta"
locationName="classes/WebClient/nl/app_properties"/>
</portletentities:title>
<portletentities:access-control application-role="Maximo Administrator"
role-type="Privileged User"/>
<portletentities:access-control application-role="administrator"
role-type="Privileged User"/>
</portletentities:portlet-entity>
6. In the Maximo_HOME\bin directory, refresh the language packs by running the following command:
solutionInstaller.bat -action refreshLangs
pkgpath C:\ibm\SMP\pmp\base_services_7.1.1.3.zip license accept
wasuser <wasuser> -waspwd <waspwd> -wasrxauser <wasrxauser> -wasrxapwd <wasrxapwd>
65
Maximo business objects from the deployment engine gets out of sync
with the ones in the application server
The Maximo business objects that the deployment engine uses need to be in sync with the Maximo
business objects deployed in the application server. A desync can potentially break the production
deployment engine.
Symptoms
If you install a fix pack for a different base services product in a base services environment, then the fix
pack is only deployed on the application server. Because of this, the Maximo business objects that the
deployment engine is using might desync with the ones in the application server, causing errors.
Causes
The Maximo business objects that the deployment engine uses need to be in sync with the Maximo
business objects deployed in the application server. A desync can potentially break the production
deployment engine.
Symptoms
After the Change and Configuration Management Database (CCMDB) installation, the Manage Users and
Manage Groups in the ISC (Integrated Solutions Console) display the following error:
CWLAA6003: Could not display the portlet, the portlet may not be started.
Causes
this is due to the corrupted ISC after CCMDB installation
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
To
1.
2.
3.
Windows
2000
UNIX
Windows
2000
UNIX
Symptoms
Installation fails during the core components installation.
Windows
2000
Windows
2000
67
UNIX
2000
Linux
Windows
2000
2000
Linux
3. Log on to the database server as the database instance owner and restore the database:
DB2
a. Open the file TIO_HOME/config/dcm.xml to verify the database name and user name. The
name element contains an alias for the database name, and the username element contains
the user name.
b. Change the user to your DB2 instance owner. The default database owner is ctginst1. For
example:
su - ctginst1
e. If the command lists other applications, run the following command to disconnect them
db2 force applications all
g. Stop DB2:
v If the server does not have a virtual IP address: db2stop
v If the server has a virtual IP address: db2gcf -d -p 0 -i ctginst1
h. Stop all DB2 interprocess communications by running ipclean.
i. Start DB2:
v If the server does not have a virtual IP address: db2start
v If the server has a virtual IP address: db2gcf -u -p 0 -i ctginst1
j. Delete and uncatalog the existing database:
db2 drop db db_name
where
v db_name is the name of the database
v user_name is the user name of the user restoring the database
v password is the password of the user
v location is the full path location of the backup
Oracle
68
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
where
v user_name is the user ID that has sysdba privileges on the database
v password is the password for the specified user
v db_name is the database name
e. Run the following command to locate all the Oracle Database data files that are in use:
select name from v$datafile;
f. Ensure that the Oracle Database database instance and listener are offline.
g. Delete the .dbf files listed by the select command.
h. Delete the $ORACLE_HOME/dbs directory.
i. Change the current work directory to the backup directory that was created during the
backup.
j. Get the locations of the .dbf files from the text file that was created during the backup.
k. Copy the .dbf files locations listed in the text file.
l. Copy the entire dbs directory to $ORACLE_HOME.
m. Bring the database instance and listener back online.
4. Log on to the computer where WebSphere Application Server is installed and start WebSphere
Application Server:
Windows
2000
WAS_HOME\profiles\ctgDmgr01\bin\startManager.bat
WAS_HOME\profiles\ctgAppSrv01\bin\startNode.bat
WAS_HOME\profiles\ctgAppSrv01\bin\startServer.bat MXServer
UNIX
2000
Linux
WAS_HOME/profiles/ctgDmgr01/bin/startManager.sh
WAS_HOME/profiles/ctgAppSrv01/bin/startNode.sh
WAS_HOME/profiles/ctgAppSrv01/bin/startServer.sh MXServer
5.
Restart the core components installation. For more information, see Installing Tivoli Provisioning
Manager core components.
Symptoms
Tivoli Provisioning Manager core components installation failed. The /tmp/tclog_wrapper/tcinstall.log
log file contains one of the following error messages:
v Failed to configure the Agent Manager profile to run as tioadmin
v Failed to change the ownership of the Agent Manager profile
69
If you encounter an installation error when configuring WebSphere Application Server to run under the
user tioadmin, you need to perform some recovery steps to bring the computer back to a consistent state.
v If the log contains the error Failed to configure the Agent Manager profile to run as tioadmin:
1. Check the file cas_runastioadmin.log for a detailed error message, and then fix the problem.
2. Click Back to the Summary panel, then click Next to continue installation.
v If the log contains the error Failed to change the ownership of the Agent Manager profile:
1. Log on as root.
2. Run the following commands:
chown -R tioadmin:tioadmin <CAS_PROFILE_HOME>
chown -R tioadmin:tioadmin <WAS_HOME>/logs/manageprofiles/<PROFILE_NAME>
chown -R tioadmin:tioadmin <Agent Manager Install Location>
5. Click Back to the Summary panel, then click Next to continue installation.
v If the log contains the error Failed to configure the WebSphere Application Server Network
Deployment to run as tioadmin:
1. Check the wasND_runastioadmin.log log file for a detailed error message, and fix the problem.
2. Click Back to the Summary panel, then click Next to continue installation.
v If the log contains the error Failed to change the ownership of the WebSphere Application Server
Network Deployment:
1. Log on as root.
2. Run the following commands:
chown
chown
chown
chown
chown
chown
chown
chown
chown
-R
-R
-R
-R
-R
-R
-R
-R
-R
tioadmin:tioadmin
tioadmin:tioadmin
tioadmin:tioadmin
tioadmin:tioadmin
tioadmin:tioadmin
tioadmin:tioadmin
tioadmin:tioadmin
tioadmin:tioadmin
tioadmin:tioadmin
<APP_PROFILE_HOME>
<WAS_HOME>/logs/manageprofiles/<APP_PROFILE_NAME>
<DM_PROFILE_HOME>
<WAS_HOME>/logs/manageprofiles/<DM_PROFILE_NAME>
<WAS_HOME>/temp
<WAS_HOME>/properties/confhelp.properties
<WAS_HOME>/systemApps/isclite.ear
<CDS_INSTALL_LOCATION>
<DMS_INSTALL_LOCATION>
4. Click Back to the Summary panel, then click Next to continue installation.
Symptoms
You encounter an installation error with the Tivoli Monitoring agent installation.
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
Symptoms
During installation of the core components, one of the following errors occurs for the WebSphere
Application Server profile for the agent manager. The profile name is casprofile by default.
1. The installer checks the computer to verify that it can create the profile, and the validation fails.
2. The validation is successful, but the profile is not successfully created.
Causes
When the core components installer installs the agent manager, it automatically removes the WebSphere
Application Server profile for the agent manager if the agent manager installation fails. In some
situations, the automatic removal might not work and the profile must be removed manually before you
try to install the agent manager again.
Windows
2000
UNIX
Windows
2000
%TMP%\tclog_wrapper\create_wasprofile.log
UNIX
/tmp/tclog_wrapper/create_wasprofile.log
v
2. Fix the error described in the log.
71
3. Click Back in the core components installer to go to the panel before the installation preview.
4. Click Next. The installer verifies the requirements to create the profile again. If the validation
is successful, the installer tries to create the profile again. If the validation fails, perform the
steps described in the previous section for a failed validation.
Symptoms
The installation of the agent manager fails during the Tivoli Provisioning Manager installation.
Causes
Consult the agent manager logs to identify the cause of this problem. The agent manager log files are
located in the AM_HOME\logs directory. Possible causes might include:
v The port required for the agent manager installation might be busy.
v The agent manager has already been installed on your system.
72
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
To stop the agent manager server if the installation program created a Windows service, use the
Windows Services window or the Services folder in the Microsoft Management Console to stop the
service with the following name:
IBM WebSphere Application Server V6.1 - Tivoli Agent Manager
where app_server_name is the name of the application server where the agent manager is
installed. By default, this is AgentManager. The server name is case-sensitive.
When the agent manager server is stopped, the following message is generated:
ADMU4000I: Server app_server_name stop completed.
AIX
2000
Linux
Solaris
2000
When the agent manager server is stopped, the following message is generated:
ADMU4000I: Server app_server_name stop completed.
Windows
2000
AIX
2000
Linux
Solaris
2000
AM_HOME/bin/RunInDbEnv.sh RemoveCASTables.sh
database_password
Windows
2000
./RemoveCASTables.bat database_password
AIX
2000
Linux
Solaris
2000
./RemoveCASTables.sh database_password
73
Windows
2000
Use either the Add/Remove Programs window to uninstall the agent manager, or run the
following command from a command prompt:
AM_HOME\_uninst\uninstall.exe
AIX
2000
Linux
Solaris
2000
The program does not delete the registry database or files created in the agent manager installation
directory after installation.
4. If the agent manager application server is not named AgentManager, determine whether other Web
applications are using that application server. If no other applications are using that application
server, you can optionally delete the application server.
5. If you do not need the uninstallation logs, optionally delete the agent manager installation directory.
By default, this is the following directory:
v
Windows
2000
AIX
: C:\Program Files\IBM\AgentManager
2000
Linux
Solaris
2000
: /opt/IBM/AgentManager
2000
You might have to restart the system before you can delete the agent manager
Tip: Windows
installation directory.
6. If the registry is in a remote database, run the following command on the remote database server to
uninstall the agent manager from that system:
7. If you do not need the uninstallation logs on the remote database server, optionally delete the agent
manager installation directory. By default, this is the following directory:
v
Windows
2000
AIX
: C:\Program Files\IBM\AgentManager
2000
Linux
Solaris
2000
: /opt/IBM/AgentManager
2000
You might have to restart the system before you can delete the agent manager
Tip: Windows
installation directory.
8. If you will not be reinstalling the agent manager on this system, remove the definition of
TivoliAgentRecovery from your DNS servers.
Symptoms
The common agent and the agent manager cannot be installed.
Causes
74
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
Installing the common agent on the provisioning server, where the agent manager is also installed, is not
supported.
Symptoms
The installation of Tivoli Provisioning Manager installation fails if WebSphere Application Server was
uninstalled. The following message is displayed in the %TEMP%\tclog\tcinstall.log file
(/tmp/tclog/tcinstall.log in UNIX or Linux):
WebSphere Application
Server does not appear to be installed on the system.
ACTION: Install WebSphere Application
Server
Causes
If WebSphere Application Server was uninstalled but the WebSphere Application Server installation
directory was not removed, the Tivoli Provisioning Manager installer might identify WebSphere
Application Server as installed, and then fail during theTivoli Provisioning Manager installation.
Windows
2000
AIX
Solaris
2000
C:\Program Files\IBM\WebSphere\AppServer
/usr/IBM/WebSphere/AppServer
2000
Linux
/opt/IBM/WebSphere/AppServer
.
v Click Back in the installer until you reach the Configure the target servers panel. Click Next so that
the installer can check again for installed components. On the Validation Summary panel, the Found
column displays No if WebSphere Application Server is fully uninstalled. You can now continue with
the installation.
Symptoms
The device manager service installation or configuration failed, or the device manager service fails to
start.
Verify that all the device classes and job types are registered. Type the following
command:
UNIX
75
/opt/IBM/DeviceManager/bin/deviceclass.sh -list
2.
Windows
2000
C:\Program Files\ibm\DeviceManager
UNIX
2000
Linux
/opt/IBM/DeviceManager
2. Ensure that the dmsadmin user ID was successfully created on the database server.
Ensure that the password is not set to expire at the next login.
Verify that the passwords provided to the device manager database installation are correct by
connecting to DB2 with the user name and password specified. Run the following DB2
command;
Note: This command only works if the device manager database was created when the database
configuration was completed.
Ensure that the DB2 instance specified is correct. To list the valid DB2 instances, type db2ilist
from a DB2 command environment.
UNIX
/etc/services
Windows
2000
\Windows\system32\drivers\etc\services
v If there are problems starting device manager service, check the following items:
If you receive the message DYM2794E: Failed to create the database connection pool in the
WebSphere Application Server SystemOut.log file, ensure that DB2 is started and that the DB2 client
is configured correctly.
If you receive a message about no protocol found in the WebSphere Application Server
SystemOut.log file, verify the values for the proxy settings that are used to construct the Tivoli
Provisioning Manager for Job Management Service federator server URL (DMS_PROXY_PROTOCOL and
DMS_PROXY_HOSTNAME have not been changed. Restart the DMS_AppServer after making any changes to
the WebSphere environment variables.
If you receive an AccessControlException error that references a JDBC driver for the database, check
your security settings in WebSphere Application Server.
- If Global Security was enabled, which, Java 2 Security is enabled by default.
- If Java 2 Security is enabled, the device manager server servlet gets an AccessControlException
error when it starts. The servlet calls the JDBC driver to access a system resource for which it
does not have permission. To eliminate the AccessControlException message and start Tivoli
Provisioning Manager for Job Management Service federator, follow the steps for enabling
security as described in the WebSphere Application Server documentation.
76
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
Symptoms
During installation on AIX, installation of the management center fails. The installer exits with a Java core
dump that includes the following error message:
SIGSEGV received at 0xda6be0ec in /tmp/ismp002/libaixppk.so. Processing terminated
Causes
This error is a known problem for the InstallShield installer. It is caused by a problem with the native
library libaixppk.so, which is used by the AIX platform pack.
Symptoms
While the installer verifies prerequisites during Tivoli Provisioning Manager core components or Web
components installation, the following message appears:
The Installation Wizard is checking the system prerequisites.
After waiting a few minutes, the installer seems to hang and the Next button remains disabled.
Causes
There might be a problem with your Cygwin installation.
Symptoms
The following message appears in the installation panel:
WARNING: DB2 bind warning occurred during Tivoli Provisioning Manager
for OS Deployment installation. You must bind again after the installation.
For more information, see the Troubleshooting Guide.
Chapter 2. Installation and upgrade problems
77
Causes
If you have a DB2 client version 9.5 and a DB2 server version 9.1, the IBM Data Server Runtime Client
cannot be used to bind the database utilities and DB2 CLI bind files.
set DB2INSTANCE=DB_INSTANCE
AIX
2000
Linux
su - DB_INSTANCE
where DB_INSTANCE is the DB2 instance that was used to install Tivoli Provisioning Manager. The
default instance is ctginst1 for both Windows and UNIX.
2. To BIND, run the following commands:
db2
db2
db2
db2
db2
terminate
CONNECT TO TPMFOSD
BIND path\db2schema.bnd BLOCKING ALL GRANT PUBLIC SQLERROR CONTINUE
BIND path\@db2ubind.lst BLOCKING ALL GRANT PUBLIC ACTION ADD
BIND path\@db2cli.lst BLOCKING ALL GRANT PUBLIC ACTION ADD
where path is the full path name of the directory where the bind files are located, such as
INSTHOME\sqllib\bnd where INSTHOME represents the home directory of the DB2 instance. db2ubind.lst
and db2cli.lst contain lists of required bind files used by DB2 database products. Packages that are
already bound will return an SQL0719N error. This is expected.
3. Verify that the Tivoli Provisioning Manager for OS Deployment is running. For more information, see
Starting and stopping Tivoli Provisioning Manager components.
Symptoms
Tivoli Provisioning Manager fails with an error message that is similar to the following:
D:\Program is not recognized as an internal or external command,
operable program or batch file.
Causes
This error occurs when all of the following conditions are true:
v You chose a different installation directory from the default directory.
v The selected path contains a space, and the folder name with the space does not exist.
v Short name capability is disabled.
By default, Windows supports the ability to create short names for directories whose names contain more
than eight characters. These abbreviated names contain the first six characters of the original name and
then a two-character extension. For example, D:\Program Files can be abbreviated by the system as
78
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
D:\Progra~1. This capability must be enabled if you want to install Tivoli Provisioning Manager in a
directory other than the default directory, and if the directory name contains spaces.
Symptoms
The silent installation program for Tivoli Provisioning Manager exits before the installation is completed.
Causes
WebSphere Application Server was not started before the silent installation started.
Symptoms
The silent installation of core components for Tivoli Provisioning Manager exits before the installation is
completed. The tcinstall.log file contains the following error message:
[timestamp] ERROR DiskSpaceCheckWizardAction - Disk space check failed.
[partition]- [required space] MB of disk space is required, but only [free space] MB is available
Causes
There is insufficient free space on the partition mentioned.
79
Increase the amount of free space on the partition. If the required free space and available free space are
different by a margin of 1000 MB, run the following command to bypass the disk space checks:
-W DiskSpaceSeq.active="False"
Command example:
install/bin/setupSolarisSparc64.bin -options <response file path and name>
-silent -W WzdSeq_PreInstallCheck.active="false" -W DiskSpaceSeq.active="False"
Symptoms
During installation, the installation fails with the following error:
An error has occurred. See the log file
/var/tmp/TopologyInstaller/workspace/.metadata/.log
The log file also contains an error that begins with org.eclipse.swt.SWTError: Font not valid.
Causes
This error has been observed when accessing a remote computer with Reflection X. The error occurs if a
recognized font cannot be resolved at startup time.
Symptoms
The DNS suffix does not accept hyphens.
Causes
This issue applies to a custom installation. When you specify WebSphere Application Server settings on
the Tivoli Provisioning Manager configuration tab of the installer, you cannot use the hyphen (-) character
in the Domain Name Suffix field.
80
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
2. Open the response file in a text editor and modify the domain name suffix so that it includes the
hyphen character. Save your changes.
3. Perform a silent installation. See the appendix "Performing a silent installation" in the Tivoli
Provisioning Manager Installation Guide for instructions.
Symptoms
An error occurs when installing the dynamic content delivery component of Tivoli Provisioning Manager
on a UNIX server. A warning message similar to the following example is in the log file cdsisxtrace.log.
Warning: internal error parsing Java arguments. Launcher command may be
missing Java Arguments.
Causes
The response file for installing the dynamic content delivery management center might be corrupted.
Extra messages are displayed when the su - command is used to switch users, and might cause
corruption as a result.
The installer uses standard output to obtain the output of commands. If the profile is configured to
display extra messages when you switch to another user with the su - command, this extra text is
included in the command output that the installer receives. This causes the installation to fail.
Symptoms
Installation of the dynamic content delivery service fails. In the log file /opt/ibm/tivoli/ctgde/logs/
cds_upgrade.txt, the following error is displayed:
INSTALLER_PATH=/extra/ibm/tivoli/tio/CDS/scripts/./setup.binChecking the environment
variables specified in the JVM files to find the JVM...
Verifying... /bin/java -cp /tmp/istemp7613004171417/Verify.jarVerify java.vendor
java.versionVerification passed for / using the JVM file /tmp/istemp7613004171417/
relative_to_upgrade.jvm.
JavaHome is not resolved correctly in the jvm file /tmp/istemp7613004171417/
relative_to_upgrade.jvm.
Failed to launch the application.
Causes
81
The location of Java cannot be found by the installer. This error occurs when Java is installed in the
/bin/java directory, when /bin is the directory listed in the PATH variable.
If this command is not available on your system, run the following command instead:
type java
2. If the returned value is /bin/java, run the following command to display the contents of the PATH
variable:
echo $PATH
3. If the first part of the path is /bin, update the PATH variable so that /bin does not resolve the java
command. There are several options for making this change:
v Move /bin to the end of the list of paths in the PATH variable. Normally the java command will
resolve to /usr/bin/java.
v Create a symbolic link for /bin/java under another directory and add that path to the front of the
PATH variable. For example, if you have a link in /usr/bin to the java command, ensure that
/usr/bin is at the front of the PATH variable, or place /usr/bin before /bin in the list of paths.
Symptoms
When the device manager service attempts to communicate with the JDBC driver on an Oracle 10.2.0.4
server, a java.lang.ArrayIndexOutOfBoundsException error is generated.
Causes
This error is caused by a Java just-in-time compiler (JITC) optimization in the IBM JDK 1.4.2 provided
with Tivoli Provisioning Manager. To avoid the error, disable this optimization.
Symptoms
The Installation of core components fails with an error message indicating that the tioadmin user already
exists. However, /etc/passwd does not have any references to the tioadmin user.
Causes
82
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
If the tioadmin user is not mentioned in /etc/passwd, then the user account was not created locally on
the computer. The computer might have a GSA client installed and the GSA cell has a user account with
the name tioadmin.
Symptoms
The installation appears to proceed successfully, but when you check for the user tioadmin, it has not
been created.
Causes
On Linux, the tioadmin user creation fails if the tioadmin group already exists before you install. No
error appears, so the installer cannot detect that the user creation operation has failed. The system cannot
return to a previous stage of the installation.
Because the user tioadmin is not created, the server environment is unstable. Various elements of the
installation require tioadmin to exist. For example, because WebSphere Application Server is configured
to start with tioadmin, WebSphere Application Server cannot start.
Symptoms
After installing a core component, relaunching the installer to install the rest of the core components will
fail at the DMS configuration.
Causes
ISMP registry in the system cause this problem.
83
Symptoms
The following error message appears:
ERROR: Installation did not complete successfully.
View the log at \tclog_wrapper\tcinstall.log for more details.
Causes
There are multiple versions of Cygwin on the system registry which interfere with the dependency check.
2000
DB2
<backup_dir>/DB2Backup_AfterMBS
Oracle
2000
<backup_dir>/OracleBackup_AfterMBS
where <backup_dir> is the directory that you selected at the end of the base services installation.
3. Select Back followed by Next to try again.
Symptoms
The following message can appear in thesql.log file in the <Agent Manager Install Location>/logs/
datastore/ directory:
INFO: CTGEM0575I Running the command: CREATE USER CDB IDENTIFIED BY
CDB DEFAULT TABLESPACE users TEMPORARY TABLESPACE temp.
<TimeStamp> com.ibm.tivoli.cas.manager.datastore.utils.ddl
DDLFileExecutor execute
WARNING: CTGEM0576W The following SQL exception occured:
ORA-28003:password verification for the specified password failed
ORA-20004: Password must be at least 6 characters long.
Causes
An Oracle policy restricts user passwords to greater than 3 characters.
84
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
Symptoms
Installation failed during a default installation with the error message Failed to install IBM Tivoli
Provisioning Manager Web components.
b. Run the following command in the DB2 command window: set db2instance=ctginst1
c. Restart the database.
Server does not have a virtual IP
Run the following commands:
db2stop force
db2start
85
5. Restore the deployment engine registry. Run the following command at the command prompt:
call "C:\Program Files\ibm\Common\acsi\bin\de_restoredb.cmd" -bfile "C:\ibm\SMP\DE_BACKUPS\AfterActions<timestamp>"
6. Remove the deployed information center. Run the following command at the command prompt:
rmdir /S /Q "C:\Program Files\IBM\WebSphere\AppServer\systemApps\isclite.ear\tpm_olh.war"
7. Start WebSphere Application Server. Run each command that starts with call on a single line.
call "C:\Program Files\IBM\WebSphere\AppServer\profiles\ctgDmgr01\bin\startManager.bat"
call "C:\Program Files\IBM\WebSphere\AppServer\profiles\ctgAppSrv01\bin\startNode.bat"
8. Run the default installation again. You must use the same user name and password that you used to
run the default installation previously.
Symptoms
The Web components installation has failed with the error message Failed to install IBM Tivoli
Provisioning Manager Web components.
C:\ibm\SMP.
/opt/IBM/SMP
c. Restore the backup of the base services home directory to the removed base services folder. The
backup name is backup_folder/MBSBackupBeforeTPM.zip, where backup_folder is the location that
you specified in the launchpad after installing the base services.
UNIX
2000
Linux
3. Restore the deployment engine registry. Enter the following command on a single line:
Windows
2000
2000
Linux
where base_services_folder is the directory where the base services are installed.
86
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
4. Log on to the computer where WebSphere Application Server is installed as tioadmin and recover the
backup data:
a. Stop WebSphere Application Server Network Deployment.
Windows
2000
WAS_HOME\profiles\app_profile\bin\stopNode.bat
-user was_adminID -password was_admin_pwd
WAS_HOME\profiles\dm_profile\bin\stopManager.bat
-user was_adminID -password was_admin_pwd
UNIX
2000
Linux
WAS_HOME/profiles/app_profile/bin/stopNode.sh
-user was_adminID-password was_admin_pwd
WAS_HOME/profiles/dm_profile/bin/stopManager.sh
-user was_adminID -password was_admin_pwd
where,
app_profile
The WebSphere Application Server profile.
was_adminID
The WebSphere Application Server administrator ID. If you are using read-only LDAP
authentication, the default user ID is wasadmin.
was_admin_pwd
The password for the WebSphere Application Server administrator. If you are using read-only
LDAP authentication, enter the password for the wasadmin user.
dm_profile
The deployment manager profile.
b. Restore the deployment manager profile configuration. Enter the following command on a single
line:
Windows
2000
WAS_HOME\bin\restoreConfig.bat backup_folder\
WASBackup_afterTPMCore_ctgDmgr01.zip -logfile
backup_folder\restore_dmgr.log -user was_adminID
-password was_admin_pwd -profileName dm_profile
UNIX
2000
Linux
WAS_HOME/bin/restoreConfig.sh backup_folder/
WASBackup_afterTPMCore_ctgDmgr01.zip -logfile
backup_folder/restore_dmgr.log -user was_adminID
-password was_admin_pwd -profileName dm_profile
where backup_folder is the backup directory where the backup data is stored.
c. Restore the application server profile configuration. Enter the following command on a single line:
Windows
2000
WAS_HOME\bin\restoreConfig.bat backup_folder\
WASBackup_afterTPMCore_AppSrv01.zip -logfile
backup_folder\restore_appSrv01.log -user was_adminID
-password was_admin_pwd -profileName app_profile
UNIX
2000
Linux
WAS_HOME/bin/restoreConfig.sh backup_folder/
WASBackup_afterTPMCore_AppSrv01.zip -logfile
backup_folder/restore_appSrv01.log -user was_adminID
-password was_admin_pwd -profileName app_profile
Chapter 2. Installation and upgrade problems
87
5.
Remove the deployed information center if it exists using the Administrator user. To do this, delete
the file WAS_HOME/systemApps/isclite.ear/tpm_olh.war.
6.
2000
DB2
a.
Log on to the database server as the database instance owner and recover the database.
Windows
2000
set DB2INSTANCE=<db2instance>
db_adminID
The database instance owner that was used to install Tivoli Provisioning Manager.
db_admin_pwd
The password of the database instance owner that was specified during Tivoli Provisioning
Manager installation.
backup_files_location
The directory specified in the Backup Files Location field in the Directories for Core
Components panel.
Recover the Oracle database. For information, see your Oracle documentation. The location
of the backup is backup_files_location/OracleBackup_AfterTPMCore, where backup_files_location is the
directory specified in the Backup Files Location field in the Directories for Core Components panel.
8. Log on to the computer where WebSphere Application Server is installed and start WebSphere
Application Server.
7.
Oracle
2000
Windows
2000
WAS_HOME\profiles\dm_profile\bin\startManager.bat
WAS_HOME\profiles\app_profile\bin\startNode.bat
UNIX
2000
Linux
WAS_HOME/profiles/dm_profile/bin/startManager.sh
WAS_HOME/profiles/app_profile/bin/startNode.sh
Symptoms
An error is displayed, indicating that the node agent was not started during Web components installation.
Causes
This error can be created from a variety of causes. Check the following items:
1. Verify this that the node agent is started. Log on to the WebSphere Application Server console for the
node agent and see if the status is green. You can also run the startNode.bat command to check if the
node agent is started.
2. If the node agent is running, check the node agent logs for an error that indicates that the node agent
is not started. The following error is an example:
88
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
In this example, the start script cannot determine if the node agent is running because it cannot access
the server due to incorrect credentials. If you are able to log on to the WebSphere Application Server,
but you receive this error, the problem might be a mismatch between data that is stored in the
properties for the installation and the values you are providing.
89
Description
Location
Package log
<Maximo_HOME>\solutions\logs\
<PACKAGE_NAME>\
<Maximo_HOME>\logs\
CTGInstallMessageXX.log
<Maximo_HOME>\logs\
CTGInstallTraceXX.log
XX is a two digit number such as 00.
These logs contain the trace output of
the PSI subsystem.
Note: You might encounter messages
similar to the following in the
MAXIMO_DEPLOY_ERR.err file found in
the <Maximo_HOME>\solutions\logs
directory for a process manager once
it has been installed:
v sys-package-mgr: processing new
jar, C:\IBM\SMP\lib\icl.jar
v sys-package-mgr: processing new
jar, C:\IBM\SMP\lib\
CTGInstallCommon.jar
v sys-package-mgr: processing new
jar, C:\IBM\SMP\lib\
CTGInstallResources.jar
Although these messages appear in
an error log file, they are
informational only, and do not
represent deployment errors. These
messages can be safely ignored.
90
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
Description
Location
C:\Program Files\IBM\Common\acsi\
logs\<USERNAME>\de_msg.log
<WAS_HOME>\profiles\<PROFILE>\
logs\AboutThisProfile.txt
C:\Program Files\IBM\Common\acsi\
logs\<USERNAME>\de_trace.log
<WAS_HOME>\profiles\<PROFILE>\
logs\<SERVER_NAME>\startServer.log
<WAS_HOME>\profiles\<PROFILE>\
logs\<SERVER_NAME>\stopServer.log
<WAS_HOME>\profiles\<PROFILE>\
logs\<SERVER_NAME>\SystemErr.log
<WAS_HOME>\profiles\<PROFILE>\
logs\<SERVER_NAME>\SystemOut.log
For example, if your WebSphere
Application Server is installed in the
C:\IBM\WebSphere\AppServer\, your
profile name is AppSrv01, and your
server name is server1, your logs
would be in this location:
C:\IBM\WebSphere\AppServer\
profiles\AppSrv01\logs\
AboutThisProfile.txt
Maximo Logs
<Maximo_HOME>\maximo\tools\maximo\
log\updatedb<TIMESTAMP>.log
For example, if your Maximo install
location is C:\IBM\SMP\Maximo, and
that you executed ththe "UpdateDB
command on April 19th at
approximately 5:06:07PM, the logging
information would be written to
these files: C:\IBM\SMP\Maximo\tools\
maximo\log\
updatedb20070419170607.log
91
Description
Location
<Maximo_HOME>\wasclient\logs\
CTGIN_wsadmin.traceout
<Maximo_HOME>\wasclient\logs\
wsadmin.traceout
<Maximo_HOME>\wasclient\logs\
wsadmin.valout
For example, if your Tivoli
Provisioning Manager install location
is the C:\IBM\SMP directory, then the
following log files would contain the
Thin WAS Client tracing information:
C:\IBM\SMP\wasclient\logs\
CTGIN_wsadmin.traceout
C:\IBM\SMP\wasclient\logs\
wsadmin.traceout
C:\IBM\SMP\wasclient\logs\
wsadmin.valout
It is a good practice to rename existing logs before attempting a package install. It is useful to have a log
that consists only of the information related to the success or failure of current package installation to
facilitate problem determination.
Symptoms
While the installer verifies prerequisites during Tivoli Provisioning Manager core components or Web
components installation, the following message appears:
The Installation Wizard is checking the system prerequisites.
After waiting a few minutes, the installer seems to hang and the Next button remains disabled.
Causes
There might be a problem with your Cygwin installation.
Symptoms
92
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
Causes
Cygwin is not installed. Tivoli Provisioning Manager requires Cygwin, and required Cygwin settings are
configured during the installation process. Cygwin is not automatically installed during the Tivoli
Provisioning Manager silent install.
Symptoms
During the first discovery target server validation after installing Cygwin, an error message similar to the
following is displayed:
First discovery failed: /home/administrator does not exist
Causes
After Cygwin is installed, no /home/Administrator directory is created. When the first discovery does not
detect this directory, the error message is displayed.
Symptoms
The Cygwin installation fails.
Causes
The download site that you chose for the Cygwin install might be unavailable.
93
Symptoms
You receive an error message that refers to missing tools, such as Telnet or FTP.
Causes
If you installed Cygwin manually, you might be missing some of the required Cygwin installation
packages.
The command generates a report called versionReport.html, which identifies the installed version of
WebSphere Application Server and all installed maintenance packages.
v The version of the database server.
DB2
Oracle To check the version of Oracle Database, run the SQL command select * from v$version
v The version of Java. Change to the WAS_HOME directory and run:
Windows
2000
java -version
UNIX
2000
Linux
./java -version
Windows
2000
2000
Windows services that were active during the installation, for example, antivirus software.
v Windows
v If you are logged on to the computer locally. Running the installation using Remote Desktop is not
supported.
94
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
Procedure
1. If you performed a default installation, review information about the values used for the installation.
You might need this information to perform some recovery actions. You can also use these values if
want to reinstall the product using the custom installation option.
2. Middleware installation: See The middleware installer logs for information about the middleware
installation logs.
3. Discovery: The installer uses discovery software to identify software and hardware on your computer.
Table 10. Discovery logs
Type of information
Header
Installation of Inventory
discovery
Windows
2000
%TEMP%\cit\cit.log
UNIX
/tmp/cit/cit.log
Inventory discovery scan
log
Windows
2000
%TEMP%\CITTrace.log
UNIX
/tmp/cit/CITTrace.log
The results of discovery
Windows
2000
%TEMP%
UNIX
/tmp or /var/tmp
Results are stored in XML files with the fully qualified domain name in the file name.
For example if the fully qualified domain name is tpmserver.example.com, the file
names include:
cit_tpmserver.example.com_output.xml
tpmserver.example.com_hwoutput.xml
tpmserver.example.com_swoutput.xml
tpmserver.example.com_vpdoutput.xml
For some errors, for example, insufficient disk space, you can click Back in the installer to go to the
panel before the error occurred, resolve the problem by making more space available, and then click
Next to continue with the installation.
v
Windows
2000
%TIO_LOGS%\install
2000
Linux
AIX
$TIO_LOGS/install
v
4. Software installation: The following log files are created during the software installation:
Log file
Cygwin
95
Log file
Windows
%TIO_LOGS%\install
UNIX or Linux
$TIO_LOGS/install
Logs for the Tivoli Provisioning Manager core component installer are located in
TIO_LOGS/install_wrapper.
If these logs are not available, you can also check the following locations:
Windows
%TMP%\tclog and %TMP%\tclog_wrapper
UNIX or Linux
/tmp/tclog and /tmp/tclog_wrapper
WebSphere Application
Server
DB2
96
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
Log file
Agent Manager
Agent Manager
Windows
AgentManager\logs\AMReturnValues.log
AgentManager\logs\am_upgrade.log
UNIX or Linux
AgentManager/logs/AMReturnValues.log
AgentManager/logs/am_upgrade.log
where AgentManager is the Agent Manager installation directory.
Agent Manager certificate generation
wsadmin.traceout
Tivoli Provisioning
Manager for Job
Management Service
federator
97
Log file
Collect the log files from the computer where the base services are installed:
v Run the following command:
Windows
2000
MAXIMO_HOME\scripts\LogZipper.bat
UNIX
MAXIMO_HOME\scripts\LogZipper.sh
Windows
2000
AIX
2000
Linux
Collect the log files from the computer where WebSphere Application Server is
installed:
v Logs under the application server directory, for example, C:\IBM
\WebSphere\AppServer\profiles\ctgAppSrv01\logs
v Deployment manager logs in the deployment manager directory, for example,
C:\WebSphere\DeploymentManager\logs
Tivoli common directory
Windows
2000
UNIX
C:\Program Files\IBM\tivoli\common\COP\logs
2000
Linux
/usr/ibm/tivoli/common/COP/logs
5. Starting Tivoli Provisioning Manager. When you start Tivoli Provisioning Manager, the file
tio_start.log is created in the default location
v
Windows
2000
C:\Program Files\IBM\tivoli\common\COP\logs
UNIX
2000
Linux
/usr/ibm/tivoli/common/COP/logs
v
6. Uninstallation: When you uninstall Tivoli Provisioning Manager core components, the log files are
located in
Windows
2000
%TIO_LOGS%\uninstall
2000
Linux
AIX
$TIO_LOGS/uninstall
v
If the logs are not available in this location, check the following location:
98
Windows
2000
UNIX
%TMP%/tclog_uninstall
2000
Linux
/tmp/tclog_uninstall
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
Symptoms
You are getting errors when trying to access the web interface.
Causes
The Lightweight Directory Access Protocol (LDAP) server might be shut down.
If the LDAP server is running, a confirmation message is displayed. If the LDAP server is not running,
start the LDAP server by running the following command:
ibmdirctl -D user_name -w password start
Solution 2
Run the Tivoli Directory Server Web Administration tool to check the status of the LDAP server.
1. Make sure that the Tivoli Directory Server Web Administration tool is installed on the WAS server.
For information on how to install it, go to http://www.ibm.com/developerworks/tivoli/library/twebadmin/index.html.
2. In a Web browser, go to http://host_name:9080/IDSWebApp/IDSjsp/Login.jsp
3. Log in with the appropriate user name and password. The Tivoli Directory Server Web
Administration tool starts.
4. If you cannot log in, you need to start the LDAP server. On the LDAP server, from the
LDAP_Install_dir/appsrv/bin directory, run:
startServer [.sh|.bat] server1
5. In the Tivoli Directory Server Web Administration tool, in the navigation bar, click Server
administration. The status of the LDAP server is displayed.
6. If the server is not running, click Start or Restart to start the LDAP server.
Symptoms
99
After successfully installing Tivoli Provisioning Manager on a computer running a Turkish locale, you are
unable to log in.
Causes
Tivoli Provisioning Manager can be installed on a computer running any locale but the user will see
English if the locale is not one of the supported languages. Turkish is not one of the supported languages.
When the user logs in, the default Turkish locale does not recognize the English language.
Symptoms
You cannot change your password.
Causes
The password policy parameters are incorrect (such as minimum length, minimum number of alphabetic
characters, and other parameters), so the LDAP server cannot validate the password.
UNIX
Windows
2000
2000
Linux
: startServer.sh
: startServer.bat
100
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
Symptoms
If a session in Tivoli Provisioning Manager is left idle until it expires, any user is then able to access the
session without validating their credentials. Some pages might have exception messages because the user
is not validated.
Causes
This is a security issue. If users log on to Tivoli Provisioning Manager and leave the session idle for
longer than the HTTP Session timeout value configured in WebSphere Application Server, user
information is not invalidated and user credentials remain available until the configured LTPA token
timeout occurs.
: setupCmdLine.bat
v
UNIX
: . ./setupCmdLine.sh. Notice the space between the periods. The special form for this command
sources the command to make the setting active for all processes started from the command shell.
4. Start the update installer. Change to the WAS_HOME\updateinstaller directory and run the following
command:
v
101
Windows
2000
: update.bat
v
UNIX
: ./update.sh
5. In the installer, enter the installation location of WebSphere Application Server and select Install
maintenance package.
6. Enter the file name of the fix: pk25740.pak.
7. Install the maintenance package.
8. When the installation is complete, log on to the WebSphere Application Server administrative
console as tioadmin at the following URL: http://<hostname:port>/admin.
where hostname is the fully-qualified domain name of the Tivoli Provisioning Manager computer and
port is the WebSphere Application Server Admin host secure port that you defined during
installation. The default port number is 9044. For example:
https://tpmserver.example.com:9044/admin
11.
12.
13.
14.
Symptoms
If the user that started Tivoli Provisioning Manager logs off of Windows, all tasks that use the scalable
distribution infrastructure fail. All SOAP services are stopped.
Causes
On Windows, when the user that started Tivoli Provisioning Manager logs off, the SOAP services are
stopped and the scalable distribution infrastructure will not function. This will cause all related tasks to
fail. Tivoli Provisioning Manager will then attempt to run the tasks using the deployment engine as an
alternate method.
102
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
Symptoms
You add a new user using the WebSphere Administrative Console and then log on as that user shortly
after the user account is created. Logon is successful, but you cannot see the Start Center for the user.
Causes
The Start Center is created for users in the Maximo database. The following settings influence how often
user information is updated in the database:
v The WebSphere Application Server Virtual Member Manager synchronization interval.
v WebSphere Application Server search cache timeout. WebSphere Application Server uses the cache to
save data retrieved from the LDAP server to improve performance.
By default, synchronization occurs every 5 minutes and the cache timeout interval is 10 minutes. Because
the cache timeout is longer than the synchronization interval, new user information is not provided to the
Maximo database until the cache timeout expires.
Symptoms
Chapter 3. Logging on or logging off problems
103
After the installation of Tivoli Provisioning Manager , the Maximo Console shortcut from the Start menu
of the administrative workstation does not work.
Causes
The shortcut was created during bases services installation. During the core components installation, the
port is updated to the port provided by the user.
where host_name is the host name of the provisioning server, and port is the port specified by the user
during core components installation. The default value is 9443.
104
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
Symptoms
In the web interface, pop-up windows and dialog boxes might not display properly when they are
located above select boxes. The select boxes might cover the options that are displayed in the pop-up
window or dialog box. You cannot choose the options that appear in the pop-up window or dialog box
because they are covered by the select boxes.
Causes
This is a known limitation with Internet Explorer Version 6.0.
Symptoms
The left hand navigation in the user interface of a Traditional Chinese installation of Tivoli Provisioning
Manager is missing.
Causes
JavaScript is not enabled in your Web browser.
105
1.
2.
3.
4.
5.
Symptoms
The performance of the web interface is slow.
Causes
There is a high volume of traffic in the web interface.
fully_qualified_domain_name
The fully-qualified domain name of the Tivoli Provisioning Manager server.
port
106
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
Errors when using the web interface while a local firewall is enabled
Some desktop firewall applications that are running locally on the client computer might conflict with the
Tivoli Provisioning Manager web interface.
Symptoms
When you try to do administrative tasks from the Tivoli Provisioning Manager web interface while
firewall applications are running on the client computers, certain features of the desktop firewall might
interfere with the user interface functions and cause errors.
Causes
Some desktop firewall applications that are running locally on the client computer, such as Zone Labs
Integrity Client, can remove the HTTP Referer field from the header of the HTTP request. In Zone Labs
Integrity Client, this feature is enabled using the Remove private header information setting.
When enabled, this setting automatically replaces the value of the HTTP Referer field with the XXXXXXX
string. As a result, a number of functions in the Tivoli Provisioning Manager web interface will not work.
The error messages that are displayed are not descriptive.
Symptoms
On a Solaris computer, the web interface does not load. The following error is generated:
The system is out of resources.
Consult the following stack trace for details.
java.lang.OutOfMemoryError
at java.util.zip.ZipFile.open(Native Method)
at java.util.zip.ZipFile.<init>(ZipFile.java:111)
at java.util.zip.ZipFile.<init>(ZipFile.java:71)
at com.sun.tools.javac.v8.code.ClassReader.openArchive(ClassReader.java:972)
at com.sun.tools.javac.v8.code.ClassReader.list(ClassReader.java:1218)
at com.sun.tools.javac.v8.code.ClassReader.listAll(ClassReader.java:1339)
Chapter 4. Web interface problems
107
at
at
at
at
at
at
at
at
at
at
at
at
com.sun.tools.javac.v8.code.ClassReader.fillIn(ClassReader.java:1361)
com.sun.tools.javac.v8.code.ClassReader.complete(ClassReader.java:1052)
com.sun.tools.javac.v8.code.Symbol.complete(Symbol.java:372)
com.sun.tools.javac.v8.comp.Enter.visitTopLevel(Enter.java:467)
com.sun.tools.javac.v8.tree.Tree$TopLevel.accept(Tree.java:390)
com.sun.tools.javac.v8.comp.Enter.classEnter(Enter.java:442)
com.sun.tools.javac.v8.comp.Enter.classEnter(Enter.java:456)
com.sun.tools.javac.v8.comp.Enter.complete(Enter.java:596)
com.sun.tools.javac.v8.comp.Enter.main(Enter.java:582)
com.sun.tools.javac.v8.JavaCompiler.compile(JavaCompiler.java:331)
com.sun.tools.javac.v8.Main.compile(Main.java:569)
com.sun.tools.javac.Main.compile(Main.java:47)
Causes
This issue is caused by a Java problem on Solaris.
4. Restart the provisioning server using the instructions in the Starting the provisioning server (UNIX or
Linux) topic.
Symptoms
An exception error occurs preventing the user from viewing the affected part of the user interface.
Causes
This error occurs because the amount of detail in the database tables is too large.
108
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
Symptoms
The WebSphere Application Server web interface has slow response time.
Causes
Your computer is experiencing a high volume of traffic.
109
110
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
Symptoms
When you run a VMMSYNC cron task, the information from LDAP does not get synchronized into the
Tivoli Provisioning Manager system. No records created in LDAP can be seen in the user interface.
Causes
There are several possible causes for this:
v incorrect LDAP setup
v incorrect user credentials
v administrative mode is turned on for database configuration
Symptoms
When you request the VMMSYNC cron task to run, the task does not work.
Causes
The LDAP distinguished names in the GroupMapping and UserMapping parameters contain quotation
marks (" ").
111
Remove the quotation marks from the GroupMapping and UserMapping parameters.
1. Navigate to Go To > System Configuration > Platform Configuration > Cron Task Setup.
2. In the list, find the VMMSYNC cron task.
3. Click on the VMMSYNC cron task.
4. Click the Parameters tab and expand the GroupMapping parameter.
5. In the Value field, find the LDAP information within the <basedn> tags and remove any quotation
marks around the distinguished names.
6. Expand the UserMapping parameter and remove any quotation marks around the LDAP
distinguished names within the <basedn> tags.
7. Click Save.
8. Restart the provisioning server.
Symptoms
A Tivoli Provisioning Manager user other than MAXADMIN has update permissions to provisioning groups
applications, and can change provisioning groups created for the purpose of security.
Causes
The security groups that are created on the basis of provisioning groups have no security constraints set
up.
Restrict the user access to the newly created group by creating appropriate conditions for the group:
1. Click Go To > Administrator > Conditional Expression Manager.
2. Add a new condition by clicking the New Row button.
3. Define the name for the condition by choosing the EXPRESSION as its Type, and then type in the
following Expression:
(EXISTS (select 1 from group_membership gm, tpgroup g where g.name =
new_group_name AND g.id=gm.group_id and
is_nested_group=Y and gm.dcm_object_id=:id))
OR (:name = new_group_name)
where new_group_name is the name of the group defined in the step above.
112
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
Create a data restriction with the new condition Once the condition is created for the group, add a
READONLY data restriction to it with the following actions:
1. Click Go To > Security > Security Groups .
2. Select the security groups that you created.
3. Click the Data Restrictions tab, and then select New Row to create a data restriction.
4. Define Object as TPGROUP, and Type as READONLY.
5. Choose Select Value from the Detail Menu drop down list.
6. Select the newly selected condition name.
7. Save the settings by clicking
You have now set a data restriction that will restrict the access to security groups you want to protect.
Symptoms
The message BMXAA0024E - ADD is not allowed on WOACTIVITY is displayed when a user attempts add a
task to a plan in a work order using the Work Order Tracking application.
Causes
A default site is not configured for the user.
Symptoms
Some records are listed twice when looking at provisioning applications in the Security Groups
application.
Causes
Applications have the same labels for different sign options (option names) when displayed in the
Security Groups > Applications tab. These are valid distinct function options. For example, one might be
used in a menu and the other in a button.
113
You can modify this by enabling or disabling the options for a particular security group. This change is
typically done in pairs.
Symptoms
If you include special characters like comma (,), equals (=), plus (+), less than (<), greater than (>),
number sign (#), semicolon (;), backslash (\), and quotation marks () in the user name or role name, the
following error occurs:
COPCOM132E An error occurred during the LDAP operation: cn=#dffded:
[LDAP: error code 34 - Invalid DN syntax].
Causes
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 in the Tivoli Software Information Center.
Symptoms
When a session times out, the user is not logged off if basic authentication is being used.
Causes
The user is not automatically logged off when using basic authentication. If you click Refresh or press F5
after getting the timeout message, you will be taken back to the console without a password prompt.
Symptoms
When you add a new access group in a one-node Microsoft Active Directory (MSAD) setup, the group is
not displayed immediately.
114
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
Causes
It can take up to one minute to refresh the page because the refresh interval for the MSAD server is one
minute.
Symptoms
When you access Tivoli Provisioning Manager using secure socket layer (SSL), not all content is SSL
enabled. After you submit the user name and password, you receive a warning message asking if content
that is not encrypted with SSL during the initial login can be displayed.
Causes
The Web browser that you used to access Tivoli Provisioning Manager is outdated (for example, Internet
Explorer 6). Use a new version of the Web browser to avoid the security warnings.
Symptoms
Errors occur when you try to change the user password in the provisioning Web interface.
Causes
Changing the user password in the Web interface is not supported.
115
<install_path>\idstools\bin\startWebadminApp.bat
UNIX
<install_path>/idstools/bin/startWebadminApp
where install_path is the directory where you installed Tivoli Directory Server. For detailed
instructions, see the topic called Starting the Web application server to use the Web Administration
Tool: http://publib.boulder.ibm.com/infocenter/tivihelp/v2r1/index.jsp?topic=/com.ibm.IBMDS.doc/
install18.htm.
2. Users can launch the tool using the following Web address:
http://<hostname>:12100/IDSWebApp/IDSjsp/Login.jsp
The LDAP administrator can update the permissions by running the following command:
ldapmodify -D <adminDN> -w <AdminPwd> -i <modifyACL.ldif>
For example:
ldapmodify -D cn=root -w password -i modifyACL.ldif
where the modifyACL.ldif file contains the following information, for example:
dn: cn=tioappadmin,dc=ibm,dc=com
changetype: modify
add: aclentry
aclentry: access-id:cn=this:at.userpassword:rwsc
Symptoms
When importing a key or certificate in to a keystore or truststore, the following error may be shown:
Java.io.IOException: Error in loading the keystore: Private key decryption error:
(java.security.InvalidKeyException: Illegal key size)
Causes
116
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
The error is caused by the restricted policy on the JCE that is installed by default.
Symptoms
After updating the maximo.properties, when starting the TPM, an error similar to the following can be
seen in the SystemOut.log.
javax.crypto.BadPaddingException
Causes
The problem is caused by the editor that is being used for updating the maximo.properties. The editor
adds an extra character into the encrypted password section.
117
GSKit key manager does not recognize CMS key database type
When configuring DB2 for SSL communication, the GSKit key manager does not recognize the CMS key
database type. Because of this, you cannot generate a new keystore file.
Symptoms
The GSKit key manager does not recognize the CMS key database type. You receive an error message
stating that the CMS Java native library is not found.
Causes
This problem might occur if you have an older JDBC version that was installed with DB2 v 9.5 FP3a.
Symptoms
You cannot delete users from Tivoli Provisioning Manager using the Maximo user interface. You receive
the following error message when you try to delete users:
DMXAA0026E - The method cannot be called because application server security is enabled.
Environment
You are using LDAP to manage the user repository.
6.
7.
8.
9.
118
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
Procedure
Check the contents of the following directories:
v On the Tivoli Provisioning Manager server:
TIO_LOGS\console.log
$TIO_HOME/tmp/cit_subagent/platform/target_id_timestamp
Note: By default this directory is deleted. You should set a property to keep it.
v On the computer on which the common agent is not installed:
/tmp/cit_discoveryId
Symptoms
When running Initial Discovery, very limited information about the discovered computers is returned if
no user credentials are provided.
Causes
User credentials are needed to access full information about the discovered computers.
Symptoms
119
After running a Rembo Hardware Discovery against a target computer, the value for cpu.type is not
correctly inserted into the data model.
Causes
The discovery cannot always determine whether the target computer has a 32-bit or 64-bit processor. The
discovery populates a 32-bit value in the data model by default, but with this value it is not possible to
install a 64-bit operating system image on the target computer.
Symptoms
Microsoft Active Directory discovery only displays the short names of the discovered computers, and not
their fully qualified host names.
Causes
Microsoft Active Directory discovery only detects the information which was defined in the Microsoft
Active Directory registry.
Symptoms
No hardware information is returned after running a Microsoft Active Directory discovery against a
computer.
Causes
A Microsoft Active Directory discovery only detects the information which was defined in the Microsoft
Active Directory registry.
120
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
Symptoms
An inventory scan on a computer discovered by Microsoft Active Directory discovery fails if the
computer does not have Tivoli Common Agent installed.
Causes
The operation fails because the service access point is not defined for this computer.
Symptoms
The discovery of a first machine is completed successfully. The discovery of a second machine on the
same hostplaform is completed with a message stating that the machine exists in the data model. All data
from the previous discovery is overwritten by the second one.
Causes
The operation fails because the virtual computers on the same hostplatform have the same MAC address.
121
CCW_CHAN_NUM="3"
CCW_CHAN_MODE="GBEOSA"
QETH_LAYER2_SUPPORT="1"
QETH_OPTIONS="fake_ll=1"
To change the MAC address on Red Hat on zSeries Systems, perform the following steps:
1. Create the configuration file in /etc/sysconfig/network-scripts/ifcfg-eth0:
DEVICE=eth0
BOOTPROTO=static
IPADDR=9.26.177.39
NETMASK=255.255.255.0
NETTYPE=qeth
ONBOOT=yes
PORTNAME=GBEOSA
SUBCHANNELS=0.0.7874,0.0.7875,0.0.7876
MACADDR=00:01:02:03:DC:08
OPTIONS="layer2=1"
122
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
Symptoms
Tivoli Common Agent cannot be installed on a computer using Microsoft Active Directory.
Causes
This operation fails because the service access point is not defined for the target computer.
Symptoms
When running a Microsoft Updates discovery on UNIX target computers using Tivoli Provisioning
Manager, the operation fails.
5. Install the cabextract utility on the UNIX target computers you want to discover using the Microsoft
Updates discovery:
a. Download cabextract-1.2.tar.gz from the http://www.cabextract.org.uk/ Web site.
b. Perform the following actions to install the cabextract utility:
1) Navigate to the directory where you downloaded the rpm cabextract utility.
2) Run the following command to install the cabextract rpm package:
rpm -ivh RPM_NAME
123
6. Install the cabextract utility on the AIX target computers you want to discover using the Microsoft
Updates discovery:
a. Download cabextract-1.2.tar.gz from the http://www.cabextract.org.uk/ Web site.
b. Run the following commands to install the cabextract utility:
v $ gzip -cd < cabextract-1.2.tar.gz | tar xf v $ cd cabextract-1.2
v $ ./configure
v $ make
v $ make install
Symptoms
The inventory discovery does not detect the correct locale of Linux computers if Tivoli Common Agent is
not installed on them.
Causes
The computer locale is not discovered correctly because the computer locale variables in the
etc/environment file are not set.
Symptoms
When running a discovery, some deadlock issues arise.
Causes
The AM.Discovery.Thread.Count variable specifies how many threads to use when processing discovery
data that is returned from the agent manager during an agent manager discovery run. If no value is
specified, then the default value is used, which is 8.
124
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
As a workaround for deadlock situations during a discovery run, the value of the
AM.Discovery.Thread.Count variable can be set to 1, which means that only one thread is processing the
data.
Symptoms
After discovering a computer with network discovery and then installing the common agent on it,
another data model record is created for that computer but it displays a different computer name.
Causes
If the host names specified for the target computer in the DNS and on the operating system do not
match, then the network discovery creates two separate data model records are created for the same
target computer.
Symptoms
Windows Vista target computers cannot be discovered using the discovery wizard provided to perform a
network RXA-based discovery.
125
c. Disable the user account control if you administer a workstation with a local user account
(Security Account Manager user account). Otherwise, you will not connect as a full administrator
and will not be able to perform administrative tasks. To disable the user account control perform
the following steps:
1) Click Start > Run.
2) Type regedit, and press Enter.
3) Locate and click the following registry subkey:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System
4) Right-click LocalAccountTokenFilterPolicy, and click Modify. If the
LocalAccountTokenFilterPolicy registry entry does not exist, follow these steps:
a) From the Edit menu, click New, and then click DWORD Value.
b) Type LocalAccountTokenFilterPolicy, and then press Enter.
5) In Value enter 1 , and click OK.
6) Restart the computer.
2. The target computers must have the Remote Registry service started, which represents the default
configuration, in order for Remote Execution and Access (RXA) to connect to the target computer.
Verify the service status clicking Administrative Tools > Services and start the Remote Registry
service if needed.
Symptoms
After running the network RXA-based discovery, the discovery might fail and the workflow log might
display an error message similar to the following:
CTGRI0001E The application could not establish a connection to
2002:091A:0519:11F5:020D:60FF:FED4:F416.
Causes
If the IPv6 addresses of the computers have been used in the discovery configuration, the Windows 2003
Server Enterprise SP2 target computers cannot be reached when doing a network RXA-based discovery.
c. On the Edit menu, click Add Value, and then add the following registry value:
DWORD key IPv6Protection
Add with hex value 00000014 (0x00000014).
126
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
e. On the Edit menu, click Add Value, and then add the following registry value:
Value name: DisableStrictNameChecking
Data type: REG_DWORD
Radix: Decimal
Value: 1
Symptoms
After running the RXA-based network discovery against a Windows XP 32-bit computer with only the
IPv6 protocol enabled, the computer cannot be discovered.
Causes
The RXA-based discovery uses the Microsoft SMB protocol to communicate with a managed computer.
On Windows XP 32-bit computers, SMB only supports IPv4 communication and IPv6 addresses are not
supported. This is a known Microsoft limitation.
Causes
The HMC discovery can detect all the details for the virtual servers having the same name, but these
virtual servers are not added to the data model due to limitations in the data model integrator.
127
Wrong version displayed for Web logic 10.X computer discovered from
TADDM
Symptoms
When discovering from TADDM a computer with Web logic version 10.0 installed, on the Software tab of
the discovered computer the Web logic version displayed is 10.3, even if the actual version is 10.0.
Causes
This error is due to the discovered computer which might be created. During the creation of the
computer, a security check is performed to verify if the user has access to the new computer. If the user
has no access, the exception is thrown.
128
After it is added, the user will have write access to the computer to be created. Run the discovery
logged on as the user with the write access.
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
129
Limitations
limitations
v For Windows golden master image, because of Sysprep limitations, it is not possible to change the
administrator password during the deployment if the system profile contains a non-empty
administrator password. This limitation only applies if you run Sysprep yourself manually.
130
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
v Check the deployment server. The provisioning server logs unrecoverable errors messages into event
manager.
v If the service does not start, run rembo.exe from the command-line with the following options: rembo
-d -v 4. This will run the provisioning server as a console application, with all debugging output
redirected to your command window. You can increase the debug level (the -v parameter) to 6 for
maximum detail. See OS deployment server command-line options for more on command line
arguments. If the error message is related to your network configuration, try to fix your network
configuration and run the server again. In particular, you must change the Interfaces global
parameter if your computer has more than one network interface.
If it still does not work, contact your IBM Software Support representative.
rembokey ]
v -d prints debug info to the standard output, does not run as daemon (do not detach)
v -v sets the verbosity level (default: 2)
v -c specifies the config file name (the default is rembo.conf)
The verbosity levels are defined as:
v
v
v
v
v
0
1
2
3
4
:
:
:
:
:
no output
log error messages only
log error and warning messages
log error, warning and info messages
same as 3, but also log notice messages
131
If all of these steps fail, try to obtain a flash memory upgrade from your network card vendor, and flash
the network card rom with the newest upgrade. If the flash process fails, there is a chance that no
bootrom is installed on your network card.
If you are still not seeing the PXE messages, ask for support from your network card manufacturer.
Alternatively, you can create a network boot media to enable your target to connect to your OS
deployment server.
132
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
v
v
v
v
All the files from the logs directory of the OS deployment server
The OS configuration information for your DHCP server
The OS configuration information for your OS deployment server
A memory dump of the network traffic between the servers and the remote-boot target (use the MS
Network Monitor on Windows NT/2000)
133
134
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
Symptoms
Under Windows, the OS deployment server stops responding without any apparent cause.
Causes
This might be due to the limited number of port and sockets available by default on Windows operating
systems. Use of the Java API might cause to reach this limit.
Symptoms
The size of the swap partition on a Linux operating system after unattended deployment is larger than
the size set in the unattended system profile.
Causes
The unattended installation uses the swap partition and requires a larger space than set on the system
profile details.
135
Symptoms
Underscores _ appear on the screen of the target instead of the expected name which displays correctly
on the OS deployment server.
Causes
The correct fonts are not loaded to the target because the language of the OS deployment server does not
use these fonts. The problematic characters are shown as underscores _.
Causes
Rerunning of image capture tasks is not supported.
Symptoms
Deployment or redeployment fails during network transfers on some targets with either one of the
following Broadcom chips:
v BCM5700
v BCM5701
v BCM5702
v BCM5703
v BCM5704
These Broadcom chips can be potentially included in the following IBM servers, among other IBM and
non-IBM servers:
v HS20
v LS20
v x335
v x355
136
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
v x3655
Causes
This is a firmware defect which cannot be fixed in Tivoli Provisioning Manager for OS Deployment.
9.0.x
9.0.13 or above
10.0.x
10.4.10 or above
10.4.x
10.4.10 or above
11.0.x
11.4.0 or above
Contact your hardware support to obtain a new firmware version with the required PXE level.
Causes
The origin of the problem seems to reside in the version of the firmware and in the operating system
which was previously deployed on the target.
Symptoms
137
You are deploying a SuSE Linux Enterprise Server system profile on a PowerPC target with more than
one network card. The deployment starts, searches for a DHCP address for its first network card and
does not find it. The message Sending DHCP request for <firstnetworkcard> is displayed, where
<firstnetworkcard> is the name of the first network card of the target. The target switches to interactive
installation.
Causes
You have registered you target with a network card which is not the first.
Symptoms
The Web interface extension is correctly installed and is running, but it is not detected by the OS
deployment server. A red icon for the Web interface extension is displayed.
Causes
The OS deployment server is not listening to the correct interface and cannot therefore detect the Web
interface extension.
Symptoms
138
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
When deploying a SLES 10 on PowerPC, the deployment starts correctly. The YAST installer installs files
on the target and correctly restarts the target to continue the installation process with target
configuration. However, when the target restarts once more, the installation process stops because a
firmware exception is caught. The target hangs.
When using the same media to install the target manually, the installation proceeds smoothly.
Causes
This seems to happen only on old firmware.
Symptoms
You receive the error message: COPCOM730E: The target computer does not satisfy the requirements for
the configuration template.
Causes
If you are working on Windows and your target system does not expose the cpu.type property under
hardware resources, you will receive this error message.
139
Symptoms
When installing an image using Tivoli Provisioning Manager for OS Deployment on a computer that
supports Wake on LAN, Tivoli Provisioning Manager supports powering on the computer using Wake on
LAN. Wake on LAN does not work on some Red Hat Linux and SLES systems after the computer was
shut down normally.
Environment
Tivoli Provisioning Manager for OS Deployment can be installed on the following platforms that might
be affected by this limitation:
v Red Hat Enterprise Linux (RHEL): version 4 (i386)
v SuSE Linux Enterprise Server (SLES), version 9 and version 10 (i386)
140
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
To enable Wake on LAN, run the following command for each port that supports Wake on LAN before
shutting down the Linux computer:
ethtool -s <target_port> wol g
Symptoms
When images of UNIX, Linux, and Solaris operating systems are captured on computers displaying
double-byte characters (DBCS), they are installed as English to a target computer. For example, an image
of a Japanese Red Hat operating system is installed as English.
141
142
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
Causes
The depot server is inactive and the download plan must include a peer from the zone. The dual stack
computer is registered in the dynamic content delivery administration console with IPv6 address format.
The dynamic content delivery administration console only records the IPv6 address format of the dual
stack computer, and this information is used in the download plan for the IPv4 computer. The IPv4
endpoint is not able to download the file from the peer even though the peer has a dual stack
configuration. The dynamic content delivery administration console continues to prepare the download
plans until the dynamic content delivery timeout occurs (the dynamic content delivery default timeout
value is set to approximately 2 hours). Because the IPv4 endpoint is not able to download the file, the
task fails.
File distribution times out if the device manager service timeout is set
to one hour
Symptoms
The file distribution times out if the device manager service timeout value is set to one hour.
Causes
The depot server is inactive. The target computer is not able to connect to the peers which contain the file
to be downloaded. Therefore, the file download does not take place and the task times out.
143
v From the provisioning global settings, change the value for the variable DMS.Job.Interval.In.hours to 2
hours or more.
v Restart the depot server and then restart the Tivoli Common Agent services.
v Distribute the file to an IPv4 computer or to a dual stack computer registered with an IPv4 address in
the Dynamic Content Delivery management center.
To check the endpoint IP address registered on the Dynamic Content Delivery management center, follow
the next steps:
1. Open the Dynamic Content Delivery properties file:
v
AIX
Solaris
2000
HPUX
/usr/tivoli/ep/runtime/agent/subagents/cdsclient.properties
Red Hat
SUSE
/opt/tivoli/ep/runtime/agent/subagents/cdsclient.properties
2000
C:\Program Files\tivoli\ep\runtime\agent\subagents\cdsclient.properties
v Windows
2. In the properties file, ensure that the key value pair of user_ip is IPv4 address. If you change the file
key value pair, then you must also change the value initial_login_done=true to false.
Symptoms
If you manually do a distribution of a software package before you install it, the software package
redistributes automatically during installation, overwriting the first distribution in the process and
making it unnecessary.
Causes
Software packages (but not software package blocks) are distributed and installed at the same time by
default. They normally do not do the two tasks separately. When you manually do a distribution first
before installing a software package, a second software package is created even though the files have not
changed since the first packaging. Because this second software package was created with a different
MD5 hash, the result is that the whole software package gets redistributed, overwriting the first
distribution in the process.
144
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
Symptoms
Distribution of software products that do not have the SoftwareInstallable.Distribute logical
management operation implemented on target computers that are not SDI enabled fails with the
following error if the target computers were filtered using the By Group option:
COPDEX137E: There is no workflow that implements the VALUE_0 logical operation
associated with device VALUE_1.
Causes
The following factors contribute to this failure:
v The software products that have been selected for distribution do not have the
SoftwareInstallable.Distribute logical management operation implemented.
v The computers targeted for distribution are not SDI enabled, which means that they have do not have
an SDI-SAP defined.
v The target computer filtering was done using the By Group option.
Symptoms
After successfully migrating the server, the File Publish operation does not work. One or more error
messages similar to the following messages might be displayed:
COPDEX040E An unexpected deployment engine exception occurred:
COPINF002E Failed to publish file: /opt/IBM/tivoli/tpm/repository/TCA_upgrade_SPB/spb/TCA_upgrade_AIX.spb
with id 46210 to CDS depot servers.
CTGDEC029E The file, TCA_upgrade_AIX.spb, could not be uploaded successfully to any of the depot servers
chosen by the management center.
CTGDEC035E The upload proxy certificate was denied by the depot server.
The file, downloadGridtmp15101073668464212321247841674319, could not be uploaded to server:
tpmserver32.in.ibm.com:2100.
145
Causes
This problem is due to the time difference between the depot and the server.
Symptoms
You upgrade the Provisioning Manager server from version 7.1 to version 7.1.1. You also upgrade the
depot from version 1.4.1.0 to version 1.4.2.0. You then try to install a software package on a 7.1 UNIX or
Linux target computer and the installation apparently completes correctly. However, the software package
is not present on the target computer.
Causes
This problem is due to an internal defect in the subagent code which is resolved in Provisioning
Manager, version 7.1.1.
Causes
This is a known issue with the 7.1 software package block handler.
146
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
Symptoms
When you try publish a file after re-creating the depot, a series of messages like the following messages
is returned:
COPDEX040E An unexpected deployment engine exception occurred:
COPINF002E Failed to publish file:
C:/Program Files/IBM/tivoli/tpm/repository/testtextfile5.txt with ID
16444 to CDS depot servers.
CTGDEC030E The management center was unable to find potential depot servers to upload the file.
The file, testtextfile5.txt, could not be uploaded. Make sure that there is at least one
active depot server available,
that it has enough space to store the file, and that it is not in
an unreachable or restricted zone.
Causes
If you delete a depot without uninstalling the depot stack, then re-create the depot, the correct server
version and disk space information are missing in the management center administrative console
Symptoms
When a file distribution task is canceled, agents that have already started processing the job will continue
processing it. Results for the additional jobs that are in progress to finish the (now canceled) job are
communicated back to the provisioning server.
Causes
When a task is canceled, its job is canceled only on the provisioning server. This does not stop any agent
that has already begun processing the job.
Symptoms
Chapter 8. Software distribution problems
147
When you are distributing or installing software products, database lock time-outs occur and the task
status is not updated.
Causes
Database lock time-outs might occur when submitting a software product distribution or installation task
with over 10000 targets.
Symptoms
When you manually associate a discovered software resource on a computer with a software definition,
you can only select a software product, patch, or operating system software definition.
The following scenario is described:
v You manually associated a discovered software resource on a computer with a software stack
definition.
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.
Causes
You can only associate a discovered software resource with a software product, patch, or operating
system software definition. Associations with a software stack or distributed application are not
supported.
148
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
Symptoms
You cannot import a software signature when using Linux on IBM System z.
Causes
An out of memory exception occurs because the 1024MB that is required for the task to run is too large
for the Java virtual memory (JVM).
Symptoms
Running a query using the JDBC type 2 driver to pull all Windows software signatures might cause the
computer to run out of memory.
This entry ensures that the command line interface frees a LOB locator when the next LOB is to be
fetched.
149
tm != null
2008-06-20 09:28:01,058 DEBUG [Status Updater] (DmsService.java:313)
djs completion status = STARTED for agent 142579
2008-06-20 09:28:01,077 DEBUG [Status Updater] (DmsService.java:302)
statusIter.hasNext()
2008-06-20 09:28:01,081 DEBUG [Status Updater] (DmsService.java:309)
tm != null
2008-06-20 09:28:01,084 DEBUG [Status Updater] (DmsService.java:313)
djs completion status = OK for agent 142579
2008-06-20 09:28:01,095 ERROR [Status Updater] (DmsService.java:389)
Failed to process job results: Job Id = 121395021637614776
2008-06-20 09:28:01,097 ERROR [Status Updater] (DmsService.java:390)
dms.DmsService:
dms.DmsService:
dms.DmsService:
dms.DmsService:
dms.DmsService:
dms.DmsService
In the Oracle installation JDBC directory, backup the ojdbc14.jar file as ojdbc14_10201.jar.
Copy the new ojdbc14_10202.jar to the Oracle installation JDBC directory and rename it to ojdbc14.jar.
Restart the ./tio.sh server.
Restart Oracle.
Method 2
Using this method, only DMS uses the version 10.2.0.2.0 driver. All other components will use the version
10.2.0.1.0 driver. Perform the following steps:
1.
2.
3.
4.
5.
150
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
Symptoms
A computer has a compliance check listed more than once.
Causes
This occurs when a computer is a member of more than one group and two or more of these groups
define the same compliance check. Because each compliance check has specific settings, they can be set
up differently from each other, and there might be conflicting compliance checks.
For example, one group might require that a certain software product be installed, and another group,
that the computer belongs to, might prohibit the same software.
Symptoms
A computer has a compliance check listed more than once.
Causes
This occurs when the same compliance check is defined for a computer and also for at least one group to
which that computer belongs. Because each compliance check has specific settings, they can be set up
differently from each other, and there might be conflicting compliance checks.
151
For example, one group might require that a certain software product be installed, and one of the
computers in the group might prohibit the same software.
Symptoms
The compliance inventory scan will not finish successfully.
Causes
If you are running a compliance inventory scan on a target computer or group for any of the following
compliance checks:
v AIX Activity Logging
v AIX Remote Root Login
v Linux System Logging
v
v
v
v
v
v
v
v
v
v
Windows
Windows
Windows
Windows
Screen Saver
Services
Unauthorized Guest Access
User Password
then the common agent must be installed on the target machines. If the common agent is not installed,
then the compliance inventory scan will fail.
Symptoms
You cannot modify a compliance check directly when it is inherited from another group.
Causes
152
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
If a computer is a member of a group, it inherits all of the compliance checks of its parent group. These
compliance checks are listed in the Compliance tab for the computer, but you cannot modify an inherited
compliance check directly.
Symptoms
New users are created successfully. But those users are not listed in the user interface. This can only
happen on a non-English installation of Tivoli Provisioning Manager.
Causes
The value of the EMAILTYPE domain was translated.
Symptoms
The following message is given when you run a Windows Firewall compliance check on a computer that
is using Windows Native Firewall, and when the Track traffic setting is set to Yes:
Change the value of the "Track traffic" setting for the firewall
software "Windows Native Firewall" to match the compliant value "true"
Causes
This occurs if the computer is the member of a domain. This is a known limitation.
153
Symptoms
You receive no recommendation after running a Linux System Logging check on SUSE Linux Enterprise
Server 10 (x86 32-bit).
Causes
The SCM collector agent of the common agent does not collect syslog information about SUSE Linux
Enterprise Server 10 (x86 32-bit).
Symptoms
You attempt to perform a remediation task but you receive the following error message:
The recommendation with ID: ID_number is not in a valid state for the run action
Causes
You cannot perform a remediation task if you have not approved the related recommendation from the
web interface.
Symptoms
When you define a Windows Power-On Password security check in the Compliance tab and run a scan
and check task on a computer, the following incorrect recommendation might be generated:
Run an inventory scan to discover information about
the "Windows Power-on Password" setting for this computer
Causes
This error occurs when the BIOS properties of a specific computer do not contain the power-on password
setting value. In this case the information about the power-on password cannot be detected by the Tivoli
Provisioning Manager Inventory Discovery and a wrong recommendation is generated.
154
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
Symptoms
When you create a software configuration template for a WebSphere Application Server installation,
selecting IBM WebSphere Application Server - xxx for both creating the template and defining the
software configuration check, the recommendation generated after running a compliance scan and check
might become incorrect, and cause the following message to be displayed:
Define the configuration settings on the computer for the software installation
"Profile: default" to match the compliant value.
Causes
The TADDM discovery populates the data model with IBM WebSphere Application Server - xxx as the
base WebSphere Application Server installation. This object contains only some installation parameters.
When the compliance check is run, the parameters are checked also against Profile: default as the base
WebSphere Application Server installation. This generates recommendations that are incorrect.
155
XML files will be generated on the target computer in the common agent installation directory. The files
will have the following name patterns: scm_<hostname>_collectors<timestamp>.xml and
scm_<hostname>__converted<timestamp>.xml,
156
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
Symptoms
When trying to perform a multiple patch installation, some patch installations might fail. The following
error message is displayed:
COPCOM116E The operation timed out.
Causes
Microsoft limitations regarding multiple patch installation can cause some patch installations to fail.
Symptoms
Duplicate patch recommendations are listed in the OS Patches and Updates compliance check.
Causes
If your computer has compliance checks from both OS Patches and Updates and from its provisioning
group, then the patch recommendations for it will be generated twice.
For example, if your computer has 20 patch recommendations because of the OS Patches and Updates
compliance check being run, these issues will be listed twice in the Recommendations tab (once for each
check) and a total of 40 patch recommendations will be listed in the General tab for the computer.
However, if you access the Issues and Recommendations tab for a specific check, the patch
recommendations will only be listed once.
157
Symptoms
If you are using a Windows XP computer as your Microsoft patch download server, you might receive an
Out of Disk error when attempting to download the 32-bit version of Windows 2003 Service Pack 2.
Causes
There is a maximum download size restriction on the WinHTTP COM object that Microsoft provides with
some versions of Windows, and is a limitation that is acknowledged by Microsoft.
Symptoms
The installation of Service Pack 2 (KB914961) on Windows 2003 and Windows XP (64 bit) target
computers fails when running a script remotely on the target computer. You receive the following error:
Error Code: 0x800705B3
Error Desc: This operation requires an interactive Windows station.
Causes
158
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
This problem is due to a Microsoft limitation. The Service Pack 2 installer requires an interactive
Windows station when installing on Windows 2003 and Windows XP (64 bit) targets.
Symptoms
When attempting to install certain Windows patches, the installation reports success, but the Windows
Update Agent (WUA) scan does not find the patch installed. This problem might occur when attempting
to install patches that have been superseded by newer ones.
Causes
This known issue is caused by a WUA problem.
Symptoms
The uninstallation of Windows Update Agent fails. A messages similar to the following might be
displayed:
Windows Update Agent installation has failed because
some files are being used by another process.
Please reboot the endpoint and try to install WUA again.
Causes
The uninstallation might fail because Windows Update Agent files are being used by another process.
Symptoms
159
Provisioning Manager is trying to uninstall an unsupported version of Windows Update Agent from the
target computer before installing a supported version. The following versions are not supported and must
be removed:
v 7.1.6001.65
v 7.2.6001.784
v 7.2.6001.788
The uninstallation of Windows Update Agent fails. One of the following messages, or a similar message,
might be displayed:
Cause: WUA version 7.1.6001.65 and the operating system Microsoft Windows
Server 2008 Enterprise are installed on the computer 52297. The supported
WUA located in the directory /wua/windowsupdateagent cannot be installed
with the Force option.
COPDEX123E A InstallationError exception occurred.
The exception was caused by the following problem:
Could not uninstall the unsupported WUA 7.2.6001.788 from the target computer.
To resolve the problem:
1. Reboot the target and run the WUA installation again.
2. Verify that the installer for WUA 7.2.6001.788 exists in
the directory /wua/windowsupdateagent/7.2.6001.788 in the file repository 1450.
Causes
The uninstallation might fail because the version of Windows Update Agent installer is wrong.
Symptoms
You have uninstalled an unsupported version of Windows Update Agent, either manually or by
Provisioning Manager. When you try to scan for missing patches, the scan fails with the following error
message:
COPCOM123E A shell command error occurred:
Exit code=1,
Error stream="",
Output stream="valid WSUS in registry
valid WUStatusServer in registry
Scanning...
Class doesnt support Automation
The scan operation has failed with the error code: 0x1AE
A possible cause might be that the system cannot connect to the
WSUS server or the Internet.
Also verify that TPM and/or WSUS is properly configured.
Causes
160
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
Symptoms
In a small Windows environment, after the following tasks are performed:
1. Acquire patches
2. Set up compliance
3. Scan for missing patches
4. Generate the list of recommendation for the target computers
5. Install the patches
When scanning for missing patches again to verify the compliance results, the patches that were installed
are still displayed in the recommendations list. Also, if running an inventory scan on the target
computers, the result of the scan shows that patches are not installed on the target computers.
Causes
The provisioning server does not communicate with the Microsoft Windows Server Update Services
(WSUS) server. As a result, a patch that is approved on the web interface is not necessarily approved on
the WSUS server.
Symptoms
Patch installation on Windows target computers fail and no patches are listed in the Add/Remove
Programs panel. Error messages are generated in the %WINDIR%\windowsupdate.log file that read similar to
the following: FATAL: MSI DLL version is 2.0. Version 3.1 is required.
Causes
Chapter 10. Patch management problems
161
The installation of the Windows Update Agent is a requirement for managing patches in Windows
environments. Windows Update Agent 2.0 requires both BITS and Windows installer 3.1 to be installed to
run properly.
Symptoms
When doing Windows offline patch management using the scalable distribution infrastructure, the task of
publishing approved patches to a depot fails. Errors indicate a problem running the workflow
MS_SOA_InstallPatchStack. The following error might be generated:
COPINF029E The system failed to run the workflow MS_SOA_InstallPatchStack
in order to process execution through the infrastructure.
Causes
The patch installable cannot be downloaded to the Tivoli Provisioning Manager repository.
Symptoms
When doing Windows patch management in large environments in the configuration where UNIX or
Linux is installed on the provisioning server and a Microsoft patch download server is used, errors are
generated when running Microsoft Updates Discovery. The following error might be generated:
COPDEX123E A ParsingFailure exception occurred. The exception was caused by
the following problem: A Parsing Failure has occurred. xmlSource is located:
/opt/IBM/tivoli/tpm/repository/wua/wsusscancab/update/package.xml.
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
Symptoms
You are managing patches in an AIX environment. When specifying the updates to scan for, you select
Latest Level for the Maintenance Strategy Model field to scan for both technology levels and service
packs.
After following the steps in the information center to generate the patch recommendations, two
recommendations are displayed for your target computers:
v the latest technology level, for example AIX_TL 5300-07
v the latest service pack, for example, AIX_TL 5300-07-02
If approving the recommendation to install only the technology level on the target computer, both the
technology level and the latest service pack for that technology level are installed on the target computer.
Procedure
1.
2.
3.
4.
5.
Symptoms
The task of downloading and distributing patches fails on AIX target computers.
Causes
The problem is caused by the large size of the files that are transferred, approximately 2-3 GB, between
the AIX satellite server and the provisioning server. This also occurs in large file transfers between the
163
provisioning server and target computers. The default settings for the file size prevent large files from
being transferred, and causes the patch download and distribution to fail if the files being transferred are
too large.
Symptoms
You have added new AIX target computers to the data model, but you have not run a scan on the target
computer yet. If you install the patches from the Patch Installation page instead of the Recommendations
tab for the target computer, then the scan does not run for missing patches.
Causes
Because the scan was not done on the target computer, there is no discovery associated with the target
computer.
Symptoms
When you try to connect, a message like the following message is returned:
COPDEX123E A UniqueCatalogNameError exception occurred.
The exception was caused by the following problem:
Error adding catalog catalog_name service.
RETURNCODE:1, ERROR-MESSAGE: The catalog name
catalog_name exists in the service list.
Please try a unique catalog name.
Causes
One of the parameters you entered is incorrect.
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
Provisioning Manager checks all the parameters you provided for the command and stops at the first
error it encounters. If you receive this error message, check all the parameters you entered to ensure that
they are all correct. In the example provided, the user entered the name of a catalog existing in the
database.
Symptoms
When you try to connect SUSE Linux update site in running the SUSE Linux patch scan, a message like
the following message is returned:
Error getting refreshing the catalog service SLES10-Updates. RETURNCODE:1,
ERROR-MESSAGE:ERROR: Failed to parse XML metadata: Cant add repository at
ftp://ftp.suse.com/pub/suse/update/10.1:
Unknown source type for ftp://ftp.suse.com/pub/suse/update/10.1
COPDEX123E A UniqueCatalogNameError exception occurred.
The exception was caused by the following problem:
Error adding catalog catalog_name service.
RETURNCODE:1, ERROR-MESSAGE: The catalog name catalog_name exists in the service list.
Please try a unique catalog name.
Causes
The link provided in the SUSELinux.Update.Server.url variable might be outdated.
Symptoms
Patch installation fails on Solaris target computers. Error messages might look similar to the following:
Failure: Cannot connect to retrieve detectors: / Not Found
The resource identified by / could not be found
and
Failure: Cannot connect to retrieve Database/current.zip: / Not Found
The resource identified by / could not be found.
Causes
The problem is caused by requirements that are missing from the target computers.
165
Symptoms
On a target computer where the SUSE Linux 10 base image is installed (without any service pack), the
patch called agfa-fonts-2003.03.19-32.6 cannot be installed.
Causes
This problem is caused by a third party license agreement that you must accept manually.
Symptoms
If managing patches for SLES Linux environments using the ZENworks model, after scanning the SLES10
or SLES10 SP1 target computers, the patch information displays default values: Description, Category,
and Release Date are blank, and Reboot is false.
Causes
The ZENworks Linux management server does not provide patch information.
Symptoms
Patch installation on SUSE Linux environments fails with the following error:
COPDEX123E A PatchInstallError exception occurred. The exception was caused by
the following problem: Error installing patches. Please refer
/tmp/temp11428.log file for more details.
RETURNCODE:1 ERROR:ERROR: Dependency resolution failed:
Resolvable id 116289 does not exist.
Causes
166
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
Causes
The timeout setting might be too restrictive.
167
168
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
Symptoms
During the upgrade from Tivoli Provisioning Manager 7.1 to 7.1.1, the following error occurs:
COPUTL091E
A required pre-defined value was not changed from VMWare to VMware.
Causes
The VMWare value in version 7.1 is changed to VMware during the upgrade to version 7.1.1. If the error
occurs, the value was not changed.
Symptoms
An error will happen when creating a VMware virtual server using a ESX server that has run the
inventory discovery. If the inventory discovery has been run for a ESX server and it is selected to create a
virtual server. The creation workflow might fail with the following error:
COPDEX040E
An unexpected deployment engine exception occurred:
COPCOM606E The system cannot find managed memory type
hardware resource on host platform {ESX server name}.
Causes
This limitation is caused by the fact that inventory discovery can not discover the memory that is
allocated to the virtualization management.
169
server, remove it from TPM DCM, then start "VMware VI3 - HostPlatform Resource and Virtual Machine
Discovery". The ESX server will be added in by "VMware VI3 - HostPlatform Resource and Virtual
Machine Discovery" and be configured properly to manage the virtualization.
Symptoms
For a ESX server with multiple CPUs, "VMware VI3 - HostPlatform Resource and Virtual Machine
Discovery" will not work if the inventory discovery against it has been run before it. The error is:
COPDEX172E The CPUResID variable is a single value variable, cannot assign an array value to it.
Causes
This limitation is caused by the fact that VMware virtualization expect only one CPU resource when
allocating the resource allocations to virtual machines
Symptoms
Create LPAR failure with error message: COPCOM123E A shell command error occurred:....
Causes
It might be caused by the fact that virtual I/O server name does not conform with the DNS naming rule.
TPM requires virtual server name to be defined in DNS and resolved to IP address. Therefore it needs to
conform to both HMC and DNS naming rules.
170
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
Symptoms
The following error displays when running VMware VI3 - Virtual Center Discovery:
Cannot connect to URL https://<Virtual Center IP Address>/sdk
using user <user name> because:;
nested exception is: javax.net.ssl.SSLHandshakeException:
com.ibm.jsse2.util.h: NO trusted certificate found.
Causes
The keytool command was run in a wrong directory. It needs to be run in $JAVA_HOME/jre/lib/security.
In this directory you find an existing cacerts file.
Symptoms
When you create a dedicated WPAR and specify the values for the /usr and /opt file system sizes in the
virtual server template, the creation of the WPAR fails with the following error message:
mkwpar: 0960-287 Error: /usr requires at least 2288096 blocks
Causes
The /usr and /opt file system sizes are too small. The sizes must be large enough to copy all of the
required files from the /usr and /opt directories of the host platform server.
So, the minimum file size required for the dedicated WPAR is 1,117MB.
171
Symptoms
When you try to install Tivoli Common Agent on an AIX WPAR, the installation task fails with the error
message COPDEX123E.
Causes
Tivoli Common Agent cannot be installed on shared zones. Shared or non-shared (dedicated) WPARs are
determined by the value of the WPAR.privateusr variable in the virtual server template. To view the
virtual server template, navigate to Go To > IT Infrastructure > Provisioning Inventory > Virtual Server
Template and then select the server template that was used to create the WPAR. A value of no for the
WPAR.privateusr variable means that the server template will create a shared WPAR. Installing Tivoli
Common Agent to a WPAR that has been created with this setting will fail.
Note: Because Tivoli Common Agent cannot be installed on any shared zones, this issue also applies to
shared Solaris zones. However, if the installation fails with Solaris, no error message is given.
Symptoms
You upgrade the Provisioning Manager server from version 7.1 to version 7.1.1. You also upgrade the
depot from version 1.4.1.0 to version 1.4.2.0. You then try to install a software package on a 7.1 UNIX or
Linux target computer and the installation apparently completes correctly. However, the software package
is not present on the target computer.
Causes
This problem is due to an internal defect in the subagent code which is resolved in Provisioning
Manager, version 7.1.1.
Symptoms
An attempt to synchronize an AIX WPAR with its host LPAR fails with the following error message:
172
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
Causes
This is a known limitation with AIX 6.1 LPARs.
After the file sets have been removed, run the synchronization again.
Symptoms
When you try to install the common agent on a shared-IP Solaris zone, the installation fails and an error
message similar to the following is displayed:
COPDEX123E An AgentInstallException exception occurred.
The exception was caused by the following problem:
Agent installation failure.
Agent install return code log file contents:
An error during the GUID installation.
Causes
The Globally Unique Identifier (GUID), version 1.3.3, packaged with Tivoli Common Agent needs to
query the network interface MAC address at installation time. In a shared-IP Solaris zone, the network
interface MAC address is not accessible, so the GUID installation fails.
173
174
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
Symptoms
A provisioning task cannot be scheduled and submitted from the web interface.
Causes
The activity plan was saved as a draft, which can only be done in the Activity Plan Editor.
After this is done, use the following steps to run the provisioning task.
1. Click Go To > Task Management > Provisioning Tasks > Provisioning Task Definitions.
2. Click Activity Plan from the list of provisioning task definitions.
3. From the Select Action menu, click Run Provisioning Task.
4. Click Select to select the target computers on which you want to run the provisioning task.
5. Click Schedule to specify some scheduling options for the provisioning task.
6. Click Submit to run the provisioning task.
Symptoms
You cannot delete multiple provisioning tasks in the Provisioning Task Definitions application and
instead receive an information message that tells you that shared provisioning tasks can only be deleted
by their owners.
Causes
Shared provisioning tasks can only be deleted by their owners. If the provisioning tasks that you have
selected include shared provisioning tasks created by other owners, you cannot delete them directly.
Copyright IBM Corp. 2003, 2011
175
Symptoms
If the Tivoli Provisioning Manager server was interrupted in any way (for example, due to a power
failure or the deployment engine being stopped) while a task is in progress, that task remains in progress
even after Tivoli Provisioning Manager recovers. Any objects that the task is holding will not be released.
Causes
When the provisioning server is reset, tasks that are in progress will fail with a Java Virtual Machine
error.
Symptoms
The following error occurs when a task is running:
>@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY!
Someone could be eavesdropping on you right now (man-in-the-middle attack)!
It is also possible that the RSA host key has just been changed.
The fingerprint for the RSA key sent by the remote host is
176
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
4c:e2:db:b3:38:de:5f:f3:54:34:47:50:33:a0:be:86.
Please contact your system administrator.
Add correct host key in /home/tioadmin/.ssh/known_hosts to get rid of this message.
Offending key in /home/tioadmin/.ssh/known_hosts:3
RSA host key for 9.23.17.47 has changed and you have requested strict checking.
Host key verification failed.
Causes
This error occurs when SSH between the provisioning server and the target computer detects a change in
the RSA key. For example, this might occur when a particular target computer is re-imaged, because then
the SSH keys would no longer match with the keys from the provisioning server. It is a built-in SSH
mechanism that prevents access from other computers that try to impersonate a known computer. This
error message tells the system administrator that the target computer is no longer the same. If the system
administrator determines that the computer is not an offending computer (which is the case when
re-imaging) then the provisioning server provides a convenient way to solve this.
Symptoms
If you do an install software task using the following steps, the task will fail:
1. Go to IT Infrastructure > Software Catalog > Software Product Import.
2. Enter the data for all of the fields.
3. Select Windows OS.
4. Select Custom Extract and Install.
5. Set the Configuration template parameter for the created software product as:
Extract command - unzip <file name>
Install command - <file name> -q
Note:
v The file will extract using the unzip command but the extracted file does not have read and run
permissions.
Chapter 12. Provisioning task problems
177
v The workflow will assign the required permissions for the extracted file.
Causes
This is caused by the coexistence of Windows and Cygwin while using the extraction utility. The
extraction utility will not correctly set the permission of unpacked files when Cygwin is installed.
Symptoms
After you run the clean-up-deployment-requests command, the following deployment task error
message occurs:
COPDEX029E The system cannot continue the deployment request
from a previous deployment engine JVM session.
Causes
Another user has already run the clean-up-deployment-requests command on the provisioning server.
178
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
3) ExecuteCommand is a workflow variable that contains the exact string to be executed. To make
this string visible in the execution history, add the following line just above the
Device.ExecuteCommand call:
log debug ExecuteCommand
4) Save and compile the workflow. Run the workflow again and then observe the clear text
command in a debug statement in the execution history.
179
3. Follow good provisioning workflow programming techniques by implementing log elements in your
program. Logs are generated from provisioning workflow log elements. To add log elements to a
workflow, do the following steps:
a. Make the workflow editable by running these commands in the shell prompt:
db2 connect to tc user <user name> using <password>
db2 update workflow 4 set is_editable=Y
where workflow_name=<workflowname>
b. Add log statements into the workflow above the commands that you want to log. For example:
Log info "Starting execution"
Device.ExecuteCommand (DeviceId, ....
where
type
Is the type of log statement. The available types are debug, info, warning, and error.
log_message
Is the log message that you want displayed when the log statement is triggered. You can
enter a text message, or a variable name that leads to a text message.
With log statements implemented, the workflow history log displays your specified messages after
each workflow is run. Log messages are displayed according to the log level selected in the web
interface. For example, no log warning messages are displayed if warning was not selected in the
workflow history web interface window.
Note: Log error messages do not stop workflow executions from completing.
See log for more information about log elements.
4. The properties of the log.level global variable, determine if the message text of a log element is
recorded in the provisioning workflow run history. To define the log.level global variable:
a. Click Go To > Administration > Provisioning > Provisioning Global Settings.
b. Click the Variables tab.
c. Click Edit > Add Variable.
d. Name the variable log.level in the Key field, with a component of Deployment engine, and a
value of debug|info|warning|error.
When a provisioning workflow is run, the logs generated inside a provisioning workflow are filtered
based on the value of this variable, with debug having the lowest priority and error having the
highest priority.
For example, if log.level is info, then you can see only the output from log info, log warnings and log
error. You cannot see the output from log debug statements. If the log.level is error, you will see the
output from log error only.
All provisioning workflows must use an appropriate log level for each situation. You can turn on
verbose logging by changing the global variable.
For example, a provisioning workflow that does a file copy might have the following log statements:
v If the source file is not found: log error file not found.
v If the source file is larger than one GB: log warning Large file: It will take some time to
process.
v For debugging: log debug file my_file.exe is being copied from hostA to hostB using scp,
username Administrator.
If you set the log.level variable to warning, debug messages are not recorded in the log. You might see
the warning message if the file is large. If you suspect that there is something incorrect in your
provisioning workflow, you can switch to log debug so that you can see all messages.
180
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
5. If you created a new global variable for your provisioning workflow, make sure that you had selected
Deployment engine for the component. If you select Entire system, the provisioning workflow will
fail.
Compilation errors
You can use the following information to help resolve compilation errors.
Symptoms
You might receive the following compilation error:
ERROR DETAIL:
Workflow line: 11
Error Code = COPDEX049EwiNoSuchOperand
ERROR MESSAGE = COPDEX049E The "language" operand
does not exist for instruction ID: 49368.
Causes
There is an entry for instruction ID 49368 in the WORKFLOW_INSTRUCTION table, but no corresponding
LANGUAGE operand for that instruction in the WORKFLOW_INSTRUCTION_OPERAND table.
You must also edit the following lines. Change the INFO parameter into DEBUG:
log4j.category.com.thinkdynamics=INFO, consolefile, errorfile
log4j.category.com.ibm.tivoli=INFO, consolefile, errorfile
Note:
This is not a default function. Debug mode is not enabled for console.log files for a standard
installation.
After you have completed the changes to enable Debug mode, you must restart the Tivoli
Provisioning Manager server for the changes to take effect. For information see Starting or stopping
the provisioning server on UNIX or Linux or Starting and stopping the provisioning server on
Windows.
v When you only configure the log4j settings, it does not log commands issued by the deployment
engine. To log commands issued by the deployment engine, you must enable full debug mode.
Chapter 13. Provisioning workflow problems
181
1.
2.
3.
4.
Note: Full debug mode enables logging of deployment engine commands in both the user interface and
the log file. The logging change takes effect immediately for each instance when a provisioning workflow
is run.
For security reasons, a method is provided to obscure passwords and other sensitive data that appears in
product logs. For more information, refer to the Obscuring sensitive data topic.
console.log
This log file stores all event logs for workflow and workflow executions including messages,
traces, and debugging information.
msg.log
This log file stores the globalized event messages for the deployment engine component.
trace.log
This log file stores error messages that can be reviewed by Tivoli Software Support.
Troubleshooting scripts
The Device.ExecuteCommand logical operation and Scriptlets both run on managed computers. In this case,
there are three areas that can potentially cause problems:
v The managed computer environment is not configured properly
SSH will use the PATH defined at SSH server compilation time, and not the PATH that was defined by
the user who is running the command. The following table lists the compilation time paths for
supported operating systems.
Table 13. Compilation time PATHs for supported operating systems
Operating System
PATH
Solaris 8 and 9
PATH=/usr/bin:/bin:/usr/sbin:/sbin:
/usr/local/bin
PATH=/usr/bin:/bin:/usr/sbin:/sbin
Red Hat 3
PATH=/usr/local/bin:/bin:/usr/bin
Cygwin
PATH=/bin:/usr/sbin:/sbin:/usr/bin
If the system path has been modified on your system, this setting overrides the default SSH server
compilation time PATH. To verify this setting, from the command line run:
182
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
workflowLogExport tool
This command line utility exports the run history of one or more specified provisioning workflows to a
log file that can be either in XML format (the default option) or in any other file format of your choice.
This command line utility exports the workflow execution logs into an XML file. The tool simplifies the
process of sending provisioning workflows to IBM Tivoli Software Support so that they can access the log
information that they need to diagnose a provisioning workflow problem without accessing your
computer remotely. The user can export the run history of individual provisioning workflows, or the run
history of several logs into a log file whose name, file format, and location you can specify.
The command line utility is available at the following location:
v
Windows
2000
%TIO_HOME%\tools
where %TIO_HOME% is the Tivoli Provisioning Manager home directory.
v
UNIX
2000
Linux
$TIO_HOME/tools
Syntax for Windows: Enter the following command on one line:
workflowLogExport.cmd (-n <workflow_name>* | -r <request_id>)
[-f <export_filename>] [-i <input_filename>]
where:
[-n <workflow_name>*]
Is a command option that specifies the name of the provisioning workflow whose run history
you want to export to a log file. The asterisk (*) indicates that you can include multiple
provisioning workflow names in this variable. If you do not specify one or more provisioning
workflow names, workflowLogExport generates the provisioning workflow run history for all
provisioning workflows.
183
where the command options are the same as the command options for Windows.
Returned file: The provisioning workflow run history is exported into a log file with a file name and
format that you can specify. If you do not specify them, the provisioning workflow run history is
exported by default to the workflowLogExport.xml file in the %TIO_LOGS% directory.
Log content structure: provisioning workflow > deployment request > workflow execution log >
workflow execution log detail
This is a sample provisioning workflow log export:
<?xml version="1.0" encoding="UTF-8"?>
<workflow-execution-history>
<workflow id="21" name="Test Workflow 99999">
<deployment-requestid="10020">
<execution-log id="21" date="Mar 10,2005 11:48:54 AM" position="1"
<call-stack-level="1" lo
<log-details position="2" name="Test Details Name"
Test Details Values</log-details>
</execution-log>
</deployment_request>
</workflow>
</workflow-execution-history>
Symptoms
When you run a provisioning workflow to deploy resources, you see a DB2 error telling you that an SQL
exception has occurred.
184
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
Causes
This error can occur when the application heap size is not large enough to process the request.
where $DB2_DB_NAME is the name of the database that you want to modify.
3. Under the sqllib\bnd directory, run the following command to rebind the packages:
db2 connect to $DB2_DB_NAME db2 "bind @db2ubind.lst blocking all grant public"
db2 "bind @db2cli.lst blocking all grant public CLIPKG 6"
Symptoms
Tivoli Provisioning Manager displays a DB2 error. For example
:com.ibm.tivoli.orchestrator.de.dao.PersistentStateException:
COPDEX038E A persistent/database state error: [IBM][CLI Driver][DB2/NT]
SQL0302N EXECUTE <DB text> SQLSTATE=22001 occurred.
Causes
The provisioning workflow variable values are limited to 4000 bytes. When a scriptlet or Java plug-in
returns a value longer than 4000 bytes, an error occurs.
Symptoms
DB2 Universal Database deadlocks occur when the computer runs a logical operation.
Causes
The DB2 database configuration parameter (lock list) value is not large enough.
185
Adjust the lock list size value from 50 to 2000. Depending on the volume of traffic on the servers and the
size of your data model, you might want to select a more appropriate value.
For more information about setting the lock list value, search the DB2 for Linux, UNIX, and Windows
Support page: http://www-01.ibm.com/software/data/db2/support/db2_9/
Symptoms
A provisioning workflow does not install.
Causes
This can occur when provisioning workflows, parameters, and variables are not named correctly.
Tip: Any Unicode character can be used to enter comments in provisioning workflow scripts.
Symptoms
The UnzipSWDCLI provisioning workflow times out with the following error message:
COPCOM116E The operation timed out.
186
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
Causes
This problem can occur when the coreutils package is missing. This package is a prerequisite of Solaris,
version 10.
.
c. Run the following command to extract the file:
tar -xvf /opt/IBM/tivoli/tpm/sie/bundles/solaris2.tar
Procedure
1. Click Go To > Task Management > Provisioning Tasks > Provisioning Workflow Status.
2. Search for the workflow executions that you are interested in:
v To search for workflow execution for a particular provisioning workflow, click the arrow icon next
to the workflow name.
v To search for workflow executions for a specific day, type the date in the Start Date field.
Chapter 13. Provisioning workflow problems
187
Symptoms
When using an application server URL with Internet Explorer 6, provisioning workflows cannot be
exported in the Export Workflow pull-down menu in the Provisioning Workflows window. This problem
does not occur with web server URLs or with Internet Explorer 7.
Causes
The software to block pop-up windows on Internet Explorer is conflicting with the menu.
Causes
188
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
When running scriptlets in Tivoli Provisioning Manager, the system will expect that the command
prompt ends in the $, # or > symbols. The PS1 environment variable governs what your prompt looks
like. If you change this variable on your target computer or on the provisioning server, you might have
problems when running provisioning workflows.
For example, on most UNIX systems, when you are logged in as tioadmin, by default, you see the
following command prompt:
$
If you change the PS1 variable for tioadmin to be tioadmin, you will see the following as the command
prompt:
tioadmin>
For more information about troubleshooting provisioning workflows, see the Developing automation
packages section in the information center.
Symptoms
If you get this error: bash: fork: Resource temporarily unavailable, it might be accompanied by this
message:
COPCOM123E A shell command error occurred:VALUE_0 Exit code=VALUE_1,
Error stream=VALUE_2, Output stream=VALUE_3.
Causes
You have exceeded the number of processes allowed by your operating system.
189
Symptoms
When you are running a provisioning workflow, you might see the following error:
COPCOM123E This shell command error occurred: Exit value=1, Error stream="",
Result stream="no bash in /bin/usr/bin /usr/sbin /usr/local/bin . /usr/bin /
etc /usr/sbin /usr/ucb /usr/bin//usr/java131/jre/bin /usr/java131/bin / nmlprod
/common/scripts /nmlprod/common/bin /opt/seos/bin".
Symptoms
When you are running a provisioning workflow, you might see the following error:
COPCOM123E A shell command error occurred: Exit code=1,
Error stream="Command: `su - tioadmin` failed. ", Output stream=" su:
incorrect password "
This adds the user tioadmin to the wheel group. This allows provisioning workflows to run without
error.
Symptoms
Copying a file from the provisioning server to a managed computer using the Device.CopyFile
provisioning workflow fails if the file name includes double-byte characters (DBCS).
Causes
190
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
Depending on the placement of double-byte characters in the file name, the file will be copied with a
corrupted file name, and might also be copied to an unexpected file path. This issue also applies when
copying files from a managed computer to the provisioning server.
Symptoms
An automation package that was installed in a previous version of Tivoli Provisioning Manager can be
updated to a newer release. The updating process might fail with an error message stating that the data
model object for the automation package to be updated already exists.
For example, updating the VMware_Virtual_Infrastructure automation package to a newer release of
Tivoli Provisioning Manager might fail with the following error message:
ERROR COPCOM557E The system cannot create a discovery object
VMware VI3 - HostPlatform Resource and Virtual Machine Discovery,
because it already exists.
Symptoms
A workflow hangs when it tries to call the Lock_DCM_Object object. Several workflows (such as
Sun_UCE_Assemble_Client) call this object.
Causes
The required object (Lock_DCM_Object) was not released correctly by the last workflow that used it. This
can occur because of system failure or because the deployment engine was reset during a task execution.
191
Symptoms
The workflow fails with an error stating that the ID you specified is not a system ID. For example:
COPDEX123E An IllegalArgumentException exception occurred:
The exception was caused by the following problem:
No system defined with ID <system_ID>.
Causes
The SDI_Agent_setHostconfig provisioning workflow accepts as parameter only the device ID of a
computer. The workflow checks that the ID provided corresponds to an existing computer in the
environment.
Symptoms
The following error message occurs:
COPCOM123E A shell command error occurred:java.io.IOException:
Cannot allocate memory Exit code=0, Error stream="", Output stream=""
Causes
This error occurs when there is insufficient system memory or the configuration of the connection-pool
setting is incorrect.
192
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
193
194
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
Symptoms
Reports that are exported to Comma Separated Values (CSV) file format can then be imported to
spreadsheet applications, such as Microsoft Excel. When trying to import non-English CSV reports into
Excel , the text becomes garbled.
Causes
CSV files are written in UTF-8 format (abbreviation for Universal Transformation Format). UTF-8 converts
16-bit unicode characters into 8-bit ASCII characters. Microsoft Excel does not currently support UTF-8 in
CSV format.
195
where<Language_code> is the locale code for the language that you are interested in. For example,
GB2312 is the code for simplified Chinese.
3. Open the <Report_name>_output.csv file in Excel.
All characters are properly displayed.
Instead of running the previous command more than once for converting more CSV files, you might
want to create a script file that uses the command in step 2 and specifies the names of all the CSV files
that require conversion. You can run the script to convert all the required files at once.
In addition to the solutions described previously, the following operating system and Excel requirements
must be met before the characters are displayed properly:
Operating system requirements
Try matching the language of the imported CSV report with the operating system language. For
example, for Japanese, try importing the file on a computer that is running a Japanese operating
system. If you cannot meet this requirement, set the user locale of your system to the language of
your choice, so that you can use the standard settings for that language. To do this, perform the
following steps:
1. Click Start > Settings > Control Panel, and then open Regional Options.
2. On the General tab, change the user locale to the language you are interested in.
3. Click OK.
Excel requirements
You can set the Microsoft Office language settings to the language of your choice by performing
the following steps:
1. Click Start > Programs > Microsoft Office Tools > Microsoft Office XP Language Settings
2. On the Enabled Languages tab, set the Default version of Microsoft Office to the language
of your choice.
3. Ensure that the language that interests you is on the Enabled languages list:
a. In the Available languages list, click the language that interests you.
b. Click Add to add the selected language to the Enabled languages list.
c. Click OK.
Symptoms
Unknown characters appear when generating a report that contains double-byte characters (for example,
Cyrillic, Chinese, or Japanese characters) after exporting the report as CSV file.
Causes
Some applications do not support UTF-8 encoding or open CSV files (that use UTF-8) using ASCII
encoding, which results in garbled text being displayed.
196
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
Use an application that supports UTF-8 encoding, such as Notepad. Alternatively, open the CSV report
using Microsoft Excel 2003. To open the report result file:
1. After the download is completed, change the file extension to .txt. Ignore the prompted warning.
2. Open the text file in Microsoft Excel 2003.
3. In the Text Import Wizard select Delimited in Original Data type, then select Unicode UTF-8 in File
origin.
4. Click Next.
5. Specify the comma character as the file delimiter.
6. Click Finish.
You can also change your Web browser language preferences to see the language display correctly.
1. In Internet Explorer, click Tools > Internet Options.
2. Click Languages > Add.
3. In the list, select the language that you want to add and click OK.
4. In the Language field, select the new language and click Move Up. Click OK and then close the Web
browser.
5. Open the Web browser and log on to Tivoli Provisioning Manager.
The new language will now be displayed in your Web browser.
Symptoms
When you run a report that provides detailed information, only some of the results are printed in the
exported report in Common Separated Value (CSV) format.
For example, if you run the report called tp_serverDetails.rptdesign to see server details (including
networking and other resource details) the exported CSV formatted report results only provide the server
name and server ID details.
Causes
The other result fields for a report are created in sub-reports under the top-level report. In this example,
the hardware resource and networking details are provided in the sub-reports.
Symptoms
Running the importreports.cmd command to import a report results in the error Unable to locate
tools.jar.
Causes
An extra library is referenced in the environment script.
197
Disregard this error message. The importing of the report completes successfully even though you receive
this error.
Symptoms
Microsoft Internet Explorer version 7 hangs if you are using the Web browser to view multiple report
results.
Causes
There is a memory leak in Microsoft Internet Explorer version 7. The memory usage of the iexplore.exe
file grows even after you have closed the report results.
Symptoms
When you click Generate Request Pages, the action seems to perform correctly but you cannot open the
report.
Causes
The request pages did not generate properly.
:%WAS_HOME%\profiles\ctgAppSrv01\logs\MXServer
2000
Linux
: $WAS_HOME/profiles/ctgAppSrv01/logs/MXServer
SystemErr.log
Windows
2000
UNIX
198
:%WAS_HOME%\logs\server1
2000
Linux
: $WAS_HOME/logs/server1
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
Symptoms
v If two persons logged on with the same user ID are modifying the same scenario, the most recent
changes are saved in the scenario.
v Clicking the Rewind icon goes back only a number of steps in a scenario.
v Importing an existing scenario creates a duplicate scenario on the interface.
Symptoms
The pop-up window that is used to provide instructions to users is not visible because Web Replay is not
running in a full-screen browser window.
Causes
The browser window is too small, which makes the pop-up window appear off-screen.
Symptoms
Web Replay scenarios do not work with certain Web browsers.
Causes
Web Replay scenarios that are created in one Web browser might not work properly if you run them in
another Web browser. For example, Web Replay scenarios that are created in Internet Explorer might not
work properly in Firefox, and vice versa.
Copyright IBM Corp. 2003, 2011
199
Symptoms
When creating or running a scenario, Microsoft Internet Explorer ends the session with one of the
following errors:
Microsoft Internet
Explorer stack overflow
or
Internet
Explorer Cannot Open the Internet Site - Operation Aborted
Causes
The Web browser is running out of memory.
Symptoms
When creating a Web Replay scenario, the highlight appears and disappears too fast, which might result
in recording the wrong element on the web interface.
Causes
The browser cache contains data which causes this behavior.
200
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
Symptoms
When running a scenario, if you do not type data when required to, an error message is generated on the
web interface, but the Web Replay scenario advances to the next step.
Symptoms
v When running scenarios, interface pages with a large number of items might take a long time to
display.
v If there are a large number of scenarios available, it might take a long time for Web Replay to respond
to user commands.
Symptoms
When creating a scenario with many steps in Microsoft Internet Explorer, Web Replay takes a long time
to respond.
Causes
An issue with how Microsoft Internet Explorer handles memory with javascript might cause the browser
to run out of memory.
Symptoms
When running a Web Replay scenario, the highlight box is not placed properly for menus if the previous
step is an automatic step.
Causes
Chapter 15. Web Replay problems
201
This behavior is expected because all menu items, such the Go To menu items, need be recorded either as
all manual steps or as all automatic steps.
Symptoms
After creating and removing some categories in Web Replay, the removed categories that were not
assigned to a scenario appear to exist, but do not actually exist.
Causes
In Web Replay, a category is created only when a scenario is assigned to it. A new category needs to be
assigned to a specific scenario, or else the category will give the impression that it exists when it does not
exist.
Symptoms
A user can log in but cannot access the Web Replay link. If access is granted, permission to play or edit a
particular scenario is denied.
Causes
In order to run or re-create Web Replay scenarios, you must be a member of one of the following security
groups, depending on whether Run , Re-create, or access to all operations permission is needed:
v WR_USER_PERMISSION
v WR_ADMIN_PERNISSION
v WR_SYSADMIN_PERMISSION
These groups are documented in the Web Replay User's Guide. The Tivoli Provisioning Manager security
groups have access to the Maximo Web Replay applications, but permission is needed in order to play or
edit some scenarios.
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
Access to playing provisioning-related scenarios is available for appropriate security groups by default.
203
204
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
Procedure
1. Check the installation of the Software Package Editor.
The Software Package Editor launched from the web interface requires that the Java Web Start tool is
installed on the workstation. Java Web Start is contained in the Java Runtime Environment Version
1.4.2 or later releases. The Eclipse-based Software Package Editor is launched from an Eclipse
installation only on supported Windows platforms.
2. Verify that the deployment engine is up and running.
Check the log files for provisioning workflows stored in the path %TIO_LOGS%\console.log.
3. Verify the information located on the preferences panel of the Eclipse interface (Window >
Preferences > Software Package Editor).
v Type the following Web address in a Web browser: https://Web_Server_hostname.port/root_path/
SPEListPackages. For example,
https://Web_Server_hostname:9443/SPE/SPEPackageList
If the information specified on the preferences panel is correct, then an unformatted list of software
packages is displayed similar to the following output. Boldface is used to highlight software
package names and versions:
VivPackage#lab133094-region 1.0
"Java IBM Windows Installable 1.4.2ptTCA Solaris Installable FOR
TMA 1.3.2.7 TCA Windows
Installable FOR TMA 1.3.2.7 New1Viv#lab133094-region 1.0#
Java IBM Linux390 Installable 1.4.2
v If Use SSL is selected and your provisioning server uses HTTPS over SSL, ensure you have
imported the SSL certificate in the cacerts keystore.
205
v Verify that the password specified for the user is correct, and that the user has been created on the
provisioning server. To verify the creation of the user from the Tivoli Provisioning Manager web
interface, select System Management > Manage User.
Note: During installation, a system administrator user (tioadmin) and a web interface administrator
user (admin by default) are created. The web interface administrator has all permissions for all
objects in the data model. The tioadmin user is not assigned to an access collection by default, and
therefore you must manually assign the permissions to the user. To assign all permissions for all
objects in the data model:
a. Log on to the web interface with the user tioadmin.
b. Click System Management > Manage Users.
c. Click the tioadmin user.
d. Select Edit > Assign Access Permissions.
e. Under Available Access Groups, select sample:all-objects.
f. Under Available Permissions, select sample:all-permissions.
g. Click Save.
Symptoms
An error occurs when you run eclipseLauncher.bat to start the Software Package Editor on a Windows
computer.
Causes
You do not have the latest Microsoft service pack.
Symptoms
The Software Package Editor runs running slowly when accessing remote drives.
Causes
Performance of the Software Package Editor might be degraded if remote drives were mapped to the
computer after Software Package Editor was launched.
206
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
Symptoms
An operation launched from the Software Package Editor returns an OutOfMemoryError error.
Causes
Error might be returned if the software package being processed is too large.
Symptoms
If you download a software package block (SPB) containing platform-dependent variables (for example,
file paths of source files) on Windows when the SPB was originally created in UNIX or Linux, the SPB
gets corrupted.
Causes
This problem only occurs with SPBs created using Tivoli Provisioning Manager version 5.1, and has been
resolved in later versions.
207
Symptoms
Uploading and downloadingsoftware package blocks (SPB) to and from the file repository on the Tivoli
Provisioning Manager server fails if the name of the software package block contains double-byte
character set (DBCS) characters.
Causes
Cygwin does not support DBCS characters in software package block names.
Symptoms
Uploading and downloadingsoftware package blocks to and from the file repository on the Tivoli
Provisioning Manager server fails, if the name of the file path to the repository contains double-byte
character set (DBCS) characters.
Causes
Cygwin does not support DBCS characters in the file path to the repository.
Symptoms
The Software Package Editor does not start when performing the following steps on the web interface:
1. Click Go To > IT Infrastructure > Software Catalog > Software Products.
2. Select Start SPE from the Select Action menu.
Causes
The software to block pop-up windows in your Web browser might be preventing the Software Package
Editor from opening.
208
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
Alternately, the Java Web Start tool might not be installed on the workstation.
Causes
The Java Web Start 1.5.0_u16 might be installed on the workstation.
209
Symptoms
You will receive an error when you try to upload a migrated software package containing at least one
add_directory command for which the source path contains a variable whose value depends on the
platform where there package was built. For example, a definition of the add_directory command in the
location = $(source.$(os_name)) and the software package block (SPB) contains the default_variable
section:
default_variables
drive = c:
source.Windows_95 = $(drive)$(source_path)
source_path = /demo
source.Windows_NT = $(drive)$(source_path)
source.AIX = $(source_path)
end
Causes
If you build this software package on AIX and it is downloaded and unpacked with the Software
Package Editor on a Windows computer, the variable Windows definition prefix is added to the
source_path of the contained add_directory stanza. In this example, the source_path location attribute
from the built package is resolved as /demo but the Windows definition has added a prefix and stored
the source_path as c:/demo inside the resulting package. When the Software Package Editor attempts to
rebuild the package before uploading it to a file repository, you will receive an error message that the
path is not recognized.
Windows
2000
AIX
Solaris
2000
C:\Program Files\tivoli\ep
HPUX
2000
Linux
/usr/tivoli/ep
/opt/tivoli/ep
210
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
Symptoms
Installation of the Package Example software package block has the status of Submitted for a long time.
Causes
Resolving the problem
Run the TCA_PingAgent to make sure there are successful communications.
Procedure
1. On the target computer, change directory to/opt/tivoli/ep/runtime/agent and run the following
command:
agentcli spbhandler install -n "Linux TestPackage".1.0 -f -R y
/tmp/Linux_Test.spb
Check what is reported in the error log error-log-#.xml. You can check the agent log files by
following the instructions at the following link: Information for troubleshooting software package
blocks on Tivoli Common Agent computers on page 210
2. InstallPackageWithVariables is used to pass the user variables needed by the software package block
(SPB) to be installed properly.
The usage flow is:
v Create a software module containing an SPB installable (from the Tivoli Configuration Manager
migration or from the Software Package Editor).
v Run the SOA task (infrastructure.software.SoftwareTaskManager.java) that starts the
SoftwareModule.Install workflow using java code, which creates the software installations for each
target.
v If the SPB contains the default_variables section, the contained variables and their default values
are stored inside the software module software resource template with the leading % sign to
distinguish them from the operational variables such as FORCE or
REMOVE_SPB_AFTER_PROCESS
v When the software module is required to be installed using SOA, the JES job is created (in
DmsSoftwareService) and the keys-values arrays are filled in with these variables and passed as job
item attributes.
211
Procedure
On the target computer, go to the /opt/tivoli/ep/runtime/agent directory and then enter the following
command:
agentcli spbhandler state -n *
This should produce the following output::
*** Exit code = 0
*** Extra data = ----*** Standard output:
DISSE0164I Name : PackageExample
DISSE0165I Version : 1
DISSE0166I State : IC------------------------------------DISSE0164I Name : TPM End User Interaction Service Installable
DISSE0165I Version : 5.1.1.0
DISSE0166I State : IC------------------------------------*** Standard error:
Procedure
On the target computer, go to the /opt/tivoli/ep/runtime/agent directory and run the following
command:
agentcli spbhandler remove -n "TPM End User Interaction Service Installable.5.1.1.0"
Symptoms
212
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
When uninstalling a software package block (.SPB file) on Windows target computers, the operation ends
successfully but the software product is not removed from the target computer.
Causes
When an uninstall operation is triggered from the console, the real operation performed at the agent level
is an undo operation (rollback) instead of a physical remove operation.
Procedure
v You can use multiple software package blocks. Produce a set of correlated .SPB files which contain the
software product split in several packages.
v In case of remote images, you can reference them in the .SPB file using the is_image_remote option. By
enabling this option, you can specify whether image files are obtained from a directory on a remote
server at installation time.
Symptoms
When importing a software package block (.SPB file) into Tivoli Provisioning Manager using the Import
Software Product wizard, the definition and the template for the software package are not correctly set.
This information is also not displayed by the Software Package Editor on the repository.
Causes
Any software package block you import using the product wizard does not get the right template and the
right definition.
213
Symptoms
When opening an already created software package block (.SPB file) from a file repository using Software
Package Editor on AIX platforms, the operation fails and displays the following error:
The file access permissions do not allow the specified action.
Causes
This problem is caused by a permission issue related to the destination path of the file repository.
Symptoms
You cannot uninstall a software product using Tivoli Provisioning Manager and the following error
message is displayed:
DISSE0026E Software package package_name was not found in the catalog.
DISSE0005E Operation unsuccessful.; return code = 9
Causes
The uninstallation fails if the software product was installed as a software package block (SPB) without
Tivoli Common Agent.
Symptoms
If attempt a software import but entered an incorrect file name in the Software Product Import page, the
software import fails but a software product is still added to the data model.
Causes
If you entered a file path that specifies where the file is going to be imported, an import task is generated
to copy the file from the root of the file repository to the specified file path. If the file does not exist in
the root of the file repository, this task will fail, and generate an error message similar to the following:
214
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
Despite this error message, a software product was still created in the data model, but will contain an
installable that is not working because the import task failed.
Note: If the package path in the Software Product Import page was a / symbol, which specifies the root
of the file repository, then no import task is generated.
215
216
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
Symptoms
After you submit a request to start an activity plan, the activity plan does not start. The following
information can be found in the log located in the activity plan engine OSGi configuration folder
TIO_HOME/eclipse/tpmconfig/activityplan:
!ENTRY org.eclipse.update.configurator 2006-09-22 09:47:22.422
!MESSAGE Could not load from shared install
!STACK 0
java.lang.Exception
at org.eclipse.update.internal.configurator.ConfigurationParser.processConfig
(ConfigurationParser.java:304)
at org.eclipse.update.internal.configurator.ConfigurationParser.startElement
(ConfigurationParser.java:106)
at org.apache.xerces.parsers.AbstractSAXParser.startElement
(Unknown Source)
at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown Source)
...
Causes
This issue is caused by a limitation of Eclipse 3.1.2 that prevents it from starting multiple applications.
Symptoms
When saving or exporting an activity plan using the Activity Plan Editor, the following error message is
displayed:
bad magic number at offset=0
Causes
The Web browser is using a Java Runtime Environment (JRE) version that is incompatible with the
Activity Plan Editor. The Activity Plan Editor only supports Sun JRE versions 1.5.0 or newer.
217
v Uninstall JRE. The Activity Plan Editor will automatically download the appropriate JRE version the
next time the tool is used.
v Uninstall JRE and then manually install Sun JRE version 1.5.0 or higher.
Symptoms
Activity plans created using the Activity Plan Editor are displayed only in English.
Causes
The display language of the Activity Plan Editor is based on the browser locale setting and not on the
locale setting of Tivoli Provisioning Manager.
Windows
2000
UNIX
218
%SystemDrive%
/tmp
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
Symptoms
You get errors when you try to access the registry.
Causes
The registry might not be available, or might not be correctly configured.
The message contains server1 as the application server name even if the agent manager is installed in
a different application server.
Symptoms
The following security error is generated by the Firefox Web browser when a user tries to log on to Tivoli
Provisioning Manager:
Your certificate contains the same serial number as another certificate issued
by the certificate authority.
Please get a new certificate containing a unique serial number.
Copyright IBM Corp. 2003, 2011
219
Causes
The certificate generated by an agent manager instance has been trusted before and the certificate is
stored locally on the customer side. When the user tries to log on to another instance of Tivoli
Provisioning Manager with another instance of the agent manager, the agent manager will generate
another certificate, but with the same serial number.
Symptoms
The common agent or resource manager cannot register or communicate with the agent manager despite
having the correct passwords.
Causes
This can be caused by any of the following problems:
v Agent Manager configuration files, such as AgentManager.properties or Authorization.xml, are
missing or have been altered.
v Security credentials are not valid, have expired, or have been revoked.
v A common agent is being installed on a computer that already has a common agent installed on it, and
the agent manager is configured to prevent duplicate registration.
v A common agent is attempting to reregister, but that feature is not available.
This problem can be caused when trying to reinstall a common agent after uninstalling a release before
version 1.3. In earlier releases, uninstalling the common agent did not change its registry entry, and as
a result the common agent appears to be reregistering when it is reinstalled.
The same problem can occur if the common agent cannot contact the agent manager when it is
uninstalled. This might happen if the common agent is uninstalled while it is not connected to a
network.
v The clocks on the common agent or resource manager and the agent manager are not synchronized.
v The common agent cannot connect to the agent manager during the agent installation.
220
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
Symptoms
Operating system limitations might cause problems when connecting to the local DB2 database on UNIX
platforms.
Environment
The agent manager installer creates a local DB2 database named IBMCDB by default. In the local DB2
client, the entry exists under the same alias as the database name (that is, IBMCDB), which can be
displayed as follows:
db2 => list db directory
System Database Directory
Number of entries in the directory = 1
Database 1 entry:
Database alias = IBMCDB
Database name = IBMCDB
Database drive = /home/db2inst1
Database release level = a.00
Comment =
Directory entry type = Indirect
Catalog database partition number = 0
Alternate server hostname =
Alternate server port number =
The created database is then aliased under a new name in the same way, a number is appended to its
name until an unique name is found. By default, the local database is created under IBMCDB0, and the
original database name is used to alias this database, but on a virtual node (because it is local) listed
previously. This results in the following output:
Chapter 18. Agent Manager troubleshooting
221
The agent manager application is still accessing the IBMCDB database, but the connection uses a local
TCP/IP loopback. Typically when connecting to the local database, no credentials are needed because the
authorization is verified on the basis of the user system account. In this case, when aliases are created,
the user will always be asked for credentials of the authorized database user. The problem might also
arise when someone wants to drop the agent manager database. The agent manager uninstaller does not
remove the database, and therefore the aliases remain unchanged. However, to properly remove the
database manually the following commands need to be run:
db2 => uncatalog db IBMCDB DB20000I The UNCATALOG DATABASE command
completed successfully.
DB21056W Directory changes may not be effective until the directory cache
is refreshed.
db2 => catalog db IBMCDB as IBMCDB DB20000I The CATALOG DATABASE command
completed successfully.
DB21056W Directory changes may not be effective until the directory cache
is refreshed.
db2 => uncatalog db IBMCDB0 DB20000I The UNCATALOG DATABASE command
completed successfully.
DB21056W Directory changes may not be effective until the directory cache
is refreshed.
db2 => uncatalog node LHOST0 DB20000I The UNCATALOG NODE command
completed successfully.
DB21056W Directory changes may not be effective until the directory cache
is refreshed.
After issuing these commands, the database can be freely dropped using the drop db IBMCDB command.
222
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
Procedure
1. Open WebSphere Administrative Console.
Note: If you use the embedded version of IBM WebSphere Application Server, you need to install the
administrative console first.
2. Expand Environments.
3. Select Virtual Hosts.
4.
5.
6.
7.
Results
The agent recovery service is now configured not to listen on port 21080 for recovery requests.
Procedure
1. Start the administrative console.
Note: If you use the embedded version of IBM WebSphere Application Server, you need to install the
administrative console first.
2. Click Servers > Application Servers > <app_server_name> > Logging and Tracing > Diagnostic
Trace.
where <app_server_name> is the name of the application server where the agent manager applications
are installed (for example, AgentManager).
3. In the General Properties area of the Configuration page, make sure that Enable Trace is checked.
4. In the Trace Specification field on the Runtime page, type one of the values specified in the
following table:
Task
mgr.*=all=enabled
mgr.*=entryexit=enabled
mgr*=debug=enabled
mgr,*=event=enabled
The Trace Output area shows the name and path of the file that contains the trace information. A
typical location is ${SERVER_LOG_ROOT}/trace.log, where the WebSphere environment variable
${SERVER_LOG_ROOT} represents the runtime log directory, such as app_server_root/logs/
app_server_name.
5. Click OK.
6. In the Taskbar, click Save to save the change to the master configuration.
7. In the Save to Master Configuration area, click Save again to confirm the change.
223
Symptoms
Logs indicate a problem starting the certificate authority.
Causes
A common cause is a problem with the certificates.
Symptoms
You cannot start the agent manager application server.
Causes
There are multiple possible causes of this problem:
v Ensure that you are not running an application besides the agent manager server that also uses port
21080, such as a Web server application like Microsoft Internet Information Server (IIS). Such
applications cause the following error when starting agent manager server, regardless of whether you
are starting it manually or as part of the installation:
Error 100: Cannot create another system semaphore.
If you see this message, stop the conflicting application and then start the agent manager server again.
v If you get a NoServerDefinedException when you use the StartServer command to start the agent
manager application server, ensure that you specified the correct server name. Although the default
name of the agent manager application server is AgentManager, the agent manager might be in a
different application server, such as server1.
v If you configured WebSphere Application Server on UNIX or Linux to run as a user other than root
and get a FileNotFoundException exception or a Permission denied error, ensure that the user ID that
runs the WebSphere processes has permission to read the agent manager files, particularly the files in
the AM_HOME/certs directory.
224
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
Symptoms
The agent manager fails to install.
225
Agent Manager server does not install or start properly when registry
is in a database
Errors might occur if DB2 Enterprise Server Edition was not installed properly or if the server that
controls the registry database is not running.
Symptoms
The agent manager server does not install or start properly when the registry is in a database, or you
receive errors when accessing the registry.
Causes
DB2 Enterprise Server Edition might not be installed properly or the DB2 server that controls the registry
database might not be running.
226
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
A type 4 JDBC driver lets the agent manager connect to a remote database without requiring a
database client or server on the agent manager server. This type of connection is used only with a
DB2 database.
The following table summarizes how the location of the registry influences the type of database
software required and which JDBC driver is used.
Table 14. Determining what type of JDBC driver is used
Location of registry
JDBC driver
Local
Type 2
Type 2
No
Type 4
Authorization.xml
AuthXMLAddUser
AgentManager.properties
EncryptAMProps
The command returns a single output string, which is the encrypted password.
2. Copy the encrypted password from the display and paste it into the password field of the file.
3. Save the file.
v On the lightweight runtime:
1. Use the lwiEncryptPwForWCT command to encrypt a password in the lightweight runtime. The
command takes a single argument in which you enter the clear text password that you want to
encrypt. For example:
LWI_HOME/bin/lwiEncryptPwForWCT mynewpassword
227
The command returns a single output string, which is the encrypted password.
2. Copy the encrypted password from the display and paste it into the password field of the file.
3. Save the file.
Procedure
1. Stop the agent manager server if it is running.
2. If you have not already run the agent manager uninstallation wizard, run it now to remove the
agent manager entries from the installation program registry in the vpd.properties file.
3. Remove the agent manager entries from the InstallShield MultiPlatform list of installed products.
v
Solaris
2000
a. Locate the agent manager directories in the Solaris product registry. The following command is
one technique:
grep -i manager /var/sadm/pkg/*/pkginfo | grep -i agent
228
Windows
2000
%WINDIR%\vpd.properties, where %WINDIR% is the Windows installation directory,
typically C:\WINNT or C:\Windows.
AIX
2000
Linux
/usr/lib/objrepos/vpd.properties
/root/vpd.properties
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
4. If the agent manager server is configured to start automatically after a Windows system restarts, run
the following command to delete the Windows service for the agent manager.
app_server_root\bin\WASService.exe -remove "Tivoli Agent Manager"
5. Ensure that the WebSphere application files were deleted. If the following files exist in the
app_server_root/installedApps/cell directory, delete them.
v AgentManager.ear
v AgentRecoveryService.ear
6. If the agent manager server is configured to start automatically after an AIX, Linux, or Solaris system
restarts, remove the entries in the /etc/inittab file that start the server.
v Remove the following entry that starts the agent manager server. This entry exists on all systems.
In this example, WebSphere Application Server is installed in the /opt/IBM/WebSphere/AppServer
directory.
am:2345:once:/opt/IBM/WebSphere/AppServer/bin/rc.am >/dev/console 2>&1
v If the registry is in a local DB2 database, remove the entry that starts the DB2 Server. The entry is
not created if the registry is in a remote DB2 database, or a local or remote Oracle database. In this
example, db2inst1 is the DB2 user name for accessing the registry:
amdb:2345:once:su - db2inst1 -c db2start >/dev/console 2>&1
Windows
2000
AIX
C:\Program Files\IBM\AgentManager
2000
Linux
Solaris
2000
/opt/IBM/AgentManager
Note: On a Windows system, you might have to restart the system before you can delete the agent
manager installation directory.
Procedure
1. Optionally, remove the agent manager objects from the registry database.
229
Note: Only remove the agent manager tables from the database or remove the registry database if all
products that use the registry have been uninstalled.
2. If the database is shared with other programs, remove the agent manager-specific tables from the
database by following the procedure for your database type. You can do this step on the agent
manager server, even if the registry is in a remote database.
3. Delete the LWI_HOME/runtime/agentmanager directory.
4. If no other programs are using the lightweight runtime, you can optionally delete the
LWI_HOME/runtime/agentmanagerdirectory.
a. Remove the entries for the agent manager ports from the LWI_HOME/conf/webcontainer.properties
file. For example, remove the statements shown in bold face type to delete the configuration for
the default ports 9511, 9512, and 9513:
#Web Container SSL configuration properties
#Mon Jun 05 22:53:38 CDT 2006
com.ibm.ssl.clientAuthentication.9512=true
com.ibm.ssl.keyStorePassword.9512=[xor] /Mqp9w\=\=
com.ibm.ssl.clientAuthentication.9511=false
com.ibm.ssl.keyStorePassword.443=[xor] 9MW08GTL+uut1b0\=
com.ibm.ssl.keyStorePassword.9511=[xor] /Mqp9w\=\=
com.ibm.ssl.keyStore.9512=
../agentmanager/eclipse/plugins/AgentManager/certs/agentManagerKeys.jks
com.ibm.ssl.keyStore.9511=
../agentmanager/eclipse/plugins/AgentManager/certs/agentManagerKeys.jks
com.ibm.ssl.keyStore.443=/../../security/keystore/ibmjsse2.jks
com.ibm.ssl.trustStorePassword.9512=[xor] /Mqp9w\=\=
com.ibm.ssl.trustStorePassword.9511=[xor] /Mqp9w\=\=
com.ibm.ssl.clientAuthentication.443=false
com.ibm.ssl.trustStore.9512=
../agentmanager/eclipse/plugins/AgentManager/certs/agentManagerTrust.jks
com.ibm.ssl.trustStore.9511=
../agentmanager/eclipse/plugins/AgentManager/certs/agentManagerTrust.jks
com.ibm.ssl.trustStore.443=/../../security/keystore/ibmjsse2.jts
sslEnabled=true
com.ibm.ssl.trustStorePassword.443=[xor] 9MW08GTL+uut1b0\=
b. Delete the entries for the agent manager ports from the LWI_HOME/conf/overrides/
config.properties file. The statements to delete are shown in bold face type:
#LWI port configuration properties
#Fri Jun 02 17:23:04 CDT 2006
com.ibm.pvc.webcontainer.vhost.configfile=
C\:\\LWI7.0\\conf\\overrides\\VHost.properties
com.ibm.pvc.webcontainer.port.secure=[9512,9511]
com.ibm.pvc.webcontainer.port=9513
c. Change the default launch profile for the lightweight runtime in the config.properties file in the
LWI_HOME/conf directory. In the following example, bold face type indicates the line that must be
changed:
#
# Default Launch Profile used for LWI
#
com.ibm.lwi.profile=profile.AgentManager
#
# LWI Launch Profile definitions
#
profile.Base=base
profile.Agent=agent,agent/subagents
profile.AgentManager=baseutils,database,uimin,agentmanager
profile.UIMin=uimin
profile.UIFoundation=uimin,uifoundation
profile.UIMax=uimin,uifoundation,uimax
profile.Console=console,uimin,uifoundation
profile.Webservices=webservices
profile.Endpoint=agent,agent/subagents,baseutils,console,uimin,uifounda...
profile.Extended=baseutils,console,database,uimin,uifoundation,uimax,...
230
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
Select one of the other profiles defined in the lightweight runtime launchprofile section of the file.
The default value of the profile for the lightweight runtime is profile.UIFoundation. To restore
that value, change the profile specification as shown in this example:
#
# Default Launch Profile used for LWI
#
com.ibm.lwi.profile=profile.UIFoundation
Results
The agent manager is now removed from the lightweight runtime.
Symptoms
The agent manager rejects requests for registration.
Causes
Either of the following issues will cause the agent manager to reject requests for registration:
v You gave an incorrect resource manager user name or password.
v You specified a resource manager user that does not have the authority to register the specified type of
resource manager.
Symptoms
The common agent or resource manager can initially contact the agent manager but then fails farther
along in the contact process.
Causes
The agent manager was configured with a short host name instead of a fully qualified host name, or is
otherwise configured with a host name that cannot be resolved by the common agent or resource
manager.
231
Procedure
Use the health check tools that are available in the toolkit/bin subdirectory of the agent manager
installation directory (AM_HOME).
Note: Do not use theWebSphere Application Server serverStatus command to determine whether the
agent manager is running. An application server can start even if it is not fully operational. For example,
if the registry database is inaccessible because of a network or authorization problem, the serverStatus
cannot register common agents or process database queries from resource managers without access to the
registry.
Procedure
v To display the version of the agent manager application, run the following command:
Windows
2000
AM_HOME\bin\GetAMInfo.bat AgentManager
UNIX
2000
Linux
Solaris
2000
HPUX
AM_HOME/bin/GetAMInfo.sh AgentManager
Note: The application name, AgentManager, is not related to the name of the application server in
which you install the agent manager. For example, if you install the agent manager in to the
application server named server1, the application name remains AgentManager.
v To display the version of the agent recovery service, run the following command:
Windows
2000
AM_HOME\bin\GetAMInfo.bat AgentRecoveryService
UNIX
2000
Linux
Solaris
2000
HPUX
AM_HOME/bin/GetAMInfo.sh AgentRecoveryService
Symptoms
When installing a common agent, the agent manager rejects its request for registration.
Causes
232
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
The wrong agent manager or resource manager password causes the agent manager to reject the request
for registration from the common agent.
233
234
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
Symptoms
Authentication errors occur after installing the common agent.
Causes
Authentication errors can be caused by the following:
1. Incorrect password.
2. Corrupted or missing authentication files in agent_installdir\cert directory, where agent_installdir is
the agent installation directory.
UNIX
2000
Linux
jre/bin/java -cp lib/ep_install.jar:lib/ep_common.jar
com.tivoli.agent.install.EncrPwdInConfFile config/endpoint.properties
Registration.Server.PW password
3. Restart the common agent.
Symptoms
When the common agent is installed on HP-UX, the agent ID cannot be read, preventing the common
agent from registering. This problem is intermittent. The following information is written to the log:
Copyright IBM Corp. 2003, 2011
235
java.lang.Exception: 231628960
at com.tivoli.agentmgr.resources.GUIDHelper.getHostId
(GUIDHelper.java:53)
at com.tivoli.agent.id.IDServiceImpl.getEndpointId
(IDServiceImpl.java:99)
at com.tivoli.agent.id.IDServiceImpl.checkForOEMInstall
(IDServiceImpl.java:60)
at com.tivoli.agent.id.IDActivator.start(IDActivator.java:54)
at com.ibm.osg.smf.BundleContext$1.run(BundleContext.java:1300)
at java.security.AccessController.doPrivileged(Native Method)
at com.ibm.osg.smf.BundleContext.start(BundleContext.java:1282)
at com.ibm.osg.smf.Bundle.startWorker(Bundle.java:709)
at com.ibm.osg.smf.Bundle.start(Bundle.java:655)
at com.tivoli.agent.system.SMFLauncher.startSMF(SMFLauncher.java:240)
at com.tivoli.agent.system.SMFLauncher.main(SMFLauncher.java:94)
Caused by: 231628960
at com.tivoli.srm.guid.GuidOFactory.<init>(GuidOFactory.java:79)
at com.tivoli.agentmgr.resources.GUIDHelper.getHostId
(GUIDHelper.java:48)
... 10 more
Causes
Java exception #231628960 means that the GUID shared library cannot be read.
236
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
Use the kill -9 command to stop both processes. Stop both processes quickly, to prevent them
from starting each other up again.
v Other operating systems:
ps -aef | grep nonstop
ps -aef | grep java
Use the kill command to stop the process ID with the lowest number for each process. (Linux
has multiple process IDs shown, pointing up to lowest starting ID).
3. Use the uninstallation wizard to uninstall all common agents on the workstation. If more than one
common agent is installed, run the wizard for each one. For any common agent that you can not
uninstall, delete the common agent installation directory, including all files and subdirectories.
4. Clean up the ep.reg file and, if it exists, the ep.bak file:
v If you are uninstalling all common agents from the system, delete both files.
v If you are uninstalling a specific common agent, delete the line in each file that lists the
installation directory of the common agent you are uninstalling. For example, to uninstall the
common agent installed in the /opt/tivoli/ep1 directory, delete the line that begins like this:
0 | cygnus0317b | /opt/tivoli/ep1 | 1.3.0.5 | 0 | 1.4.2 | IBM Corp...
237
8. Remove the entry for the common agent in the registry. On the server, use the RetrieveAgents,
PurgeAgents, and LogicallyDeleteAgents utilities to identify and remove registry entries for the
common agent.
9. On Windows operating systems, restart the operating system to remove the Windows service.
10. Optionally, delete the common agent installation directory.
11. Optionally, uninstall the Tivoli GUID. On Windows, use Add or Remove Programs to uninstall
TivGuid.
The common agent is removed from your system.
Procedure
1. Switch off the security enhancement using either of these commands:
setenforce 0
or
echo 0 > /selinux/enforce
2. Install the common agent.
3. Turn on the security enhancement back using either of these commands:
setenforce 1
or
echo 1 > /selinux/enforce
4. Restart the computer.
What to do next
The common agent is now installed.
Symptoms
The common agent does not detect the IP address change.
Causes
238
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
Symptoms
After installation, the common agent is unable to read the GUID upon startup on Linux x86 and Linux
ppc. The following message is logged in the traceAgent.log file when the common agent is starting up
and tries to read the GUID:
13:05:18.980+01:00 com.tivoli.agent.id.IDServiceImpl
getEndpointId main java.lang.Exception: 231628950
Causes
The GUID failed to install. During the installation of the common agent, the Tivoli GUID is installed.
After the common agent is installed, it attempts to read the GUID upon startup. If the agent cannot read
the GUID, it will fail to start.
Symptoms
You cannot install the common agent on a Solaris computer system.
Causes
Due to a known limitation with Java Runtime Environment (JRE) for Solaris 1.3.1, you cannot install the
common agent on a Solaris computer system if you are using any of the following locales:
-en_US.UTF-8
-de_DE.UTF-8
-fr_FR.UTF-8
-it_IT.UTF-8
-es_ES.UTF-8
239
Set the locale of the Solaris system to a non-UTF-8 locale to perform the installation. Use the export LANG
command to set the locale. For example, run the command export LANG=fr_FR.ISO8859-1 to change the
locale to fr_FR.ISO8859-1. After the installation is complete, reset the system to the original locale. You
can use common agent commands to check and change the locale:
1. Ensure that the common agent is running.
2. Change to the directory where the common agent is installed.
3. Run the following command to check the current locale setting:
agentcli logmgr getlocale
where language is a two-letter lowercase code defined by ISO-639 and region is a two-letter
uppercase code defined by ISO-3166.
For example, to set the location to United States English, use the following command:
agentcli logmgr setlocale en US
Symptoms
You cannot register target computers with the provisioning server in a firewall environment.
This issue has been described in an environment where a firewall is used between the provisioning server
and the target computers. The updated firewall toolkit from Tivoli Provisioning Manager 5.1.0.1 (Fix Pack
1) has been used.
This behavior has been consistently described in firewall environments, and occasionally in non-firewall
environments.
Causes
The target computers cannot complete their registration with the provisioning server when the firewall
toolkit is used.
The process appears to work properly up to the final step when the target certificate is passed back to the
target computer. The certificate is not created on the target computer (only three files are created in the
cert directory on the target, namely agentTrust.jks CertificateRevocationList, and pwd). When the
provisioning server attempts to create a target, it is able to connect to the target, install the common agent
binaries, and start the agent. The agent is able to communicate back to the provisioning server, but the
final certificate file (target key file) is not created on the target computer.
240
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
Symptoms
Common agent installation fails on Red Hat 5 with the following error message:
COPDEX123E A AgentInstallException exception occurred.
The exception was caused by the following problem:
Agent failed to Install with install error:
The installation process was cancelled by the user.
In the workflow logs, the following error is reported by Tivoli Provisioning Manager:
std err:
Log: common_agent_1.4.2.0_200902171611_linux.tar has been extracted into /tmp/tcatemp
Log: common_agent_1.4.2.0_200902171611_linux.tar has been removed from /tmp/tcatemp
Log: agentTrust.jks copied to: /tmp/tcatemp/cert
No Java Runtime Environment (JRE) was found on this system
Causes
Red Hat 5 has the Security-Enhanced Linux firewall utility enabled by default. This firewall prevents
Tivoli Provisioning Manager from installing the common agent.
Note: You can manually check if the firewall is enabled by entering the getenforce command at a Linux
command line. If enforcing is returned, it means the firewall is enabled.
v Edit the configuration file on the Linux computer. The file is found in the /etc/selinux/config
directory. In the file, find this line:
SELINUX=enforcing
241
Procedure
To determine the version of the currently installed common agent, run the following command:
v On
Windows
2000
operating systems:
%CA_HOME%\endpoint.bat version
Results
The output of the command indicates the version, major release, minor release (modification level), and
fix pack level of the common agent. It also includes a build identifier.
Windows
2000
service
UNIX
2000
Linux
service.sh
v
The script creates an archive file named CASservice.zip file in the Install directory.
If you have more than one common agent on a managed system, run the tool in the Install directory of
the common agent for which you want to capture diagnostic information.
Note: If you plan to send multiple CASservice.zip files to IBM Software Support, rename the files so that
they each have unique names.
Symptoms
If the compliance check Require Tivoli Common Agent (TCA) 1.4.2 is created and the end file does not
have Tivoli Common Agent installed, a recommendation to install Tivoli Common Agent 1.4.2 will be
provided. After installing Tivoli Common Agent 1.4.2, TCA 1.4.2 will show up in the installed software
list of the target computer but has not actually been installed.
Causes
A remediation workflow calls the provisioning workflow SoftwareModule.Install against Tivoli Common
Agent 1.4.2, but the result that it produces is incorrect. It creates a Tivoli Common Agent 1.4.2 installation
on the provisioning server, but does not install Tivoli Common Agent 1.4.2 on the target computer.
242
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
To verify that the Tivoli Common Agent is installed, create a compliance check against the Tivoli
Common Agent stack instead of against Tivoli Common Agent 1.4.2.
Useful commands
A list of common agent commands, including commands for uninstalling and logging.
Symptoms
Uninstall the common agent and subagents.
1. Change to the following directory:
v
Windows
2000
UNIX
: C:\Program Files\tivoli\ep\_uninst
2000
Linux
: /opt/tivoli/ep/_uninst
AIX
: /usr/tivoli/ep/_uninst
v
2. Run the following command
Windows
2000
UNIX
2000
Linux
./uninstall -console
Windows
2000
: C:\Program Files\tivoli\ep\runtime\agent
UNIX
2000
Linux
: /opt/tivoli/ep/runtime/agent/
v
2. Run the following command:
Windows
2000
: C:\Program Files\tivoli\ep\runtime\agent
UNIX
2000
Linux
: /opt/tivoli/ep/runtime/agent/
v
2. Run the following command:
Windows
2000
service.bat
UNIX
2000
Linux
service.sh
243
In the event of a common agent or subagent problem, you can either schedule a task using this workflow
or run the workflow to collect the target computer logs. The workflow provides information regarding
the target computer on which the common agent is running.
For each target computer that the workflow is run against, the %TIO_LOGS%\tivolicommonagent directory
($TIO_LOGS/tivolicommonagent for UNIX or Linux) on the Tivoli Provisioning Manager server receives an
archive (.zip or .tar) with the deviceID_IDnumber_TimeStamp_actualTimeStamp_CASservice.zip/tar file
name. The archive contains all the startup and console logs for that target computer, and can be used for
troubleshooting or sent to IBM Software Support for analysis.
Symptoms
On Windows, Tivoli GUID fails to install properly and the following error is given in the
runtime/agent/logs/guid_install.log log file:
Failed to connect to server. Error: 0x80070422
Causes
If you install the common agent, the installer also installs the Tivoli GUID component. On Windows
platforms, the Microsoft Windows Installer is responsible for that. For this reason, the Windows Installer
system service cannot be turned off, or else the first error will be caused. Moreover, when installing Tivoli
GUID there cannot be any other MSI installations in progress, which is the cause of the second error.
Symptoms
You cannot reinstall the common agent on Windows.
Causes
The Windows computer was not restarted after the previous Tivoli common agent was uninstalled. In
some cases, if Windows cannot delete a service, it will mark that service for deletion on the next restart of
the computer. In these cases, the common agent installer will not be able to install the common agent
because the installer detects the previous common agent which, although marked for deletion, still exists
until the next restart.
244
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
Symptoms
An installation on a UNIX operating system fails when using copy or put file commands.
Causes
The /tmp directory or device might be full on the UNIX computer. The common agent installation copies
files to the /tmp/tcatemp directory.
Symptoms
The Tivoli Common Agent installation fails. You cannot use the default level of the Windows user access
control mechanism for Windows 7 target computers.
Causes
There are four security levels for Windows UAC on Windows 7 computers. Level 3, which is the default
level, does not allow Tivoli Common Agent to be installed.
Environment
Tivoli Provisioning Manager v7.1.1 and Windows 7 target computers.
Symptoms
The IBM Tivoli Common Agent discovery scan fails after manually removing the C:\Program
Files\tivoli\cit directory (opt/tivoli/cit for UNIX). For example, you might have removed this
directory manually when uninstalling the common agent and then encountered this failure after
reinstalling the common agent.
245
Causes
Common Inventory Technology (CIT) is a shared component that must not be removed manually. If you
manually delete the CIT directory from a target computer, all of the products and technologies that are
installed on that computer and are reliant on CIT will fail.
Description
error-log-0.xml
error-log-1.xml,
error-log-2.xml
error-log-3.xml
nonstop.log
nonstopbundle.log
trace-log-0.xml
trace-log-1.xml,
trace-log-2.xml, or
trace-log-3.xml
The following table lists the runtime logs for the common agent and subagents.
Table 16. Installation logs for the common agent
Log File
Description
$CA_HOME/runtime/agent/logs/agentcli.log.0
$CA_HOME/runtime/agent/logs/install/epInstall.log
$CA_HOME/runtime/agent/logs/install/
epInstallStatus.log
$CA_HOME/runtime/agent/logs/install/
epUnInstallStatus.log
246
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
Description
AgentCliErr.log*
AgentCliOut.log*
InstallNonstopUtilErr.log*
InstallNonstopUtilOut.log*
lwiJavaHomeErr.log
lwiJavaHomeOut.log
LwiStatusErr.log*
LwiStatusOut.log*
SetFileSecurityErr.log*
SetFileSecurityOut.log*
tivGuidInstallErr.log
tivGuidInstallOut.log
WindowsInstallUtilErr.log*
WindowsInstallUtilOut.log*
winTivGuidInstall.log
Symptoms
After upgrading the common agent, the computer name is not updated. If there was already a system
with a name in the data model, the name does not change on subsequent discoveries, even if the host
name reported by the agent changed.
Causes
The computer name is not updated
Symptoms
A security error (for example, SSLHandshakeException) occurs when:
v The common agent attempts to register with the agent manager.
v The common agent is contacted by another entity (for example, a resource manager) already registered
with the agent manager.
Causes
247
The system clock on the agent system does not match the clock on the agent manager computer. The
agent manager compares the clocks in Universal Time Coordinated (UTC).
Symptoms
The endpoint.properties file is truncated (approximately 6-8 lines long instead of approximately 20). The
common agent cannot register and cannot be uninstalled.
Causes
Windows was not restarted after uninstalling the common agent. This problem can occur in the following
situation:
1. The user tries to uninstall the common agent, but the common agent uninstaller on Windows cannot
delete the endpoint.properties file if it is locked or in use. It therefore queues deletion for the next
restart.
2. The user installs a new common agent in the same directory, which creates a new
endpoint.properties file that must not be deleted, but the file is still queued for the next restart.
3. When the user reboots the computer, the endpoint.properties file is deleted from the newly installed
common agent.
4. When the common agent starts, it tries to register and creates a truncated version of the
endpoint.properties file. The common agent cannot work properly. It cannot register because the
port value is missing in endpoint.properties file, resulting in a parsing error. It also cannot be
uninstalled because the uninstaller is looking for values in the endpoint.properties file that are not
there.
Symptoms
You receive an SSLHandshakeException exception while installing a resource manager or common agent.
Causes
The signer certificate on the resource manager or common agent do not match the certificates offered by
the agent manager server when the two computers attempt to set up a secure SSL connection. If the
certificates do not match, the resource manager or common agent cannot determine whether it is
communicating with the correct agent manager server.
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
1. If you just created new certificates for the agent manager server, make sure that the agent manager
server was restarted after the new certificates were created. The agent manager server will not start
using the new certificates until it restarts.
2. Make sure that the resource manager or the common agent have a copy of the current truststore file
for the agent manager server. The truststore file contains the signer certificate for the agent manager
server. A simple way to do this is to copy the file to the resource manager or the common agent
again.
3. Try the program that failed again.
Symptoms
Testing communication with the TCA_PingAgent workflow hangs on Windows computers.
Causes
A nonstop process might still be running because the previous uninstall did not remove all components.
This error might indicate that the common agent cannot open the port, which means that it is already
open by something else.
249
Procedure
v Check the msgAgent.log file in the agent_installdir\logs directory for any errors that might have
occurred during installation.
v On a Windows endpoint, you can open the Windows Services control panel and look for a service
called IBM Tivoli Common Agent. Make sure that the service is started.
v At a command prompt, run the following command from the common agent installation directory:
Windows
2000
2000
Linux
Symptoms
Files from a recently installed Tivolicommon agent are deleted after the computer is restarted.
Causes
In some cases, Windows will mark files for deletion upon the next restart if it cannot delete those files
during the uninstallation process. If a user uninstalls Tivoli Common Agent and Windows cannot delete
all the files immediately, it will mark them for deletion upon restart. If the user installs another version of
the common agent on that computer without restarting, the files that were marked for deletion will be
deleted upon the next restart of that computer.
where service_name is the name of the service listed in the Windows Services control panel. The
default service name is IBMTivoliCommonAgent0.
v Method 2: Use the Regedit program to delete the service from the Windows Registry.
2. Remove the common agent entry from the common agent registry (located in %ProgramFiles%\tivoli\
ep.reg). You might have more than one entry if you have more than one common agent on that
computer. Remove only the entry for this common agent, which you can identify by its installation
location.
250
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
Procedure
1. Stop the common agent.
2. Delete the contents of agent_installdir/runtime/agent/cert.
3. Verify that the agent.ssl.truststore.download parameter is set to true in file endpoint.properties
located in agent_installdir/runtime/agent/config.
4. Restart the common agent.
Symptoms
You cannot register either the common agent or the resource manager.
Causes
This can happen if you select the installation option to provide a copy of the agentTrust.jks truststore
file to the common agent or resource manager, and then point to the wrong file. For example, you might
point to the agentTrust.jks file in the cert directory of the installation image instead of pointing to the
real file on a network share. Another possible cause is that you pointed to the agentTrust.jks file of your
production environment when the common agent or resource manager is connecting to a test
environment.
Symptoms
Chapter 19. Common agent problems
251
Uninstalling the common agent manually results in the status being refreshed to display stopped. The
status must be updated as uninstalled.
Causes
The common agent status will not be updated to uninstalled. The common agent uninstall will not send
a message to the provisioning server. The Agent Manager is updated.
Symptoms
The installation of the common agent on a target computer fails.
Causes
The password for the common agent on the target computer contains a double quotation mark. The
double quotation mark is not a valid character.
Symptoms
The installation of the common agent returns the following error:
The response file parameter CASInstall.InstallType
contains an unsupported value or is not specified.
The value must be install or upgrade.
Causes
The target computer already had an agent installed that is not the currently supported agent version.
252
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
Symptoms
Communication problems between the common agents and the agent manager might include, for
example, a failed ping agent, or failed subagent installations when installing the common agent.
Causes
The Domain Name Server (DNS) was not set up properly. By default, the agent manager requires the
common agent computers to be able to resolve the fully qualified name of the agent manager server.
Symptoms
Tivoli Common Agent installation fails on Solaris SPARC target computers with the following error
message:
COPDEX123E A AgentInstallException exception occurred. The exception was caused by the following problem:
Agent failed to install with install error: The installation process was cancelled by the user.
Causes
The target computers are missing required SUNW packages, such as SUNWxcu4.
253
Symptoms
Registration of device manager targets causes an OutOfMemory error. The error appears in the WebSphere
Application Server log file %WAS_HOME%\profiles\ctgAppSrv01\logs\MXServer\SystemOut.log in Windows
($WAS_HOME/profiles/ctgAppSrv01/logs/MXServer/SystemOut.log in UNIX or Linux).
where host_name is the WebSphere Application Server host name and port is the secure host port. The
default port number is 9443.
2. Change the number of open connections.
a. Navigate to Servers > Application servers > server_name > Ports.
b. Click View associated transports for the appropriate port.
c. Change the Maximum open connections setting to 2500.
3. Change the maximum heap size:
a. Navigate to Servers > Application servers > server_name > Process Definition > Java Virtual
Machine.
b. Change the Maximum Heap Size setting to 1024 MB.
254
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
Distribution
The Dynamic Depot Selection (DDS) algorithm in dynamic content delivery determines the best depots in
which to cache a file when it is passed into a list of target computers. It uses a configurable ratio between
depots and target computers to figure out how many depots to put in the target list.
It generates a custom target list for the deployment. You will not see this target list in the list of user
defined target lists. The default ratio between depots and target computers is 50. If you do not have more
than 50 target computers, it will only put the file on a single depot. For example, if you have 100 target
computers, and CDS_DDSS_RATIO=20 then it will try to publish to 5 depots. That is, if 5 depots have been
created.
You can change this ratio by creating a variable with the name CDS_DDSS_RATIO under Systems
Mangement > Global Settings.
Retry window
The retry window represents the time, in seconds, that a distribution is set to expire. The distribution will
expire so that the client can keep retrying the download if it fails (for example, if the management center
is too busy or the depot servers are too busy during the first try). By default, Tivoli Provisioning Manager
sets the retry value to 7200 seconds.
You can change this window by creating a variable named retryWindowSec under Systems Management
> Global Settings. The value of maxRetryIntervalSec is the maximum time to wait between retries, in
seconds. The default for this value is 30 seconds. You can change the default value by creating a variable
with name maxRetryIntervalSec and specifying its value in seconds.
Procedure
1.
2.
3.
4.
255
Symptoms
When you create a depot, ensure that you specify a directory relative to the subagents directory. If you do
not, you will receive the following error:
CTGDEC119E The cache manager sub-component detected a failure
during an I/O operation.
The error was: Unable to create directory.
The file was: C:\Program Files\tivoli\ep\subagents\cds\C:\data
Symptoms
The reinstallation of a depot server, which has been previously deleted from the Manage Depots page
using the Remove option might fail with the following exception recorded in the agentInstall.log file:
...
com.tivoli.cas.install.common.InstallGUID, err, java.lang.Exception:
Cannot get system GUID
STACK_TRACE: 14
java.lang.Exception: Cannot get system GUID
at
com.tivoli.agentmgr.resources.GUIDHelper.getSystemGuid(GUIDHelper.java:247)
at
com.tivoli.cas.install.common.InstallGUID.saveGUID(InstallGUID.java:139)
at
com.tivoli.cas.install.common.InstallGUID.execute(InstallGUID.java:129)
at
com.installshield.wizard.RunnableWizardBeanContext.run(RunnableWizardBeanContext.java:21)
Caused by: java.lang.Exception: 231628960
at
com.tivoli.agentmgr.resources.GUIDHelper.getHostId(GUIDHelper.java:83)
at
com.tivoli.agentmgr.resources.GUIDHelper.getSystemGuid(GUIDHelper.java:241)
...
256
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
Causes
The depot server was deleted and unregistered from the dynamic content delivery management center,
but the GUID is still present. The depot needs to be completely removed from that computer
Procedure
1. Add the following line to the %TIO_HOME%\config\log4j.prop file:
log4j.category.com.ibm.tivoli.orchestrator.datacentermodel.helper.
ComplianceHelper=<LOG LEVEL>
2. Set the value of <LOG LEVEL> to anything higher than DEBUG. For example, OFF, FATAL, ERROR, or WARN
are all valid entries.
Procedure
v cds_trace_depot.log: Search for addFile: It will indicate if the file was published.
v error-log.#.xml: This log will verify if it received a job to process. Look for a message that is similar
to this:
2006.04.24 15:08:43-05:00 JES023I Processing job: name = SPBDistribute,
requestId = 20dc8ea1d3ce11dabc68000d609d5a54
All log files for the common agent can be collected at Log files for the common agent on page 246
v tmp.log: This log will verify if it received a call, copyFile, to the FileManagementService. Look for a
message that is similar to this:
Chapter 20. Dynamic content delivery troubleshooting
257
Description
ERROR
WARN
INFO
All messages (informational, warning and error) are logged. No tracing is logged.
DEBUG_MIN
DEBUG_MID
DEBUG_MAX
By default, the logging and tracing level of all components is set to DEBUG_MIN. To configure the logging
and tracing level of a component, set the component_name.logger.level property for that component in
the cdsLog.properties file to the required level.
For example, to set the logging and tracing level for a depot server to the maximum setting, set the
server.logger.level property in the depot server cdsLog.properties file to DEBUG_MAX as shown in the
following example:
server.logger.level=DEBUG_MAX
258
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
file_name1.log
The log file previous to file_name.log.
file_name2.log
The log file previous to file_name1.log.
For example, the depot server writes messages to msg_depotserver.log. When that file reaches 8 MB, it is
renamed msg_depotserver1.log and a new msg_depotserver.log file is created. When that file reaches 8
MB, msg_depotserver1.log is renamed msg_depotserver2.log, msg_depotserver.log is renamed
msg_depotserver1.log, and a new msg_depotserver.log is created.
To configure the maximum number of log and trace files for a component, set the
component_nameFileHandler.maxFiles property for the component in the cdsLog.properties file. For
example, to set the maximum number of log and trace files for the depot server to 5, set the
serverFileHandler.maxFiles property in the depot server cdsLog.properties file as shown in the
following example:
serverFileHandler.maxFiles=5
To configure the maximum size of log and trace files for a component, set the
component_nameFileHandler.maxFileSize value for the component in the cdsLog.properties file. Specify
the value in KB.
For example, to set the maximum size of log and trace files for the depot server to 10 240 KB (10 MB),
set the serverFileHandler.maxFiles property in the depot server cdsLog.properties file as shown in the
following example:
serverFileHandler.maxFileSize=10240
Description
ERROR
WARN
INFO
All messages (informational, warning and error) are logged. No tracing is logged.
DEBUG_MIN
DEBUG_MID
DEBUG_MAX
By default, the logging and tracing level of all components is set to DEBUG_MIN. To configure the logging
and tracing level of a component, set the component_name.logger.level property for that component in
the cdsLog.properties file to the required level.
For example, to set the logging and tracing level for a depot server to the maximum setting, set the
server.logger.level property in the depot server cdsLog.properties file to DEBUG_MAX as shown in the
following example:
server.logger.level=DEBUG_MAX
259
file_name1.log
The log file previous to file_name.log.
file_name2.log
The log file previous to file_name1.log.
For example, the depot server writes messages to msg_depotserver.log. When that file reaches 8 MB, it is
renamed msg_depotserver1.log and a new msg_depotserver.log file is created. When that file reaches 8
MB, msg_depotserver1.log is renamed msg_depotserver2.log, msg_depotserver.log is renamed
msg_depotserver1.log, and a new msg_depotserver.log is created.
To configure the maximum number of log and trace files for a component, set the
component_nameFileHandler.maxFiles property for the component in the cdsLog.properties file. For
example, to set the maximum number of log and trace files for the depot server to 5, set the
serverFileHandler.maxFiles property in the depot server cdsLog.properties file as shown in the
following example:
serverFileHandler.maxFiles=5
To configure the maximum size of log and trace files for a component, set the
component_nameFileHandler.maxFileSize value for the component in the cdsLog.properties file. Specify
the value in KB.
For example, to set the maximum size of log and trace files for the depot server to 10 240 KB (10 MB),
set the serverFileHandler.maxFiles property in the depot server cdsLog.properties file as shown in the
following example:
serverFileHandler.maxFileSize=10240
Contents
cdsLog.properties
msg_admingui.log
trace_admingui.log
msg_cdsmgr.log
trace_cdsmgr.log
msg_cdssec.log
trace_cdssec.log
260
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
Table 19. Log and trace files for the management center (continued)
File name
Contents
msg_distribution.log
trace_distribution.log
msg_monitoring.log
trace_monitoring.log
msg_client.log
trace_client.log
msg_EPM_Install.log
trace_EPM_Install.log
MC_DB_Install.err
MC_DB_Install.out
MC_WAS_*
msg_EPM_Install.log
trace_EPM_Install.log
trace_manager_install.log
trace_rxa.log
msg_rxa.log
CDS_DB2_install_schema.log
The log and trace files are in ASCII format. If an .err file displays 0 KB as file size, the file might not
necessarily be empty.
Symptoms
The silent installation of the dynamic content delivery management center fails.
Causes
The value of the LICENSE_ACCEPT_BUTTON parameter is not set to TRUE.
261
The service access points for software distribution were not created
automatically
This will occur if the tpmserver.xml and infrastructure.xml files were not successfully imported as part
of the agent installation.
Symptoms
The service access points on the Tivoli Provisioning Manager server, the file repository for the dynamic
content delivery management center, and the variables that are required for software distribution using
the scalable distribution infrastructure are not created automatically.
Causes
The tpmserver.xml and infrastructure.xml files were not successfully imported as part of the agent
installation.
Windows
2000
%TIO_LOGS%\install\xmlimport.log
%TIO_LOGS%\install\xmlimport_soa.log
v
UNIX
$TIO_LOGS/install/xmlimport.log
$TIO_LOGS/install/xmlimport_soa.log
Symptoms
There are two servers on Tivoli Provisioning Manager server. When a file is published on the first server,
it is also published on the second depot server.
Causes
There is not enough space on the first depot server to save a file.
Symptoms
262
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
After successfully uninstalling the depot agent stack, you find that the entry for the depot stack in Tivoli
Provisioning Manager has not been removed.
Causes
The uninstallation of the depot does not link with the removal of the depot from the dynamic content
delivery system. It will cause the depot to still exist in Tivoli Provisioning Manager even though the
depot is not available. Any files published to this depot will not get to the depot until a new depot is
installed again for the same depot instance on the same computer.
Symptoms
On the Depot page, if the data directory limit value is changed, the used space value is not updated
automatically.
Causes
The value for the used space is refreshed every 24 hours.
263
264
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
Symptoms
Agent receives an HTTP Unauthorized (401) response code.
Causes
Agent can receive an Unauthorized (401) response code for a number of reasons, including:
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.
v The client certificate provided as part of the SSL handshake was revoked.
Description
/TEMP_DIR/DMS_install.log
/TEMP_DIR/DMS_uninstall.log
/DeviceManager/log/dms_config_trace.log
265
Description
/DeviceManager/log/dms_migrate_trace.log
Symptoms
Running a lightweight management server with DB2 generates some exceptions.
Causes
Some device classes (plug-ins) are not configured to run with a lightweight device management server.
You might receive exceptions for the missing device classes. However, a lightweight device management
server will start and run normally with its more limited set of device classes. You might also receive
exceptions if the database cannot be accessed.
266
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
Symptoms
A manual installation of device manager service hangs for an indefinite amount of time without an error
message.
Causes
The SSL configuration is incorrect. Ensure that the properties files are on the correct drive and that any
use of a backslash (\) on Windows is escaped, (\\). For example, here is a correct
DMSSLConfig.properties file:
TPM_KEYSTORE_LOCATION=C:\\IBM\\tivoli\\tpmfsw\\cert\\agentKeys.jks
TPM_KEYSTORE_PASSWORD=[xor] 7PfsyzDMzebo05HrTPXGxQ==
TPM_TRUSTSTORE_LOCATION=C:\\IBM\\tivoli\\tpmfsw\\cert\\agentTrust.jks
TPM_TRUSTSTORE_PASSWORD=[xor] 7PfsyzDMzebo05HrTPXGxQ==
267
The current values for these parameters are located in the jes.properties file in the common agent.
When you run the workflow, the target computer will update the property file and then set the runtime
value without restarting the common agent.
If the common agent is not able to save the change to the property file, the workflow will fail and the
runtime value will remain unchanged. The property file has to be updated, or else restarting the common
agent or rebooting the computer will revert the file to its original value.
Procedure
1. Check if publishing was successful. Look at the TIO_LOGS\console.log file on the Tivoli Provisioning
Manager server. The file might need to be replicated to the depot server. Verify that the file is on the
depot.
Note: If you do not publish explicitly, then the dynamic publishing will be used.
2. Check if the job was submitted successfully. Look at the TIO_LOGS\console.log file on the Tivoli
Provisioning Manager server.
3. On the target computer, check if a job is received for processing. Look at the ep_install_dir
error-log-#.xml file. You can check the agent log files by following the instructions at the following
link: Information for troubleshooting software package blocks on Tivoli Common Agent computers
on page 210. The debug mode must be turned on to see the following: INFO: JES023I Processing job:
name = SPBInstall, requestId.
4. Look for a call to the FileManagementService, copyFile: INFO: TPMFMS001I File copy:...
5. Check to see if the job has been processed, and the related status is success.
6. Check the status of the job completion event sent back to the device manager: INFO: ****RECEIVED
JOB STATUS EVENT com.ibm.tivoli.osgi.service.event.Event@109558d.
7. Check the dynamic content delivery cds_trace_client.log file. Verify the following:
a. JES requests the file from the dynamic content delivery:
com.ibm.tivoli.cds.client.protocolhandlers.cds.CDSURLConnection
getInputStream JES Job Processor
8. Check TIO_LOGS\console.log to see if the results were received on the Tivoli Provisioning Manager
server. Check the SDI Status Updater thread to see if the DMS Status Count is bigger than zero.
JobStatus
v JOB_STATE_QUEUED = 1;
268
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
v
v
v
v
v
JOB_STATE_SUBMITTED = 2;
JOB_STATE_CANCELLED_ALL = 4;
JOB_STATE_CANCELLED_PARTIAL = 5;
JOB_STATE_COMPLETE_ALL = 6;
JOB_STATE_COMPLETE_PARTIAL = 7;
v JOB_STATE_FAIL = 8;
v JOB_STATE_REJECTED = 9;
WorkItemStatus
v WORK_ITEM_STATUS_EXECUTING = 1;
v
v
v
v
WORK_ITEM_STATUS_COMPLETED = 2;
WORK_ITEM_STATUS_FAILED = 3;
WORK_ITEM_STATUS_CANCELLED = 4; (not used)
WORK_ITEM_STATUS_PENDING = 5; (not used)
where:
v DMS_F_Pi is the device manager federated polling interval set in the WebSphere Application Server or
the lightweight runtime.
v JES_Pi is the job execution services polling interval on the common agent. This is set in the Tivoli
Common Agent stack or in the jes.properties file on the target computer.
v JT is the time it takes the scalable distribution infrastructure job to run. This can include the time it
takes to download files, run scans, and upload results.
v DI is the time it takes the dmsresultserver to process the incoming results from all of the target
computers. It is typically a quick process, but it can take some time, depending on the number of
target computers.
269
Turning on tracing for the device manager involves editing the traceConfig.properties file by doing the
following steps:
Procedure
1. Locate the traceConfig.properties file.
v Location of the device manager only:
/opt/ibm/tivoli/tpmfsw/tioprofile/installedApps/<hostname>Node01Cell/
DMS_WebApp.ear/dmserver.war/WEB-INF/classes/traceConfig.properties
v Location of the device manager (includes all of the device manager servers in a cluster):
/opt/ibm/tivoli/tpmfsw/DeviceManager/config/dmserver.war/ WEB-INF/classes/
traceConfig.properties
component.resultscollector=false
component.twgapi=false
component.database=true
component.enrollserver=true
component.datconverter=false
component.mcollect=false
component.notificationhandler=false
component.api=true
component.userservices=true
component.federator=true
What to do next
When the changes have been implemented, restart the server so that the changes will take effect.
Note: If you think there are problems, copy the trace files to another location so that they are not
overwritten.
270
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
Procedure
1. Log on to the WebSphere Application Server console.
2. Navigate to Servers -> Application Servers -> server1 -> Web Container Settings -> Web container
transport chains.
3. Record the WCInboundDefault port number.
4. Navigate to Environment ->Virtual Hosts -> TPMVirtualHost -> Host Alias.
5. Ensure that there is an entry for the host name and port. This is the port from step 3.
6. Restart WebSphere Application Server.
7. Launch dmconsole and specify the device manager server. For example:
<fully_qualified_hostname>:port
271
8. Change the directory to dmconsole_dev and run the DMconsole.bat file. For the user name and
password, use dmadmin / dmadmin. Leave the other fields with their default values. Ignore the error
that appears.
9. In the left navigation pane, click Jobs and then click Submit.
Results
You will now be able to view your jobs. Click View > Refresh to update the data.
Procedure
v Run the command:
https://<fully_qualified_host_name_server>:9045/dmserver/TraceServlet?trace=set
Symptoms
New jobs are not reaching the target computer.
Causes
The device manager client might not be polling.
Windows
2000
<agent_install_dir>\runtime\agent
UNIX
272
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
If the installation completed successfully, you will see a message similar to the following:
The file:C:\bundles\osgiagentservlet.jar bundle
was successfully installed.
If the startup is successful, you will see a message similar to the following:
BTC3146I The file:C:\bundles\osgiagentservlet.jar bundle was
successfully started.
5. Use a browser that is in the same system as the agent to navigate to http://localhost:21080/
osgiagentservlet. The OSGi agent control panel will be displayed.
6. On the Device Information screen, check that Polling enabled is selected.
7. To change the agent account configuration, select Edit Account Configuration from Admin
Functions, on the left.
273
274
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
Procedure
1. Check if you can access c$ on the target computer. You need to be able to access \\servername\c$ to
continue.
2. Check that Windows Firewall is not blocking the required ports. See the online help for more info on
RXA and requirements to connect to Windows target computers.
3. Use Telnet to connect to port 139. If the port is listening, you will get a blank screen because port 139
does not support Telnet. If the port is not listening, the computer will pause for a short time before
generating an error message.
4. If port 139 is listening, run the command netstat -an on the target. Ensure that both TCP 135 and
TCP 139 are listening. If TCP 139 is not listening, the network interface card (NIC) must be set to
Enable NetBIOS over TCPIP.
5. Disable Simple File Sharing by doing these steps:
a. In a Windows Explorer window, click Tools > Folder Options, and then click the View tab.
b. In the Advanced settings list, clear the Simple File Sharing check box.
c. Click Apply and then click OK.
6. Enable file and printer sharing by navigating to Control Panel > Network Connections > Local Area
Connection > Properties and then selecting File and Printer Sharing for Microsoft Networks.
7. Verify that the remote registry service is running.
8. Check for blocked traffic:
a. Navigate to Control Panel > Administrative Tools > Local Security Policy.
b. Right-click IP Security Policies on Local Computer and then select Manage IP filter lists and
filter actions.
c. Select the blocked items and then click Remove.
Procedure
1. Edit the $TIO_HOME/config/jlog.properties file.
2. Make the appropriate changes as indicated by comments inside the file.
275
Symptoms
Remote Execution and Access (RXA) cannot establish connections with any UNIX target computer that
has all remote access protocols (RSH, REXEC, or SSH) disabled.
Causes
RXA does not supply SSH code for UNIX machines. You must ensure SSH is installed and enabled on
any target computer you want to access using SSH protocol. Versions of OpenSSH that are version 3.71 or
newer contain security enhancements that were not available in earlier releases. In all UNIX
environments except Solaris, the Bourne shell (sh) is used as the target shell. On Solaris targets, the Korn
shell (ksh) is used instead, due to problems encountered with sh.
In order to use SFTP for file transfers, in addition to calling SSHPProtocol.setUSESFTP(true), make sure
that the SFTP server is enabled on the target computer. Note that the location of the sftp-server directory
is dependent on your operating system. It is typically found in the following locations:
v
Solaris
2000
: /usr/lib/ssh/sftp-server
2000
Linux
: /usr/libexec/openssh/sftp-server
HPUX
AIX
: /opt/ssh/libexec/sftp-server
: /usr/sbin/sftp-server
The ssh_config file contains a line similar to the one below. Make sure the line that enables the
sftp-server subsystem is not commented out, and that it points to the operating system-specific location
of the sftp-server subsystem. For example:
Subsystem sftp /one_of/the_paths/shown_above
276
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
Description
AMReturnValues.log
am_install.log
am_upgrade.log
auth_stdout.log
auth_stderr.log
certGen_stdout.log
certGen_stderr.log
datastore.out
datastore_stdout.log
datastore_stderr.log
ds_install.log
dh_stdout.log
db_stderr.log
encrypt_stdout.log
encrypt_stderr.log
guid_install.log
guid_stdout.log
guid_stderr.log
msg_EPM_Install.log
trace_EPM_Install.log
277
Description
serverStatus_out.log
serverStatus_err.log
startserver_stdout.log
startserver_stderr.log
jacl/amApp_out.log
jacl/amApp_err.log
jacl/appServer_out.log
jacl/appServer_err.log
jacl/checkcell_out.log
jacl?checkcell_err.log
jacl/checknode_out.log
jacl/checknode_err.log
jacl/jdbc_out.log
jacl/jdbc_err.log
jacl/ssl_out.log
jacl/ssl_err.log
jacl/virHost_out.log
jacl/virHost_err.log
Description
uninstall.log
AMUninstallReturnValues.log
msg_EPM_Install.log
trace_EPM_Install.log
278
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
Description
datastore.out
ds_install.log
db_stdout.log
db_stderr.log
279
server1. However, this is not true for the embedded version of IBM, on which the agent recovery services
logs are not supported.
Symptoms
The WebSphere Application Server backup tool will not run.
Causes
If you have the agent manager installed with WebSphere Application Server in a version earlier than
6.0.2.15 and then upgraded to the version required, it might not be possible to run the backup tool
(receiving a message saying that the control service is not available instead). You can check if this is the
cause of the problem by looking in the WebSphere Application Server wsadmin.traceout log file.
This command refreshes .jar files, and you will be able to run the backup tool after running it.
Symptoms
Agent Manager fails to install or upgrade with the embedded version of IBM WebSphere Application
Server.
Causes
If you install or upgrade the agent manager with the embedded version of IBM WebSphere Application
Server, you need to ensure that there is enough disk space for the operating system temporary directory.
User response: To correct the problem, change the location of the operating system temporary directory.
280
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
Default settings
By default, the following parameters of the WebSphere Application Server JVM are set during the
installation:
initialHeapSize=6MB
maximumHeapSize=256MB
This also applies to the embedded version of IBM WebSphere Application Server.
Procedure
v
Windows
2000
AIX
firststeps.bat
2000
Linux
Solaris
2000
HPUX
firststeps.sh
281
282
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
Symptoms
In a portlet of type All DCM Objects (generally named Data model object finder), the graph that
represents the result set is not created.
Causes
This is a base services limitation.
Symptoms
When the primary Tivoli Provisioning Manager server is disabled and the user attempts to manually
open Tivoli Provisioning Manager from the secondary server, the following message appears:
ALR0027I: Waiting for the currently running lightweight run time to exit.
Causes
The file system does not release the lwi.lck file after the primary server is disabled.
Symptoms
There is no information for Where Clause and Remarks in the DEPLOYMENTREQUESTSTATUS relationship and
Remarks information is missing from the WORKFLOW relationship when you do the following steps:
1. Click Go To > System Configuration > Platform Configuration > Database Configuration.
Copyright IBM Corp. 2003, 2011
283
Causes
The Where Clause is not needed for this relationship and the Remarks information is not mandatory.
Symptoms
Turning on Admin mode from the Database Configuration application takes a long time.
Causes
Interactive user sessions or background processing might be occurring at the same time Admin mode is
turning on.
Symptoms
After turning on auditing within Maximo, running the configdb script results in the following error
message:
SQLCODE=-670, SQLSTATE=54010
Causes
Resolving the problem
284
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
After auditing is enabled, the name of the auditing table is displayed in the Audit Table field.
1. Copy and paste this name in the Find field and search for this audit table.
2. Click on the audit table name in the search result.
3. Click on the arrow beside the Storage Partition field and select IBM32KSPACE.
4. Click the Save toolbar button.
5. Stop the server.
6. Run the configdb script again.
Now the script will run without error.
Causes
The Tivoli Provisioning Manager installation fails with DB2 when the terminal server is enabled. There is
a db2.exe application error. The DB2 command will not work.
Symptoms
You receive the following error:
COPCOM093E The JDBC driver caused an SQL exception.
COPJEE272E (Problem ID: UI449932). com.thinkdynamics.kanaha.datacentermodel
.DataCenterSystemException:
COPCOM093E The JDBC driver caused an SQL exception
Causes
This is caused by frequency committing to a database, causing a lock timeout. In the $TIO_LOGS/j2ee
file, you will find this information:
Caused by: com.thinkdynamics.kanaha.util.exception.DatabaseDeadlockException:
DB2 SQL error: SQLCODE: -911, SQLSTATE: 40001, SQLERRMC: 68
285
When you turn on these settings, remember to recycle the instance (that is, stop the database and then
start it again).
Symptoms
The upload server might time out on an idle connection to the Oracle server if the following conditions
are met:
v The provisioning server runs on Solaris with a remote Oracle database.
v The upload server is on a separate server that connects to the Oracle server using a firewall.
If the timeout occurs, the following error message is displayed:
COPCOM093E The JDBC driver caused an SQL exception.
Causes
Firewall timeout for idle connections might sever a connection. This can cause JDBC applications to hang
while waiting for a connection.
Symptoms
The embedded messaging feature does not work on Windows 2000. Instead, you see a message similar to
the following example:
Unable To Locate DLL The dynamic link library MSVCP60.dll could not be found
in the specified path...
Causes
The embedded messaging feature is missing the msvcp60.dll file on Windows 2000 Server platforms. The
prerequisite checker in the installer program does not check for this DLL file on the Windows 2000 Server
platform. If you select the Windows 2000 Support Tools during Windows 2000 Server installation, the
286
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
installation program for Windows 2000 Server installs the DLL file in the C:\Program Files\Support
Tools directory. The DLL file is installed during the installation of Windows 2000 Advanced Server in the
C:\WINNT\system32 directory.
Symptoms
When the log directory is on the same file system as Tivoli Provisioning Manager, it can reach or exceed
the capacity of the file system. This can prevent the application from creating new log files.
Causes
The capacity of the file system is not large enough.
Symptoms
The provisioning server does not start on Windows, and a message appears in the WebSphere
Application Server log (SystemOut.log in the %WAS_HOME%\logs\server1 directory) similar to the
following:
3c450cad LdapRegistryI E SECJ0352E: Could not get the users matching the pattern
wasadmin because of the following exception javax.naming.AuthenticationException:
[LDAP: error code 49 - Invalid Credentials]
Causes
In this configuration, IBM Tivoli Directory Server might treat DB2 as if it has started, even if it has not.
Chapter 24. Other problems
287
Symptoms
When using a non-login shell on Linux, the provisioning server does not start from GNOME or KDE
terminals. The following symptoms might appear:
1. The output of the tioStatus command shows that the deployment engine, policy engine, and the
DMS result server did not start:
ADMU0116I: Tool information is being logged in file
/opt/ibm/tivoli/tpm/tioprofile/logs/server1/serverStatus.log
ADMU0128I: Starting tool with the tioprofile profile
ADMU0500I: Retrieving server status for server1
ADMU0508I: The Application Server "server1" is STARTED
2007-10-20 21:13:29,824 INFO log4j configureAndWatch is started with
configuration file: /opt/ibm/tivoli/tpm/config/log4j-util.prop
2007-10-20 21:14:00,115 INFO COPCOM422I The deployment engine is not started.
2007-10-20 21:14:00,986 INFO COPCOM424I The policy engine is not started.
2007-10-20 21:14:00,989 INFO COPCOM484I The agent shell server is started.
2007-10-20 21:14:01,000 INFO COPCOM560I The activity plan engine is started.
2007-10-20 21:14:01,002 INFO COPCOM585I The SOAP service is started.
2007-10-20 21:14:01,018 INFO COPCOM588I The DMS Result Server is not started.
2. Displaying the value of the LD_LIBRARY_PATH environment variable from a command shell (for
example, echo $LD_LIBRARY_PATH) returns null.
3. A message appears in the $TIO_LOGS/console.log file:
COPCOM093E The JDBC driver caused an SQL exception.
com.thinkdynamics.kanaha.datacentermodel.DataCenterSystemException:
COPCOM093E The JDBC driver caused an SQL exception.
...
Caused by: com.ibm.db2.jcc.a.SqlException:
Failure in loading T2 native library db2jcct2
at com.ibm.db2.jcc.t2.a.a(a.java:31)
at com.ibm.db2.jcc.t2.T2Configuration.<clinit>(T2Configuration.java:75)
at com.ibm.db2.jcc.DB2SimpleDataSource.getConnection
(DB2SimpleDataSource.java:183)
at com.ibm.db2.jcc.DB2SimpleDataSource.getConnection
(DB2SimpleDataSource.java:144)
at org.apache.commons.dbcp.DataSourceConnectionFactory.createConnection
(DataSourceConnectionFactory.java:42)
at org.apache.commons.dbcp.PoolableConnectionFactory.makeObject
(PoolableConnectionFactory.java:290)
at org.apache.commons.pool.impl.GenericObjectPool.borrowObject
(GenericObjectPool.java:771)
at org.apache.commons.dbcp.PoolingDataSource.getConnection(
PoolingDataSource.java:95)
at com.thinkdynamics.kanaha.datacentermodel.inprocess.
ConnectionManager.getConn(ConnectionManager.java:93)
Causes
288
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
When starting from a non-login shell, .TCprofile is not sourced and therefore LD_LIBRARY_PATH is not set
properly.
To ensure that the .TCprofile script does not run twice, remove the above lines from the .bash_profile
and .profile files in the tioadmin home directory.
Symptoms
When the database server is on a multiprocessor computer, the remote connection to the database might
hang. The database server then logs the following error in the db2diag.log file:
DIA3208E Error encountered in TCP/IP protocol support. TCP/IP function "accept".
Socket was "920". Errno was "10061".
Causes
Not enough connection managers are allocated from the database server.
Symptoms
289
When you submit an incorrect SOAP parameter from the command line, Tivoli Provisioning Manager
returns an error message. A detailed Java exception message is also displayed.
Causes
A SOAP client can be run on a computer other than the Tivoli Provisioning Manager server. In such a
scenario, the SOAP client is a thin client that has no message log available.
Symptoms
Tivoli Provisioning Manager does not function as you would expect when you run an XML import while
all the Tivoli Provisioning Manager processes are running.
Causes
Tivoli Provisioning Manager processes cache some information, and they depend on JMS messages for
notification when events occur (for example, when the system runs logical management operations and
workflows). However, an XML import does not send any notifications to the Tivoli Provisioning Manager
processes. It just loads the database.
Windows
2000
UNIX
Symptoms
You might experience slow response times when running Tivoli Provisioning Manager on Windows 2003
Enterprise Edition operating system environments with 4 GB of physical memory.
Causes
The page file size might be too small.
290
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
You can obtain better performance by increasing the page file size beyond the 4095 MB page file size
limit that Windows 2003 sets as default. To do this:
1. Set the /PAE flag in your boot.ini file. You can add the PAE switch as shown below:
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Windows Server 2003, Enterprise"
/noexecute=optout /fastdetect /PAE
Note: The c:\boot.ini file is a write-protected system file. You might have to change the file
permissions to edit it.
2. Open Windows Registry and change the key value of the registry key that controls the page file:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\SessionManager\MemoryManagement. Set the
PagingFiles value to c:\pagefile.sys 3069 8192.
3. Restart your computer.
Symptoms
When you click Information Center on the web interface, the information center displays in English,
even if the provisioning server was installed in a different language.
Causes
The information center is English by default.
where db_user is the database runtime user. The default value is maximo.
Causes
291
The message indicates that the user is configured so that the account does not lock during the install
process. Thebase services installer did not change the password policy you configured.
Symptoms
You are unable to log in to Cisco routers and switches if the routers or switches have the greater than
symbol (>) or the number sign (#) in them. You are also unable to log in if you switch login prompts.
Causes
Cisco routers and switches which use a greater than symbol (>) or a number sign (#) in the login banner
are not supported.
Symptoms
If you select an object in a dialog or a table, and then search for a different term, your original item
selection is cleared.
Causes
Only the last searched object (or objects) is displayed when searching.
Symptoms
You receive the error BMXAA0012E - Cannot insert/update a record without a default insert site
when trying to do an action that requires a default insert site to be configured. This can occur even if you
do have a default insert site configured, but is not active.
Causes
This can occur if the default insert site has not been configured. If it has been configured, then the
configuration might not have taken effect (for example, you have not logged out of your sessions yet).
292
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
Additionally, configuration and usage of sites in conjunction with the MAXADMIN user (that is, the user is
configured for mxe.adminuserid) could cause system problems because background sessions for that user
might be active frequently.
Symptoms
An error occurs when you run the versionInfo command on a Windows 64bit computer.
Causes
This command is not supported for Windows-64 bit computers.
Symptoms
Running a network discovery fails with errors indicating that there are problems with the networking
configuration on an AIX WPAR target computer.
Causes
An AIX WPAR virtual server might be missing networking information, or the networking information is
not configured correctly.
Symptoms
After starting the provisioning server using the tio.cmd start command and then stopping the
provisioning server using the tio.cmd stop command, errors are found in the console.log and trace.log
files.
Chapter 24. Other problems
293
Causes
This is normal behavior that comes after running the above commands.
Symptoms
You are working in a non-English locale, and error messages are only being displayed in English.
Causes
This is a localization issue.
Symptoms
Files in a UNIX or Cygwin environment have specific permissions for the owner of the file, the group for
the file, and other users.
Causes
There are various factors that can cause can change the permissions of a file. Consider the following
factors when editing text files:
v Default user permissions. Each user has default permissions for files that they create, and those
defaults can be changed with the umask command. This means that file permissions for the user who
created a file can be different than the permissions for another user. If you edit a file in Cygwin using
an editor such as vi, it is recommended that you log on as the owner of the file.
v If you are using a text editor that automatically creates file backups, your updated file might have
different permissions than the original file.
294
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
You can check the current permissions of a file in Cygwin by typing the following command:
ls -l filename
Symptoms
The following message might be displayed in Status of my recent provisioning workflows in the Start
Center:
COPCOM618E The network discovery could not find any of the specified resources.
2. Expand Local Computer Policy > Computer Configuration > Administrative Templates > Network
Connections > Windows Firewall > Standard Profile.
3. Ensure that Windows Firewall: Do not allow exceptions is Not Configured.
4. Ensure that Windows Firewall: Allow file and printer sharing exception and Windows Firewall:
Allow local port exceptions are Enabled.
5. Expand Local Computer Policy > Computer Configuration > Windows Settings > Security Settings
> Local Policies > Security Options.
6. Ensure that Network security: LAN Manager authentication level is set to Send NTLMv2 response
only.
7. Open Windows Firewall in the Control Panel.
8. Add the following port numbers. ClickExceptions > Add port.
9045
9046
9510
9511
9512
9513
9514
9515
2. Expand Local Computer Policy > Computer Configuration > Windows Settings > Security Settings
> Local Policies > Security Options.
295
3. Ensure that Network security: LAN Manager authentication level is set to Send NTLMv2 response
only.
4. Ensure that User Account Control Admin Approval Mode for the Build-in Administrator account is
set to Disabled.
5. Expand Local Computer Policy > Computer Configuration > Windows Settings > Security Settings
> Windows Firewall with Advanced Security > Windows Firewall with Advanced Security - Local
Group Policy Object > Inbound Rules.
6. Create a new inbound File and Print Sharing rule, which will allow SMB inbound traffic.
7. Create a new inbound Protocol and Ports rule for following TCP ports:
9045
9046
9510
9511
9512
9513
9514
9515
Symptoms
A provisioning task or provisioning workflow fails with the following message:
-bash: $\r: command not found
Causes
This is an issue that only applies when Tivoli Provisioning Manager is installed on a Windows operating
system, and occurs when you manually start Cygwin. If you edited a bash startup file such as .bashrc or
/etc/profile with a DOS-based editor, then the line endings might have changed to CR/LF instead of LF,
which causes the error to occur.
Manually restart the Cygwin shell to verify that the error has been solved.
296
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
Message logs
Message logs record Tivoli Provisioning Manager system events as text messages so they can be reviewed
later by customers or by IBM Tivoli Software Support. Typically, messages are used to provide
information about how the system or application is performing, and to alert the system administrator to
exceptional conditions when they occur. If an error occurs, you can check the message logs for
information about the error, the cause of the error, and possible resolutions for the error.
Message logs have the file name msg.log, and are stored in the subfolder for each software component.
Messages are localized based on the locale configured on the provisioning server. There are multiple
levels of message logs, and they can be filtered by message log level and software component.
Note: Variables in a message are represented by Value_n where n is a unique value within the message.
Message elements
Each message includes a message ID, message text, and explanation text. Some messages also include
action text when the user can take an action.
Example:
COPDEX101E: A security exception occurred while the system parsed the profile XML file:
Explanation: The ITM Obtain OS Profiles provisioning workflow generates an XML file that
contains the list of profiles installed in Tivoli Management Agent. This profile XML file is copied
to Tivoli Provisioning Manager and then it is parsed by the Profile XML Parser. The XML parser
cannot read the profile XML file because a security error occurred. This is a file permissions issue.
Either the parent directory of the profile XML file is missing appropriate file permissions, or the
profile XML file is missing the appropriate file permissions.
Operator response: Verify that the login user is assigned read and write access to the parent
directory of the ProfileXMLParser.
Message ID
String of 10 alphanumeric characters that uniquely identifies the message. In the preceding
example, the message ID is COPDEX101E.
Message text
Explains the reason for the message, what the message means, and possible causes of the
message with recommended steps you can take (for those messages that require some action on
your part). In the preceding example, the message text is: A security exception occurred while the
system parsed the profile XML file.
Explanation
Contains additional information about the cause of the message, and describes the action that the
system took or will take. In the example, the explanation follows the label Explanation.
Action
Describes what you must do to proceed, to recover from the error, or to prevent a problem from
occurring. Actions can include:
297
Action title
Description
System Action
Operator Response
Administrator Response
Programmer Response
Message ID format
The message ID consists of 10 alphanumeric characters that uniquely identify the message. Each message
ID includes:
v
v
v
v
Subsystem
APM
COM
Common
DEX
Deployment engine
DSE
Discovery
GRP
Group management
INF
Infrastructure
JDS
JEE
NET
Network management
PCH
Patch management
QLX
SRV
Server management
SWD
Software deployment
TCA
TDM
TSK
UTL
Utilities
298
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
BTC1007E BTC1010E
Description
Messages
The section contains a list of possible messages that you might encounter while using the product. The
messages are listed according to the identifier of the product feature or component that produces the
message.
BTC
This section lists the messages for the Tivoli Common Agent Services.
BTC1007E
BTC1008W
299
BTC1011E BTC1032E
was unable to obtain the security certificate and key
pair from the agent manager.
BTC1012E
300
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
BTC1045E BTC1048E
BTC1045E
301
BTC1049E BTC2202E
attempt to renew the certificate revocation list. If the
log indicates that a problem occurred on the agent
manager, check the agent manager log file for
associated exceptions and error messages. If the
problem persists, contact customer support.
BTC1049E
302
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
BTC2203E BTC3001E
underlying system. If the IP configuration of its
underlying system is incorrect, network
communications involving the common agent will not
work.
Administrator response: Verify that the IP
configuration of the system on which the common
agent is installed is correct. If the problem persists,
contact customer support.
BTC2203E
BTC2210E
BTC2403E
BTC2207E
303
BTC3002E BTC3010E
Administrator response: Verify that there is sufficient
disk space and that the user has the appropriate
authority to write to the file system.
BTC3002E
BTC3005E
BTC3006E
304
BTC3010E
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
BTC3011E BTC3116E
System action: The bundle was not installed.
Administrator response: Verify that the specified
bundle exists at the specified location, the location is
accessible, the bundle is not corrupted, and the bundle
manifest is valid.
BTC3011E
BTC3013E
BTC3111E
BTC3012E
BTC3014E
BTC3116E
BTC3015E
305
BTC3117E BTC4035E
BTC3117E
306
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
BTC4036E BTC4045E
BTC4036E
BTC4043E
307
BTC5019E BTC5047E
System action: After rejecting the incoming
connection, the common agent returned began to
listening on the port specified in its properties file.
Administrator response: Verify that both the common
agent and the entity that is attempting to contact it, has
valid credentials. If the problem persists, contact
customer support.
BTC5019E
BTC5025E
BTC5046E
308
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
BTC5048E BTC5051E
the upgrade. Possible exceptions include:
FileNotFoundException - The file does not exist or
cannot be opened for reading. IOException - An error
occurred while reading from the file.
NumberFormatException - The status value cannot be
parsed as an integer.
Administrator response: Make sure that the
logs/install/epInstallStatus.log file exists. Open the file
with a text editor to obtain the upgrade status.
BTC5048E
309
BTC5052E BTC5071E
Make sure the target directory, data_directory , is
writable. After you correct the problem, start the
upgrade again.
BTC5052E
310
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
BTC5072E BTC7037E
BTC5072E
BTC7008E
BTC70263E
BTC5075E
311
BTC7038E BTC7087W
converter type object. If the converter class was not
found then CLI is unable to get arguments to CLI
service.
System action: The CLI command failed because the
converter class has not been found. The requested CLI
service has not been processed.
Administrator response: Verify that the arguments
passed to the requested CLI service. If there is no
converter class for the specified argument type, cast the
parameter to the java.lang.String type.
BTC7064E
BTC7038E
312
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
BTC7088W BTC7110E
BTC7088W
BTC7103E
BTC7104E
313
BTC7111E BTC7143E
BTC7111E
RestrictedCertValidator validation
failed. The feature name from the caller
certificate could not be obtained.
RestrictedCertValidator validation
failed. The service value is not registered
with the
com.ibm.tivoli.cas.agent.connector.restricted
property.
RestrictedCertValidator validation
failed. The following property
com.ibm.tivoli.cas.agent.connector.restricted
- list - does not contain the feature name
which is written in the certificate
featureName.
Explanation: The
com.ibm.tivoli.cas.agent.connector.restricted property of
the requested service does not contain the feature name
which is written in the caller's certificate.
System action: The caller is not allowed to execute the
operation on the requested service because the
validation of the restricted certificate failed.
Administrator response: Check the registration
properties of the requested service. Verify whether it
has the com.ibm.tivoli.cas.agent.connector.restricted
property equal to the feature name stored in the caller's
certificate.
314
BTC7115E
RestrictedCertSecurityChecker
validation failed. The caller certificate
from the servlet request could not be
retrieved.
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
BTC7151E BTC7233E
BTC7151E
BTC7228E
BTC7152E
BTC7230E
BTC7154E
BTC7233E
BTC7226E
315
BTC7234E BTC7264E
Administrator response: Install and start required
bundle with the help of the target bundle to resolve
this issue.
BTC7234E
BTC7259E
BTC7252E
BTC7262E
316
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
BTC7265E BTC7275W
BTC7265E
BTC7271E
BTC7274E
317
BTC7276E BTC7401E
BTC7276E
BTC7279E
BTC7283E
BTC7296E
BTC7280E
BTC7297E
BTC7281E
318
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
BTC7402E BTC7417E
BTC7402E
BTC7417E
319
BTC7418E BTC7467E
password confirmation field is empty. The registration
password is mandatory parameter in the configuration
of the common agent. Without this password the
common agent will not be able to register - obtain
certificates from the agent manager. The install
dialog/console masks the value which is entered into
the password fields. Because of this it is necessary to
type the password twice to make sure that a typing
error did not occur.
BTC7419W
BTC7420W
BTC7421W
BTC7422W
BTC7423W
BTC7424W
BTC7437E
320
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
BTC7468E BTC7471E
BTC7468E
321
BTC7472E BTC7474E
BTC7472E
322
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
BTC7475E BTC7484E
BTC7475E
323
BTC7485E BTC7488E
occurred and the system GUID cannot be created. The
common agent installer is not able to proceed. The
installation process has been stopped. All changes
which were made on the destination host until the
error conditions ocurred have been rolled back. The
common agent installer's log file (epInstall.log) should
contain more information about the error and what
could be the cause of the error.
BTC7487E
BTC7485E
324
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
BTC7490E BTC7498E
CASInstall.WebContainerSSLPort. Make the changes or
comment the whole properties. Save the response file
and restart the common agent installer.
BTC7490E
325
BTC7501E BTC7520E
BTC7501E
BTC7506E
BTC7516E
BTC7505E
326
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
BTC7521E BTC7613E
BTC7521E
BTC7605E
BTC7609E
BTC7522W
327
BTC7614E BTC7820E
BTC7614E
BTC7616W
BTC7819E
BTC7618E
BTC7818E
328
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
BTC7822E BTC7825E
problem persists gather all the log files
(LWI_HOME/runtime/agent/logs and
LWI_HOME/logs directories) and contact customer
support.
BTC7822E
329
BTC7826E BTC7837E
BTC7826E
330
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
BTC7838E BTC7846E
BTC7838E
BTC7840E
331
BTC7847E BTC7848E
Administrator response: If you are running the
common agent installer, review the installation log files
in order to find the problem cause. The installation log
file (epInstall.log) can be found in the common agent
installation directory LWI_HOME/runtime/agent/
logs/install/epInstall.log. The pre-installation log file
(epPreInstall.log) and the external processes outputs
can be found in the same directory. If you are running
the post-install configuration tool, review the
configure.log.x file which is created in the
LWI_HOME/runtime/agent/logs/directory. The
external processes outputs can be found in the
LWI_HOME/runtime/agent/logs/configure directory.
If the problem is related to the local system
environment, make necessary corrections and restart
the common agent installer or the post-install
configuration tool. If the problem persists, gather all the
log files (LWI_HOME/runtime/agent/logs directory)
and contact customer support.
BTC7847E
332
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
BTC7849E BTC7851E
BTC7849E
333
BTC7852E BTC7853E
proceed. The installation process has been stopped. All
changes which were made on the destination host until
the error conditions appeared have been rolled back.
Administrator response: Review the installation log
file (epInstall.log), which can be found in the common
agent installation directory LWI_HOME/runtime/
agent/logs/install. The log file should contain the
information about the parameters, with which the
command was executed and also the names of the
command output files. The names should start with the
following prefixes ''SetFileSecurityOut.log'' and
''SetFileSecurityErr.log''. A timestamp information is
added to the name (the same value to the stdandard
output and the stdandard error files) in order to
differentiate the outputs if the command is invoked
several times during the installation. Review the output
files in order to find the problem cause. If the problem
is related to the local system environment, make
necessary corrections and restart the common agent
installer. If the problem persists, gather all the log files
(LWI_HOME/runtime/agent/logs directory) and
contact customer support.
BTC7852E
334
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
BTC7854E BTC7856E
several times during the installation. Review the output
files in order to find the problem cause. If the problem
is related to the local system environment or the user
account definition, make necessary corrections and
restart the common agent installer. If the problem
persists, gather all of the log files (LWI_HOME/
runtime/agent/logs directory) and contact customer
support.
BTC7854E
335
BTC7857E BTC7859E
output and the stdandard error files) in order to
differentiate the outputs if the command is invoked
several times during the installation. Review the output
files in order to find the problem cause. If the problem
is related to the local system environment, make
necessary corrections. Investigate and fix also the issue
which was the cause of the upgrade process roll back.
Restart the common agent installer. If the problem
persists, gather all the log files (LWI_HOME/runtime/
agent/logs directory) and contact customer support.
BTC7857E
336
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
BTC7862E BTC7879E
is added to the name (the same value to the stdandard
output and the stdandard error files) in order to
differentiate the outputs if the command is invoked
several times during the installation. Review the output
files in order to find the problem cause. If the installer
completed successfully, restart the common agent if it is
not registered properly. If the upgrade process
(installer) failed, stop the legacy common agent
manually. If the problem is related to the local system
environment, make necessary corrections and restart
the common agent installer. If the problem persists,
gather all the log files (LWI_HOME/runtime/agent/
logs directory) and contact customer support.
BTC7862E
BTC7870E
No password provided.
337
BTC7903E BTC8020W
gather all the log files (LWI_HOME/runtime/agent/
logs directory) and contact customer support.
BTC7903E
338
BTC8015E
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
BTC8115E BTC8123E
constructor is available and does not throw an
exception.
BTC8115E
BTC8119E
BTC8116E
BTC8122E
339
BTC8124E BTC8137E
BTC8124E
BTC8129E
BTC8126E
BTC8135E
BTC8137E
340
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
BTC8138E BTC8207E
BTC8138E
BTC8203E
341
BTC8208E BTC8222E
BTC8208E
342
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
BTC8228E BTC8245E
Save the response file and restart the common agent
installer.
BTC8228E
Explanation: The mandatory parameter's value installLocation - was not provided. Response file, which
Chapter 25. Messages
343
BTC8246E BTC8269E
is passed as an argument to the common agent installer
launcher, contains empty value defined for the
installLocation parameter (installLocation=,
installLocation=null or installLocation= ). The common
agent installer is not able to proceed. The installation
process has been stopped. No changes were made on
the destination host.
Administrator response: Verify the value of the
property installLocation in the common agent installer
response file. Set the value or comment the whole
property if the default value is acceptable. Save the
response file and restart the common agent installer.
BTC8246E
344
BTC8249E
Explanation: The parameter's value - installLocation contains unsupported characters (for example national
characters). The installation directory name should
consist of the characters from the ASCII set (name
should be based on the English alphabet). The common
agent installer is not able to proceed. The installation
process has been stopped. No changes were made on
the destination host.
Administrator response: Verify the value of the
installLocation property in the common agent installer
response file. Set the value, or comment the whole
property if the default value is acceptable. Save the
response file and restart the common agent installer.
BTC8269E
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
BTC8275E BTC8281E
Explanation: The parameter's value - the common
agent destination directory - contains unsupported
characters (for example national characters). The
installation directory name should consist of the
characters from the ASCII set (the name should be
based on the English alphabet). The common agent
installer is not able to proceed.
Administrator response: Enter the correct value into
the destination directory field and proceed with the
installation.
BTC8275E
345
BTC8282E BTC8401E
the destination host have been rolled back.
Administrator response: Review the destination host
configuration: file systems mounts and permissions.
Review the installation log file (epInstall.log) which can
be found in the common agent installation directory:
installLocation/runtime/agent/logs/install/
epInstall.log. ''installLocation'' is the path to the root
directory of the common agent installation. If the
problem is related to the local system environment,
make necessary corrections and restart the common
agent installer.
BTC8282E
346
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
BTC8402E BTC8418E
service definition'' dialog is correct and proceed with
the installation. In the silent mode verify the value of
the CASInstall.WindowsAccountPassword property in
the common agent installer response file. Set the correct
value, save the response file and restart the common
agent installer.
BTC8402E
347
BTC8423E BTC8426E
operational. There is no possibility to setup secure
connection with the common agent. Depending on the
user choice the non-registered common agent instance
might be left on the local system or rolled back.
Administrator response: If the installer is running in
the silent mode and the option
CASInstall.RollbackOnRegistrationFailure=true is
specified or if the suitable choice was made in the
interactive installer mode the instance of the common
agent is left on the local system. If the problem is
related to the local system environment after necessary
changes agent can be registered to the fully operational
state. The common agent should be restarted in this
case. It is also a good solution to leave the common
agent on the system if the timeout specified for the
registration's verification was too short. If the common
agent instance was rolled back it is possible, after
investigation of the problem cause, to install the
common agent again. The following list of some hints
might help find the solution of this issue: Review the
common agent log files. These log files can be found in
the installLocation/logs directory. ''installLocation'' is
the path to the root directory of the common agent
installation. Verify the agent manager connection
information provided to the common agent installer.
Make sure that the registration password is correct.
Make sure that the configuration of the agent manager
is correct (its services are not advertised on the
''localhost'' address). Check if the timeout for
registration verification is not too short (minimum 60
seconds). Look for other messages in the installation
log files that might be preventing the registration. The
main installation log file (epInstall.log) can be found in
the common agent installation directory:
installLocation/runtime/agent/logs/install/
epInstall.log. ''installLocation'' is the path to the root
directory of the common agent installation. Review the
common agent registration server log. There is also the
flag CASInstall.WaitForRegistration in the installer
response file and a suitable option in the interactive
mode which gives the possibility to skip the
registration verification after the installation.
BTC8423E
348
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
BTC8427E BTC8467E
common agent installer. Another option is to uninstall
the existing common agents and to install a new
common agent with the CASInstall.OEMInstall=''true''
parameter specified.
BTC8427E
<LWI_instance_name>/lwi. ''LWI_instance_root''
directory can be omitted, however it is not
recommended. ''lwi'' subdirectory can be omitted.
Administrator response: Change the value of the
installLocation parameter in the common agent installer
response file. Save the response file and restart the
common agent installer.
BTC8465E
349
BTC8468E BTC8485E
BTC8468E
BTC8484E
350
BTC8479E
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
BTC8486E BTC8497E
Administrator response: Check if the file is not locked
by a process which prevents it from any relocation.
Review the log files for information.
BTC8486E
BTC8492E
351
BTC8498E BTC8617E
BTC8498E
352
BTC8615E
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
BTC8618E BTC8753W
BTC8618E
BTC8627E
Initialization of a component
responsible for the SLP advertisment
has failed.
COPAPM
This section contains messages with the COPAPM identifier for activity plan applet messages for Tivoli
Provisioning Manager.
Chapter 25. Messages
353
COPAPM001E COPAPM025W
COPAPM001E VALUE_0 was unable to start because
it is in VALUE_1 state.
COPAPM002E The task VALUE_0 failed to start.
COPAPM003E Activity plan engine cannot find any
task dispatcher to dispatch jobs.
354
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
COPAPM026E COPAPM040E
COPAPM026E The activity VALUE_0 contains the
following unsupported targets type
VALUE_1.
COPAPM027E The activity VALUE_0 contains the
unsupported conditioning by depot
VALUE_1
COPAPM028E The type VALUE_0 is not supported
by the activity VALUE_1.
COPAPM029W The following operation VALUE_0 is
no longer supported for activity
VALUE_1. The activity will be converted
to Not Supported Operation and the
plan must be modified before becoming
executable.
COPCOM
This section contains messages with the COPCOM identifier for common subsystem messages for Tivoli
Provisioning Manager.
Chapter 25. Messages
355
COPCOM001E COPCOM011E
COPCOM001E The system cannot delete the
VALUE_0 file.
SP=SoftwarePackageValue;I=True.
User response: Verify that the correct discovery object
was used. Verify that the discovery object has the
required filter string properties.
356
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
COPCOM012E COPCOM036E
COPCOM012E The server VALUE_0 does not have a
locale value.
357
COPCOM037E COPCOM067E
COPCOM037E An unexpected shell command error
occurred and the system cannot create
the InputStreamHelper for the error
stream.
358
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
COPCOM068E COPCOM095E
COPCOM068E The system cannot find the interface
card port: VALUE_0.
359
COPCOM1000E COPCOM132E
COPCOM1000E There are no software modules in
the database that has boot server
capabilities.
COPCOM101E
360
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
COPCOM133E COPCOM162E
COPCOM133E The monitoring configuration
VALUE_0 is already associated with
VALUE_1.
Explanation: A monitoring configuration with the
same name is already associated with the current
resource.
User response: Ensure that the monitoring
configuration is correct. If changes need to be made,
add an association with the appropriate monitoring
configuration.
COPCOM134E The password that you are trying to
update cannot be null or empty for
username VALUE_0.
361
COPCOM163E COPCOM197E
COPCOM163E The system cannot find the VALUE_0
password credentials.
362
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
COPCOM198E COPCOM231E
COPCOM198E The system cannot find the VALUE_0
file system.
COPCOM199E The system cannot find the VALUE_0
physical volume.
COPCOM200E The system cannot find the VALUE_0
physical partition.
COPCOM201E The system cannot find the VALUE_0
system storage capabilities.
COPCOM202E The system cannot find the VALUE_0
fibre channel port with port number.
COPCOM203E The system cannot find the VALUE_0
data path.
COPCOM204E The system cannot find the VALUE_0
zone set.
COPCOM205E The system cannot find the VALUE_0
zone.
COPCOM206E The system cannot find the VALUE_0
zone membership data.
COPCOM207E A worldwide name is not defined for
the VALUE_0 fibre channel port.
COPCOM208E The system cannot find the VALUE_0
storage volume in the VALUE_1 storage
area network frame.
COPCOM209E The system cannot find the logical
volume VALUE_0 in the volume
container VALUE_1.
COPCOM210E The system cannot find the logical
volume settings VALUE_0 in the volume
container settings VALUE_1.
COPCOM211E The system cannot find the fibre
channel port with port number VALUE_0
in system VALUE_1.
COPCOM213E The system cannot find the zone
VALUE_0 in the fibre channel fabric
VALUE_1.
363
COPCOM232E COPCOM262W
COPCOM232E The system cannot delete the
resource VALUE_0 because it is part of
an allocation.
COPCOM233E The system cannot find the VALUE_0
license key.
COPCOM234E The system cannot find the VALUE_0
license broker.
COPCOM235E The system cannot find the VALUE_0
license pool.
COPCOM236E The system cannot find the
supported requirement type: VALUE_0.
COPCOM237E The system cannot find the VALUE_0
software module.
COPCOM238E The system cannot find the VALUE_0
resource allocation.
COPCOM239E The system cannot find the data
center model object ID for IP address
VALUE_0.
Explanation: The IP address is not valid.
User response: Provide the correct IP address of the
resource.
COPCOM240E The system cannot find the VALUE_0
signal descriptor.
COPCOM241E The system cannot find the VALUE_0
volume container access settings.
COPCOM242E The system cannot find the VALUE_0
storage volume on the port.
COPCOM244E The system cannot find the VALUE_0
software association.
364
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
COPCOM263E COPCOM292E
COPCOM263E The Tivoli Enterprise Console (TEC)
cannot use VALUE_0 as the event class
name.
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. All TEC events sent by the Send TEC Event Java
plug-in must conform to the Tivoli Enterprise Console
standard. The TEC event class name that was provided
to the system does not conform to the standard.
365
COPCOM293E COPCOM323E
COPCOM293E The system cannot find the VALUE_0
storage manager template.
366
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
COPCOM324E COPCOM347E
COPCOM324E The value for other-storage-functiontype attribute is not specified.
COPCOM325E The system cannot find the VALUE_0
RAID redundancy mapping.
COPCOM326E The system cannot delete the default
VALUE_0 storage function type.
COPCOM327E The system cannot find the source
application tier resource VALUE_0.
COPCOM328E The system cannot find the target
application tier resource VALUE_0.
COPCOM329E The system cannot find the VALUE_0
storage template.
COPCOM330E The user VALUE_0 does not have
VALUE_1 permission on the VALUE_2
VALUE_3 with ID VALUE_4.
COPCOM331E The subscription with ID VALUE_0
cannot be canceled, because the
provision schedule task ID cannot be
found in its service instance with ID
VALUE_1.
COPCOM332E The subscription with ID VALUE_0
cannot be canceled, because it is not in
the pending state.
COPCOM333E The subscription with ID VALUE_0
cannot be deleted, because it is not in
the Inactive_Expiried, Inactive_Failed, or
Inactive_Terminated state.
COPCOM334E The subscription with ID VALUE_0
cannot be canceled or stopped, because
it is already in the Inactive state.
COPCOM335E The subscription with ID VALUE_0
cannot be re-subscribed, because its
service instance with ID VALUE_1 does
not contain a provision schedule task
ID.
COPCOM336E The subscription with ID VALUE_0
cannot be re-subscribed, because its
service instance with ID VALUE_1 is not
in the Provision_Error state.
367
COPCOM348E COPCOM375E
COPCOM348E The system cannot create the
offering, because an offering VALUE_0
already exists.
COPCOM349E The template VALUE_0 was not
found.
COPCOM350E The template parameter VALUE_0
was not found.
COPCOM351E The application name VALUE_0
cannot be found for Service.
COPCOM352E The data center model object type
VALUE_0 is not supported for creation
of services.
COPCOM353E The service with ID VALUE_0 cannot
be found.
COPCOM354E The offering with ID VALUE_0
cannot be found.
COPCOM355E The scheduled task type VALUE_0 is
not valid.
COPCOM357E The Order of ID VALUE_0 cannot be
found.
COPCOM358E The service with name VALUE_0
cannot be found.
COPCOM359E The service instance of ID VALUE_0
cannot be found.
COPCOM360E The subscription of ID VALUE_0
cannot be found.
COPCOM361E AgentManager has thrown an
exception. See the embedded exception
for details.
COPCOM362E An error occurred while registering
with Agent Manager at address
VALUE_0. See the embedded exception
for details.
COPCOM363E The system cannot find the
endpoint.properties file.
368
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
COPCOM376W COPCOM392E
of the Constraint to be created. The constraint creation
failed.
User response: Verify the correct type of the new
Constraint to be created.
COPCOM376W The Constraint with the name
VALUE_0 is not added, because a
constraint with the same name already
exists.
Explanation: An existing Constraint with the same
name prevents the addition of the new constraint.
User response: Verify the correct name of the new
Constraint to be added.
COPCOM377E Internal Error: Null AgentGUID was
specified.
Explanation: The database does not have any agent
GUID for a server.
User response: Ensure that Common Agent is
installed on the server and the AgentID property has
the GUID of the agent.
COPCOM378E AgentManager did not find the
Agent ID VALUE_0.
Explanation: The AgentId property on the Server
might be incorrect.
User response: Ensure that the AgentId property
contains the correct GUID for Common Agent.
COPCOM379I Usage: dcmExport.cmd/sh [-d]
[outputFilename] 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).
COPCOM380E Incorrect command syntax. Usage:
XmlImport.cmd/sh file_URL [file_URL]*
Example: XmlImport.cmd
file:/c:/myDirectory/myInput.xml.
COPCOM381E The system cannot find the VALUE_0
software instance.
COPCOM382E The system cannot find the VALUE_0
software installation.
369
COPCOM393E COPCOM407E
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.
370
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
COPCOM408E COPCOM421I
COPCOM408E The Endpoint subscriber: VALUE_0
does not exist.
Explanation: The Endpoint subscriber does not exist
in the TCM environment.
User response: Ensure that the Endpoint is a
subscriber to a Profile Manager.
COPCOM410E The filter VALUE_1 is a duplicate for
the filter list named VALUE_0.
Explanation: There are duplicate exclude filters in the
list.
User response: Ensure that the filter definition does
not contain duplicate exclude filters.
COPCOM411E The filter VALUE_1 is a duplicate for
the filter list named VALUE_0.
Explanation: There are duplicate include filters in the
list.
User response: Ensure that the filter definition does
not contain duplicate include filters.
COPCOM412E The filter VALUE_1 is in conflict with
other filters in the filter list named
VALUE_0.
Explanation: The filter conflicts with other filters in
the filter list.
User response: Ensure that there are no conflicts in
the filter list.
371
COPCOM422I COPCOM439E
COPCOM422I The deployment engine is not started.
372
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
COPCOM440E COPCOM455E
COPCOM440E The data returned from the RIM
object is not valid.
Explanation: The RIM object provides all the
interactions to the IBM Tivoli Configuration Manager
database. A lookup of an item returned data that did
not conform to the proper type format.
Administrator response: Verify that the IBM Tivoli
Configuration Manager database has no errors by
running the ckdb. This command identifies and repairs
errors.
COPCOM441E A connection to the RIM object
VALUE_0 could not be closed.
Explanation: The RIM object provides all the
interactions to the IBM Tivoli Configuration Manager
database. A failure to disconnect to the RIM object
could be caused by a network connection, an error with
the IBM Tivoli Configuration Manager server, or some
other error.
User response: Verify that the hostname of the IBM
Tivoli Configuration Manager is correct and that a
connection to the server can be established.
Administrator response: Verify that the RIM object is
valid. 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.
Explanation: The only valid hardware filter types are
Gateway and Subscribers.
User response: Verify that the type specified in the
TCM_Import_Filtered_Endpoints workflow is either
Gateway or Subscriber.
COPCOM443E The system cannot create the file
VALUE_0.
Explanation: The discovered IBM Tivoli Configuration
data is written to an XML file so that it can be
imported into the IBM Tivoli Provisioning Manager
server. An error occurred while attempting to create
this XML file.
User response: Verify that the file VALUE_0 does not
already exist. Ensure that the file is not locked and has
write permissions.
COPCOM444E The user credentials provided for the
IBM Tivoli Configuration Manager
server are not valid or do not exist.
Explanation: The username password combination
that is specified in the SAP credentials for the IBM
Tivoli Configuration Manager values is incorrect or was
not specified.
373
COPCOM456E COPCOM476E
that there is a software module that can install Tivoli
Common Agent on the specified operating system.
374
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
COPCOM477E COPCOM502E
COPCOM477E The alternate gateway port is not
correct.
375
COPCOM503E COPCOM527E
COPCOM503E Error converting path VALUE_0 to dos
style path.
376
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
COPCOM528E COPCOM542E
COPCOM528E Cannot add property value ID
VALUE_0.
377
COPCOM543E COPCOM573I
COPCOM543E The system cannot find the interface
card type: VALUE_0.
COPCOM544E The file system size cannot be greater
than the physical volume size.
COPCOM545E Failed query the Active Directory
server with: VALUE_0.
COPCOM546I Report ran successfully.
COPCOM547I See attachment for the results.
COPCOM548E An unexpected error occurred: Class
VALUE_0 set in sourceClass attribute of
ka:search tag not found.
COPCOM549I The redefinition of Discovery name
VALUE_0 was ignored.
COPCOM550E The software resource template
definition VALUE_0 was not found.
COPCOM551E The software resource template
definition parameter VALUE_0 was not
found.
COPCOM552E The software resource template
definition parameter value VALUE_0
was not found.
COPCOM553E The template parameter value
VALUE_0 was not found.
COPCOM554I Usage: packageLogs [log_directory]
[config_directory]\n log_directory The
directory where the log files.\n If it is
not specified, the default log directory
specified by the system environment
will be used.\n config_directory The
directory where the configuration
files.\n If it is not specified, the default
configuration directory specified by the
system environment will be used.\n
COPCOM555E Cannot delete server before deleting
the depot VALUE_0.
378
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
COPCOM574E COPCOM597E
COPCOM574E Not valid credentials.
COPCOM575E The device is not supported.
COPCOM576E The IP address does not exists on the
network.
COPCOM577E The service is not running on the
host.
COPCOM578E The protocol used is wrong.
COPCOM579E The device is offline.
COPCOM580E The specified discovery configuration
is not an Initial Discovery.
COPCOM581E The Initial Discovery is already
running.
COPCOM582I Successful ping.
COPCOM583E The user, VALUE_0, is not found in
the LDAP. However the user account has
already been created in the data model.
Explanation: This user does not exist in the LDAP
registry. If the user is in the registry, then IBM Tivoli
Provisioning Manager cannot find the user with the
specified filter in the user-factory.xml.
User response: Verify if the user is in the LDAP
registry, and the user filter specified in the
user-fcatory.xml.
COPCOM584E LDAP registry cannot be connected.
Explanation: You Cannot connect to LDAP registry;
IBM Tivoli Provisioning Manager uses the information
in the user-factory.xml to connect to LDAP.
User response: Check whether the LDAP registry is
operational. It might be necessary to check the
information of the LDAP specified in the
user-factory.xml.
COPCOM585I The SOAP service is started.
379
COPCOM598E COPCOM611E
COPCOM598E Non fibre channel port VALUE_0
cannot have logical connections.
380
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
COPCOM613E COPCOM632E
COPCOM613E The workflow VALUE_0 with
deployment request ID: VALUE_1) has
failed.
381
COPCOM633E COPCOM651E
COPCOM633E The list of settings specified for the
[VALUE_0] compliance check of the
[VALUE_1] group are not valid.
User response: User should correct the list of not
valid settings for the specified group and then import
the compliance checks again.
COPCOM634E The import operation failed.
Duplicate names were found for the
VALUE_0 computer in the data model.
Explanation: The computer name must be unique for
the import operation to complete successfully.
User response: As the best practices, users should
define a unique computer name in the data model. If
the computer name is defined as a short name, change
it to the fully qualified hostname to make it unique.
COPCOM635E The import operation failed.
Duplicate names were found for the
VALUE_0 group in the data model.
Explanation: The group name must be unique for the
import operation to complete successfully.
User response: As the best practices, users should
define a unique group name in the data model. If a
group name is not unique, use name space to make the
group name unique in the data model.
COPCOM636E The [VALUE_0] setting belonging to
the [VALUE_1] compliance check of the
[VALUE_2] group is not valid or its
value is out of range.
User response: User should correct the not valid
setting and then import the compliance checks again.
COPCOM637E The system configuration file
VALUE_0 could not be read.
COPCOM638E The IP address VALUE_0 and the
IPv6 address VALUE_1 do not match the
protocol interface type VALUE_2.
382
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
COPCOM654E COPCOM715E
Maximo security framework.
User response: Ensure that the VMMSYNC has been
run and that the Maximo groups are added into the
Maximo table. After the problem is fixed, run the
workflow again.
COPCOM654E Errors were found during migraiton.
A summary of all the encountered
problems is shown as following.
COPCOM657E Migration of permission roles to
Maximo security group failed with error.
Check $TIO_LOG/console.log for
messages returned from the workflow.
COPCOM660E mapping DCM.View and
DCM.Update to Maximo Security
Restriction failed with error.
COPCOM661E The provisioning group for the access
security group, VALUE_0, cannot be
found.
COPCOM700E Cause:
383
COPCOM716E COPCOM748W
COPCOM716E There are no boot servers that
support the operating system of the
selected computer.
COPCOM717E An image with name {0} already
exists on boot server {1}. The image
name must be unique.
COPCOM718E This functionality is not available
because no workflow that implements
the logical management operation {0} is
assigned to {1}.
Explanation: A workflow that implements the logical
management operation {0} is not assigned to {1}.
User response: To enable this functionality, click the
Workflow tab and assign a device driver or a workflow
to {1}. The workflow must implement the logical
management operation {0}.
COPCOM719E The system cannot find the software
capability.
COPCOM720E Type a name for the image capture
task.
Explanation: Type a name for the image capture task.
COPCOM721E The timeout value is not valid.
COPCOM722E Select a source computer to capture
the image from.
COPCOM724E Select a source image to replicate.
COPCOM725E Type a name for the replicate image
task.
COPCOM726E Type a name for the destination
image.
384
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
COPCOM749E COPCOM787E
running, go to the Provisioning Task Tracking page and
verify that no boot server tasks are either scheduled to
run or currently running.
COPCOM749E The selected boot server cannot be
promoted to parent because it is not a
child boot server.
385
COPCOM788E COPCOM816W
COPCOM788E The mail server is not configured
properly. To set up the mail server, click
Go To > Administration > Provisioning
> Provisioning Global Settings and click
the Notification tab. Specify the mail
server settings and save them.
COPCOM789W Do you want to delete the data path?
COPCOM790E The "Enable Password" and "Confirm
Enable Password" for Password
Credential with Search Key {0} for
Service Access Point {1} do not match.
Type the passwords again.
COPCOM791E The "Passphrase" and "Confirm
Passphrase" for RSA Credential with
Search Key {0} for Service Access Point
{1} do not match. Type the passphrases
again.
COPCOM792E The "Private Key" and "Confirm
Private Key" for RSA Credential with
Search Key {0} for Service Access Point
{1} do not match. Type the private keys
again.
COPCOM793E The "Password" and "Confirm
Password" for Password Credential with
Search Key {0} for Service Access Point
{1} do not match. Type the passwords
again.
386
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
COPDEX001E COPDEX035E
COPDEX
This section contains messages with the COPDEX identifier for deployment subsystem messages for
Tivoli Provisioning Manager.
COPDEX001E The system cannot obtain a JNDI
context.
COPDEX002E The system cannot use the VALUE_0
JMS destination.
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.)
COPDEX004E The system cannot perform the type
conversion for VALUE_0 because the
type information was not set. (Field
argument type is null.)
387
COPDEX036E COPDEX066E
COPDEX036E An unassignable expression is bound
to output parameter VALUE_0.
388
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
COPDEX067E COPDEX102E
COPDEX067E The system cannot parse the XML
data: VALUE_0.
COPDEX077E The system cannot delete a query that
begins with a VALUE_0 variable.
COPDEX087E The workflow expects a locale that is
different from the one that is specified.
The locale of the device VALUE_0 is set
to VALUE_1. The workflow expects the
locale to be: VALUE_2.
COPDEX092E The system cannot find the VALUE_0
workflow. The system cannot export the
execution logs for this workflow.
COPDEX093E The system cannot create the VALUE_0
output file. Verify the directory path
and try again.
COPDEX094E The system cannot recognize the
VALUE_0 command option. Valid
options are -n [workflow name] or -r
[request id], -i [input file name] and -f
[output file name].
COPDEX096E The property retrieval query VALUE_0
is not valid. Review the documentation
to find the recommended procedures.
COPDEX097E The discovery keys file VALUE_0 is
not valid.
Explanation: The system cannot read the
DiscoveryKeys.ini file because the file includes errors.
User response: Correct the errors in the
DiscoveryKeys.ini file located in the
TIO_HOME/config subdirectory.
COPDEX098E The system obtained an empty profile
XML file name.
Explanation: The ITM Obtain OS Profiles workflow
generates an XML file that contains the list of profiles
installed in Tivoli Management Agent. This profile
XML file is copied to the IBM Tivoli Provisioning
Manager and then it is parsed by the Profile XML
Parser. The system encountered a problem when the
name of the profile XML file was an empty string.
User response: Verify that the ITM Obtain OS Profiles
workflow specifies the correct path to the
ProfileXMLParser Java plug-in.
389
COPDEX103E COPDEX111E
profiles was not transferred or generated correctly.
User response: Verify that the system successfully
processed the jdom.jar file, the XML data produced by
the wdmlseng command at the ITM server, and the file
transfer from the IBM Tivoli Monitoring server to the
server.
390
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
COPDEX115E COPDEX143E
COPDEX115E The system did not find the device ID
VALUE_0 in the data center model.
COPDEX116E The VALUE_0 is not locale sensitive. It
must include the LocaleInsensitive
qualifier.
COPDEX117E An error occurred when the system
tried to read the input file VALUE_0.
COPDEX118E An error occurred when the system
tried to export the workflow execution
log. The error is VALUE_0.
391
COPDEX144E COPDEX171E
COPDEX144E The number of parameters is not
valid. The workflow/LDO/JavaPlugin:
VALUE_0 requires VALUE_1 variables
instead of VALUE_2.
COPDEX145E The number of parameters is not
valid. The workflow/LDO/JavaPlugin:
VALUE_0 requires VALUE_1 variables
instead of VALUE_2.
392
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
COPDEX172E COPDEX193E
COPDEX172E The VALUE_0 variable is a single
value variable, cannot assign an array
value to it.
COPDEX173I Agent shell server heart beat
VALUE_0.
COPDEX174I Usage: workflowLogExport.cmd/sh
(-VALUE_0 [workflow name] or
-VALUE_1 [request id]) -VALUE_2
[output file name] -VALUE_3 [input file
name]. Example:
workflowLogExport.cmd -r 12345 -f
c:/myDirectory/myOutput.xml (if
outputFilename is not specified, the
default output file is: VALUE_4 ).
COPDEX175I The workflow logs are extracted in:
VALUE_0.
COPDEX176E The parameter VALUE_0 cannot be
null.
COPDEX177E Usage: workflowdoc [-d
destinationdirectory] [-pd
packagedescriptor] [-p packagename]
[sourcefiles]\n -d destinationdirectory
The destination directory where the
generated files.\n If it is not specified,
the current directory will be used.\n -pd
packagedescriptor The file name of an
automation package descriptor file (that
is tc-driver.xml file).\n The
documentation will be generated for all
workflows specified in the descriptor
file.\n It cannot be used together with
the -p option or sourcefiles.\n -p
packagename The name of the
automation package for which the
documentation will be generated.\n If it
is not specified, only the workflow
documentation is generated.\n It cannot
be used together with the -pd option.\n
-todos Include @todo annotations in the
generated files.\n sourcefiles List of
workflow source file names separated
by spaces.\n The elements in this list
can contain paths. Wildcards are
allowed in file names, but not in path
names.\n If it is not specified, the
system will generate documentation for
all .wkf files in the current directory. It
cannot be used together with the -pd
option.\n
393
COPDEX194E COPDEX208E
COPDEX194E Unused javaimport VALUE_0.
COPDEX195E The instruction ID VALUE_0 does not
exist.
Explanation: The workflow execution cannot find the
next instruction.
User response: Verify that the workflow is not
compiled or deleted while while it is running.
COPDEX196E The system cannot resolve the value
of the parameter VALUE_0.
COPDEX197E The value for parameter VALUE_0 is
too large to be persisted into database.
394
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
COPDSC001E COPDSC022E
COPDSC
This section contains messages with the COPDSC identifier for discovery messages for Tivoli
Provisioning Manager.
COPDSC001E The discovery {0} does not exists.
User response: Install the discovery {0}.
COPDSC002E The discovery method parameter is
missing.
395
COPDSC023E COPDSE015E
COPDSC023E The discovery wizard does not contain
any action. Add one or more actions to
the wizard.
COPDSC024E The Start and End IP addresses in the
range do not use the same IP protocol.
Explanation: The IP addresses in the range must use
the same IP protocol. They must both be either IPv4 or
IPv6.
COPDSE
This section contains messages with the COPDSE identifier for compliance messages.
COPDSE001E The system cannot update the
Windows Unauthorized Guest Access
compliance check with security
compliance check ID VALUE_0 because
the compliance check could not be
found in the data center model.
396
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
COPDSE016E COPDSE037E
COPDSE016E The system cannot validate the
non-supported compliance check setting
type: VALUE_0.
COPDSE017E The system cannot delete the file with
VALUE_0 ID. There is an associated
VALUE_1 with VALUE_2 ID that must be
deleted first.
COPDSE018E The property with the key value of
VALUE_0 in the device with VALUE_1
ID is not defined.
COPDSE019E The system cannot update the given
Windows screen saver setting because
the user account it belongs to cannot be
found in the data center model. The
user name of the account is VALUE_0.
COPDSE020E The Message log file name setting for
the VALUE_0 facility is not defined in
VALUE_1 with VALUE_2 ID.
COPDSE021E The system cannot instantiate the
compliance check with type VALUE_0.
COPDSE022E An event cannot be fired because one
or more of the broker, event, or
eventType objects is null. Their values
are broker: VALUE_0, event: VALUE_1,
and eventType: VALUE_2.
COPDSE023E The system cannot update the given
user defined compliance check because
it cannot be found in the data center
model. Its compliance check ID is
VALUE_0.
COPDSE024E An unexpected error occurred when
trying to call the method VALUE_0 on
VALUE_1 with VALUE_2 ID.
COPDSE025E Only a single computer can be used as
the source of actual state information for
the purpose of creating compliance
checks.
COPDSE026E Only a computer or a provisioning
group can be the target of a compliance
check. The given device with VALUE_0
ID is neither a provisioning group nor a
computer.
397
COPDSE038E COPDSE056E
COPDSE038E The system cannot perform the
selected action because there is no
recommendation being selected.
COPDSE039E The system cannot perform the
selected action because incompatible
recommendations have been selected for
multiple computers.
COPDSE040E The recommendation with ID:
VALUE_0 and target ID: VALUE_1 cannot
be added to the recommendation list
with target ID: VALUE_2.
398
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
COPDSE057E COPDSE109E
COPDSE057E Incorrect Patch approval source Id:
VALUE_0 for OS Patch and Update
compliance check, it should be either
patch id or patch group id.
COPDSE058E The system cannot create the software
configuration template for installation
VALUE_0 because its configuration
parameters cannot be scanned.
COPDSE059E The system cannot create the software
configuration template for installation
VALUE_0 because it does not have
software resource template.
COPDSE060E The system cannot delete the
discovery VALUE_0, because it is used
by software configuration compliance
check for software VALUE_1 of group or
computer VALUE_2.
COPDSE061E The system cannot delete the software
definition VALUE_0, because it is used
by software configuration compliance
check of group or computer VALUE_1.
COPDSE062E The system cannot delete the
discovery VALUE_0, because it is used
by software configuration compliance
check template VALUE_1.
COPDSE063E The system cannot delete the software
definition VALUE_0, because it is used
by software configuration compliance
check template VALUE_1.
COPDSE064E The system cannot get remediation
configuration.
COPDSE065E The system detected multiple
definitions for VALUE_0 in the
remediation configuration.
COPDSE066E The system cannot create a new
schedule to run compliance check or
compliance scan and check because
there is no compliance check defined for
the group or computer VALUE_0.
COPDSE067E The system cannot load Java class
with name: VALUE_0.
399
COPDSE110E COPDSE219I
COPDSE110E The specified software installation
state VALUE_0 is not supported.
COPDSE111E The specified group type VALUE_0 is
not supported.
COPDSE198I A compliance check of the computer
VALUE_0 has completed and one or
more noncompliant items was
identified. For details, refer to the
information on the Compliance tab for
this computer.
COPDSE199I A compliance check of the group
VALUE_0 has completed and one or
more noncompliant items were
identified. For details, refer to the
information on the Compliance tab for
this group.
COPDSE200I The compliant value for the AIX
Remote root login allowed setting is
VALUE_0 but the actual value is
VALUE_1.
COPDSE201I Change the value of the AIX Remote
root login allowed setting to VALUE_0
to match the compliant value.
COPDSE202I The compliant value for the Maximum
elapsed time setting is VALUE_0 hours,
but the actual value is VALUE_1 hours.
COPDSE203I Run an Windows antivirus scan.
COPDSE204I There is no supported antivirus
software installed.
COPDSE205I Install an antivirus software product,
such as Symantec AntiVirus, Trend
Micro Anti-Virus, McAfee VirusScan or
Sophos Anti-Virus.
COPDSE206I The compliant value of the Maximum
virus definition age setting is VALUE_0
days, but the actual value is VALUE_1
days.
400
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
COPDSE220I COPDSE244I
COPDSE220I The compliant value of the Active
setting for user VALUE_0 is VALUE_1,
but the actual value is VALUE_2.
401
COPDSE245I COPDSE266I
COPDSE245I Change the value of the Running state
setting of the VALUE_0 service to
VALUE_1 to match the compliant value.
COPDSE246I The compliant value of the VALUE_0
file for the Create Folders/Append Data
setting is VALUE_1, but the actual value
is VALUE_2.
COPDSE247I Change the value of the Create
Folders/Append Data setting for the
VALUE_0 file to VALUE_1 to match the
compliant value.
COPDSE248I The compliant value of the VALUE_0
file for the Delete Subfolders and Files
setting is VALUE_1, but the actual value
is VALUE_2.
COPDSE249I Change the value of the Delete
Subfolders and Files setting for the
VALUE_0 file to VALUE_1 to match the
compliant value.
COPDSE250I The compliant value of the VALUE_0
file for the Delete setting is VALUE_1,
but the actual value is VALUE_2.
COPDSE251I Change the value of the Delete setting
for the VALUE_0 file to VALUE_1 to
match the compliant value.
COPDSE252I The compliant value of the VALUE_0
file for the Traverse Folder/Execute File
setting is VALUE_1, but the actual value
is VALUE_2.
COPDSE253I Change the value of the Traverse
Folder/Execute File setting for the
VALUE_0 file to VALUE_1 to match the
compliant value.
COPDSE254I The compliant value of the VALUE_0
file for the Read Attributes setting is
VALUE_1, but the actual value is
VALUE_2.
COPDSE255I Change the value of the Read
Attributes setting for the VALUE_0 file
to VALUE_1 to match the compliant
value.
402
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
COPDSE267I COPDSE288I
COPDSE267I Change the value of the Change
Permissions setting for the VALUE_0
file to VALUE_1 to match the compliant
value.
403
COPDSE289I COPDSE310I
COPDSE289I Change the Minimum retention period
of application data to be equal to or
greater than the compliant value:
VALUE_0 days.
404
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
COPDSE311I COPDSE335I
COPDSE311I Change the value of the Windows
Service enabled to start automatically
setting for the firewall software
VALUE_0 to match the compliant value
VALUE_1.
COPDSE312I The compliant value of the Successful
system events setting is VALUE_0, but
the actual value is VALUE_1.
COPDSE313I Change the value of the Successful
system events setting to match the
compliant value VALUE_0.
COPDSE314I The compliant value of the Failed
system events setting is VALUE_0, but
the actual value is VALUE_1.
COPDSE315I Change the value of the Failed system
events setting to match the compliant
value VALUE_0.
COPDSE316I The compliant value of the Successful
logon events setting is VALUE_0, but
the actual value is VALUE_1.
COPDSE317I Change the value of the Successful
logon events setting to match the
compliant value VALUE_0.
COPDSE318I The compliant value of the Failed
logon events setting is VALUE_0, but
the actual value is VALUE_1.
COPDSE319I Change the value of the Failed logon
events setting to match the compliant
value VALUE_0.
COPDSE320I The compliant value of the Successful
object access setting is VALUE_0, but
the actual value is VALUE_1.
COPDSE321I Change the value of the Successful
object access setting to match the
compliant value VALUE_0.
COPDSE322I The compliant value of the Failed
object access setting is VALUE_0, but
the actual value is VALUE_1.
405
COPDSE336I COPDSE360I
COPDSE336I The compliant value of the Successful
account management setting is
VALUE_0, but the actual value is
VALUE_1.
COPDSE337I Change the value of the Successful
account management setting to match
the compliant value VALUE_0.
COPDSE338I The compliant value of the Failed
account management setting is
VALUE_0, but the actual value is
VALUE_1.
COPDSE339I Change the value of the Failed account
management setting to match the
compliant value VALUE_0.
COPDSE340I The compliant value of the Successful
directory service access setting is
VALUE_0, but the actual value is
VALUE_1.
COPDSE341I Change the value of the Successful
directory service access setting to match
the compliant value VALUE_0.
COPDSE342I The compliant value of the Failed
directory service access setting is
VALUE_0, but the actual value is
VALUE_1.
COPDSE343I Change the value of the Failed
directory service access setting to match
the compliant value VALUE_0.
406
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
COPDSE361I COPDSE403E
COPDSE361I Run a compliance check for this
computer to determine the compliance
status for the VALUE_0 setting.
COPDSE362I The compliant value for the Status
setting is VALUE_0, but the actual value
for the agent is VALUE_1.
COPDSE363I Execute agent commands as necessary
to make the agent's Status compliant
with the setting VALUE_0.
COPDSE364I The compliant value for the Maximum
elapsed time between contact setting is
VALUE_0 hours, but the actual value for
the agent is VALUE_1 hours.
COPDSE365I Change the value of the Maximum
elapsed time between contact setting to
be less than or equal to VALUE_0 hours.
COPDSE366I It is not possible to determine if the
VALUE_0 setting is compliant for the
computer because no compliance check
for this setting has been run.
COPDSE367I Run a compliance check to determine
the compliance status for the VALUE_0
setting for this computer.
COPDSE368I There is no supported firewall
software installed.
COPDSE369I Install a firewall software product,
such as Symantec Client Firewall,
McAfee Desktop Firewall, Windows
Native Firewall or Zone Alarms
Integrity Flex Firewall.
COPDSE370I Microsoft patch list or approved patch
list has changed since the last patch
scan, or the last patch scan was not
successful.
COPDSE371I Run patch discovery scan again.
COPDSE372I Patch VALUE_0 (id: VALUE_1) has no
software installable suitable for the
system VALUE_2 (id: VALUE_3).
407
COPDSE404E COPDSE577E
COPDSE404E The recommendation with ID: {0} is
not in a valid state for the run action.
Explanation: The run action is only allowed for
recommendations that are in the following states:
Approved, Failed, Implementing, Implemented.
User response: Select another set of recommendations
for the specified operation or specify an operation that
is compatible with the states of the selected
recommendations.
COPDSE405W The number of selected targets
exceeds the maximum recommended
value, which might affect performance.
Do you want to continue?
COPDSE407E Cannot add more than one patch
check.
Explanation: A Patch compliance check is already
defined for the current object. You cannot add more
than one patch compliance check.
COPDSE408W The template {0} is currently
referenced by a compliance check for a
computer or group. Are you sure you
want to delete it?
408
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
COPGRP001E COPGRP013E
COPGRP
This section contains messages with the COPGRP identifier for group messages.
COPGRP001E Cannot add the object VALUE_0 with
type VALUE_1 to the group VALUE_2
with type VALUE_3 because their types
are incompatible.
Explanation: The object cannot be added to the group
because the type of the group and the type of the object
are not compatible.
COPGRP002E Cannot add the group VALUE_0 to the
group VALUE_1 because it would cause
a membership cycle.
Explanation: The source group cannot be added to the
target group because the target group is already a
member of the source group or another group that is a
member of the source group.
COPGRP003E An error occurred during XML import
processing. The group with object ID
VALUE_0 could not be updated because
it could not be found.
Explanation: An update operation for a group failed
because the group could not be found.
COPGRP004E An error occurred during XML import
processing. The group with object ID
VALUE_0 could not be deleted because
it could not be found.
Explanation: A delete operation for a group failed
because the group could not be found.
COPGRP005E An error occurred during XML import
processing. The group membership with
object ID VALUE_0 could not be
updated because it could not be found.
Explanation: An update operation for a group
membership failed because the group could not be
found.
COPGRP006E An error occurred during XML import
processing. The group membership with
object ID VALUE_0 could not be deleted
because it could not be found.
Explanation: A delete operation for a group
membership failed because the group could not be
found.
409
COPGRP014E COPINF013E
COPGRP014E An access group cannot be created for
the VALUE_0 group because it is a
dynamic group. Access groups can only
be associated with static groups.
COPGRP015E The group VALUE_0 is empty and not
dynamic
COPGRP016E No query was specified for the
<q></q>{0}<q></q> dynamic group.
Explanation: <p>An attempt was made to determine
the list of members for a dynamic group, but no query
has been specified for the group. The operation to get
the list of members failed.</p>
COPGRP100E The specified group name already
exists.
Explanation: The same group name cannot be used
for more than one group.
User response: Specify a different group name and
save the group.
COPINF
This section contains messages with the COPINF identifier for infrastructure messages.
COPINF001E
COPINF004E
COPINF005E
COPINF006E
COPINF007E
COPINF008E
COPINF009E
COPINF010E
COPINF011E
COPINF012E
COPINF013E
COPINF002E
410
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
COPINF014E COPINF043E
COPINF014E
COPINF029E
COPINF015E
COPINF016E
COPINF017E
COPINF031E
COPINF018E
COPINF032E
COPINF019E
COPINF033E
COPINF020E
COPINF034E
COPINF021E
COPINF022E
COPINF026E
COPINF027E
COPINF028E
COPINF035E
COPINF036E
COPINF037E
COPINF038E
COPINF039E
COPINF040E
COPINF041E
CDS_DynamicPublishEnable property
is false and Software Product VALUE_0
has not been pre published.
COPINF042E
COPINF043E
411
COPINF044E COPINF120E
COPINF044E
COPINF045E
COPINF046E
COPINF047E
COPINF048E
COPINF049E
COPINF050E
COPINF052E
412
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
COPINF121E COPINF146E
COPINF121E The Fully Qualified Hostname field is
a required field.
413
COPINF147E COPJEE009E
COPINF147E Select at least one virtual IP address
for the action.
COPINF148W Do you want to delete the selected
virtual IP addresses?
User response:
COPJDS
This section contains messages with the COPJDS identifier for Job Distribution Service subsystem
messages.
COPJDS001E An incorrect value was specified for
parameter VALUE_0.
COPJEE
This section contains messages with the COPJEE identifier for J2EE subsystem messages.
COPJEE001E The system cannot generate the logical
deployment because it could not find
the application module VALUE_0.
414
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
COPJEE010E COPJEE037E
COPJEE010E The logical deployment template node
VALUE_0is not supported.
Explanation: The logical deployment template node
supports physical machine, virtual machine, application
tier, external, and load balancer. All other logical
deployment template node types are not compatible.
COPJEE011E The system tried to access a user
interface configuration instance before it
was initialized. Reload the page, wait
for the page to load completely, and
then proceed.
COPJEE013E The system cannot initialize the
deployment request VALUE_0.
COPJEE014E The deployment engine could not
complete the request. The request
domain VALUE_0 is missing EJB
interaction class information. The
ejbInteractionProxy attributes and the
ejbInteractionMethod attributes must be
specified.
COPJEE015E The application cannot find the host
system for ID VALUE_0.
COPJEE016E The system cannot find the license
broker for ID VALUE_0.
COPJEE017E There is not enough data to validate the
pool and application tier. Either the
application tier is not managed or the
application tier pool ID is null.
COPJEE018E There is not enough data to validate the
pool and application tier. The
application tier ID is null and the pool
ID is null.
COPJEE019E The system cannot find the software
product ID VALUE_0.
COPJEE020E An unexpected error occurred. The
unknown credentials type ID is
VALUE_0.
COPJEE025E An unexpected deployment engine
exception occurred. The lock manager
ID VALUE_0 is not valid.
415
COPJEE038E COPJEE063E
COPJEE038E The system cannot find the user
credentials VALUE_0.
416
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
COPJEE064E COPJEE094E
back again as a resource pool server.
COPJEE064E The system has identified an exception
in the fault management integration
subsystem. See the nested exception for
more details.
COPJEE065E The system does not support manual
deployment when you operate in
VALUE_0 mode.
COPJEE068E The deployment request parameter
VALUE_0is missing.
COPJEE069E The NIC ID must be specified when the
device includes more than one NIC.
COPJEE070E The recommendation VALUE_0 is
obsolete and has been replaced.
417
COPJEE095E COPJEE128I
configuration with the same device driver and
monitoring application for this resource.
User response: Ensure that the monitoring
configuration used for this discovery is correct. If
changes need to be made, add a discovery association
with the appropriate monitoring configuration.
418
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
COPJEE129I COPJEE167E
COPJEE129I The system is processing request ID:
VALUE_0 VALUE_1 to remove a server
from the virtual IP.
COPJEE130I The system is processing request ID:
VALUE_0 VALUE_1 to create a
connection.
COPJEE131I The system is processing request ID:
VALUE_0 VALUE_1 to remove a
connection.
COPJEE132I The system is processing the request to
create a connection between the two
subnets.
COPJEE133I The system is processing the request to
remove an ACL.
COPJEE134I The system is processing the request to
enable an ACL.
COPJEE135I The system is processing the request to
disable an ACL.
COPJEE136I The system is processing request ID:
VALUE_0 VALUE_1 to reboot the device
hardware.
COPJEE137I The system is processing request ID:
VALUE_0 VALUE_1 to reboot the device
software.
COPJEE138I The system is processing request ID:
VALUE_0 VALUE_1 to initialize the
device.
COPJEE141I The system is processing request ID:
VALUE_0 VALUE_1.
COPJEE149E One or more service access points are
associated with this device.
COPJEE150E One or more serial cards are associated
with this device.
COPJEE151I The system has initiated data center
interaction ID: VALUE_0.
419
COPJEE176E COPJEE208E
COPJEE176E This product has already been added. It
might be nested in other stacks.
COPJEE177E This stack has already been added.
Perhaps it is nested in other stacks.
COPJEE178E The system cannot delete the terminal
server because service access points or
credentials are associated with the
device.
COPJEE179E The system cannot delete the terminal
server because NICs are associated with
the device.
COPJEE180I The system is processing request ID:
VALUE_0 VALUE_1 to add a virtual IP
to the load balancer.
COPJEE181E The system cannot add the virtual IP to
the load balancer because the load
balancer ID is not valid.
COPJEE182I The system is processing request ID:
VALUE_0 VALUE_1 to remove a virtual
IP from the load balancer.
COPJEE183E The system cannot process request ID:
VALUE_0 VALUE_1 to remove the virtual
IP from the load balancer because the
load balancer or the virtual IP are not
valid.
COPJEE189I The system is processing request ID:
VALUE_0 VALUE_1 to remove a real IP
from the load balancer.
COPJEE190E The system cannot remove the real IP
from the virtual IP because the virtual
IP, load balancer, or real IP ID is not
valid.
COPJEE191I The system is processing request ID:
VALUE_0 VALUE_1 to add a real IP to
the load balancer.
COPJEE192E The system cannot add a real IP to the
virtual IP because the virtual IP, load
balancer, or real IP ID is not valid.
420
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
COPJEE209E COPJEE268E
COPJEE209E The system cannot create the discovery
technology association with this
resource.
Explanation: The system failed to create a discovery
technology association due to an error.
User response: Try to create the discovery technology
association again. If the problem continues, contact
your data center database administrator.
421
COPJEE269E COPJEE302E
COPJEE269E The system cannot add the DcmObject
with ID VALUE_0 to the DCF with ID:
VALUE_1. The DcmObjectType is not
supported by the DCF.
422
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
COPJEE303E COPJEE334E
COPJEE303E The consumable size must consist of an
integer value and an unit value in 'K',
'M', 'G' or 'T'; if the size is in bytes, do
not enter any unit value.
COPJEE304E The LUN VALUE_0 in fibre channel port
VALUE_1 is not available.
COPJEE305E Storage volume VALUE_0 in storage
subsystem VALUE_1 already exists.
COPJEE308E The HBA port or FA Port with ID
VALUE_0 does not have a WWN
defined.
COPJEE309E The fibre channel switch with ID
VALUE_0 does not have a domain ID
defined.
COPJEE310E The system cannot remove zone
members for a zone because no fibre
channel ports are present.
COPJEE311E The storage volume with ID VALUE_0
does not belong to the storage pool with
ID VALUE_1.
COPJEE312E The storage volume with ID VALUE_0
does not belong to the storage
subsystem with ID VALUE_1.
COPJEE313E The given SAN port with ID VALUE_0
does not belong to the SAN fabric with
ID VALUE_1.
423
COPJEE335E COPJEE357E
COPJEE335E Instantiation of DB driver VALUE_0
failed.
COPJEE336E An SQL exception occurred while
executing the reporting SQL statement
VALUE_0 for report VALUE_1.
424
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
COPJEE358E COPJEE377E
COPJEE358E The report cannot be found in the
database VALUE_0. Make sure the report
is registered and check whether the
report is in the REPORT database table.
Explanation: The report cannot be found in the
REPORT database table.
COPJEE359E The database connection failed to
commit when creating the user
specification for the report. Report:
VALUE_0, report ID: VALUE_1, User
specification name: VALUE_2, User ID:
VALUE_3.
Explanation: The database connection fails to commit.
COPJEE360E The database connection failed to
commit when creating the report.
Report: VALUE_0.
Explanation: The database connection fails to commit.
COPJEE361E The database connection failed to close
when creating the report. Report:
VALUE_0.
Explanation: The database connection fails to close.
COPJEE362E The JSP file was not created when using
report creator. JSP file: VALUE_0.
Explanation: This is a file IO exception.
COPJEE363E The JSP file path for the report already
exists. Path: VALUE_0.
Explanation: The file already exists.
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, was not
entered.
COPJEE366E The user's report definition was not
created. Report: VALUE_0.
Explanation: This is an internal code error.
425
COPJEE378E COPJEE391W
COPJEE378E Fibre channel port number VALUE_0 is
out of range in the fibre channel switch.
COPJEE379E The workflow was already added.
COPJEE380E An SQL exception occurred while
executing the scheduled
Group_Status_Updater snapshot task.
Explanation: The database failed to commit.
User response: Verify that the database is operating
correctly.
COPJEE381E An unexpected user interface error
occurred. Wrong configuration for:
action=VALUE_0, objectType=VALUE_1.
Explanation: This happens when the requested page
item collection does not exist.
COPJEE383I The number of records returned by the
query : VALUE_0 is higher than the
maximum number of records expected:
VALUE_1.
Explanation: This happens when the query is too
generic.
User response: The query for recommendations needs
to be refined.
COPJEE384E You cannot delete the user-defined
report VALUE_0, because you are not its
owner.
COPJEE385E You cannot delete the report definition
VALUE_0, because you are not its owner.
COPJEE386E IP address VALUE_0 is already used by
other network interface of this system.
User response: Make sure the IP address specified is
not used by other network interface of the same
system.
COPJEE387E The system cannot create the credential
because its search key VALUE_0 is
already used by other credential of this
access point.
User response: Make sure the search key of the
credential is not used by other credentials of the access
point.
426
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
COPJEE392E COPJEE397E
the last selected software are available on the selected
computers.
Administrator response: The requirements of last
selected software cannot be matched by the capabilities
of any selected computers.
COPJEE392E The system cannot delete the software
module VALUE_0 when applications are
still associated.
Explanation: A software module cannot be deleted
when it has one or more applications associated with it.
User response: Before deleting the software module,
delete the associated applications.
COPJEE392W No computers in VALUE_0 group
matched the requirements of the
selected software.
Explanation: No computers in the last selected group
match the pre-requisites of the selected software.
User response: Ensure that the pre-requisites for the
selected software are met by the computers in the
selected group. Selected software cannot be installed on
any of the computers from the last selected group.
Administrator response: The capabilities of all
computers in the last selected group do not match the
requirements of the selected software.
COPJEE393E The system cannot create the
credentials, because the search key
VALUE_0 is not unique across the local
TIO server and this server for the same
credential type. Another credential type
on the local TIO server or this server is
already using the same search key.
Explanation: For proper communication, the search
key for the same credential type must match between
the local TIO server and this server.
User response: Ensure that the search key is not
already used on the local TIO server or by a different
credential type on this server .
COPJEE393W The VALUE_0 software is not installed
on any computer.
Explanation: The last selected software is not installed
on any computer.
User response: The last selected software is not
installed on any computer.
Administrator response: The last selected software is
not installed on any computer.
427
COPJEE397W COPJEE411W
COPJEE397W Import operation failed.
COPJEE398W File VALUE_0 cannot be accessed.
Import operation failed.
COPJEE399W The category does not contain any
reports to export.
COPJEE400W The report could not be created.
COPJEE401W The report could not be deleted due to
IO errors.
COPJEE402W The VALUE_0 software cannot be
distributed on some computers.
Explanation: The last selected software cannot be
distributed on selected computers.Selected computers
do not match the pre-requisites of the selected software
User response: The pre-requisites of last selected
software cannot be satisfied by the selected computers.
Administrator response: The requirements of the last
selected software do not match the capabilities of the
selected computers.
428
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
COPJEE412E COPJEE417E
User response: Ensure that all the computers in the
last selected pool satisfy the pre-requisites for the
selected software. Some computers in the last selected
pool did not satisfy the pre-requisites for the selected
software. Software will not be installed on such
computers.
Administrator response: The capabilities of some
computers in the last selected pool do not match the
requirements of the selected software. Software will not
be installed on incompatible computers.
COPJEE412E No run-command credentials are
defined for computer VALUE_0.
Explanation: The run-command credentials are
required.
COPJEE412W
COPJEE414W
429
COPJEE417W COPJEE433W
User response: Define the specified Discovery
Configuration.
COPJEE417W
COPJEE419W
430
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
COPJEE434W COPJEE441W
COPJEE434W
COPJEE438W
COPJEE435W
COPJEE439W
COPJEE441W
431
COPJEE442E COPJEE447W
selected agent. Some computers in the last selected tier
did not satisfy the pre-requisites for the selected agent.
Agent will not be installed on such computers.
Administrator response: The capabilities of some
computers in the last selected tier do not match the
requirements of the selected agent. Agent will not be
installed on incompatible computers.
COPJEE442E Failed to print report metadata elements.
COPJEE442W
432
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
COPJEE448E COPJEE564W
Administrator response: Some computers from the
selected pool do not have the capability to match the
requirements of the selected agent.
COPJEE448E The hub cannot be added because
VALUE_0 already exists.
Explanation: A hub cannot be added if one already
exists.
COPJEE448W No configuration templates for
software VALUE_0 matching all targets.
Reduce target selection and try again.
Explanation: None of the configuration templates for
a software matched all the selected targets
User response: Ensure that at least one of the
configuration template requirements for each selected
softwares matched the capabilities of the targets
selected.
Administrator response: Ensure that at least one of
the configuration template requirements for each
selected softwares matched the capabilities of the
targets selected.
COPJEE449E The VALUE_0 cannot be added because
the host name VALUE_1 is already
defined.
Explanation: A hub or spoke cannot be added if its
host name is already defined for another hub or spoke.
COPJEE449I A temporary report size limit of
VALUE_0 has been set.
COPJEE564W
433
COPJEE565W COPJEE572W
Administrator response: Some computers from the
selected group did not have any software installation
with SoftwareResource.Upgrade LDO associated.
COPJEE565W
434
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
COPJEE573W COPNET020E
COPJEE573W
COPNET
This section contains messages with the COPNET identifier for networking messages.
COPNET001E There are multiple MPLS paths with
the name: VALUE_0.
435
COPNET021E COPNET584W
COPNET021E The system cannot find the real IP
VALUE_0.
COPNET022E The system cannot find the load
balancer type VALUE_0.
COPNET023E The system cannot find the VALUE_0
router.
COPNET024E The system cannot find the VALUE_0
access control list.
COPNET025 The system cannot find the address
space VALUE_0.
User response: Define the address space.
436
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
COPNET585W COPOSD016E
COPNET585W The device cannot be accessed due to
SNMP agent not running.
Explanation: The device is not SNMP enabled because
an SNMP agent is not running.
User response: Activate the SNMP agent on the
device and then run the discovery again.
COPOSD
This section contains messages with the COPOSD identifier for OS deployment with the Tivoli
Provisioning Manager for OS Deployment boot server.
COPOSD001E Attribute VALUE_0 is not specified,
unable to load page.
437
COPOSD017E COPOSD029E
COPOSD017E Error cancelling OS deployment
activity VALUE_0.
438
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
COPPCH001E COPPCH025W
COPPCH
This section contains messages with the COPPCH identifier for patch management messages.
COPPCH001E Select one or more patches that you
want to uninstall.
439
COPPCH026E COPPCH056E
COPPCH026E There are no patches to download.
Run the discovery to populate the list of
patches so that you can download them.
COPPCH027E There are no patches to select. Either
all available patches are selected
already, or there are no patches
published.
User response: Verify that patches have been
published so that you can unpublish them.
COPPCH028E There are no depots to select. Either
all available depots are selected already,
or there are no patches selected.
User response: Select the patches that you want to
unpublish to a depot.
COPPCH029E Remove all depots that you have
selected, then select all patches that you
want to unpublish, and then select the
depots again.
COPPCH030E Type a name for the patch
unpublishing task.
COPPCH031E Select one or more patches to be
unpublished.
Explanation: At least one patch must be selected for
the patch unpublishing task.
COPPCH032E Select one or more depots for the
patch unpublishing task.
Explanation: At least one depot must be selected for
patch unpublishing task.
COPPCH034E Select one or more patches that you
want to publish.
COPPCH035E Select one or more depots to publish
the patches to.
COPPCH036E Type a name for the patch publishing
task.
COPPCH039E Select one of the Patch Upgrade
options.
440
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
COPPCH057E COPQLX008E
COPPCH057E Passwords typed do not match,
re-enter your passwords
Administrator response: Password and Confirm
Password should be same.
COPPCH059W Verify that WUA is downloaded in
the file repository before installing it. If
WUA has not been downloaded, go to
the Windows Update Agent Installation
page to download and install WUA.
User response: Verify that WUA is downloaded in the
file repository.
COPPCH062E There is no YUM file repository
configured. Use the File Repositories
page to configure a YUM file repository.
COPQLX
This section contains messages with the COPQLX identifier for data model query language execution
messages.
COPQLX001E The system cannot find the data center
model object VALUE_0.
441
COPQLX009E COPQLX028E
COPQLX009E The system cannot process the data
update: VALUE_0.
COPQLX010E The variable name VALUE_0 is not
valid.
COPQLX011E The system requires an object here:
VALUE_0.
COPQLX012E The system requires an attribute here:
VALUE_0.
COPQLX013E The system requires an object or an
attribute here: VALUE_0.
COPSRV
This section contains messages with the COPSRV identifier for server management messages.
442
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
COPSRV002W COPSRV026W
COPSRV002W Credential creation failed.
443
COPSRV030W COPSRV059W
COPSRV030W Host Platform id is empty
Explanation: The host platform is not selected or
empty
User response: Select at least one host platform for the
action
COPSRV031W Are you sure you want to synchronize
the selected virtual servers?
COPSRV032W Are you sure you want to run
inventory scan?
COPSRV035E Virtual Server Name is a required
field.
User response: Enter a valid name in Virtual Server
Name field.
COPSRV036E Name is a required field.
COPSRV040E No host platforms are selected for this
action.
Explanation: At least one host platform must be
selected for the action.
User response: Select at least one host platform for the
action.
444
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
COPSRV060E COPSRV081E
COPSRV060E Specify a value in the Software field.
COPSRV061E Specify a value in the Software
Version field.
COPSRV062E A service access point of type {0} is
already defined for port {0}.
Explanation: A service access point of type {0} for port
{0} cannot be defined because it already exists.
User response: Make sure that the port for which you
want to define a service access point is not used.
COPSRV063E An operating system is already
defined.
Explanation: An operating system is already installed
on the computer.You cannot add an operating system
for that computer.
COPSRV064E The interface that manages the NIC
resource is already defined. You can
only have one interface to manage the
NIC resource.
COPSWD
This section contains messages with the COPSWD identifier for software deployment messages.
Chapter 25. Messages
445
COPSWD002E COPSWD036E
COPSWD002E Select at least one software for
deletion
446
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
COPSWD037E COPSWD066E
COPSWD037E Remove all depots that you have
selected, then select all softwares that
you want to unpublish, and then select
the depots again.
COPSWD038E Type a name for the software product
unpublishing task.
COPSWD039E Select one or more software products
to be unpublished.
Explanation: At least one software products must be
selected for the software unpublishing task.
COPSWD040E Select one or more depots for the
software unpublishing task.
Explanation: At least one depot must be selected for
software unpublishing task.
COPSWD041E Type a name for the software product
publishing task.
COPSWD042E Select one or more softwares to be
published.
Explanation: At least one software must be selected
for the software publishing task.
COPSWD043E Select one or more depots for the
software publishing task.
Explanation: At least one depot must be selected for
software publishing task.
COPSWD044E There are no files to select. Either all
available files are selected already, or
there are no files published.
COPSWD046E Select one or more files that you want
to publish.
COPSWD047E Select one or more computers or
provisioning groups to publish the files
on.
COPSWD048E Type a name for the file publish task.
COPSWD049E Select one or more files that you want
to UnPublish.
447
COPSWD067E COPTCA001E
User response: Select at least one software for
installation.
COPSWD067E Installable Path is a required field.
COPSWD068E The software product does not have
any installables and cannot be installed.
COPSWD069E Some of the selected software
products cannot be installed.
COPSWD070E A module with the same name,
version, vendor, and build already
exists.
COPSWD071E The installable name already exists.
Type a different name for the
installable.
COPSWD072E From the selected software products,
one or more are not installed on any
computer.
COPTCA
This section contains messages with the COPTCA identifier for common agent subsystem messages.
COPTCA001E Cannot get proxy for interface on
Agent: VALUE_0.
448
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
COPTCA002E COPTCA024E
configured correctly and that the appropriate subagents
are installed.
COPTCA002E Unable to connect to the common
agent endpoint running on computer
VALUE_0 at IP port VALUE_1. Ensure
that the Tivoli Common Agent service is
started and available.
Explanation: The Agent Manager cannot communicate
properly with the agent. Verify that the Agent is
configured correctly and the appropriate subagents are
installed.
COPTCA003E The argument VALUE_0 is not valid.
Make sure that the parameter is of the
right type and that it is not empty.
COPTCA004E The subagent VALUE_0 failed to
install on the endpoint.
Explanation: For more information, check the log file
logs/msgAgent.log on the endpoint in the agent install
directory.
COPTCA005E The subagent VALUE_0 failed to start
on the endpoint.
Explanation: For more information, check the log file
logs/msgAgent.log on the endpoint in the agent install
directory.
COPTCA006E Error installing subagent VALUE_0 on
the endpoint: VALUE_1.
Explanation: For more information, check the log file
logs/msgAgent.log on the endpoint in the agent install
directory.
COPTCA007E The subagent VALUE_0 failed to
uninstall on the endpoint.
Explanation: For more information, check the log file
logs/msgAgent.log on the endpoint in the agent install
directory.
COPTCA008E Error uninstalling subagent VALUE_0
on the endpoint.
Explanation: For more information, check the log file
logs/msgAgent.log on the endpoint in the agent install
directory.
COPTCA009E Error Copying Subagent jar VALUE_0
to the endpoint.
449
COPTCA025E COPTDM016I
COPTCA025E Could not find the Discovery Results
Upload server.
Explanation: The global variable
Discovery.Upload.HostName is not defined correctly.
COPTDM
This section contains messages with the COPTDM identifier for automation package manager subsystem
messages.
COPTDM001E The system does not support the
VALUE_0 operating system running
Kula.
COPTDM002I Driver directory: VALUE_0.
COPTDM003E The application is not specified.
COPTDM003I Installing driver VALUE_0, force:
VALUE_1, installItems: VALUE_2.
COPTDM004E Authentication is required, but the
system cannot find the credentials for
SAP ID VALUE_0 and search key
VALUE_1.
450
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
COPTDM017E COPTDM040E
COPTDM017E The system cannot find the default
protocol endpoint for device ID
VALUE_0, operation VALUE_1.
COPTDM017I Associating workflow VALUE_0 with
Device Model VALUE_1.
COPTDM018E The system cannot find the device
operation type VALUE_0.
COPTDM018I Uninstalling driver item VALUE_0.
COPTDM019I Removing DCM_OBJECT entry for
TCDriver VALUE_0.
COPTDM020E The system cannot find the service
access point ID VALUE_0.
COPTDM020I Executing postinstallation workflow
for TCDriver VALUE_0.
COPTDM021E The system cannot find the server
with IP address VALUE_0.
COPTDM021I Deleting Device Model data for
VALUE_0, ID =VALUE_1.
COPTDM022E The system cannot find the VALUE_0
software product.
COPTDM022I Dissociating the device model data
from data center model object VALUE_0,
ID =VALUE_1.
COPTDM023E The system cannot find the virtual IP
address VALUE_0.
451
COPTDM041E COPTDM075E
COPTDM041E The left hand side string is null, but
the right hand side string is VALUE_0.
COPTDM042E The left hand side string is VALUE_0,
but the right hand side string is
different.
COPTDM044E The argument is not valid. The
RuntimeParameters value is null.
COPTDM045E The argument is not valid because
the RuntimeParameters value cannot be
null.
COPTDM051E The system cannot find the VALUE_0
software stack within VALUE_1.
COPTDM052E The system cannot look up the
software stack entry with parent ID
VALUE_0 and child stack ID VALUE_1.
COPTDM054E An unexpected error occurred. The
system cannot find the VALUE_0
workflow.
COPTDM057E An unexpected driver error occurred.
The VALUE_0 server is already known
by the load balancer VALUE_1.
COPTDM059E The database connection is not
functioning properly.
COPTDM060E The JDBC driver caused an SQL
exception.
COPTDM061E The DCM object is not configured to
retrieve the packager information.
COPTDM062E The system cannot allocate the IP
address.
COPTDM063E The system cannot allocate the server.
COPTDM064E The system cannot allocate virtual
server VALUE_0.
COPTDM065E The system cannot commit unknown
discovered devices from the NetView
dump file: VALUE_0.
Explanation: An error occurred while the system
attempted to commit the unknown devices to the
database from the Java plug-in
452
DiscoveryNetviewGetNewDevices.
User response: Try running the NetView Discover
workflow again. If the problem continues, contact your
database system administrator.
COPTDM066E The system cannot configure
monitoring for the VALUE_0 resource
that uses the VALUE_1 monitoring
application. Request ID: VALUE_2.
Explanation: The system cannot configure monitoring
for the resource.
User response: Search the workflow execution history
for errors that use the request ID. Review all the
transitions and then try again.
COPTDM068E The layer 1 interface type is not valid
for switch port VALUE_0/VALUE_1 on
device ID VALUE_2.
COPTDM069E The system cannot find the access
control list by network interface ID
VALUE_0.
COPTDM070E The system cannot find the service
access point for device ID VALUE_0 with
protocol VALUE_1 and context VALUE_2.
COPTDM071E The system cannot find a service
access point for device ID VALUE_0 with
protocol VALUE_1 and credentials key
VALUE_2.
COPTDM072E The system cannot find the service
access point for device ID VALUE_0 with
protocol VALUE_1 on port VALUE_2 and
context VALUE_3.
COPTDM073E The system cannot find the VALUE_0
discovery keys file.
Explanation: The DiscoveryKeys.ini file might not be
located in the config subdirectory.
User response: Create the DiscoveryKeys.ini file and
copy it to the TIO_HOME/config subdirectory.
COPTDM074E The system cannot find the software
entity parameter for entry ID VALUE_0
named VALUE_1.
COPTDM075E The system cannot find the
management IP address for device ID
VALUE_0.
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
COPTDM076E COPTDM100E
COPTDM076E There are no client credentials on
device ID VALUE_0 that are usable for
the host SAP ID VALUE_1. Review the
documentation for SAPs and credentials
and ensure your client and host
credentials match.
COPTDM077E The system cannot find the
monitoring application with ID
VALUE_0.
Explanation: The system cannot find the monitoring
application with the given ID.
User response: Provide a valid monitoring application
ID.
COPTDM078E The system cannot find the
netboot-enabled NIC for system ID
VALUE_0.
COPTDM079E The system cannot find the network
interface name for network interface ID
VALUE_0.
COPTDM080E The system cannot find the password
credentials VALUE_0.
COPTDM081E The system cannot find the software
product parameter for product ID
VALUE_0 named VALUE_1.
COPTDM082E The system cannot find the RSA
credentials VALUE_0.
COPTDM083E The system cannot find credentials
for the file copy with the SAP ID
VALUE_0 and credentials key VALUE_1.
COPTDM084E The system cannot find the SNMP
credentials VALUE_0.
COPTDM085E The system cannot find the
credentials for device ID VALUE_0 and
the SAP ID VALUE_1 with the
credentials key VALUE_2.
COPTDM087E The system cannot find the software
product ID VALUE_0.
COPTDM088E The subnetwork ID is not specified
and the system cannot derive the
subnetwork ID from the IP address.
453
COPTDM101E COPTDM128E
COPTDM101E The system cannot start the
monitoring resource VALUE_0 using the
VALUE_1 monitoring application.
Request ID VALUE_2.
Explanation: The system cannot start monitoring the
resource.
User response: Search the workflow execution history
for errors that use the request ID. Review all 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.
User response: Search the workflow execution history
for errors that use the request ID. Review all of the
transitions and then try again.
COPTDM103E The system cannot uninstall the
application on VALUE_0.
COPTDM104E The system detected an exception in
the Java Static Method Invocation
command driver
(MethodInvocationVariableBroker).
COPTDM105E An error occurred in the embedded
logical management operation.
COPTDM106E The system cannot find compatible
SAPs between device ID VALUE_0 and
VALUE_1 for operation VALUE_2.
COPTDM107E The argument (VALUE_0=VALUE_1) is
not valid. Make sure that the parameter
is of the right type and that it is not
empty.
COPTDM108E The integer value VALUE_0 is not
valid.
COPTDM109E The load balancing algorithm
VALUE_0 is not valid.
COPTDM110E The SNMP value
(VALUE_0=VALUE_1, type VALUE_2) is
not valid.
454
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
COPTDM129E COPTDM171E
COPTDM129E For this operation, the credentials ID
VALUE_0 must be RSA credentials.
COPTDM130E For this operation, the credentials ID
VALUE_0 must be SNMP credentials.
COPTDM131E The SecureShell (SSH) configuration
is not valid.
COPTDM132E The credentials ID VALUE_0 must be
password credentials or RSA credentials.
COPTDM133E The timeout value
VALUE_0=VALUE_1 is not valid.
COPTDM134E The switch configuration for VLAN #
VALUE_0 is not correct.
COPTDM136E The IP address cannot be null.
COPTDM137E The load balancer reached its
maximum number of real servers.
COPTDM138E A default route must be specified for
the destination subnetwork.
COPTDM141E The PING failed.
455
COPTDM172E COPTDM186E
COPTDM172E An error occurred when the system
uninstalled the VALUE_0driver because
the driver status must be VALUE_1.
COPTDM173E The configuration directory must be
specified in the tcdrivermanager.xml
file.
COPTDM174E The driver directory must be
specified in the -Dkanaha.drivers= VM
property.
COPTDM175E The format for the automation
package documentation item is not
valid. An exception occurred while the
system was reading the documentation
item.
COPTDM176E An error occurred when the system
run the configureMonitoring logical
management operation for the VALUE_0
resource using the VALUE_1 monitoring
application.
Explanation: An error occurred while the system run
the MonitoringApplication.ConfigMonitoring logical
management operation.
User response: Search for a workflow that implements
the MonitoringApplication.ConfigMonitoring logical
management operation. If the workflow exists, examine
the transitions in the workflow.
456
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
COPTDM187E COPTDM204E
COPTDM187E The automation package VALUE_0 is
not found in the directory VALUE_1
specified by tcdrivermanager.xml in
your configuration directory.
COPTDM188E The installed automation package
VALUE_0 has a newer version. Installed
Version: VALUE_1 To be installed
version: VALUE_2.
COPTDM193E Multiple default values were set for
template property VALUE_0.
COPTDM194E No license is found for the device
driver VALUE_0.
COPTDM195E No driver information is found for
automation package VALUE_0.
COPTDM196E The argument is not valid. The
automation package cannot be null.
Explanation: The method for installing automation
package has been passed an incorrect argument.
457
COPTMF001E COPTMF018E
COPTMF
This section contains messages with the COPTMF identifier for the Tivoli Management Framework
messages in Tivoli Provisioning Manager.
COPTMF001E
COPTMF001I
COPTMF002E
COPTMF002I
Start Replication
COPTMF003E
COPTMF003I
COPTMF010I
COPTMF005E
COPTMF005I
COPTMF004E
.
COPTMF014E
COPTMF014I
COPTMF007I
COPTMF015I
COPTMF008E
COPTMF008I
Plan Replicated
COPTMF016I
COPTMF010E
458
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
COPTMF018I COPTMF033I
COPTMF018I
COPTMF026I
COPTMF019I
COPTMF027I
COPTMF023E
COPTMF023I
COPTMF031E
COPTMF024E Base Software Package name for
delta install is not valid.
COPTMF024I
Replicating repeaters.
COPTMF031I
Invalid parameter.
459
COPTMF034E COPTMF048E
COPTMF034E Values for Auto-accept and Undo
parameters are not consistent.
COPTMF034I
COPTMF042I
COPTMF035I
COPTMF043I
COPTMF038I
COPTMF040I
460
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
COPTMF048W COPTMF075E
COPTMF048W The replication process completed
successfully even if some no blocking
problems occurred. See the summary
above and the log file for more details.
COPTMF049E The value specified for the From
Fileserver parameter is not valid.
COPTMF049W When replicating VALUE_0 a
problem was encountered. The
replication of these resources might not
be complete.
COPTMF050E The value specified for the
Auto-accept parameter is not valid.
COPTMF051E The value specified for the
Auto-commit parameter is not valid.
COPTMF052E The value specified for the From
Depot parameter is not valid.
COPTMF053E The value specified for the
Disposable parameter is not valid.
COPTMF054E The parameters specified to execute
operation VALUE_0 are not valid.
COPTMF055E Operation VALUE_0 failed. See the
log files for more information.
COPTMF056E No target has been specified or the
specified type does not match the
operation requirements.
461
COPTMF076E COPTMF107E
COPTMF076E The value specified for the Allow
Defer parameter is not valid.
COPTMF077E The value specified for the Allow
Reject parameter is not valid.
COPTMF078E The value specified for the Default
Action parameter is not valid.
COPTMF079E The value specified for the Default
Timeout parameter is not valid.
COPTMF080E The value specified for the Default
Timeout Unit parameter is not valid.
COPTMF081E The value specified for the Multicast
parameters is not valid.
COPTMF082E The requested operation is not
executed due to a validation failure.
COPTMF083E The value specified for the parameter
VALUE_0 is not valid.
COPTMF084E An error occurred while performing
database operations
COPTMF085E Software Package VALUE_0 does not
exist and it cannot be created on server
VALUE_1
COPTMF086E Reference to object VALUE_0 of type
VALUE_1 is ambiguous: provide fully
qualified name.
COPTMF087E Unable to retrieve region name for
object VALUE_0
COPTMF089E File Repository VALUE_0 is not a
valid TMF server.
COPTMF090E Failed adding Policy Region:
VALUE_0 Label: VALUE_1 Object Id:
VALUE_2
COPTMF091E Failed adding Gateway: VALUE_0
Label: VALUE_1 Object Id: VALUE_2
462
COPTMF095E
COPTMF103E
COPTMF104E
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
COPTMF108E COPTASK002E
COPTMF108E An error occourred replicating a TMF
Task.
COPTSK
This section contains messages with the COPTSK identifier for task messages.
COPTASK001E Task definition not found: VALUE_0.
463
COPTSK001E COPTSK119E
COPTSK001E Task definition not found: VALUE_0.
464
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
COPTSK121W COPTSK141W
COPTSK121W This action affects all {0} tasks in this
result set.<br></br>Deleting a task will
also delete its history. Are you sure that
you want to delete the selected tasks?
COPTSK122W This action affects all {0} tasks in this
result set.<br></br>A number of {1}
tasks cannot be deleted because they are
not completed or are shared. The
remaining {2} tasks can be
deleted.<br></br>If you want to delete
the remaining tasks, click <b>Yes</b>.
If you do not want to delete any tasks,
click <b>No</b>.<br></br>If you also
want to delete the incomplete tasks, go
to the Provisioning Task Tracking page
to cancel these tasks, and then go to the
Provisioning Task Definitions page to
delete these tasks. Deleting a task will
also delete its history.
COPTSK123W This action affects all {0} tasks in this
result set.<br></br>You cannot delete
these tasks because they are not
completed or are shared. If you want to
delete the incomplete tasks, go to the
Provisioning Task Tracking page to
cancel the tasks, and then go to the
Provisioning Task Definitions page to
delete the tasks. Deleting a task will
also delete its history.
COPTSK125W You cannot delete the task because it
is not completed. If you want to delete
the task, cancel the task first.
COPTSK127W You have selected to delete {0} tasks.
A number of {1} tasks cannot be deleted
because they are not completed. The
remaining {2} tasks can be
deleted.<br></br> If you want to delete
the remaining tasks, click <b>Yes</b> .
If you do not want to delete any tasks,
click <b>No</b>. <br></br>If you also
want to delete the {1} tasks that are not
completed, cancel them first.
COPTSK128W The tasks that you want to delete are
not completed and cannot be deleted. If
you want to delete these tasks, cancel
them first.
COPTSK130W You cannot cancel the task because it
is completed.
465
COPTSK142W COPTSK214E
COPTSK142W This action affects all {0} tasks in this
result set.<br></br>You cannot delete
these tasks because they are not
completed. If you want to delete these
tasks, cancel them first.
COPTSK147W You cannot refresh the target list
because the task is either running or
completed.
COPTSK149W The target lists for selected tasks
cannot be refreshed, because the tasks
are either running or completed.
COPTSK151W This action affects all {0} tasks in this
result set.<br></br>You cannot refresh
any target lists because the tasks are
either running or completed.
COPTSK154W You have selected to delete {0}
tasks.<br></br> A number of {1} tasks
cannot be deleted because they are not
completed. The remaining {2} tasks can
be deleted and {3} of them are associated
with base services tasks.<br></br> If
you want to delete the remaining tasks,
click <b>Yes</b> . If you do not want to
delete any tasks, click <b>No</b>.
<br></br>If you also want to delete the
{1} tasks that are not completed, cancel
them first.
COPTSK156W This action affects all {0} tasks in this
result set.<br></br>A number of {1}
tasks cannot be deleted because they are
not completed. The remaining {2} tasks
can be deleted and {3} of them are
associated with base services
tasks.<br></br>If you want to delete the
remaining tasks, click <b>Yes</b>. If
you do not want to delete any tasks,
click <b>No</b>.<br></br>If you also
want to delete the {1} tasks that are not
completed, cancel them first.
466
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
COPTSK302W COPTSK319W
COPTSK302W You cannot delete the task because it
is currently running. If you want to
delete the task, cancel the task first.
Explanation: See message.
User response: See message.
COPTSK304W You have selected to delete {0} tasks.
A number of {1} tasks cannot be deleted
because they are running. The
remaining {2} tasks can be
deleted.<br></br>If you want to delete
the remaining tasks, click <b>Yes</b>.
If you do not want to delete any tasks,
click <b>No</b>.<br></br>If you also
want to delete the {1} tasks that are
running, cancel them first.
Explanation: See message.
User response: See message.
COPTSK305W The tasks that you want to delete are
running and cannot be deleted. If you
want to delete these tasks, cancel them
first.
Explanation: See message.
User response: See message.
467
COPUTL001E COPUTL025I
COPUTL
This section contains messages with the COPUTL identifier from the utilities subsystem messages.
COPUTL001E An unexpected data migration system
exception occurred. Exception: VALUE_0.
468
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
COPUTL026I COPUTL066E
COPUTL026I Begin validating migrated database ...
469
COPUTL067E COPUTL095E
COPUTL067E Pattern VALUE_0 is not a valid regular
expression.
Explanation:
470
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
COPUTL096W COPUTL201E
DESCRIPTION='Not Compliant' where
NAME='Critical'
COPUTL096W The migration of the common agent
requirements has failed.
Explanation: A database access exception has occurred
while creating a requirement name VALUE_0 with the
pre-defined value VALUE_2 under the requirement
type VALUE_1.
User response: After the migration, manually create a
requirement name VALUE_0 with the pre-defined value
VALUE_2 under the requirement type VALUE_1. To
make this change in the provisioning database, log into
the Web interface and run the application called
Software Validation.
COPUTL097W The activity plan instance VALUE_0,
id=VALUE_1 was not migrated.
Explanation:
User response: For details, check the datamigration
log, TIO_LOGS/migration/dataMigration.log.
Manually migrate the activity plan instance using the
steps documented in the Migration Guide.
COPUTL098W The favorite task VALUE_0,
id=VALUE_1 was not migrated.
Explanation:
User response: For details, check the datamigration
log, TIO_LOGS/migration/dataMigration.log.
Manually migrate the favorite task using the steps
documented in the Migration Guide.
COPUTL099W The scheduled task VALUE_0,
id=VALUE_1 was not migrated.
Explanation:
User response: For details, check the datamigration
log, TIO_LOGS/migration/dataMigration.log.
Manually migrate the scheduled task using the steps
documented in the Migration Guide.
COPUTL100W The endpoint task VALUE_0,
id=VALUE_1 was not migrated.
Explanation:
User response: For details, check the datamigration
log, TIO_LOGS/migration/dataMigration.log.
Manually migrate the endpoint task using the steps
documented in the Migration Guide.
471
COPUTL202E CTGCFG006E
COPUTL202E Scheduled start time must be after the
current time.
Explanation: A start time in the past was selected for
the task.
User response: Select a start time in the future.
COPUTL203E Error uploading file : {0}
COPUTL204E Select a file to upload.
COPVIR
This section contains messages with the COPVIR identifier for the virtualization messages.
COPVIR001E The system cannot delete the resource
pool with ID: VALUE_0 because there
are resource allocation settings that use
it.
CTGCFG
This section contains messages with the CTGCFG identifier from the dynamic content delivery
component.
CTGCFG001E Problem parsing parameters, no
command specified. Use '-?' or '-help' as
the first parameter for command usage
information.
Explanation: No subcommand was specified for the
command requiring a subcommand.
Administrator response: Retry the operation
specifying a valid subcommand.
CTGCFG002E Problem parsing parameters,
unknown command specified: command.
Use '-?' or '-help' as the first parameter
for command usage information.
Explanation: Either no subcommand or an unknown
subcommand was specified.
Administrator response: Retry the operation
specifying a valid subcommand.
CTGCFG003E Problem parsing parameters, required
parameter parameter was not provided.
Use '-?' or '-help' as the first parameter
for command usage information.
Explanation: All required parameters for the specified
subcommand must be provided.
472
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
CTGCFG007E CTGDEA004E
CTGCFG007E A jar file with the same name already
exists in library path: parameter
Explanation: A jar file with the same name already
exists in library path.
CTGDEA
This section contains messages with the CTGDEA identifier from the dynamic content delivery
component.
CTGDEA001E Unable to get active deployments
from database.
Explanation: An error occurred when the distribution
agent attempted to retrieve the list of active
deployments from the database.
Administrator response: Troubleshoot the database to
determine why the DEPLOYMENT table could not be
read and fix the problem.
CTGDEA002E The deployment status for file file_id
on server server_name:server_port could
not be retrieved from the database.
Explanation: The status for the specified file could not
be retrieved from the database.
473
CTGDEA005E CTGDEA012E
CTGDEA005E The attempt to cancel the deployment
of file file_id to server
server_name:server_port failed.
Explanation: The distribution agent could not remove
the specified file and server information from the
database. Removing this information cancels the
deployment of the specified file to the specified server.
Because the information could not be removed, the file
will be deployed the next time the distribution agent
runs.
Administrator response: Troubleshoot the
DEPLOYMENT table in the database to determine why
the specified file could not be deleted and fix the
problem.
CTGDEA006W Deployment of file package_id to
depot server server_name:server_port has
taken longer than max_deployment_time
minutes. The deployment will be
canceled and another deployment will
be started.
Explanation: An error occurred during the
deployment of the specified file, or the specified depot
server cannot contact the management center with the
deployment results.
Administrator response: The transfer rate might be
too slow, causing the deployment to time out. Make
sure that the specified server is running and there are
no communication problems between it and the
management center. If the server is reachable, edit the
CONFIGURATION table in the database to change the
following values: DA_MIN_DEPLOY_SPEED_KBPS This represents the assumed minimum deployment
speed, in Kbps. It is used to calculate the maximum
time to allow for a file of a given size to be replicated.
The default value is 30 Kbps. Try decreasing this value,
or increasing the DA_MIN_DEPLOY_TIME_MIN value,
or both. DA_MIN_DEPLOY_TIME_MIN - This is the
minimum time to wait for a deployment (replication) to
complete before starting. The default time is 5 minutes.
CTGDEA007E The deployment of the file file_id, to
depot server server_name:server_port
failed.
Explanation: The specified depot server was unable to
receive the specified file. This deployment of this file
will be canceled and another deployment will be
started.
Administrator response: Examine the depot server
logs and use the logged information to troubleshoot the
problem.
474
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
CTGDEA013E CTGDEA027E
determine why the distribution agent could not retrieve
information from the REGISTRATION_MAP table in
the database.
475
CTGDEA028E CTGDEA040W
CTGDEA028E The attempt to delete the file, file_id,
from server server_name:server_port failed.
476
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
CTGDEA041E CTGDEA050E
CTGDEA041E The entry for package_id could not be
added to the database so that the
distribution agent can process it again at
its next cycle.
Explanation: The ADJUST_DISTRIBUTION table in
the database could not be updated with the specified
package ID. This package will not be deployed.
Administrator response: Troubleshoot the database to
determine why the ADJUST_DISTRIBUTION table
could not be written to and correct the problem.
CTGDEA042E Unable to release the registration
entry for file_id and server
server_name:server_port from the database.
Explanation: The entry for the specified file could not
be updated in the REGISTRATION_MAP table in the
database. The file will not be deleted from the specified
server by any other distribution agent instance since it
is locked.
Administrator response: Troubleshoot the database to
determine the reason the table could not be updated
and fix the problem. Manually set DIST_AGENT_ID to
null in the REGISTRATION_MAP entry if possible.
CTGDEA043E Unable to release locked queued
deployments.
Explanation: A database error prevented queued
deployment information from being unlocked, making
the records unavailable by other distribution agents.
Administrator response: Troubleshoot the
DEPLOYMENT table in the database to determine why
the queued deployments could not be released, and fix
the problem. Manually set DIST_AGENT_ID to null in
the DEPLOYMENT entry if possible.
CTGDEA044E Unable to release locked file entries
that need deployment.
Explanation: A database error prevented file
deployment information from being unlocked, making
the records unavailable by other distribution agents.
Administrator response: Troubleshoot the
ADJUST_DISTRIBUTION table in the database to
determine why the queued deployments could not be
released, and fix the problem. Manually set
DIST_AGENT_ID to null in the
ADJUST_DISTRIBUTION entry if possible.
CTGDEA046E Unable to retrieve the record time for
the deployment adjustment entry of file
package_id from the database.
477
CTGDEA051E CTGDEA058E
CTGDEA051E Could not delete file file_id on depot
server server_name:server_port. Check the
depot server log files for more
information.
Explanation: The management center attempted to
delete the file from the depot server, but the depot
server was unable to process the delete command.
Administrator response: Check the depot server log
files to determine why the depot server was unable to
process the delete command.
CTGDEA052E File file_id could not be replicated to
depot server server_name:server_port
because the depot server has reached its
maximum number of connections. The
file will be replicated to this depot
server later.
Explanation: See message.
Administrator response: To prevent this error from
occurring, increase the maximum number of
connections on the depot server or increase the number
of depot servers.
CTGDEA053E File file_id could not be replicated to
depot server server_name:server_port.
Check the depot server log files for
more information.
Explanation: The management center attempted to
replicate the file to the depot server but an error
occurred. The management center was unable to
determine the cause of the replication error.
Administrator response: Check the depot server log
files to determine why the depot server could not
receive the file.
CTGDEA054E Unable to replicate file file_id to depot
server server_name:server_port after
number_of_attempts attempts. Another
attempt will be made in approximately
number_of_minutes minutes. The
replication failed because either the
depot server cannot communicate with
the management center or the depot
server cannot download the file. To
troubleshoot this problem, make sure
the depot server can contact the
management center. Make sure the
depot server can download the file
successfully. Check the depot server logs
for more information. If the the depot
server cannot download the file, check
out the download report for the depot
server in the administration GUI.
478
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
CTGDEA059E CTGDED006E
Programmer response: Add any other possible return
codes to the processing logic.
CTGDEA059E File file_id could not be replicated to
depot server server_name:server_port
because the authentication failed. Make
sure the depot server can contact the
management center to obtain its
authentication certificate. Check the
depot server log files for more
information.
Explanation: The management center attempted to
replicate the file to the depot server, but the depot
server could not authenticate the command.
Administrator response: Check the depot server log
files to determine why the depot server was unable to
authenticate the replication command. Make sure the
depot server can contact the management center to
CTGDED
This section contains messages with the CTGDED identifier from the dynamic content delivery
component.
CTGDED001W An attempt to roll back database
changes could not be completed.
Troubleshoot the database to repair the
problem.
Explanation: The database could not be restored after
part of a transaction failed. The problem might be the
same problem that caused the need to roll back the
changes.
Administrator response: Troubleshoot the database to
determine why the rollback attempt failed. You might
need to manually repair inconsistencies left from an
incomplete transaction.
CTGDED002W An attempt to close a prepared
statement has failed. Troubleshoot the
database to resolve this error.
Explanation: An attempt to close a prepared statement
has failed. This error could be the result of a database
problem or because the prepared statement is null.
Administrator response: Troubleshoot the database.
Programmer response: Make sure the prepared
statement is not null.
CTGDED003W An attempt to close a result set has
failed. Troubleshoot the database to
resolve this error.
479
CTGDED008E CTGDED028E
CTGDED008E The attempt to add file file_id to
server server_name:server_port failed
because of a database error.
Troubleshoot the database to resolve
this error.
Explanation: See message.
480
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
CTGDED029W CTGDED045E
CTGDED029W The token token for file file_id and
user user_id was not found.
Explanation: The specified user could not be
authorized to download the specified private file. The
token was not found in the database.
CTGDED030E An error occurred during the attempt
by user user_id to download file file_id.
Could not verify token token because of
a database error. Troubleshoot the
database to resolve this error.
Explanation: When a user attempts to download a file
with a mode of private, a token is used to verify that
the user is authorized to download the file. The token
could not be verified because of a database error.
Administrator response: Troubleshoot the database to
resolve this error.
Programmer response: Make sure that the SQL
statement for this operation is valid.
481
CTGDED047W CTGDED062E
CTGDED047W No region was found for client
ip_address. The operation to choose
potential upload servers will try to
continue. Please update the ip
ranges/domains to ensure optimal
service.
CTGDED052E Cannot upload file, file_id, from
ip_address. No upload servers match the
specified criteria.
Explanation: The specified client attempted to upload
the specified file, but no depot servers were found
matching the upload criteria.
Administrator response: Make sure there is at least 1
depot server registered with the management center.
Examine the upload criteria to ensure that the available
depot servers have attributes that match the criteria
requested (server type, region, unrestricted ip
ranges/domains and so on).
CTGDED053W Found potential depot server
server_name:server_port but it doesn't have
enough space to host a file of size
file_size bytes. The free space determined
is free_space bytes.
CTGDED054E Unable to update status in database
for file file_id.
Explanation: An attempt was made to update the
status of the specified file in the database. A database
error prevented the status update.
Administrator response: Troubleshoot the database to
determine the cause of the error and fix it. Statuses for
files are in the PACKAGE and FILE_TABLE tables.
CTGDED055E Unable to delete file file_id from the
database.
Explanation: An attempt was made to delete the
specified file from the FILE_TABLE table in the
database. A database error occurred which prevented
the removal of the file information.
482
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
CTGDED063E CTGDED074W
User response: Request access to the file, or log on as
a user who is authorized to access the file.
483
CTGDED075E CTGDED084E
MC_DEPOT_NOTIFICATION in the management
center database. Determine if messages are to be sent
for this particular tag, and if so, create a notification
entry for this tag.
CTGDED075E A Java Messaging Service error
occurred while attempting to publish a
message for the tag named: tag. The JMS
configuration for the Topic Connection
Factory tcf or Topic topic related to the
notification entry for the application tag
tag could be incorrect or there may be a
communication problem with the
management center and the messaging
server hosting the topic.
Explanation: See message.
Administrator response: Verify that the JMS Topic
Connection Factory and Topic are configured correctly
and that a message can successfully be sent from the
Management Center to the given topic.
CTGDED076E The Management Center could not
find either the JMS Topic Connection
Factory tcf or the JMS Topic topic for the
application tag tag with the context
factory of ctxFactory and initial URL of
initURL
Explanation: The JMS Topic Connection Factory or
JMS Topic could not be obtained from JNDI.
Administrator response: Make sure that the Topic
Connection Factory and Topic exist and that the correct
context factory and initial URL were specified in the
notification entry for the specified application tag.
CTGDED077E The Management Center could not
obtain the information needed to
publish a message for the server ID
server and file ID file.
Explanation: The notification entry could not be
obtained from the Management Center database.
Administrator response: Verify that the connection to
the database is working and that the specified server
and file are valid.
CTGDED078E Data used when trying to update
target list information for a package is
corrupt.
Explanation: The append target list service
(ddssAppendTargetList) was invoked with corrupt or
incorrect input.
484
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
CTGDED085E CTGDEE004E
CTGDED085E Data used to obtain depot servers,
using dynamic depot server selection,
was corrupt or otherwise not valid.
Retry the operation (ddssPublish,
ddssAppendTargetList,
ddssGetDepotServers) using correct
input data.
CTGDED086E The package identified by the
package ID pkgID is not an active
package in the management center
database. The package might have been
deleted.
Explanation: The file associated with the specified
package ID might have been deleted from the
management center database but the package metadata
has been preserved.
Administrator response: Package status is set in the
STATUS column in the management center database in
the CDSSCHEMA.PACKAGE table. Check the status
entry for the specified package ID. The status must be
ACTIVE for the package to be considered deployable.
The file must be republished before it can be deployed.
CTGDEE
This section contains messages with the CTGDEE identifier from the dynamic content delivery
component.
CTGDEE001W Administrator adminname has created
account username.
Explanation: A new account was created by the
specified Administrator.
Administrator response: Review the details in the
event about the change and verify whether the event
was unexpected.
CTGDEE002W Depot server depot_server is running
low on available incoming connections.
Explanation: The depot server exceeded its threshold
of active connections. For example, if the depot is
configured with 30 connections and the overload
threshold is set at 80%, then 24 simultaneous
connections would trigger this event.
Administrator response: Try increasing the number of
connections configured for this depot, increasing the
number of depots providing this file (by increasing the
replication percentage or adding more depots), or
manage the number of simultaneous download
requests that are occurring.
485
CTGDEE005E CTGDEE024W
this represents the assumed minimum deployment
speed, in Kbps. It is used to calculate the maximum
time to allow for a file of a given size to be replicated.
The default value is 30 Kbps. Try decreasing this value,
or increasing the DA_MIN_DEPLOY_TIME_MIN value,
or both. DA_MIN_DEPLOY_TIME_MIN - this is the
minimum time to wait for a deployment (replication) to
complete before starting. The default time is 5 minutes.
CTGDEE005E Depot server hostname:port failed to
replicate file filename (File ID: file_id).
Explanation: The attempt of the depot server to
download the file failed.
Administrator response: Check out the depot server
logs to find possible problems with the download. The
download reports may also contain information about
the failures.
CTGDEE006W The replication of file filename (File
ID: file_id) of size filesize MB cannot be
fulfilled due to insufficient available
depot servers with enough space.
Explanation: There are not sufficient depot servers
with status of STARTED and that have enough space to
hold the file in order to fulfill the replication level.
Administrator response: Make sure the depot servers
are in STARTED state and have enough space to hold
the file or modify the replication settings.
CTGDEE007W Administrator adminname has deleted
account username.
Explanation: A user account was deleted by the
specified Administrator.
Administrator response: Review the details in the
event about the change and verify whether the event
was unexpected.
CTGDEE008W Administrator adminname has
updated account username.
Explanation: A user account was modified by the
specified Administrator.
Administrator response: Review the details in the
event about the change and verify whether the event
was unexpected.
CTGDEE013W Administrator adminname has deleted
target list tlname.
Explanation: A target list was deleted by the specified
Administrator.
Administrator response: Review the details in the
event about the target list deletion and verify whether
this was an unexpected change.
486
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
CTGDEE029W CTGDEE058W
CTGDEE029W User adminname has deleted one or
more files.
Explanation: One or more files have been deleted by
the specified user.
Administrator response: Review the details in the
event about what file was deleted and verify that this
was not an unexpected removal of a file.
CTGDEE033W Administrator adminname has
unregistered depot server servername.
Explanation: A depot server was unregistered by the
specified Administrator.
Administrator response: Review the details in the
event about what depot server was unregistered and
verify that this was not an unexpected removal of the
depot server.
CTGDEE034W Administrator adminname has
uninstalled depot server servername.
Explanation: A depot server was uninstalled by the
specified Administrator.
Administrator response: Review the details in the
event about what depot server was uninstalled and
verify that this was not an unexpected removal of the
depot server.
CTGDEE038W Depot server depot_server was unable
to initialize cache controller number
cache_number with cache partition
location cache_location.
Explanation: On depot startup there was a problem
initializing a cache controller. If other cache controllers
are available, the depot will still run with those.
Administrator response: Check the depot server log
for more details about why the cache controller could
not be initialized.
CTGDEE039W The replication of file filename (File
ID: file_id) cannot be processed because
it does not have any target servers.
Explanation: This might happen if the file has been
published to a target list that has been deleted or
modified to not include any depot servers. The file
cannot be deployed in this condition.
Administrator response: Add target servers to the file
so that it can be deployed accordingly.
CTGDEE040E The last copy of file filename (File ID:
file_id) has been deleted off depot server
server_name:server_port due to a depot
server storage error.
487
CTGDEG001E CTGDEG021E
CTGDEG
This section contains messages with the CTGDEG identifier from the dynamic content delivery
component.
CTGDEG001E An unexpected error has occurred.
Check the GUI log file for more
information. detailedException
488
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
CTGDEG023E CTGDEI128E
CTGDEG023E The depot server could not be
uninstalled. If the problem persists after
troubleshooting, you can uninstall the
depot server manually and unregister
the depot server by clearing the login
credentials and retrying this operation.
Explanation: An attempt to uninstall the depot server
was unsuccessful. This error can occur because of
problems with the network connection. This error can
also occur as a result of expired login credentials. For
example, if the ID or password of the root user on the
depot server is changed, this information no longer
matches the login credentials for the depot server that
are stored in the management center.
Administrator response: If a problem exists with the
network connection, troubleshoot the connection and
then retry the operation. If the login credentials for the
depot server have expired, update them and then retry
the operation. If you cannot resolve this problem, you
can uninstall the depot server manually. When you
uninstall a depot server manually, you must also
unregister the depot server (delete its data from the
management center) using the administration GUI.
CTGDEG024E The file_id parameter is missing
from the URL. The file could not be
downloaded.
Explanation: There is an error in the URL that is used
to launch the download applet. This URL must include
the string file_id=<fileid>, where <fileid> is the ID of
the file to be downloaded.
User response: Notify your system administrator of
the problem with the URL.
Administrator response: Correct the URL.
CTGDEG025E The file_id parameter specified does
not refer to a valid file. The file could
not be downloaded.
Explanation: There is an error in the URL that is used
to launch the download applet. This URL must include
CTGDEI
This section contains messages with the CTGDEI identifier from the dynamic content delivery
component.
CTGDEI126E
489
CTGDEI129E CTGDEI142E
CTGDEI129E
CTGDEI136E
CTGDEI131E
CTGDEI138E
490
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
CTGDEI143E CTGDEI157E
CTGDEI143E
CTGDEI151E
CTGDEI144E
CTGDEI152E
491
CTGDEI158E CTGDEI170E
CTGDEI158E
CTGDEI168E
CTGDEI163E
CTGDEI169E
CTGDEI170E
CTGDEI166E
492
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
CTGDEI171E CTGDEI183E
CTGDEI171E
CTGDEI177E
CTGDEI173E
CTGDEI179E
CTGDEI175E
CTGDEI182E
CTGDEI183E
CTGDEI176E
493
CTGDEI184E CTGDEI195E
CTGDEI184E
CTGDEI191E
CTGDEI186E
CTGDEI192E
CTGDEI188E
CTGDEI194E
494
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
CTGDEI196E CTGDEI223E
CTGDEI196E
CTGDEI213E
User response:
CTGDEI217E
CTGDEI218E
CTGDEI219E
CTGDEI220E
CTGDEI221E
CTGDEI222E
CTGDEI223E
CTGDEI204E
495
CTGDEI224E CTGDEI241E
CTGDEI224E
CTGDEI225E
CTGDEI226E
CTGDEI237E
CTGDEI238E
CTGDEI227E
CTGDEI228E
CTGDEI229E
CTGDEI236E
CTGDEI230E
CTGDEI231E
CTGDEI232E
CTGDEI233E
CTGDEI234E
CTGDEI235E
496
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
CTGDEI242E CTGDEI261E
CTGDEI242E
CTGDEI252E
CTGDEI257E
CTGDEI258E
CTGDEI259E
CTGDEI260E
CTGDEI261E
CTGDEI250E
CTGDEI251E
CTGDEI256E
CTGDEI246E
CTGDEI249E
CTGDEI248E
CTGDEI255E
CTGDEI245E
CTGDEI247E
CTGDEI254E
497
CTGDEI262E CTGDEI268E
CTGDEI262E
CTGDEI268E
498
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
CTGDEJ001E CTGDEJ010E
CTGDEJ
This section contains messages with the CTGDEJ identifier from the dynamic content delivery
component.
CTGDEJ001E CDSClient() called but a management
center URL was not specified or the
client service is not installed.
Explanation: An application called a CDSClient()
constructor, but either the client is not installed or the
constructor did not contain the URL of the
management center.
Programmer response: If this message is received on a
machine that is not running the CDS client, verify that
your application includes a valid URL for a
management center in the constructor call. If this
message is received on a machine that is running the
CDS client, reinstall the client using the ISMP installer
program that is appropriate for the operating system
on the client machine.
CTGDEJ002E Cannot find properties for file:
package_id.
Explanation: The CDS client attempted to update or
download the specified file, but the properties
associated with the file could not be found in the
management center database.
Administrator response: Use the administrative GUI
to ensure that the file (and its associated properties)
exists and retry the operation.
499
CTGDEJ011E CTGDEJ028E
CTGDEJ011E Problem parsing parameters, unknown
command given: command. Use '-?' or
'-help' as the first parameter for
command usage information.
CTGDEJ017E
exception
500
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
CTGDEJ029E CTGDEJ040E
CTGDEJ029E The replication level is not valid. The
value must be an integer number,
integer percentage, or ALL.
Explanation: The replication level is not valid. The
value must be an integer, either the number of servers
or the percentage of servers, or the value ALL.
501
CTGDEJ041E CTGDEJ052E
CTGDEJ041E The region name regionName used by
the -register option does not exist in the
new management center.
502
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
CTGDEJ053E CTGDEJ062E
CTGDEJ053E An exception occurred while
decrypting the downloaded file:
exception. The download has failed.
Explanation: While attempting to decrypt of the file,
an exception occurred that prevented the decryption
from completing.
Administrator response: Examine the exception for
more information about the failure.
CTGDEJ054E An exception occurred while copying
the downloaded file: exception. The
download has failed.
Explanation: While attempting to copy the file, an
exception occurred that prevented the copy from
completing.
Administrator response: Examine the exception for
more information about the failure.
CTGDEJ055E The download has failed. The file was
not successfully retrieved from the
servers provided in the download plan.
There might be additional automatic
retries of this download.
Explanation: The attempts to download the file from
each of the servers in the download plan were
unsuccessful.
Administrator response: Examine the trace log for
more details.
CTGDEJ056E The download failure is final -- there
are no more automatic retries available.
Explanation: The previously reported download
failure is final since all automatic retries have been
exhausted.
Administrator response: Examine the trace log for
more details.
CTGDEM
This section contains messages with the CTGDEM identifier from the dynamic content delivery
component.
Chapter 25. Messages
503
CTGDEM003W CTGDEM017E
CTGDEM003W The depot server
server_name:server_port cannot be pinged
from the monitoring agent. An attempt
will be made to restart it remotely.
504
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
CTGDEM022E CTGDEM036E
to which alerts are to be sent.
CTGDEM022E Unable to update last restart attempt
timestamp.
Explanation: The monitoring agent attempted to
update the RESTART_ATTEMPT timestamp in the
SERVER_RECOVERY table, but failed.
Administrator response: Ask the database
administrator to examine the database to discover why
the database could not be updated and fix the problem.
CTGDEM023E Unable to unlock entries in the
DEPOT_SERVER table. Troubleshoot
the database to resolve this problem.
Explanation: An attempt to unlock one or more
entries in the DEPOT_SERVER table failed.
Administrator response: Ask the database
administrator to determine why the MON_AGENT_ID
column in the DEPOT_SERVER table could not be
updated and fix the problem.
CTGDEM024E Unable to determine the time of the
most recent alert concerning corrupted
files.
Explanation: An attempt was made to retrieve the
timestamp for the last corrupt file alert from the
database, but the attempt failed.
505
CTGDEM037E CTGDEM047W
CTGDEM037E The checksum value of file file_id on
depot server server_name:server_port is
incorrect. The file appears to be
damaged. The file will be deleted from
the depot server.
Explanation: The checksum value of the specified file
on the depot server does not match the checksum value
stored in the database. The file on the depot server
appears to be damaged. The file will be deleted off the
depot server and redeployed if necessary.
Administrator response: An attempt to delete the file
from the depot server will be made automatically. If the
problem persists, contact IBM Support.
CTGDEM039E An attempt to delete an entry from
the SERVER_SYNC table referring to
depot server server_name:server_port and
file file_id has failed. Troubleshoot the
database to correct this error.
Explanation: This database record indicates that the
depot server reported not having the specified file. The
database record has been processed, but the record
could not be deleted.
Administrator response: Troubleshoot the database to
correct this error.
CTGDEM040W Unable to remotely start depot server
server_name:server_port because no
credentials (user ID and password) were
provided. Use the administration GUI to
provide the user ID and password of a
user with root privileges.
CTGDEM041W Unable to remotely start depot server
server_name:server_port because it is
running in the common agent.
CTGDEM044E Depot server server_name:server_port is
reporting a hostname different from the
one it was registered with on the
management center. It is not able to
validate upload and download requests
until this error is corrected.
Explanation: The hostname reported from the depot
server must match the hostname the depot server is
registered with. This can happen if the depot server is
not configured to report its fully qualified hostname
CTGDEQ
This section contains messages with the CTGDEQ identifier from the dynamic content delivery
component.
506
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
CTGDEQ001E CTGDEQ008E
management center log file for more information.
507
CTGDEQ009E CTGDEQ020E
CTGDEQ009E The specified administrator
(parameter_name) does not exist. Specify
the name of an existing administrator.
Explanation: See message.
User response: Specify the name of an existing
administrator.
508
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
CTGDEQ021E CTGDEQ031E
User response: Verify that you have entered a valid IP
range. Verify that the IP range you entered does not
overlap with an existing IP range.
CTGDEQ021E The specified file ID (parameter_name)
already exists. Specify a unique ID for
the file.
Explanation: See message.
User response: Verify that you have entered a unique
ID for the file.
CTGDEQ022E The specified file ID (parameter_name)
does not exist. Specify an existing file
ID.
Explanation: See message.
User response: Verify that you have entered an
existing file ID.
CTGDEQ023E The specified file ID (parameter_name)
already exists. Specify a unique ID for
the file.
Explanation: See message.
User response: Verify that you have entered a unique
ID for the file.
CTGDEQ024E The specified file ID (parameter_name)
does not exist. Specify an existing file
ID.
Explanation: See message.
User response: Verify that you have entered an
existing file ID.
CTGDEQ025E The specified region name
(parameter_name) already exists. Specify a
unique name for the region.
Explanation: See message.
User response: Verify that you have entered a unique
name for the region.
CTGDEQ026E The specified region (parameter_name)
does not exist. Specify an existing
region.
Explanation: See message.
User response: Verify that you have entered the name
of an existing region.
509
CTGDEQ032W CTGDEQ042E
CTGDEQ032W Could not create a target list for
depot server {parm1:parm2} with ID
parm3. Some product features might not
be available.
510
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
CTGDEQ043E CTGDES004E
CTGDEQ043E An IP zone with the name
(zone_name) already exists. Specify a
unique name for the zone.
Explanation: See message.
User response: Zone names must be unique.
CTGDEQ044E The IP range (IP start ip_start and IP
end ip_end) conflicts with existing IP
zone [zone_details]. Specify an IP range
that does not overlap or includes an
existing IP zone.
Explanation: An attempt was made to create or
update an IP range but the range conflicts with an
existing IP zone.
CTGDES
This section contains messages with the CTGDES identifier from the dynamic content delivery
component.
CTGDES001E The installed version of the JRE is
not compatible. Upgrade to the IBM
Runtime Environment for Java, version
1.4.1 or later.
Explanation: See message.
Administrator response: Upgrade to the IBM Runtime
Environment for Java, version 1.4.1 or later.
CTGDES002E The attempt to get the fully qualified
host name for the depot server failed.
Check the server configuration to
resolve this error.
Explanation: See message.
Administrator response: Ensure that the server.conf
file exists. Ensure that the HOSTNAME entry in the
server.conf file lists the correct fully qualified name for
the server.
CTGDES003E The attempt to get a directory name
and directory space from the
configuration file failed. Troubleshoot
the server.conf configuration file to
resolve this error.
511
CTGDES005E CTGDES013E
CTGDES005E The attempt to upload file file_name
failed due to a database error. The file
has not been uploaded. Troubleshoot
the database to resolve this error.
512
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
CTGDES014E CTGDES024E
CTGDES014E Depot Server ID=server_id
Hostname=hostname Port=port was not
found in the Management Center
database.
Programmer response:
CTGDES015E Depot Server ID=server_id
Hostname=hostname Port=port was not
unique within the Management Center
database.
Explanation: See message.
Administrator response: Contact IBM Software
Support.
Programmer response: There are multiple records in
the database which have the attributes which were sent
to query on.
CTGDES016E Depot Server ID=server_id
Hostname=hostname Port=port caused
database failure during query of the
Management Center database.
Explanation: See message.
Administrator response: Troubleshoot the database to
resolve this error.
Programmer response: Check the stack trace for a
SQL database error.
CTGDES017E Depot Server could not obtain the
Management Center hostname and port
information from the server
configuration file.
Explanation: See message.
Administrator response: Ensure there is a server.conf
file.
Programmer response: Ensure there is a server.conf
file.
CTGDES018E Depot Server could not obtain the
Server ID=server_id from the server
configuration file.
Explanation: See message.
Administrator response: Ensure there is a server.conf
file.
Programmer response: Ensure there is a server.conf
file.
513
CTGDES025E CTGDES042E
administrative GUI to examine the depot server
settings to determine why the cache controller is not
properly registering. Click Depot Servers, Manage
Depot Servers. Select a depot server and view the
settings, particularly those having to do with cache
management and the data directory. Make sure that all
directories in the list of data directories are configured
to be both readable and writeable.
CTGDES025E Cache manager error; depot server is
shutting down.
Explanation: The depot server cannot communicate
with the cache manager. The depot server cannot
receive file uploads or download files to clients.
Administrator response: Restart the depot server. If
the problem persists, contact Level 3 support.
CTGDES026W The maximum number of
connections ( max_value ) allowed for
this server has been reached.
Explanation: See message.
Administrator response: If this server reaches its
limits frequently under normal conditions, consider
increasing the maximimum number of connections for
the server. If the server is experiencing an unusually
high number of connections, check the network and
other servers for problems. Check the log file on the
management center for more information.
CTGDES027W The server could not load one or
more of the libraries required for the
proper operation of Adaptive
Bandwidth Control. Transfers will
proceed without using bandwidth
control.
Explanation: See message.
Administrator response: Verify whether Adaptive
Bandwidth Control is supported on the operating
system platform. On platforms where Adaptive
Bandwidth is supported, increase the logging level to
DEBUG_MAX, restart the failing component and check
for an exception in the trace log. The exception can
show what library file could not be loaded. On
platforms where Adaptive Bandwidth is not supported,
the transfers will proceed without using bandwidth
control.
Programmer response: Check the trace log to locate
the missing library file. Verify whether the file was
properly installed.
CTGDES038E The logging directory could not be
created. Check the output.log file for
more information.
514
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
CTGEM0000E CTGEM0003E
CTGEM
This section contains messages with the CTGEM identifier from the Agent Manager messages for Tivoli
Provisioning Manager.
CTGEM0000E An error occurred while loading
information from the agent manager
configuration file:
AgentManager.properties.
Explanation: An error occurred while loading
information on the agent manager configuration from
the AgentManager.properties file.
System action: Agent manager initialization stops. The
agent manager is not operational.
Administrator response: Make sure that the agent
manager configuration file (AgentManager.properties)
is in the correct location, and then restart the agent
manager. If the problem continues, contact IBM
Customer Support.
CTGEM0001E The listener for agent certificate
requests was not loaded. The listener
class name is listener_class_name.
Explanation: An error occurred while loading the
listener specified by listener_class_name. The agent
certificate request listener was not loaded.
System action: The function provided by the specified
listener for agent certificate requests is not available.
The absence of the listener for certificate requests can
result in the rejection of all agent registration attempts.
Administrator response: Check the WebSphere
application server message 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. If
the problem continues, it may indicate a problem with
the file system permissions or a disk failure. For other
errors, contact IBM Customer Support.
Programmer response: If the exception indicates that
the class was not found (ClassNotFoundException),
make sure that the name of the class is spelled correctly
in the Registration.Listeners.Agent.Request property of
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. If the exception is
ClassCastException, the specified class does not
implement the appropriate interface and is not a valid
listener for agent certificattion requests. Modify the
program and try again.
CTGEM0002E The listener for manager certificate
requests was not loaded. The listener
515
CTGEM0004E CTGEM0007E
the class was not found (ClassNotFoundException),
make sure that the name of the class is spelled correctly
in the Registration.Listeners.Manager.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. If the exception is
ClassCastException, the specified class does not
implement the appropriate interface, and is not a valid
listener for issued manager certificates. Modify the
program and try again.
CTGEM0004E The listener for issued agent
certificates was not loaded. The listener
class name is listener_class_name.
Explanation: An error occurred while loading the
listener for issued agent certificates specified by
listener_class_name.
System action: The function provided by the specified
listener for issued agent certificates is not available.
Administrator response: Check the 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. If the problem continues, it may
indicate 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. If the exception is
ClassCastException, the specified class does not
implement the appropriate interface, and is not a valid
listener for issued agent certificates. Modify the
program and try again.
CTGEM0005E A configuration update listener was
not loaded. The listener class name is
listener_class_name.
Explanation: The listener specified by
listener_class_name was not loaded as a configuration
update listener.
System action: The function provided by the specified
configuration update listener is not available.
Administrator response: Check the 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
516
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
CTGEM0008W CTGEM0014E
throws an exception to notify the calling program about
the problem.
Administrator response: Make sure that all of the
certificates for this agent manager or resource manager
are issued by the certificate authority for your
environment, or force it to reregister.
CTGEM0008W A certificate was renewed even
though the associated information was
not in the agent registry. The
distinguished name (DN) of the
renewed certificate is
renewal_distinguished_name.
Explanation: The certificate to be renewed is signed
and valid, but is not listed in the agent registry. The
certificate is renewed and its information is added to
the registry.
CTGEM0009E The agent manager cannot create the
public / private key pair of the
following type key_pair_type using the
algorithm key_pair_algorithm.
Explanation: The agent manager is unable to create a
public / private key pair of the following type
key_pair_type using the algorithm key_pair_algorithm.
517
CTGEM0015E CTGEM0021E
CTGEM0015E A client program attempted to use a
TCP/IP port that is not secure to invoke
an operation that requires a secure
connection. Use a secure connection
(HTTPS) for this request.
Explanation: A client program attempted to use a
TCP/IP port that is not secure to invoke an operation
that requires a secure connection. This typically
indicates one of the following problems: The client
program is using the wrong port for this request. The
port numbers in the agent configuration file were
modified after the agent was installed. The agent
manager was originally configured to run in non-secure
mode, but has been partially reconfigured for secure
mode.
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: Collect the message and
trace files and contact IBM Customer Support.
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.properties) lists the
correct port numbers for each agent manager request
type. If the configuration file is correct, collect the
message and trace files and contact IBM Customer
Support.
CTGEM0017E Client authentication is required to
process the request.
Explanation: A client program issued a request to
perform an action that requires authentication, but did
not supply a certificate with the request. This can
indicate that the agent is not correctly configured or
that the program is sending the request to the wrong
TCP/IP port.
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: Collect the message and
trace files and contact IBM Customer Support.
518
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
CTGEM0022E CTGEM0028E
traces related with this failure.
System action: The agent manager is not operational.
Administrator response: Collect the message and
trace files and contact IBM Customer Support.
CTGEM0022E The agent manager cannot connect to
the agent registry.
Explanation: A database error occurred while
connecting to the agent registry.
System action: Information gathered by the agent
manager is not written to the agent registry. However,
the agent manager continues to run.
Administrator response: Verify that the agent registry
database is operational. If it is not running locally,
make sure that you can connect to it from the agent
manager server. If tracing is not turned on, turn it on
and restart the agent manager. If the problem
continues, contact IBM Customer Support.
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 with the agent manager. The agent
manager or the resource manager that called the agent
manager is not affected by this problem. The
component ID component_ID identifies the specific
instance of the agent on a computer system by using
the root configuration directory, or installation
directory, of the agent.
Administrator response: Verify that the agent registry
database is operational. If it is not running locally,
verify that you can connect to it from the agent
manager server. If tracing is not turned on, turn it on
and restart the agent manager. If the problem
continues, contact IBM Customer Support.
CTGEM0024E The agent manager cannot store
information about the certificate with
the serial number serial_number and
distinguished name (DN)
distinguished_name in the agent registry.
Explanation: The agent manager cannot store
information about a certificate in the agent registry.
This indicates a possible problem with the database or
with the agent manager. The agent manager or the
resource manager that called the agent manager is not
affected by this problem, because it receives the
certificate even though the certificate is not stored in
the registry. The next time the agent or resource
manager contacts the agent manager, the agent
519
CTGEM0029E CTGEM0033E
program must provide both an operating system GUID
and a component ID.
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: This message indicates a
programming problem. Collect the agent manager
message and trace files and contact IBM Customer
Support.
Programmer response: Modify the calling program to
provide complete information for the certificate request.
CTGEM0029E A Web service port implementation
with the class specified by class_name
cannot be loaded.
Explanation: An error occurred while loading the Web
service port implementation with the class specified by
class_name.
System action: The function provided by the specified
Web service port implementation is not available.
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. If
the problem continues, it may indicate a problem with
file system permissions or a disk failure.
Programmer response: For a ClassNotFoundException
exception, make sure that the name of the class is
spelled correctly in the WSDL.Ports.Impl property in
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. If the exception is
ClassCastException, the specified class does not
implement the appropriate interface and is not a valid
Web service port implementation.
CTGEM0030E The agent manager cannot initialize
the authorization validation listener
(AuthorizationValidator).
Explanation: The agent manager cannot initialize the
authorization validation listener
(AuthorizationValidator).
System action: The agent manager continues to run.
However, all resource manager registration requests are
rejected.
Administrator response: Check the WebSphere
application server log and trace files for more
information. This message is associated with an
additional message (CTGEM0031E, CTGEM0032E, or
520
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
CTGEM0034W CTGEM0043E
manager. If the problem continues, contact IBM
Customer Support.
CTGEM0034W The agent manager cannot write the
agent manager ID to the file_name file.
Explanation: An error occurred while writing the
agent manager ID to the file system.
System action: The agent manager can run even if the
agent manager ID is not saved to the file system. The
next time the agent manager needs to use its ID, it
creates a new one. If the operating system GUID has
not been changed, the new agent manager ID is the
same as the original one. Creating a new agent
manager ID is a problem only when both of the
following conditions are met: The agent manager ID is
changed because an administrator requested a new
GUID. 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. If it is, check its
associated permissions, verify that the user running the
agent manager has the necessary authorization to write
to the directory, and restart the agent manager. If the
problem continues, contact IBM Customer Support.
CTGEM0035E An agent registration was rejected
because no agent registration password
is defined for the agent manager.
Explanation: The agent provided an agent registration
password with a request for registration, but the agent
manager is not configured to require an agent
registration password.
System action: The agent manager continues to run.
However, without an agent registration password, all
agent registration attempts are rejected.
Administrator response: Configure the agent to
provide the correct password. Make sure that the
Registration.Agent.Access.Password property in the
agent manager configuration file,
AgentManager.properties, contains the agent
registration password and then restart the agent
manager. If the problem continues, contact IBM
Customer Support.
CTGEM0036E The resource manager with the
component ID resource_manager_ID
cannot register because it did not
specify a manager type.
521
CTGEM0046E CTGEM0049E
CTGEM0046E Information cannot be loaded from
the agent manager configuration file,
AgentManager.properties.
Explanation: An error occurred while loading the
configuration information from the
AgentManager.properties.
Administrator response: Make sure that the
AgentManager.properties file is in the
WEB-INF/classes/resources directory of the
AgentManager.war file and that the file is readable.
When the file is available and readable, retry the
operation. If the problem continues, contact IBM
Customer Support.
CTGEM0047E The keystore file for registration
encryption cannot be accessed because
the following exception occurred:
exception
Explanation: The specified exception occurred while
attempting to read the keystore file for registration
encryption. The location of this file is specified by the
REG.keyPWfile.name property in the file
AgentManager.properties. The location is relative to the
directory specified by the ARS.directory property in the
same AgentManager.properties file.
Administrator response: Follow these steps to verify
that the information needed to locate the registration
encryption keystore file is available: Ensure that the
agent manager properties file
(AgentManager.properties) is in the
WEB-INF/classes/resources directory of the
AgentManager.war file and that the file is readable.
Ensure that the directory pointed to by the
ARS.directory property in the AgentManager.properties
file exists and is readable. Ensure that the value of the
REG.keyPWfile.name property in the
AgentManager.properties file points to a readable
registration encryption keystore file. The location of this
file is relative to the directory specified by
ARS.directory. Ensure that the AgentManager.properties
file contains an encrypted string for the value of the
Registration.Agent.Access.Password property. When the
files and properties are correct, retry the operation that
failed. 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. If the problem continues after
regenerating the keystore file, contact IBM Customer
Support.
CTGEM0048E The agent registration password
cannot be updated in the agent manager
configuration file
(AgentManager.properties) because the
following exception occurred: exception
Explanation: The specified exception occurred while
522
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
CTGEM0050E CTGEM0053E
CTGEM0050E The Authorization.xml file cannot be
upgraded because the following
exception occurred: exception
Explanation: In version 1.1 of the agent manager,
passwords in the Authorization.xml file were saved as
readable, unencrypted text. The current version stores
passwords as encrypted text. When the agent manager
is upgraded from version 1.1, the existing passwords
are encrypted. This message indicates that an exception
occurred while the passwords in the original
Authorization.xml file were being encrypted or
updated in the file. The file is not unchanged.
System action: The upgrade continues. The passwords
in the Authorization.xml file are not encrypted. The
agent manager will not be able to register resource
managers until the passwords in the file are encrypted.
Administrator response: Follow these steps to encrypt
the passwords: Make sure that you have the authority
to write the Authorization.xml file and then open it in a
text editor. To locate Authorization.xml, use the
Registration.Manager.Authorization.Config property in
agent manager configuration file
(AgentManager.properties). The location is related to
the directory specified in the ARS.directory property.
The AgentManager.properties file is in the
WEB-INF/classes/resources directory of the
AgentManager.war file. 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 <user> element. Save the file. If you
cannot encrypt the passwords using the EncryptPW
command, contact IBM Customer Support.
CTGEM0051E A resource manager user ID cannot
be added to the Authorization.xml file
because the following exception
occurred: exception
Explanation: An error occurred while attempting to
add a resource manager user ID to the
Authorization.xml file.
Administrator response: Follow these steps to verify
that the information needed to locate files and to
encrypt passwords is available: Ensure that the agent
manager configuration file (AgentManager.properties)
is in the WEB-INF/classes/resources directory of the
AgentManager.war file and that the file is readable by
the current user. Ensure that the directory pointed to by
the ARS.directory property in the
AgentManager.properties file exists and is readable by
the current user. Ensure that the value of the
REG.keyPWfile.name property in the
AgentManager.properties file is the name of the
registration encryption keystore file, relative to the
ARS.directory location. Ensure that the
Authorization.xml file exists and is readable. The
Registration.Manager.Authorization.Config property in
the AgentManager.properties file points to the
Authorization.xml file, relative to the ARS.directory
location. When the files and properties are correct, retry
the operation that failed. 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. If the problem continues after
regenerating the keystore file, contact IBM Customer
Support.
CTGEM0052E A resource manager user ID cannot
be removed from the Authorization.xml
file because the following exception
occurred: exception
Explanation: An error occurred while attempting to
remove a resource manager user from the
Authorization.xml file.
Administrator response: Follow these steps to verify
that the information needed to locate files and to
encrypt passwords is available: Ensure that the agent
manager configuration file (AgentManager.properties)
is in the WEB-INF/classes/resources directory of the
AgentManager.war file and that the file is readable by
the current user. Ensure that the directory pointed to by
the ARS.directory property in the
AgentManager.properties file exists and is readable by
the current user. Ensure that the value of the
REG.keyPWfile.name property in the
AgentManager.properties file is the name of the
registration encryption keystore file, relative to the
ARS.directory location. Ensure that the
Authorization.xml file exists and is readable. The
Registration.Manager.Authorization.Config property in
the AgentManager.properties file points to the
Authorization.xml file, relative to the ARS.directory
location. When the files and properties are correct, retry
the operation that failed. If the problem continues,
contact IBM Customer Support.
CTGEM0053E The UpdatePW program encountered
an error while performing the command
command. The exception was exception.
Explanation: UpdatePW is a Java application that
provides functions made available to users by the
EncryptPW, EncryptAMProps, AuthXMLAddUser,
AuthXMLRemoveUser and AuthXMLRemoveAuthType
commands. UpdatePW should be invoked only by one
of those commands. This message indicates that the
specified exception occurred while running the
UpdatePW program. The variable command identifies
the function that UpdatePW was attempting to
perform. It is possible to get a null pointer exception
that specifies the command null.
Administrator response: Follow these steps to verify
that the information needed to locate files and encrypt
passwords is available: Ensure that the agent manager
Chapter 25. Messages
523
CTGEM0054E CTGEM0059E
configuration file (AgentManager.properties) is in the
WEB-INF/classes/resources directory of the
AgentManager.war file and that the file is readable by
the current user. Ensure that the directory pointed to by
the ARS.directory property in the
AgentManager.properties file exists and is readable.
Ensure that the value of the REG.keyPWfile.name
property in the AgentManager.properties file is the
name of the registration encryption keystore file,
relative to the ARS.directory location. Ensure that the
file is readable. Ensure that the
AgentManager.properties file contains an encrypted
string for the value of the
Registration.Agent.Access.Password property. Ensure
that the Registration.Manager.Authorization.Config
property specifies the Authorization.xml file and that
the current user can read this file. It is possible to use a
different file name, so check the contents of the file
pointed to by this property. When the files and
properties are correct, retry the operation that failed. 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. If the
problem continues after regenerating the keystore file,
contact IBM Customer Support.
CTGEM0054E The UpdatePW program received
incorrect input arguments.
Explanation: UpdatePW is the Java application that
provides the functions made available to users by the
EncryptPW, EncryptAMProps, AuthXMLAddUser,
AuthXMLRemoveUser and AuthXMLRemoveAuthType
commands. UpdatePW should be invoked only by one
of those commands. This error might indicate that an
unauthorized program called the UpdatePW program
or that there is a programming error in one of the
authorized commands.
Administrator response: If there is an error in the
authorized commands, contact IBM Customer Support.
If UpdatePW was called by an unauthorized program,
change the unauthorized program to use one of the
authorized commands. The purpose and syntax of the
authorized commands is as follows: EncryptPW
password Encrypts password and writes the resulting
string to standard output. This allows you to either
verify or manually update an encrypted password.
EncryptAMProps password Changes the value of the
Registration.Agent.Access.Password parameter in the
agent manager configuration file
(AgentManager.properties) with the encrypted form of
the specified password. AuthXMLAddUser user_ID
password type_name [type_name ...] Creates a resource
manager user ID in the Authorization.xml file, sets its
password to the encrypted form of the password
specified, and adds the user to the user list (userList=)
of the specified authorization types. If the user is listed
in the userList attribute of any of the <authType>
elements that were not listed in the command, it is
524
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
CTGEM0060E CTGEM0065E
property in the AgentManager.properties file is the
name of the registration encryption keystore file,
relative to the ARS.directory location. When the files
and properties are correct, retry the operation that
failed. 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. If the problem continues after
regenerating the keystore file, contact IBM Customer
Support.
CTGEM0060E An error occurred while attempting to
encrypt the resource manager
registration password. The exception is:
exception
Explanation: The specified exception was caught
while trying to encrypt the resource manager password
so that it can be compared to the previously saved
encrypted password. The resource manager registration
password cannot be validated, so the operation that
requires password validation cannot take place.
Administrator response: Follow these steps to verify
that the information needed to encrypt and compare
passwords is available: Ensure that the agent manager
configuration file (AgentManager.properties) is in the
WEB-INF/classes/resources directory of the
AgentManager.war file and that the file is readable by
the current user. Ensure that the directory pointed to by
the ARS.directory property in the
AgentManager.properties file exists and is readable.
Ensure that the value of the REG.keyPWfile.name
property in the AgentManager.properties file is the
name of the registration encryption keystore file,
relative to the ARS.directory location. When the files
and properties are correct, retry the operation that
failed. 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. If the problem continues after
regenerating the keystore file, contact IBM Customer
Support.
CTGEM0061E An error occurred while attempting to
encrypt the agent registration password.
The exception is: exception
Explanation: The specified exception appeared while
encrypting the agent registration password, so that it
could be compared to the previously saved encrypted
password. The agent registration password cannot be
validated, so the operation that required password
validation cannot take place.
Administrator response: Follow these steps to verify
that the information needed to encrypt and compare
passwords is available: Ensure that the agent manager
configuration file (AgentManager.properties) is in the
WEB-INF/classes/resources directory of the
525
CTGEM0066E CTGEM0208E
CTGEM0066E
Invalid operation.
CTGEM0068E
526
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
CTGEM0213E CTGEM0400E
provided as a backup file is not a directory.
CTGEM0213E The temporary directory for the
database data export could not be
created in the following path tmpPath
Explanation: The required directory already exists or
the user does not have proper permissions to create it.
527
CTGEM0501E CTGEM0542E
User response: Save the log file and contact the IBM
Customer Support.
CTGEM0501E An exception occured while installing
the AgentRegistry database.
Explanation: It is a general exception that appears in
case of any unrecognized runtime problems.
Administrator response: Review the runtime log to
find the reason of this problem.
CTGEM0502E The SQL exception occured while
installing the AgentRegistry database.
Explanation: The SQL exception appeared while
invoking the SQL command.
Administrator response: Review the runtime log to
find the reason of this problem.
CTGEM0504W The database configuration
operation not supported.
CTGEM0505W Creating the common agent services
constraints operation not supported.
CTGEM0506W Creating the relation registry
constraints operation not supported.
CTGEM0511E An error occured while creating the
database db_name.
Explanation: The problem appeared while creating a
database object.
Administrator response: Review the runtime log to
find the reason of this problem.
CTGEM0516E An error occured while creating the
relational registry schema.
Explanation: The problem appeared while creating the
relational registry schema.
Administrator response: Review the runtime log to
find the reason of this problem.
CTGEM0520E An error occured while creating the
common agent services schema.
Explanation: The problem appeared while creating the
common agent services schema.
Administrator response: Review the runtime log to
find the reason of this problem.
528
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
CTGEM0546E CTGEM0602E
CERT_EXPIRATION_DT index on the X509_CERT
table.
Administrator response: Review the runtime log to
find the reason of this problem. It could have been
caused by the fact that the X509_CERT table is missing
or that the CERT_EXPIRATION_DT index already
exists.
CTGEM0546E An error occured while creating the
column column_name on the table
table_name.
Explanation: The problem appeared while creating the
column on a specified table.
Administrator response: Review the runtime log to
find the reason of this problem. It could have been
caused by the fact that the table is missing or that the
column already exists.
CTGEM0550E An error occurred while creating the
columns IB_FIXPACK_NUM and
IB_SYMBOLIC_NAME on the
CDB.INSTALLED_BUNDLE table.
CTGEM0573E
529
CTGEM0603E CTGEM0815E
CTGEM0603E Error: Could not get connection using
DataSource datasource
Explanation: An error occured while attempting to get
the database connection using the specified datasource.
Administrator response: Review the log files
information.
CTGEM0604E Error: An exception occurred while
attempting to retrieve the connection
errorMessage
Explanation: An error occured while attempting to
retrieve the database connection.
Administrator response: Review the log files for
information.
CTGEM0605E Error: The database type dbType is not
supported for the driverNumber type
driver.
Explanation: An error occured to get the database
connection using the specified database type driver.
Administrator response: Review the log files for
information.
CTGEM0606E Error: Could not get the connection to
dbType database at class (dbClass) using
the URL (dbUrl). Verify the host name,
port number and database name;
Explanation: An error occured while attempting to get
the database connection.
Administrator response: Review the log files for
information.
CTGEM0801W The status delta descriptor
determines that the following part of
data part_of_data should be updated, but
it is missing. The update of this part of
data will be skipped.
CTGEM0804E An error occurred while querying the
product list: exception_message
Explanation: An agent manager could not retrieve the
list of registered products.
Administrator response: Check if the database is
running and if the connection to the database host can
be established. If the problem keeps recurring contact
IBM Customer Support.
530
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
CTGEM0816E CTGEM1017E
Administrator response: Run the registration process
with the proper toolkit registration password.
CTGEM0816E The authentication type cannot
reserve the value: auth_value
Explanation: It was not possible to add the user with
the reserved authorization type.
Administrator response: Do not use the reserved
authorization type when registering users. Change the
authorization type and run the process again.
CTGEM0819E An error occurred while running the
notification engine. The error message is
error_message.
Explanation: The notification engine encountered an
error while trying to notify common agents about their
jobs.
Administrator response: See the agent manager logs
for the error details and contact IBM Customer Support
if necessary.
CTGEM0820E An exception occured while quering
for agents.
Explanation: The process of retrieving agents from the
agent manager database failed.
Administrator response: See the agent manager logs
for the error details and contact IBM Customer Support
if necessary.
CTGEM0821E An exception occured during the
database connection or the certificates
revocation.
Explanation: Some operations on the agent manager
database failed during the uninstallation or agents
removal or the certificates revocation process.
Administrator response: See the agent manager logs
for the error details and contact IBM Customer Support
if necessary.
CTGEM0822E The response file URL parameter
must come with the installation image
location URL parameter.
Explanation: If you provide the file URL response,
you also have to provide the installation image location
URL.
Administrator response: Provide the proper set of
parameters.
531
CTGEM1018E CTGEM1213E
CTGEM1018E Access to class
service_configurator_class_name is illegal.
Explanation: The instantiated class does not contain
the proper constructor.
Administrator response: Review instantiated class
CTGEM1019E A problem has occured when
initializing security handler
security_handler_class_name.
Explanation: The instantiated class does not contain
the proper constructor.
Administrator response: Review instantiated class
CTGEM1023E The operation operation_name could
not be found.
Explanation: There is no operation registered under
the specified name.
Administrator response: Review the container logs to
check if the operation was spelled correctly or if there
are no internal problems with registering operation.
CTGEM1024E The following exception occured:
exception_class_name. The exception
message is: exception_message.
Explanation: It is a general exception that occurs in
case of any unregognized runtime problem.
Administrator response: Review the container trace
log to find the reason of this problem.
CTGEM1057E DataSource object not found under
JNDI name jndi_name
Explanation: There is no JDBC DataSource object
registered in the local JNDI directory with the specified
JNDI name.
User response: Review your JDBC provider settings in
the container configuration
CTGEM1203E The notification engine could not run
the notification task for the common
agent identified by agent id because of
the following error: error message.
Explanation: The notification engine could not run a
worker thread responsible for the common agent
notification.
Administrator response: If the tracing mechanism is
enabled, save the proper trace file and contact IBM
Customer Support.
532
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
CTGEM1214E CTGEM2002E
Explanation: The notification engine could not
establish a network connection to the specified common
agent because a fatal error occurred.
Administrator response: If the tracing mechanism is
enabled, save the proper trace file and contact IBM
Customer Support.
CTGEM1214E The notification engine task thread
name could not establish a connection to
the common agent identified by agent id
using all its known IP addresses and
ports.
Explanation: The notification engine could not
establish a network connection to the specified common
agent using the TCP/IP addresses and port reported by
the common agent.
Administrator response: Check if the common agent
is running and if it is possible to establish a connection
between the notification engine and common agent
hosts using TCP/IP ports reported by the common
agent.
CTGEM1216E The notification engine task thread
name could not find a job executor for
the job with id job id and type job type
for the common agent identified by
agent id and version
version,release,modification,fixpack.
Explanation: The notification engine could not find a
proper job executor.
Programmer response: Make sure the proper job
executor for the job type and the common agent
version is registered within JobExecutorRegistry.
CTGEM1217E The notification engine task thread
name could not execute the job with id
job id on the common agent identified
by agent id because of the following
error: error message.
Explanation: An error occurred while executing the
job on the common agent.
Administrator response: If the tracing mechanism is
enabled, save the proper trace file and contact IBM
Customer Support.
CTGEM1218E The notification engine task thread
name could not set job statuses to
FINISHED for the common agent
identified by agent id because of the
following error: error message.
Explanation: Although the execution of some jobs
succeeded, their status cannot be updated. These jobs
will be executed until the status update succeeds.
Administrator response: If the engine is run from a
533
CTGEM2003E CTGEM2012E
agent manager application. AgentRecoveryService: The
agent recovery service. Possible causes for this error are
that the application is not installed or that the version
information file has been deleted.
Administrator response: Use the WebSphere
Administrative Console to verify that the application
named application_name is installed. If the application
is installed, verify that the version information file
exists and that the user has permission to read the file.
The file is located in the following directory:
installedApps/ node / application_name .ear/
application_name .war/WEB-INF The name of the
version information file for the agent manager
application is CTGEMAM vvrrmm .sys, where vvrrmm
is the version information. The name of the file for the
agent recovery service application is CTGEMREC
vvrrmm .sys.
CTGEM2003E An error occurred while trying to
read the version information file for the
application_name .
Explanation: An IOException was caught while trying
to read the version information file for
application_name . The variable application_name
specifies one of the following applications:
AgentManager: The agent manager application.
AgentRecoveryService: The agent recovery service.
Administrator response: Use the WebSphere
Administrative Console to verify that the application
named application_name is installed. If the application
is installed, verify that the version information file
exists and that the user has permission to read the file.
The file is located in the following directory:
installedApps/ node / application_name .ear/
application_name .war/WEB-INF The name of the
version information file for the agent manager
application is CTGEMAM vvrrmm .sys, where vvrrmm
is the version information. The name of the file for the
agent recovery service application is CTGEMREC
vvrrmm .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. If
possible, locate the version information file and contact
IBM Customer Support.
534
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
CTGEM2013E CTGEM2102E
System action: The command line arguments could
not be parsed, because the unknown argument was
provided.
CTGEM2013E The parameter value currentArgument
cannot be converted to the declared type
currentType .
Explanation: The command argument could not be
converted to the declared type of this argument during
parsing.
System action: The command argument could not be
converted to the declared type of this argument during
parsing.
CTGEM2014E
CTGEM2031E
CTGEM2035E
Unknown locale.
Unknown type.
535
CTGEM2103E CTGEM2115E
files (msg_EPM_Install.log and trace_EPM_Install.log),
and contact IBM Customer Support.
CTGEM2103E The required property property is
missing.
Explanation: The property property is required but
was not supplied. To find out which script failed, see
the text of the message with the following ID:
CTGEM2100I.
Administrator response: Save the message and trace
files (msg_EPM_Install.log and trace_EPM_Install.log),
and contact IBM Customer Support.
CTGEM2104E The action specified by the action
argument is not accepted by this script.
The action must be either action_1 or
action_2.
Explanation: The command-line argument action is
not accepted by this script. To find out which script
failed, see the text of the message with the following
ID: CTGEM2100I.
Administrator response: Save the message and trace
files (msg_EPM_Install.log and trace_EPM_Install.log),
and then contact IBM Customer Support.
CTGEM2105E The installation program cannot get
the ID for the object specified by the
search string search_string.
Explanation: The internal identifier for the WebSphere
configuration object specified by the search string
search_string was not found. This typically happens
when you provide incorrect input to the installation
program (for example, if you misspell the name of the
WebSphere cell).
Administrator response: Start the installation again,
providing the correct data in all input fields.
CTGEM2110E The installation program cannot load
the resource bundle resource_bundle for
the current locale, current_locale.
Explanation: The installation program cannot locate
the resource bundle resource_bundle in the current
locale, current_locale. This indicates a problem in the
files used by the installation program. This error does
not occur if you start the installation in a locale that is
not supported by the agent manager component. In
that situation, the installation uses the resource bundle
for the default locale.
Administrator response: If possible, obtain a new
copy of the installation media and start the installation
again. If you get the same message again, save the
message and trace files (msg_EPM_Install.log and
trace_EPM_Install.log), and contact IBM Customer
Support.
536
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
CTGEM2120E CTGEM2161E
Administrator response: This message typically
indicates a problem in the installation program. Save
the message and trace files (msg_EPM_Install.log and
trace_EPM_Install.log), and contact IBM Customer
Support.
537
CTGEM2162E CTGEM2199E
CTGEM2162E <p>The database server for VALUE_0
on VALUE_1 does not respond.
<p>Possible causes for this problem
include: the database user ID or
password is not correct, the database
server is not installed in the specified
location, or the database server was not
running when the agent manager
installation was started. The agent
manager installation cannot continue.
CTGEM2164E A problem occurred while creating the
agent manager registry database. The
return value was VALUE_0. Check the
db_stdout.log and db_stderr.log files in
the VALUE_1 directory for information
about the problem.
CTGEM2170W The installation program cannot add
the agent manager Windows service to
the Windows Services list.
CTGEM2171W The installation program cannot start
the Windows service for the agent
manager. You can start the Windows
services manually.
CTGEM2176E The installation program cannot
contact the computer with the host name
VALUE_0. This is the host name that the
common agents use to contact the agent
manager. The host name should be a
fully qualified host name or IP address.
The agent manager installation cannot
continue.
CTGEM2177E The agent manager VALUE_0
parameter is required but was not
specified. The agent manager
installation cannot continue.
CTGEM2190W Some of the files and folders that
were created during the agent manager
installation could not be deleted while
uninstalling. See the agent manager
installation documentation for
instructions for recovering from an
incomplete uninstallation of the agent
manager.
CTGEM2191W The embedded version of IBM
WebSphere Application Server delivered
with the agent manager installer.
538
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
CTGEM2205E CTGEM2215E
CTGEM2205E The agent manager installation did
not complete successfully.
CTGEM2209E Agent manager upgrade processing
was not successful because the agent
manager application did not install into
WebSphere Application Server. Check
the amApp_out.log, amApp_err.log, and
wsadmin.traceout.amApp files in the
VALUE_0 directory for information
about the problem. Click Finish to exit
the upgrade.
539
CTGEM2216E CTGEM2226E
CTGEM2216E A problem occurred while configuring
the agent manager virtual host in
WebSphere Application Server. A
probable cause of this error is that the
specified cell name was not recognized
by WebSphere Application Server. The
return value was VALUE_0. Check the
virHost_out.log and virHost_err.log files
in the VALUE_1 directory for
information about the problem.
CTGEM2217E A problem occurred while configuring
SSL Security in WebSphere Application
Server. The return value was VALUE_0.
Check the ssl_out.log and ssl_err.log
files in the VALUE_1 directory for
information about the problem.
CTGEM2218E A problem occurred while configuring
SSL Security with Client Authentication
in WebSphere Application Server. The
return value was VALUE_0. Check the
sslca_out.log and sslca_err.log files in
the VALUE_1 directory for information
about the problem.
CTGEM2219E A problem occurred while creating the
agent manager application server. The
EPMAppServer.jacl script returned the
value VALUE_0. A probable cause of this
error is that the specified application
server name was not found by
WebSphere Application Server. Check
the appServer_out.log and
appServer_err.log files in the VALUE_1
directory for information about the
problem. The application server name
was VALUE_2.
CTGEM2220E A problem occurred while configuring
a Java Database Connectivity provider
for the registry database. A probable
cause of this error is that the specified
cell name, node name, security context,
or application server name was not
found by WebSphere Application
Server. The EPMJdbcProvider.jacl script
returned the value VALUE_0. Check the
jdbc_out.log and jdbc_err.log files in the
VALUE_1 directory for information
about the problem. The database type
was VALUE_2.
540
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
CTGEM2227E CTGEM2307E
CTGEM2227E Incorrect values were detected in the
user input. Correct the following
problems and try again:
CTGEM2228E A problem occurred while validating
the directory name VALUE_0. Probable
causes of this error are that the directory
name contains characters that are not
allowed, or the user does not have the
sufficient authority to write to the file
system. Check the am_install.log log file
in the VALUE_1 directory for more
information about the problem.
541
CTGEM2310E CTGEM2404E
CTGEM2310E Application server archive error. The
problem is related to the archive of
embedded version of the IBM
WebSphere Application Server. Possible
causes: the archive format might not be
correct, there could be no executable to
handle the archive in your system, the
amount of free space in the temporary
directory might be too small. See the
installation logs for more details.
Explanation: The problem is related to the archive of
embedded version of the IBM WebSphere Application
Server. Possible causes: the archive format might not be
correct, there could be no executable to handle the
archive in your system, the amount of free space in the
temporary directory may be too small.
Administrator response: See the installation logs for
more details.
CTGEM2312E
542
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
CTGEM2417E CTGEM2429E
CTGEM2417E The agent manager certificate
(certs/toolkitTrust.jks file) was not
found or is not valid. The toolkit pack
might not be registered yet. If so,
register it using RegistrationTool.
Explanation: The program could not find the local
toolkit truststore. The most probable cause of this
problem is that the toolkit pack is not registered.
Administrator response: Try to register the toolkit
pack using RegistrationTool. Contact the support team
for help if necessary.
CTGEM2418E The certificate for the toolkit
(certs/toolkitKeys.jks file) was not found
or is not valid. The toolkit pack might
not be registered yet. If so, register it
using RegistrationTool.
Explanation: The program could not find the local
toolkit keystore. The most probable cause of this
problem is that the toolkit pack is not registered.
Administrator response: Try to register the toolkit
pack using RegistrationTool. Contact the support team
for help if necessary.
CTGEM2419E
CTGEM2422E
543
CTGEM2430E CTGEM2448E
CTGEM2430E
CTGEM2433E
544
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
CTGEM2449E CTGEM2474E
CTGEM2449E Parsing the schedule date is not
possible.
Explanation: There is inconsistent data in the input
file.
Administrator response: Check the log files and trace
the files for detailed information or contact the support
team for help.
CTGEM2472E
545
CTGEM2475E CTGEM2506E
CTGEM2475E Connection to the local alias of DB2
database failed.
Explanation: The connection could have failed due to
settings of database connection provided by the user
such as: user name, password, database installation
directory, database name that might not be correct.
Administrator response: Check the database settings
and enter the correct values. If the values are correct,
check the database server sanity.
CTGEM2476E Connection to local DB2 database
failed.
Explanation: The connection could have failed due to
settings of database connection provided by the user
such as: user name, password, database installation
directory, database name that might not be correct.
Administrator response: Check the database settings
and enter the correct values. If the values are correct,
check the database server sanity.
CTGEM2477E Authorization script failed. The
exception message is the following:
exception
CTGEM2482E
546
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
CTGEM2507E CTGEM2518E
uninstall the agent manager manually.
CTGEM2507E The application server could not be
stopped. The uninstallation cannot
continue.
Explanation: The script that stops the WebSphere
Application Server returned an error.
Administrator response: See the installation logs for
more details.
CTGEM2508E Removing the agent manager
applications has failed.
Explanation: Removing the agent manager and the
agent manager recovery service configuration from
WebSphere Application Server failed due to an
unrecoverable error.
Administrator response: See the installation logs for
more details.
547
CTGEM2519E CTGEM2533E
CTGEM2519E Installation of the agent manager
applications on the application server
has failed.
Explanation: Installation of the agent manager and the
agent manager recovery applications on WebSphere
Application Server failed due to an unrecoverable error.
Administrator response: See the installation logs for
more details and try to install the agent manager again.
CTGEM2520E Creating the Java Database
Connectivity provider has failed.
Explanation: The configuration of Java Database
Connectivity provider on WebSphere Application
Server has failed due to an unrecoverable error.
Administrator response: See the installation logs for
more details and try to install again.
CTGEM2521E Creation of the application server
instance has failed.
Explanation: The configuration of the application
server instance on WebSphere Application Server failed
due to an unrecoverable error.
Administrator response: See the installation logs for
more details and try to install again.
CTGEM2522E Creating the Secure Sockets Layer
configuration of the virtual host has
failed.
Explanation: Configuration of Secure Sockets Layer on
WebSphere Application Server failed due to an
unrecoverable error.
Administrator response: See the installation logs for
more details and try to install again.
CTGEM2523E Creating the the virtual host has
failed.
Explanation: Configuration of the virtual host on
WebSphere Application Server failed due to an
unrecoverable error.
Administrator response: See the installation logs for
more details and try to install again.
548
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
CTGEM2534E CTGEM2556E
CTGEM2534E Connection to Microsoft SQL Server
remote database has failed.
Explanation: The connection could have failed due to
settings of database connection provided by the user
such as: user name, password, database server host and
port, database driver directory, database name that
might not be correct. Possible causes also include: lack
of SQL CONNECT privilege for either administrative
or runtime user whose credentials you provided,
restrictive firewall rules, no database process launched
on the database hosting server.
Administrator response: Check the database settings
and enter the correct values. If the values are correct,
check the firewall settings and the database server
sanity.
CTGEM2536E Insufficient privileges of
administrative user.
Explanation: The user whose credentials you provided
(either administrator if you selected that option or
runtime user if administrator was not selected) does
not have sufficient privileges to perform database
schema modification tasks of the agent manager
installation process.
Administrator response: Refrer to the manual to
obtain information about privileges required for
Microsoft SQL Server database user and how to grant
them or contact your database administarator.
CTGEM2537E Insufficient privileges of
administrative user.
549
CTGEM2557W CTGRI0005E
CTGEM2557W Warning: The installer is unable to
remove the copy of the embedded
version of IBM WebSphere Application
Server from your workstation. You need
to perform the manual uninstallation of
the embedded version of IBM
WebSphere Application Server in the
following way: Stop the WebSphere
server either by issuing command: sc
stop was_service_name or by ending the
process tree of WebSphere including
java.exe process which was used to
launch the server. Remove the contents
of the directory: was_directory_name
Delete the WebSphere service from your
system by issuing the command: sc
delete was_service_name
Explanation: The agent manager installer is unable to
remove the embedded version of IBM WebSphere
Application Server.
CTGRI
This section contains messages with the CTGRI identifier from the Remote Execution and Access (RXA)
messages in Tivoli Provisioning Manager.
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.
550
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
CTGRI0006E CTGRI0017E
Programmer response: Verify that the local file
specified is not open or in read-only mode, and that it
exists. Also verify that enough space is available on the
target system.
CTGRI0006E An error occurred when writing to the
remote file: pathname.
Explanation: The specified file might be read-only, in
use, or there might be insufficient space on the target.
Programmer response: Ensure that the remote file
specified is not open or in read-only mode, and that
enough space is available on the target system.
CTGRI0007E An error occurred when reading the
remote file: pathname.
551
CTGRI0018E CTGRI0026E
remote protocols are enabled on the target.
CTGRI0018E An error occurred in SCP
communication.
Explanation: A secure copy (SCP) operation failed.
Programmer response: Ensure that the SSH remote
protocol is enabled on the target.
CTGRI0019E RSH could not bind to any local
privileged port.
Explanation: An RSH operation was attempted but
failed because RSH could not bind to a privileged port.
Programmer response: Ensure that the local machine
has administrative privileges to open restricted ports.
CTGRI0020E Could not find the remote user
RemoteUser.
Explanation: The specified remote username could not
be found.
Programmer response: Verify that the specified
username exists on the target machine.
CTGRI0021E The charset_name character set is not
supported.
552
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
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. Any functionally equivalent product, program, or service that
does not infringe any IBM intellectual property right may be used instead. However, it is the user's
responsibility to evaluate and verify the operation of any non-IBM product, program, or service.
IBM may have patents or pending patent applications covering subject matter described in this
document. The furnishing of this document does not give you any license to these patents. You can send
license inquiries, in writing, to:
IBM Director of Licensing
IBM Corporation
North Castle Drive
Armonk, NY 10504-1785 U.S.A.
For license inquiries regarding double-byte (DBCS) information, contact the IBM Intellectual Property
Department in your country or send inquiries, in writing, to:
Intellectual Property Licensing
Legal and Intellectual Property Law
IBM Japan, Ltd.
1623-14, Shimotsuruma, Yamato-shi
Kanagawa 242-8502 Japan
The following paragraph does not apply to the United Kingdom or any other country where such
provisions are inconsistent with local law:
INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS"
WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT
LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR
FITNESS FOR A PARTICULAR PURPOSE.
Some states do not allow disclaimer of express or implied warranties in certain transactions, therefore,
this statement might not apply to you.
This information could include technical inaccuracies or typographical errors. Changes are periodically
made to the information herein; these changes will be incorporated in new editions of the publication.
IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this
publication at any time without notice.
Any references in this information to non-IBM Web sites are provided for convenience only and do not in
any manner serve as an endorsement of those Web sites. The materials at those Web sites are not part of
the materials for this IBM product and use of those Web sites is at your own risk.
IBM may use or distribute any of the information you supply in any way it believes appropriate without
incurring any obligation to you.
553
Licensees of this program who wish to have information about it for the purpose of enabling: (i) the
exchange of information between independently created programs and other programs (including this
one) and (ii) the mutual use of the information which has been exchanged, should contact:
IBM Corporation
2Z4A/101
11400 Burnet Road
Austin, TX 78758
U.S.A.
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.
Information concerning non-IBM products was obtained from the suppliers of those products, their
published announcements or other publicly available sources. IBM has not tested those products and
cannot confirm the accuracy of performance, compatibility or any other claims related to non-IBM
products. Questions on the capabilities of non-IBM products should be addressed to the suppliers of
those products.
Trademarks
IBM, the IBM logo, and ibm.com are trademarks or registered trademarks of International Business
Machines Corp., registered in many jurisdictions worldwide. Other product and service names might be
trademarks of IBM or other companies. A current list of IBM trademarks is available on the Web at
Copyright and trademark information at www.ibm.com/legal/copytrade.shtml.
Adobe, the Adobe logo, PostScript, and the PostScript logo are either registered trademarks or trademarks
of Adobe Systems Incorporated in the United States, and/or other countries.
IT Infrastructure Library is a registered trademark of the Central Computer and Telecommunications
Agency which is now part of the Office of Government Commerce.
Intel, Intel logo, Intel Inside, Intel Inside logo, Intel Centrino, Intel Centrino logo, Celeron, Intel Xeon,
Intel SpeedStep, Itanium, and Pentium are trademarks or registered trademarks of Intel Corporation or its
subsidiaries in the United States and other countries.
Linux is a registered trademark of Linus Torvalds in the United States, other countries, or both.
Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft Corporation in the
United States, other countries, or both.
ITIL is a registered trademark, and a registered community trademark of the Office of Government
Commerce, and is registered in the U.S. Patent and Trademark Office.
UNIX is a registered trademark of The Open Group in the United States and other countries.
Java and all Java-based trademarks and logos are trademarks or registered trademarks of Oracle and/or
its affiliates.
Other product and service names may be trademarks of IBM or other companies.
554
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
Introduction
Identify and resolve problems that might occur when you are using the product.
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 Provisioning Manager.
There are a number of options available for problem determination, and they are described in this
section. The options include:
v Obtaining support to help identify your problem.
v Consulting the overall product overview.
v Using the log files for troubleshooting.
Security problems
This section describes how to recover from security problems.
Discovery problems
This section describes how to recover from Tivoli Provisioning Manager discovery problems.
OS management problems
This section describes how to recover from OS management problems.
Compliance problems
This section contains known limitations regarding compliance checks and compliance recommendations.
Copyright IBM Corp. 2003, 2011
555
On the Compliance tab of the Provisioning Computers application, the filter of the Compliance Checks
field is disabled.
On the Recommendations tab of the Provisioning Computers application, the filter of the Compliance
Recommendations field enables you to filter the recommendations only by Recommendation ID. This
limited filtering option is due to the following behavior of the base services: the base services
infrastructure does not allow you to filter non persistent objects.
Virtualization problems
This section describes how to recover from virtualization management problems.
Reporting problems
This section describes how to recover from reporting problems.
556
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
Other problems
This section describes how to recover from miscellaneous Tivoli Provisioning Manager problems.
Messages
System events taking place within Tivoli Provisioning Manager are recorded as text messages in message
logs. This section lists and describes the messages and message logs.
Troubleshooting Guide
557
558
IBM Tivoli Provisioning Manager Version 7.1.1 Problem Determination and Troubleshooting Guide
Printed in USA