HP OpenView IT/Operations Error Message Reference

HP OpenView IT/Operations Error Message Reference

HP OpenView IT/Operations

Error Message Reference

Edition 2

B6941-90005

HP OpenView IT/Operations

Version A.05.00

February 1999

Legal Notices

Hewlett-Packard makes no warranty of any kind with regard to this manual, including, but not limited to, the implied warranties of

merchantability and fitness for a particular purpose. Hewlett-Packard shall not be held liable for errors contained herein or direct, indirect, special, incidental or consequential damages in connection with the furnishing, performance, or use of this material.

Warranty. A copy of the specific warranty terms applicable to your

Hewlett-Packard product and replacement parts can be obtained from your local Sales and Service Office.

Year 2000 Readiness. Hewlett-Packard has made every effort to ensure the accuracy of our product testing. However, because each customer's environment is different from Hewlett-Packard's laboratory test environment, it is the customer's responsibility to validate the Year 2000 readiness of these products in their own environment. Therefore, information about the Year 2000 status of Hewlett-Packard products is provided “as is” without warranties of any kind and is subject to change without notice.

Hewlett-Packard makes no representation or warranty respecting the accuracy or reliability of information about non-Hewlett-Packard products. Such information, if any, was provided by the manufacturers of those products and customers are urged to contact the manufacturer directly to verify Year 2000 readiness.

The information provided here constitutes a Year 2000 Readiness

Disclosure for purposes of the Year 2000 Information and Readiness

Disclosure Act.

Restricted Rights Legend. All rights are reserved. No part of this document may be photocopied, reproduced, or translated to another language without the prior written consent of Hewlett-Packard

Company. The information contained in this document is subject to change without notice.

Use, duplication or disclosure by the U.S. Government is subject to restrictions as set forth in subparagraph (c) (1) (ii) of the Rights in

Technical Data and Computer Software clause at DFARS 252.227-7013

2

for DOD agencies, and subparagraphs (c) (1) and (c) (2) of the

Commercial Computer Software Restricted Rights clause at FAR 52.227-

19 for other agencies.

HEWLETT-PACKARD COMPANY

3404 E. Harmony Road

Fort Collins, CO 80525 U.S.A.

Use of this manual and flexible disk(s), tape cartridge(s), or CD-ROM(s) supplied for this pack is restricted to this product only. Additional copies of the programs may be made for security and back-up purposes only.

Resale of the programs in their present form or with alterations, is expressly prohibited.

Copyright Notices. ©copyright 1983-99 Hewlett-Packard Company, all rights reserved.

Reproduction, adaptation, or translation of this document without prior written permission is prohibited, except as allowed under the copyright laws.

©copyright 1979, 1980, 1983, 1985-93 Regents of the University of

California

This software is based in part on the Fourth Berkeley Software

Distribution under license from the Regents of the University of

California.

©copyright 1986-1992 Sun Microsystems, Inc.

©copyright 1985-86, 1988 Massachusetts Institute of Technology

©copyright 1989-93 The Open Software Foundation, Inc.

©copyright 1986-1997 FTP Software, Inc. All rights reserved

©copyright 1986 Digital Equipment Corporation

©copyright 1990 Motorola, Inc.

©copyright 1990, 1991, 1992 Cornell University

©copyright 1989-1991 The University of Maryland

©copyright 1988 Carnegie Mellon University

Trademark Notices. UNIX® is a registered trademark in the United

States and other countries, licensed exclusively through X/Open

Company Limited.

3

X Window System is a trademark of the Massachusetts Institute of

Technology.

OSF/Motif is a trademark of the Open Software Foundation, Inc. in the

U.S. and other countries.

Windows NT™ is a U.S. trademark of Microsoft Corporation. Windows® and MS Windows® are U.S. registered trademarks of Microsoft Corp.

Oracle®, SQL*Net®, and SQL*Plus® are registered U.S. trademarks of

Oracle Corporation, Redwood City, California. Oracle Reports™,

Oracle7™, and Oracle7 Server™ are trademarks of Oracle Corporation,

Redwood City, California.

Java™ is a U.S. trademark of Sun Microsystems, Inc.

Netscape Commerce Server and Netscape Communications Server are

U.S. trademarks of Netscape Communications Corporation.

OpenView® is a registered U.S. trademark of Hewlett-Packard Company.

4

Printing History

The manual printing date and part number indicate its current edition.

The printing date will change when a new edition is printed. Minor changes may be made at reprint without changing the printing date. The manual part number will change when extensive changes are made.

Manual updates may be issued between editions to correct errors or document product changes. To ensure that you receive the updated or new editions, you should subscribe to the appropriate product support service. See your HP sales representative for details.

First Edition: August 1997

Second Edition: February 1999

5

6

In This Book

This book provides a copy of all ITO error messages that have additional instructional text available. This book contains no information that is not also available from the user interface.

For information on how to install ITO on the management server, see the

HP OpenView IT/Operations Installation Guide for the Management

Server.

For a description of the ITO administrator’s daily setup and configuration tasks, see the HP ITO Administrator’s Guide to Online

Information.

For information about upgrading an earlier version of ITO , see the HP

OpenView IT/Operations Software Release Notes.

For information about ITO concepts, see the HP OpenView IT/

Operations Concepts Guide.

7

8

Conventions

The following typographical conventions are used in this manual.

Font Type What the Font Type Represents

Italic

Book or manual titles, and man page names

Bold

Provides emphasis

Specifies a variable that you must supply when entering a command

Parameters to a function

New terms

Computer

Text and items on the computer screen

Command names

Function names

Example

Refer to the HP OpenView IT/

Operations Administrator’s

Reference and the opc(1M) manpage for more information.

You must follow these steps.

At the prompt type: rlogin

your_name where you supply your login name.

The oper_name parameter returns an integer response.

The monitor agent observes...

The system replies:

Press Enter

Computer

Bold

File and directory names

Process names

Window/dialog box names

Text that you must enter

Use the grep

command ...

Use the opc_connect() function to connect ...

/opt/OV/bin/OpC

/

Check to see if opcmona

is running.

In the

Add Logfile

window...

At the prompt, type:

ls -l

9

Font Type What the Font Type Represents

Keycap

Keyboard keys

[Button]

Buttons on the user interface.

Menu

Items

A menu name followed by a colon (:) means that you select the menu, then the item. When the item is followed by an arrow (

->

), a cascading menu follows.

Example

Press

Return

.

Click

[Operator]

.

Click on the

[Apply]

button.

Select

Actions:Utilities->

Reports

10

The IT/Operations Documentation Map

ITO provides a set of manuals and online help which aim to assist you in using ITO and improve your understanding of the underlying concepts.

This section illustrates what information is available and where you can find it.

HP OpenView IT/Operations Printed Manuals

This section provides an overview of the printed manuals and their contents.

The HP OpenView IT/Operations Concepts Guide provides you with an understanding of ITO on two levels. As an operator, you can learn about ITO's basic structure; as an administrator, you can use this book to gain an insight into the setup and configuration of ITO in your own environment.

The HP OpenView IT/Operations Installation Guide for the Management

Server

is for administrators who install ITO software on the management server and perform initial configuration.

It includes:

• verification of software and hardware requirements

• software installation and de-installation instructions

• configuration instructions using defaults

The HP OpenView IT/Operations Administrator’s Reference is for people who install ITO on the managed nodes and are responsible for the administration and troubleshooting of ITO in general.

The HP OpenView IT/Operations Error Message Reference is for administrators involved in ITO problem solving.

It provides a copy of all ITO error messages that have additional instructional text available. This book contains no information that is not also available from the user interface.

11

Managing Your Networks with HP OpenView Network Node Manager

is for administrators and operators. It describes the basic functionality of HP OpenView Network Node

Manager which is an embedded part of ITO.

The HP OpenView ServiceNavigator Concepts and Configuration Guide provides information for administrators who are responsible for installing, configuring, maintaining, and troubleshooting the HP OpenView

ServiceNavigator. It also contains a high-level overview of the concepts behind service management.

The HP OpenView IT/Operations Reporting and Database Schema contains a detailed description of the ITO database tables and provides examples for generating reports from the ITO database.

The HP OpenView IT/Operations Software Release Notes give a description of new features. In addition, they provide information to help you:

• compare the current software’s features with those available in previous versions of the software

• determine system and software compatibility

• solve known problems

ITO Online Information

The following information is available online:

The HP ITO Administrator’s Guide to Online Information is a context-sensistive help system and contains detailed help for each window of the ITO administrator

GUI as well as step-by-step instructions for performing administrative tasks.

The HP ITO Operator’s Guide to Online Information is a context-sensitive help system and contains detailed help for each window of the ITO operator Motif GUI as well as step-by-step instructions for operator tasks.

The HP ITO Java-based GUI Online Documentation is available in HTML-format for the ITO Java-based operator GUI and the ServiceNavigator, and contains detailed information about general ITO and

12

ServiceNavigator concepts and tasks for the ITO operator, as well as reference and troubleshooting information.

The HP OpenView IT/Operations Man Pages are available online for ITO.

HP OpenView IT/Operations Developer’s Toolkit

If you purchase the HP OpenView IT/Operations Developer’s Toolkit, you receive the full ITO documentation set, as well as the following manuals:

The HP OpenView IT/Operations Application Integration Guide suggests several ways in which external applications can be integrated into ITO.

The HP OpenView IT/Operations Developer’s Reference provides an overview of all available application programming interfaces (APIs).

HP OpenView ECS Designer for NNM and ITO

If you purchase the HP OpenView Event Correlation Services (ECS)

Designer for NNM and ITO, you receive the full ECS Designer documentation set including the title:

HP OpenView ECS Configuring Circuits for NNM and ITO

which contains information you need to use the ECS

Designer product in the NNM and ITO environments.

Advanced Network Security for HP OpenView IT/Operations

If you purchase the Advanced Network Security (ANS) extension for HP

OpenView IT/Operations , you receive the following additional documentation:

Advanced Network Security for HP OpenView IT/Operations

provides information for administrators who are responsible for installing, configuring, maintaining, and troubleshooting ANS.

Electronic Version of the Manuals

All manuals except the HP OpenView IT/Operations Software Release

Notes are also included as Portable Document Format (PDF) files in the appropriate documentation software bundle. See the HP OpenView

13

IT/Operations Installation Guide for the Management Server for general installation instructions using swinstall

. The manuals are installed into the following directory on the management server:

/opt/OV/doc/<LANG>/OpC/

Alternatively, you can download the manuals from the following web site: http://ovweb.external.hp.com/lpe/doc_serv

Or, view them in HTML format at: http://docs.hp.com

ITO DynaText Library

The ITO DynaText Library is a collection of ITO manuals in online format based on DynaText. DynaText is an application for viewing, searching, printing, and annotating your online library. The browser and the manuals are available in the appropriate ITO documentation software bundle. See the HP OpenView IT/Operations Installation Guide

for the Management Server for general installation instructions using swinstall

. Once the bundle is installed, you can open the library by selecting

Online Manuals

from the

Help

menu of any primary ITO window.

14

Using the Online Help System

The ITO Motif GUI Online Help System

ITO's Motif GUI online information consists of two separate volumes, one for operators and one for administrators. In the operator's volume, you will find the HP OpenView IT/Operations Quick Start describing the main operator windows. Both volumes include:

❏ information you need to perform tasks, whether you are an operator or an administrator

❏ popup menus, reference information about ITO icons, accessible with just a point and click on the right mouse button

❏ information about errors displayed in the ITO-Error Information window. You can get help either when the error occurs or by using the message number provided to perform a keyword search within the help system

❏ an index search utility that leads you directly to the desired topic

❏ a glossary of terms that are important to users of ITO

❏ help on help for users just getting started with online information systems

❏ a printing facility, which allows you to print any or all topics in the help system (a HP LaserJet printer is required to print graphics)

You can access the help system in any of the following ways:

❏ in any active text field or on any active button, press the

F1

key,

❏ click the

Help

button in the bottom of any window

❏ open the drop-down

Help

menu from the menu bar

❏ click a symbol and use the right-hand mouse button to access the

Help

menu

You can then select task lists which are arranged by activity, or window and field lists. You can access any topic in the help volume from every help screen. Hyperlinks provide related information on other help topics.

15

You can also get context sensitive help in the

Message Browser and

Message Source Templates

window. After selecting

Help: On

Context

from the menu, the cursor changes into a question mark which you can then position over the area on which you want help. When you click the mouse button, the required help page is displayed in its help window.

The ITO Java-based GUI and OV ServiceNavigator Online Documentation

The ITO Java-based GUI online documentation helps operators to become familiar with and use the ITO product. The following information is included:

❏ Tasks—Step-by-step instructions for using ITO and the OV

ServiceNavigator

❏ Concepts—An introduction to the key concepts and features of ITO and the OV ServiceNavigator.

❏ References—Detailed information to help operators maximize their use of ITO and the OV ServiceNavigator.

❏ Troubleshooting—Solutions to common problems you may encounter while using ITO or the OV ServiceNavigator.

❏ Index—An index to help operators quickly find the information they need.

To view any topic, open the appropriate folders in the frame on the left and click on the topic title. Hyperlinks provide related information on other help topics.

Access the help system by selecting

Help: Contents

from the main menu of the Java GUI. A web browser opens and displays the help contents. Note that you must first configure ITO to use your preferred browser, see the HP OpenView IT/Operations Installation Guide for the

Management Server for more information.

16

Contents

1. Introduction

About this Book . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21

Filtering ITO Internal Error Messages . . . . . . . . . . . . . . . . . . . . . . . . . .22

2. ITO Error Messages

Internal error messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25

Error messages of public routines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .28

Error messages of agent processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .80

Error messages of manager processes . . . . . . . . . . . . . . . . . . . . . . . . . .129

Error messages of DB access. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .170

Internal Database messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .192

Message set used by the application integration program . . . . . . . . . .193

Upload/Download feature messages . . . . . . . . . . . . . . . . . . . . . . . . . . . .196

Database installation/upgrade messages . . . . . . . . . . . . . . . . . . . . . . . .221

Error messages of user interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .227

NT installation messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .243

Security related messages (commands and modules) . . . . . . . . . . . . . .261

17

Contents

18

1 Introduction

19

Introduction

20 Chapter 1

Introduction

About this Book

OpC10-0001

About this Book

This book provides a copy of all ITO error messages for which additional instructional text is available. The content of this book is identical to the error message help text available from the user interface.

For some internal error messages, however, ITO provides no additional instructional text. If you need more information about any of these messages, contact your local HP Response Center.

You can also use the command line tool opcerrget

to get the instructional text for an error message:

/opt/OV/bin/OpC/utils/opcerrget <set> <msg>

For example, to get the instructional text for error message OpC10-0001, enter:

/opt/OV/bin/OpC/utils/opcerrget 10 0001

In this book, the error messages are in numerical order, and are presented in the following format:

The text of the error message.

The explanatory help text for the error.

Chapter 1 21

NOTE

Introduction

Filtering ITO Internal Error Messages

Filtering ITO Internal Error Messages

ITO internal error messages can be extracted from or filtered out of the internal MSI so that automatic and operator-initiated actions may be attached and the message treated as if it were a normal, visible ITO messages. This functionality may be enabled both on the managed node and on the ITO management server. Depending on where the functionality is enabled, all ITO internal messages will be sent back to the local message interceptor either on the ITO management server or on the managed node, where they will be seen and treated in the same way as any other ITO message. The user enables this feature by adding the string

OPC_INT_MSG_FLT TRUE

to either the opcsvinfo

file on the management server or the opcinfo

file on the managed node.

You should set up at least one condition for the ITO internal error messages in the opcmsg (1/3) template (using message group OpC) and set the

[Suppress Duplicate]

button to avoid looping error messages.

22 Chapter 1

2 ITO Error Messages

23

ITO Error Messages

24 Chapter 2

ITO Error Messages

Internal error messages

OpC10-0001

OpC10-0002

OpC10-0011

OpC10-0012

OpC10-0013

OpC10-0014

OpC10-0018

OpC10-0020

OpC10-0030

Internal error messages

Insufficient memory

The process cannot allocate enough memory. This could be an internal error, or one of the following is true: a. Kernel parameter of maximum user's process size limit is reached.

Solution: Adapt the Kernel parameter value for maxdsiz.

b. SWAP space limitation reached. Solution: Increment SWAP space.

Unexpected function return value <

x1

> of function <

x2

>.

Internal Error. Please report this to your HP Response Center.

Illegal NULL parameter (function <

x1

>)

Internal Error. Please report this to your HP Response Center.

Illegal index <

x1

> (function <

x2

>)

Internal Error. Please report this to your HP Response Center.

Illegal value <

x1

> (function <

x2

>)

Internal Error. Please report this to your HP Response Center.

Illegal case mark (function <

x1

>)

Internal Error. Please report this to your HP Response Center.

Critical return code <

x1

> (function <

x2

>)

Internal Error. Please report this to your HP Response Center.

Invalid list.

Internal Error. Please report this to your HP Response Center.

Internal RLS cleanup.

Internal Error. Please report this to your HP Response Center.

Chapter 2 25

OpC10-0031

OpC10-0032

OpC10-0033

OpC10-0034

OpC10-0036

OpC10-0037

OpC10-0040

OpC10-0050

OpC10-0052

ITO Error Messages

Internal error messages

Internal num srv.

Internal Error. Please report this to your HP Response Center.

Cannot uname(2).

The uname(2) system call failed. This message is qualified by a system error message (errno) containing the cause of the error.

Cannot gethostname(2).

The gethostname(2) call failed. This message is qualified by a system error message (errno) containing the cause of the error.

File <

x1

> not found.

The required file <filename> could not be found.

Cannot compress file <

x1

>.

The file is not compressible or another compressing error has been detected. Solution: Compress the file manually, if possible. MPE/iX special: use the file /usr/OV/bin/OpC/install/mpecmpr on the management server.

Cannot uncompress file <

x1

>.

The file cannot be uncompressed, or another uncompressing error has been detected. Solution: Uncompress the file manually. MPE/iX special: use the file /usr/OV/bin/OpC/install/mpeucmpr on the management server or MPEUCMPR.BIN.OVOPC on the MPE/iX managed node.

Unexpected value <

x1

> in switch statement of function

<

x2

>.

Internal Error. Please report this to your HP Response Center.

Size of array <

x1

> too small.

The strftime(3C) call failed because the given array is too small. Please report this internal error to your HP Response Center.

Problems using strftime(3).

The strftime(3C) call to format a time value failed. This message is qualified by a system error message (errno) containing the cause of the error.

26 Chapter 2

OpC10-0053

OpC10-0055

OpC10-0056

ITO Error Messages

Internal error messages

Problems using localtime(3).

The localtime(3C) call to convert a time value failed. This message is qualified by a system error message (errno) containing the cause of the error.

Invalid date format <

x1

>.

Internal error. Please report this to your HP Response Center.

Invalid time format <

x1

>.

Internal error. Please report this to your HP Response Center.

Chapter 2 27

ITO Error Messages

Error messages of public routines

OpC20-0004

OpC20-0005

OpC20-0006

OpC20-0007

OpC20-0008

OpC20-0009

OpC20-0001

OpC20-0002

OpC20-0003

Error messages of public routines

Invalid queue descriptor '<

x1

>'.

Internal error. Please report this to your HP Response Center.

Invalid queue file '<

x1

>' (qd = <

x2

>, fd = <

x3

>).

The ITO queue file has been corrupted. Solution: Remove this file and restart the reporting processes. If <qd> or <fd> have values other than low positive integer numbers this might be an internal error, in which case it should be reported to your HP Response Center.

Can't open queue file '<

x1

>'.

The ITO queue file can't be opened by the reporting process. This message is qualified by a system error text (errno) containing the error cause.

Can't close queue file '<

x1

>' (qd = <

x2

>, fd = <

x3

>).

Internal error. Please report this to your HP Response Center.

Can't seek queue file '<

x1

>' (qd = <

x2

>, fd = <

x3

>).

Internal error. Please report this to your HP Response Center.

Can't read queue file '<

x1

>' (qd = <

x2

>, fd = <

x3

>).

Internal error. Please report this to your HP Response Center.

Can't write queue file '<

x1

>' (qd = <

x2

>, fd = <

x3

>).

Internal error. Please report this to your HP Response Center.

Can't truncate queue file '<

x1

>' (qd = <

x2

>, fd = <

x3

>).

Internal error. Please report this to your HP Response Center.

Can't lock queue file '<

x1

>' (qd = <

x2

>, fd = <

x3

>).

Internal error. Please report this to your HP Response Center.

28 Chapter 2

OpC20-0010

OpC20-0011

OpC20-0012

OpC20-0013

OpC20-0014

OpC20-0015

ITO Error Messages

Error messages of public routines

Can't unlock queue file '<

x1

>' (qd = <

x2

>, fd = <

x3

>).

Internal error. Please report this to your HP Response Center.

Can't open queue file '<

x1

>' due to full system table.

The ITO queue file can't be opened by the reporting process because a system file table is full. Solution: Check the system file table limits and increase them if necessary.

Can't lock queue file '<

x1

>' (qd = <

x2

>, fd = <

x3

>) due to full system table.

There are two possibilities: a. The ITO queue file can't be locked by the reporting process because the system lock table is full.

Solution: Check the system lock table limits and increase them if necessary. A tool such as Glance is appropriate for HP systems.

Note that if <qd> or <fd> have values other than low positive integer numbers this might be an internal error, in which case it should be reported to your HP Response Center.

b. An ITO queue file is located on an NFS mounted file system, and the process lockd(1M) is not running on the remote system.

Solution: Start lockd(1M) on the remote system.

Can't write queue file '<

x1

>' (qd = <

x2

>, fd = <

x3

>). No file space.

The reporting process can't append an element to the ITO queue file because either the file system is full or the file size limit is reached.

Solution: Check the file system and the size of the ITO queue file. If the file's size is too large, check that all ITO processes are running. If <qd> or <fd> have values other than low positive integer numbers this might be an internal error, in which case it should be reported to your HP

Response Center.

Queue '<

x1

>' is empty (qd = <

x2

>).

Internal error. Please report this to your HP Response Center.

Read buffer is too small.

Internal error. Please report this to your HP Response Center.

Chapter 2 29

OpC20-0016

OpC20-0020

OpC20-0021

OpC20-0025

OpC20-0026

OpC20-0027

OpC20-0028

OpC20-0029

ITO Error Messages

Error messages of public routines

Unread operation on queue file '<

x1

>' already done (qd =

<

x2

>).

Internal error. Please report this to your HP Response Center.

You must be superuser <

x1

> to run this service.

The program may be executed by the superuser <user> only.

Cannot read password file entry.

The password file /etc/passwd does not exist, or there is no entry for the effective user-ID of the execution user. Solution: Check the existence of

/etc/passwd and verify that an appropriate entry for the calling user is available.

Cannot open directory <

x1

>.

The reporting process was not able to open the directory <dir>. Check whether it exists and the required permissions are set. This message is qualified by a system error message (errno) containing the cause of the error.

Cannot read entry of directory <

x1

>.

The reporting process was not able to read the directory <dir>. This message is qualified by a system error message (errno) containing the cause of the error.

Cannot close directory <

x1

>.

The reporting process was not able to close the directory <dir>. This message is qualified by a system error message (errno) containing the cause of the error.

Cannot uncompress file <

x1

>.

The reporting process was not able to uncompress the file <file>. On

UNIX systems this happens usually using the program uncompress(1).

Check whether this program is present, executable and contained in the

PATH variable of the execution environment of the reporting process.

Cannot compress file <

x1

>.

30 Chapter 2

OpC20-0030

OpC20-0031

OpC20-0032

OpC20-0033

OpC20-0034

OpC20-0035

OpC20-0036

OpC20-0037

OpC20-0038

ITO Error Messages

Error messages of public routines

The reporting process was not able to compress the file <file>. On UNIX systems this happens usually using the program compress(1). Check whether this program is present, executable and contained in the PATH variable of the execution environment of the reporting process.

No configuration installed.

Internal error. Please report this to your HP Response Center.

Invalid object definition for object <

x1

>.

Internal error. Please report this to your HP Response Center.

Invalid object list.

Internal error. Please report this to your HP Response Center.

Multiple objects with name '<

x1

>' defined.

This can happen you you assigned a monitor and a scheduled action with the same name to a agent. Please use unique names for monitors and a scheduled actions. If this error has an other reason it is in internal error.

Please report it then to your HP Response Center.

Select call failed.

A call to select(2) failed. This message is qualified by a system error text

(errno).

Check callback of object <

x1

> returns invalid value.

Internal error. Please report this to your HP Response Center.

Processing callback of object <

x1

> returns not OK for event <

x2

>.

Qualifying error message. More information is contained in another part of the message.

Can't find object '<

x1

>' to set async. flag.

Qualifying error message. More information is contained in another part of the message.

Statistics option not compiled into module.

Internal error. Please report this to your HP Response Center.

Chapter 2 31

OpC20-0039

OpC20-0040

OpC20-0054

OpC20-0056

OpC20-0060

ITO Error Messages

Error messages of public routines

Can't open trace file <

x1

>.

Internal error. Please report this to your HP Response Center.

Can't write trace file <

x1

>.

Internal error. Please report this to your HP Response Center.

Could not find entry for 'opcgrp' in the system group file. You must be a member of this group to start a Motif GUI or run a database report.

The Unix Group 'opcgrp' is vital for the operation of ITO Motif GUIs and database reports. Please check why this group is no longer configured in

'/etc/group' and/or '/etc/logingroup'! After adding the group you must also ensure that /opt/OV/bin/OpC/opc is owned by this group and has the set group ID bit set (if at all possible, use the group ID of this file as already set).

You currently have no 'opcgrp' rights. Please check with your ITO administrator why you do not have these rights. You may also check '/etc/group' and '/etc/logingroup' to see if you are listed as a member of 'opcgrp'.

Without 'opcgrp' rights you will not be able to start a Motif GUI or run a database report unless you are a root user.

For normal operation of ITO Motif GUIs, the set group ID bit must be set for file /opt/OV/bin/OpC/opc, for group opcgrp. If you do not want this, the

ITO Administrator must ensure that ALL operators have rights for opcgrp. Users using CDE on the management server (directly or remotely) can do an 'su - <user_name>' in a shell before starting ITO or have the system administrator install an appropriate CDE patch fixing the logingroups() problem. To have rights for opcgrp, '/etc/group' and

'/etc/logingroup' MUST have the users listed as members of opcgrp. After adding a login name into '/etc/group' the user needs to log out of VUE or

CDE and login again to get the group rights.

Cannot get temporary file name.

The tempnam(3S) call to get a temporary file name failed. This message is qualified by a system error message (errno) containing the cause of the error.

32 Chapter 2

OpC20-0061

OpC20-0062

OpC20-0063

OpC20-0064

OpC20-0065

OpC20-0066

OpC20-0067

OpC20-0068

ITO Error Messages

Error messages of public routines

Unable to get status of file <

x1

>.

The stat(2) system call to get the status of <file> failed. This message is qualified by a system error message (errno) containing the cause of the error.

Unable to unlink/erase file <

x1

>.

The unlink(2) system call to remove <file> failed. This message is qualified by a system error message (errno) containing the cause of the error.

Cannot open file <

x1

>.

The open(2) or fopen(3S) call to open <file> failed. This message is qualified by a system error message (errno) containing the cause of the error.

Cannot read contents of file <

x1

>.

The read(2) or fread(3S) call to read <file> failed. This message is qualified by a system error message (errno) containing the cause of the error.

Cannot write to file <

x1

>.

The write(2) or fwrite(3S) call to write <file> failed. This message is qualified by a system error message (errno) containing the cause of the error.

Cannot close file <

x1

>.

The close(2) or fclose(3S) call to close <file> failed. This message is qualified by a system error message (errno) containing the cause of the error.

Cannot create directory <

x1

>.

The mkdir(2) system call to create the directory <dir> failed. This message is qualified by a system error message (errno) containing the cause of the error.

Cannot change permission of <

x1

>.

Chapter 2 33

OpC20-0069

OpC20-0070

OpC20-0071

OpC20-0073

OpC20-0074

OpC20-0075

OpC20-0076

OpC20-0080

ITO Error Messages

Error messages of public routines

The chmod(2) system call to change the permissions of <file> failed. This message is qualified by a system error message (errno) containing the cause of the error.

Cannot change ownership of <

x1

>.

The chown(2) system call to change the ownership of <file> failed. This message is qualified by a system error message (errno) containing the cause of the error.

Cannot seek file <

x1

>.

The lseek(2) or fseek(3S) call to seek <file> failed. This message is qualified by a system error message (errno) containing the cause of the error.

File <

x1

> is empty.

The reporting process encountered a premature 'End Of File' while reading the file <file>.

Cannot lock file <

x1

>.

The fcntl(2) system call to lock <file> failed. This message is qualified by a system error message (errno) containing the cause of the error.

Cannot unlock file <

x1

>.

The fcntl(2) system call to unlock <file> failed. This message is qualified by a system error message (errno) containing the cause of the error.

Cannot truncate file <

x1

>.

The truncate(2) call to set the size of <file> failed. This message is qualified by a system error message (errno) containing the cause of the error.

Cannot access file <

x1

>.

The access(2) call to check the accessibility of <file> failed. This message is qualified by a system error message (errno) containing the cause of the error.

Environment variable <

x1

> not set.

34 Chapter 2

OpC20-0083

OpC20-0084

OpC20-0085

OpC20-0086

OpC20-0090

OpC20-0091

OpC20-0092

OpC20-0093

ITO Error Messages

Error messages of public routines

The requested environment variable does not exist. Solution: Set the variable accordingly.

Cannot rename file <

x1

> to <

x2

>.

The rename(2) call to change the name of <oldname> to <newname> failed. This message is qualified by a system error message (errno) containing the cause of the error.

Can't create named pipe <

x1

>.

The mkfifo(3C) call to create the named pipe <file> failed. This message is qualified by a system error message (errno) containing the cause of the error.

Select failed.

The select(2) system call failed. This message is qualified by a system error message (errno) containing the cause of the error.

Can't create anonymous pipe.

The pipe(2) system call to create an unnamed pipe failed. This message is qualified by a system error message (errno) containing the cause of the error.

Can't initialize mutex.

The reporting process could not create a mutex. This message is qualified by a message from the basic software module (DCE).

Can't lock mutex.

The reporting process could not lock a mutex. This message is qualified by a message from the basic software module (DCE).

Can't unlock mutex.

The reporting process could not unlock a mutex. This message is qualified by a message from the basic software module (DCE).

No pipe reader.

The reporting process attempted to write into a pipe and detected that the reading process is not running. Make sure that all necessary ITO processes are running.

Chapter 2 35

OpC20-0094

OpC20-0095

OpC20-0096

OpC20-0097

OpC20-0098

OpC20-0099

OpC20-0100

OpC20-0101

OpC20-0102

ITO Error Messages

Error messages of public routines

No pipe writer.

The reporting process attempted to read from a pipe and detected that the writing process is not running. Make sure that all necessary ITO processes are running.

Can't write into pipe.

The reporting process failed to write data into a pipe. This message is qualified by a system error message (errno) containing the cause of the error.

Can't read from pipe.

The reporting process failed to read data from a pipe. This message is qualified by a system error message (errno) containing the cause of the error.

Can't open pipe.

The reporting process failed to open a named pipe. This message is qualified by a system error message (errno) containing the cause of the error.

Read operation on pipe timed out.

The reporting process timed out while waiting for data to be read from a pipe.

Can't copy binding: <

x1

>.

Internal NCS/DCE error. This message is qualified by a NCS/DCE specific error text. Please report this to your HP Response Center.

Server is already initialized.

Internal error. Please report this to your HP Response Center.

Can't get protocol family: <

x1

>.

Internal NCS/DCE error. This message is qualified by a NCS/DCE specific error text. Please report this to your HP Response Center.

Can't check protocol family: <

x1

>.

Internal NCS/DCE error. This message is qualified by a NCS/DCE specific error text. Please report this to your HP Response Center.

36 Chapter 2

OpC20-0103

OpC20-0104

OpC20-0105

OpC20-0106

OpC20-0107

OpC20-0108

OpC20-0109

OpC20-0110

ITO Error Messages

Error messages of public routines

Can't inquire binding: <

x1

>.

Internal NCS/DCE error. This message is qualified by a NCS/DCE specific error text. Please report this to your HP Response Center.

Can't bind to server: <

x1

>.

Internal NCS/DCE error. This message is qualified by a NCS/DCE specific error text. Please report this to your HP Response Center.

Can't set short timeout: <

x1

>.

Internal NCS/DCE error. This message is qualified by a NCS/DCE specific error text. Please report this to your HP Response Center.

Checking server failed: <

x1

>.

Internal NCS/DCE error. This message is qualified by a NCS/DCE specific error text. Please report this to your HP Response Center.

Can't shutdown server: <

x1

>.

Internal NCS/DCE error. This message is qualified by a NCS/DCE specific error text. Please report this to your HP Response Center.

Can't lookup servers: <

x1

>.

The reporting process could not lookup a desired server process because the llbd/rpcd in the node where the server should run is not reachable.

Possible causes are:

• The network is down.

• The node where the server should run is down.

• The llbd/rpcd on this node is down.

The NCS/DCE error <ncs-msg> gives more information. The type of server and the node are contained in another part of the error message.

Can't use protocol family: <

x1

>.

Internal NCS/DCE error. This message is qualified by a NCS/DCE specific error text. Please report this to your HP Response Center.

Setting shutdown check routine failed: <

x1

>.

Chapter 2 37

OpC20-0111

OpC20-0112

OpC20-0113

OpC20-0114

OpC20-0115

OpC20-0116

OpC20-0117

OpC20-0118

OpC20-0119

ITO Error Messages

Error messages of public routines

Internal NCS/DCE error. This message is qualified by a NCS/DCE specific error text. Please report this to your HP Response Center.

Server not initialized.

Internal NCS/DCE error. This message is qualified by a NCS/DCE specific error text. Please report this to your HP Response Center.

Server already registered.

Internal error. Please report this to your HP Response Center.

Server already running.

An ITO server process should start up, but there is already an instance of this server running. The type of server is contained in another part of the error message.

Can't register manager: <

x1

>.

An ITO server process is not able to register at the RPC runtime. The

NCS/DCE error <ncs-msg> gives more information.

Can't register object ID: <

x1

>.

An ITO server process is not able to register an object ID at the RPC runtime. The NCS/DCE error <ncs-msg> gives more information.

Can't register manager at location broker: <

x1

>.

An ITO server process should start up but is unable to register itself at the llbd/rpcd on the local node. Probably the llbd/rpcd is down on that node. The NCS/DCE error <ncs-msg> gives more information.

Can't unregister manager: <

x1

>.

Internal NCS/DCE error. This message is qualified by a NCS/DCE specific error text. Please report this to your HP Response Center.

Can't unregister manager at location broker: <

x1

>.

An ITO server process should go down but is unable to unregister itself at the llbd/rpcd on the local node. Probably the llbd/rpcd is down on that node. The NCS/DCE error <ncs-msg> gives more information.

Exception caught: <

x1

>.

38 Chapter 2

OpC20-0120

OpC20-0121

OpC20-0122

OpC20-0123

OpC20-0124

OpC20-0125

OpC20-0126

OpC20-0127

ITO Error Messages

Error messages of public routines

The reporting process received a signal. A description of the signal is contained in the NCS/DCE message <ncs-msg>.

Server listening failed: <

x1

>.

Internal NCS/DCE error. This message is qualified by a NCS/DCE specific error text. Please report this to your HP Response Center.

Can't convert location to numeric name: <

x1

>.

Internal NCS/DCE error. This message is qualified by a NCS/DCE specific error text. Please report this to your HP Response Center.

Can't convert location: <

x1

>.

The reporting process is unable to convert a host name to the corresponding IP address. Probably either the host name is invalid or the name service is not running. The NCS/DCE error <ncs-msg> gives more information. The host name is contained in another part of the error message.

Invalid server type.

Internal error. Please report this to your HP Response Center.

No such server registered.

This is a qualifying message generated when an ITO process could not connect another ITO server process because the server is not running.

More information is contained in another part of the error message.

No such server running.

This is a qualifying message generated when an ITO process can not connect another ITO server process because the server is registered at the llbd/rpcd on the target node but not responding. More information is contained in another part of the error message.

Last request.

Internal error. Please report this to your HP Response Center.

Duplicated request.

Internal error. Please report this to your HP Response Center.

Chapter 2 39

OpC20-0128

OpC20-0129

OpC20-0130

OpC20-0131

OpC20-0132

OpC20-0133

OpC20-0134

OpC20-0135

OpC20-0136

OpC20-0137

ITO Error Messages

Error messages of public routines

Unexpected request.

Internal error. Please report this to your HP Response Center.

Invalid client ID.

Internal error. Please report this to your HP Response Center.

Can't convert IP address.

Internal error. Please report this to your HP Response Center.

Communication failure.

Internal error. Please report this to your HP Response Center.

Invalid limit for RPC open arrays specified: <

x1

> Valid is <

x2

> - <

x3

>. Using <

x4

> bytes.

The maximum RPC open array size specified in the managed node's nodeinfo file is out of the valid range. The process continues with the reported default value.

Invalid inter RPC delay specified: <

x1

>. Valid is <

x2

> -

<

x3

>. Using <

x4

> seconds.

The delay between two RPCs specified in the managed node's nodeinfo file is out of the valid range. The process continues with the reported default value.

Invalid socket buffer size specified: <

x1

>. Valid is <

x2

>

- <

x3

> or 0 to use the default. Using the default value.

The socket buffer size specified in the managed node's nodeinfo file is out of the valid range. The process continues with the reported default value.

Can't get value from pbconf module.

Internal error. Please report this to your HP Response Center.

Invalid alternate IP address specified: <

x1

>.

The alternate IP address specified in the managed node's nodeinfo can not be processed. Valid is the following format: a.b.c.d where a through d are numbers between 0 and 255.

Can't extract port number from location: <

x1

>.

40 Chapter 2

OpC20-0138

OpC20-0142

OpC20-0143

OpC20-0144

OpC20-0145

OpC20-0146

OpC20-0147

OpC20-0148

OpC20-0149

ITO Error Messages

Error messages of public routines

Internal error. Please report this to your HP Response Center.

Can't set port number in location: <

x1

>.

Internal error. Please report this to your HP Response Center.

Can't free string: <

x1

>.

Internal NCS/DCE error. This message is qualified by a NCS/DCE specific error text. Please report this to your HP Response Center.

Can't initialize server lookup operation at rpcd: <

x1

>.

The reporting process could not lookup a required RPC server at the rpcd due to an initialization failure. This message is qualified by a NCS/DCE specific error text. Please report this to your HP Response Center.

Can't terminate server lookup operation at rpcd: <

x1

>.

Internal NCS/DCE error. This message is qualified by a NCS/DCE specific error text. Please report this to your HP Response Center.

Can't free RPC binding: <

x1

>.

Internal NCS/DCE error. This message is qualified by a NCS/DCE specific error text. Please report this to your HP Response Center.

Can't generate UUID: <

x1

>.

Internal NCS/DCE error. This message is qualified by a NCS/DCE specific error text. Please report this to your HP Response Center.

Can't generate NIL UUID: <

x1

>.

Internal NCS/DCE error. This message is qualified by a NCS/DCE specific error text. Please report this to your HP Response Center.

Can't convert UUID to string representation: <

x1

>.

Internal NCS/DCE error. This message is qualified by a NCS/DCE specific error text. Please report this to your HP Response Center.

Can't set object ID in RPC binding: <

x1

>.

Internal NCS/DCE error. This message is qualified by a NCS/DCE specific error text. Please report this to your HP Response Center.

Chapter 2 41

OpC20-0150

OpC20-0151

OpC20-0152

OpC20-0155

OpC20-0156

OpC20-0157

OpC20-0158

OpC20-0160

ITO Error Messages

Error messages of public routines

Communication failure to message agent.

An ITO process was unable to send data to the ITO message agent. This message is qualified by another message.

Can't open message logfile <

x1

>.

The reporting process could not open the logfile to put an ITO message into it. This message is qualified by a system error message (errno) containing the cause of the error.

Can't write message logfile <

x1

>.

The reporting process could not put an ITO message into the logfile. This message is qualified by a system error message (errno) containing the cause of the error.

Can't get message keyword from message catalog. Using default values.

The reporting process could not get keywords needed to log an ITO message. Hardcoded default values are used.

Execution of request failed due to server failure.

Internal error. Please report this to your HP Response Center.

Invalid logging reason specified.

Internal error. Please report this to your HP Response Center.

Can't get keyword from message catalog for key <

x1

>.

Internal error. Please report this to your HP Response Center.

<

x2

> service not registered at Local Location Broker or

DCE RPC Daemon on system <

x1

>.

An ITO process was unable to locate an RPC server of a specific type.

Check manually if the process is running, and re-start it if necessary.

Also make sure that the selected communication type matches the installed agent software. Especially this is important when adding nodes installed by another Management Server.

42 Chapter 2

OpC20-0161

OpC20-0162

OpC20-0163

OpC20-0164

OpC20-0165

OpC20-0166

ITO Error Messages

Error messages of public routines

<

x2

> service registered at Local Location Broker or DCE

RPC Daemon on system <

x1

>, but is not responding.

An ITO process has the location of a specific RPC server, but there is no process running at that location. Check manually if the process is running, and re-start it if necessary.

RPC service '<

x2

>' on system '<

x1

>' not responding.

The reporting process failed to communicate with the server process

<service> running on the node <node>. Either the server process terminated or it is not reachable due to network communication failures.

This message will be qualified by another message giving more information.

RPC service '<

x2

>' on system '<

x1

>' not reachable due to a failed lookup operation.

The reporting process failed to connect the server process <service> running on the node <node>. This message will be qualified by another message giving more information.

RPC service '<

x2

>' on system '<

x1

>' returns an error:

<

x3

>.

The reporting process failed to execute a RPC at the server process

<service> running on the node <node>. The server refused the request or failed to execute it. See the local error log file on the server system

<node>.

The UDP/IP protocol sequence is not supported on the local host. RPC server can't register at llbd/rpcd.

The system where the reporting process is running on doesn't support

UDP as networking protocol. This will prevent the ITO processes from using DCE/UDP as communication type and also from communicating with NCS processes.

The communication type <

x1

> is currently not supported to send control agent requests.

Chapter 2 43

OpC20-0167

OpC20-0168

OpC20-0172

OpC20-0201

OpC20-0202

OpC20-0203

ITO Error Messages

Error messages of public routines

The reporting process was requested to send a request to a control agent running on a managed node but the configured communication of this node cannot be used to inform the control agent. Currently only NCS or

DCE communication types are supported.

All ports in range '<

x1

>' are in use. Performing dynamic allocation for ports out of specified range.

The RPC server could not allocate a socket from the specified range.

There are either processes running which use ports from this range, or the range is too small for all ITO processes. The RPC server is now started with a port outside the specified range. Communication errors could occur if this port is blocked by a firewall.

RPC service '<

x2

>' on system '<

x1

>' returns an authentication error: <

x3

>.

The reporting process failed to execute a RPC at the server process

<service> running on the node <node> due to an authentication failure.

Usually this happens if the RPC server runs unauthenticated but the client requests authentication. See the local error log file on the server system <node>.

The file <

x2

>/<

x3

> targeted for platform <

x1

> has invalid file extension <

x4

>.

The distribution manager found an invalid file extension in the

"../hp/s900/mpe-ix" path. The only extension allowed for a file in this area is ".Z".

Can't open configuration file '<

x1

>' for writing.

The reporting process could not write the configuration file because it was unable to access the file.

Can't open configuration file '<

x1

>' for reading.

The reporting process could not read the configuration file because it was unable to access the file.

Write error writing msg source '<

x1

>'.

The reporting process could not write the configuration file because it encountered an error while writing.

44 Chapter 2

OpC20-0204

OpC20-0205

OpC20-0206

OpC20-0209

OpC20-0210

OpC20-0211

OpC20-0212

OpC20-0213

ITO Error Messages

Error messages of public routines

Syntax error in dot string '<

x1

>'.

The dot string is not in the valid SNMP object ID format.

Syntax error in interval string '<

x1

>'.

The time interval is not in the correct format. Examples for correct intervals: 1h40m10s, 35m10s, 1h, ...

Configuration file '<

x1

>' contains syntax errors.

The reporting process could not read the configuration file because the structure of the file is incorrect.

Template <

x1

> mixes old and new monitor template syntax.

The monitor template contains monitor conditions but defines also a condition in the template body itself. Edit the template and convert the condition defined in the body to an additional monitor message condition.

line <

x1

> "<

x2

>": message source or 'DESCRIPTION' expected.

Reading a template, ITO found a syntax error in the specified line. See the 'Application Integration Guide' for a description of the ITO template syntax.

line <

x1

> "<

x2

>": Logfile default / option or

'MSGCONDITION' expected.

Reading a template, ITO found a syntax error in the specified line. See the 'Application Integration Guide' for a description of the ITO template syntax.

line <

x1

> "<

x2

>": unknown character set or chset conflicts with the internal node chset.

Reading a template, ITO found a syntax error in the specified line. See the 'Application Integration Guide' for a description of the ITO template syntax.

line <

x1

> "<

x2

>": SNMP default / option or

'MSGCONDITIONS' expected.

Chapter 2 45

OpC20-0214

OpC20-0215

OpC20-0216

OpC20-0217

OpC20-0218

OpC20-0219

OpC20-0220

ITO Error Messages

Error messages of public routines

Reading a template, ITO found a syntax error in the specified line. See the 'Application Integration Guide' for a description of the ITO template syntax.

line <

x1

> "<

x2

>": Console default / option or

'MSGCONDITIONS' expected.

Reading a template, ITO found a syntax error in the specified line. See the 'Application Integration Guide' for a description of the ITO template syntax.

line <

x1

> "<

x2

>": opcmsg default / option or

'MSGCONDITIONS' expected.

Reading a template, ITO found a syntax error in the specified line. See the 'Application Integration Guide' for a description of the ITO template syntax.

line <

x1

> "<

x2

>": Monitor option expected.

Reading a template, ITO found a syntax error in the specified line. See the 'Application Integration Guide' for a description of the ITO template syntax.

line <

x1

> "<

x2

>": MsgCondition or 'SUPPRESSCONDITIONS' expected.

Reading a template, ITO found a syntax error in the specified line. See the 'Application Integration Guide' for a description of the ITO template syntax.

line <

x1

> "<

x2

>": SuppressCondition expected.

Reading a template, ITO found a syntax error in the specified line. See the 'Application Integration Guide' for a description of the ITO template syntax.

line <

x1

> "<

x2

>": Condition expected.

Reading a template, ITO found a syntax error in the specified line. See the 'Application Integration Guide' for a description of the ITO template syntax.

line <

x1

> "<

x2

>": SNMP MsgCondition or

'SUPPRESSCONDITIONS' expected.

46 Chapter 2

OpC20-0221

OpC20-0222

OpC20-0223

OpC20-0224

OpC20-0225

OpC20-0226

OpC20-0227

ITO Error Messages

Error messages of public routines

Reading a template, ITO found a syntax error in the specified line. See the 'Application Integration Guide' for a description of the ITO template syntax.

line <

x1

> "<

x2

>": SNMP SuppressCondition expected

Reading a template, ITO found a syntax error in the specified line. See the 'Application Integration Guide' for a description of the ITO template syntax.

line <

x1

> "<

x2

>": SNMP Condition expected.

Reading a template, ITO found a syntax error in the specified line. See the 'Application Integration Guide' for a description of the ITO template syntax.

line <

x1

> "<

x2

>": Set expression or 'SUPPRESSCONDITIONS' expected.

Reading a template, ITO found a syntax error in the specified line. See the 'Application Integration Guide' for a description of the ITO template syntax.

line <

x1

> "<

x2

>": Severity expected.

Reading a template, ITO found a syntax error in the specified line. See the 'Application Integration Guide' for a description of the ITO template syntax.

line <

x1

> "<

x2

>": Regroup condition expected.

Reading a template, ITO found a syntax error in the specified line. See the 'Application Integration Guide' for a description of the ITO template syntax.

line <

x1

> "<

x2

>": MSGGRP "<

MsgGroup

>" expected.

Reading a template, ITO found a syntax error in the specified line. See the 'Application Integration Guide' for a description of the ITO template syntax.

line <

x1

> "<

x2

>": Pattern string too long.

Reading a template, ITO found a pattern which is longer than allowed.

Shorten the specified pattern.

Chapter 2 47

OpC20-0228

OpC20-0229

OpC20-0230

OpC20-0231

OpC20-0234

OpC20-0235

OpC20-0236

OpC20-0240

OpC20-0241

ITO Error Messages

Error messages of public routines

Monitor name "<

x1

>" contains invalid characters

ITO allows only alphanumeric characters, '-' and '_' for monitor names.

Remove the invalid characters from the string.

Message type "<

x1

>" contains invalid characters or is too long

ITO allows at most 36 alphanumeric characters, '-' and '_' for message types. Remove the invalid characters from the string.

Can't open rgrp file "<

x1

>" for reading.

The reporting process could not read the regroup conditions file because it was unable to access the file.

Rgrp file "<

x1

>" contains syntax errors.

The reporting process could not read the regroup conditions file because the structure of the file is incorrect.

Template contains obsolete / invalid syntax version

The syntax of the template (specified with SYNTAX_VERSION

<number>) is either incompatible with the currently required ITO syntax or invalid.

Syntax error in pattern definition "<

x1

>".

The pattern contains syntax errors. See the "Administrator's Online

Help" or "Concepts Guide" for a description of the ITO pattern matching syntax.

Too many separators "<

x1

>"; using default separators instead.

ITO allows only a limited number of separator characters. Shorten the specified separator string.

Dot string too long "<

x1

>".

Internal error. Please report this to your HP Response Center.

Unknown trap variable type: <

x1

>.

Internal error. Please report this to your HP Response Center.

48 Chapter 2

OpC20-0243

OpC20-0260

OpC20-0270

OpC20-0271

OpC20-0272

OpC20-0273

OpC20-0274

OpC20-0275

ITO Error Messages

Error messages of public routines

Replaced string too long: "<

x1

>".

Internal error. Please report this to your HP Response Center.

String <

x1

> contains invalid multibyte characters.

The string contains invalid multibyte characters; check the string and remove the invalid characters.

Can't convert string from "<

x1

>" to "<

x2

>".

The requested character conversion is not supported. Check the character set defined for the managed node and the character set defined for the logfile.

Can't get iconv table size to convert string from "<

x1

>" to "<

x2

>".

You may not have enough system resources, for example, too many files may be open, or the requested character conversion may not be supported on your system. Check your system parameters for the maximum number of open files. Check the character set defined for the managed node, and the character set defined for the logfile. Check whether your operating system supports both character sets, by using the iconv command.

Can't initialize iconv to convert string from "<

x1

>" to

"<

x2

>".

The requested character conversion is not supported on your system.

Check the character set defined for the managed node and the character set defined for the logfile. Check that your operating system supports both character sets, by using the iconv command.

Output buffer is too small for iconv conversion.

Internal ITO error.

Bad input character converting string from "<

x1

>" to

"<

x2

>".

An invalid character was encountered while converting. Check the related text strings for invalid characters.

Can't close iconv table.

Chapter 2 49

OpC20-0280

OpC20-0281

OpC20-0282

OpC20-0283

OpC20-0284

OpC20-0285

OpC20-0286

OpC20-0411

OpC20-0415

ITO Error Messages

Error messages of public routines

Internal ITO error.

Can't set locale to "<

x1

>".

The given locale is not supported with ITO. Check and adapt the environment variable, "LANG".

Invalid node character set.

The node character set is not compatible with the server character set.

Ask your ITO administrator to check and modify the node configuration.

The language LANG="<

x1

>" is invalid.

Change your LANG setting. For more information, see the ITO documentation.

The codeset "<

x1

>" is invalid.

Make sure the given codeset is supported for this platform. For more information, see the ITO documentation.

The codeset "<

x1

>" is incompatible to the codeset "<

x2

>".

The two given codesets are incompatible. This is a generic error which can be caused by several conditions. Please report this to your HP

Response Center.

Cannot get the database codeset.

The database (i.e. the server internal) codeset can't be retrieved from the database. Please report this to your HP Response Center.

Cannot get codesets from nodeinfo file.

The agents nodeinfo doesn't contain valid codeset information for the node and for the server. If the nodeinfo doesn't contain the two parameters 'OPC_MGMTSV_CHARSET' and 'OPC_NODE_CHARSET', please report this to your HP Response Center.

fork(2) failed; no more memory

A fork of a process failed due to lack of memory. Retry the operation.

semget(2) failed; cannot create semaphore

50 Chapter 2

OpC20-0431

OpC20-0432

OpC20-0650

OpC20-0651

OpC20-0652

OpC20-0653

OpC20-0654

OpC20-0655

ITO Error Messages

Error messages of public routines

This problem is may cause by to small kernel parameters for semaphores.

The process '<

x1

>' could not be started.

The process <proc> could not be started. This message is qualified by another message giving more information.

The process '<

x1

>' terminated with a non-zero exit code.

The process <proc> terminated with a non-zero exit code. This is considered as failure.

Can't retrieve local IP address.

Internal error. Please report this to your HP Response Center.

The gethostbyname(3N) call failed.

The reporting process failed to resolve a host name to an IP address. This message is qualified by a system error message (errno) containing the cause of the error.

Can't open SNMP session: <

x1

>.

The reporting process failed to open an SNMP session. This message is qualified by an error message originating from the SNMP subsystem containing the cause of the error.

Can't close SNMP session: <

x1

>.

The reporting process failed to terminate an SNMP session. This message is qualified by an error message originating from the SNMP subsystem containing the cause of the error.

Can't create SNMP pdu: <

x1

>.

The reporting process failed to create an SNMP PDU. This message is qualified by an error message originating from the SNMP subsystem containing the cause of the error.

Can't bind SNMP variable to pdu: <

x1

>.

The reporting process failed to bind an SNMP variable to a PDU. This message is qualified by an error message originating from the SNMP subsystem containing the cause of the error.

Chapter 2 51

OpC20-0656

OpC20-0657

OpC20-0658

OpC20-0659

OpC20-0660

OpC20-0661

OpC20-0662

OpC20-0663

OpC20-0664

ITO Error Messages

Error messages of public routines

Can't send SNMP pdu: <

x1

>.

The reporting process failed to send an SNMP PDU. This message is qualified by an error message originating from the SNMP subsystem containing the cause of the error.

Can't get SNMP variable <

x1

>.

The reporting process failed to extract an SNMP variable from a received

PDU because the PDU contained fewer variables than the requested number.

Unsupported request type to be sent via SNMP.

Internal error. Please report this to your HP Response Center.

Receiving SNMP response failed. Status <

x1

>.

The reporting process failed to receive a required SNMP response PDU.

This message is qualified by an error message originating from the

SNMP subsystem containing the cause of the error. This is a MPE/iX specific error.

Maximum number of variables reached. Can't bind variable.

Internal error. Please report this to your HP Response Center.

Object ID too long.

A specified object ID exceeds the maximum possible length. This is an

MPE/iX specific error.

Unsupported variable type.

Internal error. Please report this to your HP Response Center.

Can't get response file descriptor.

The reporting process failed to get the file descriptor to receive SNMP responses from. This is a SNI specific error.

Can't clear SNMP variable list.

The reporting process failed to clear the SNMP variable list created for the last processed PDU. This is a SNI specific error.

52 Chapter 2

OpC20-0665

OpC20-0666

OpC20-0667

OpC20-0668

OpC20-0669

OpC20-0670

OpC20-0671

OpC20-0672

OpC20-0673

OpC20-0674

ITO Error Messages

Error messages of public routines

Can't add SNMP variable to list.

The reporting process failed to add a SNM variable to the variable list.

This is a SNI specific error.

Unexpected SNMP response received: id = <

x1

>.

The reporting process received a SNMP response not matching the sent request. This is a SNI specific error.

Can't get next SNMP variable from response.

The reporting process failed to get the a variable from a received SNMP response. This is a SNI specific error.

Unsupported MIB variable type.

The reporting process received a SNMP variable of an unsupported type.

This is a SNI specific error.

Select call to retrieve PDU failed.

The reporting process failed to call select(2) while waiting for a SNMP response. This is a SNI specific error.

All retries for PDU GET exhausted.

The reporting process timed out while waiting for a SNMP response after several retries. This is a SNI specific error.

PDU receive call failed: <

x1

>

The reporting process failed to receive a SNMP response PDU. This is a

SNI specific error.

Error at MIB variable in response PDU: <

x1

>

The reporting process failed to receive a corrupted SNMP PDU. This is a

SNI specific error.

SNMP request timed out.

The ITO Monitor Agent received no reply to an SNMP GET request which was sent because a MIB monitor is configured. Most likely the

SNMP agent is down.

SNMP request too big.

Chapter 2 53

OpC20-0675

OpC20-0676

OpC20-0677

OpC20-0678

OpC20-0700

OpC20-0701

OpC20-0702

OpC20-0703

ITO Error Messages

Error messages of public routines

If the cause of this error is unclear to you and you need help or you have the impression that this is a problem within ITO then please report this to your HP Response Center.

Invalid SNMP Name.

The ITO Monitor Agent is unable to monitor a configured MIB variable.

The variable is not known by the SNMP agent. Possibly not all MIBs are loaded or an invalid MIB variable was defined in the ITO monitor.

Invalid SNMP Value.

The SNMP agent could not return a legal value for the configured MIB variable. The SNMP agent is probably not configured correctly.

SNMP Vlaue is defined as READ ONLY.

If the cause of this error is unclear to you and you need help or you have the impression that this is a problem within ITO then please report this to your HP Response Center.

General SNMP error.

The SNMP agent failed to process the SNMP GET request. Maybe it is not configured correctly.

Can't get name of trace file.

Internal error. Please report this to your HP Response Center.

Can't open trace file '<

x1

>'.

The reporting process is unable to open the specified file for writing trace information. This message is qualified by a system error message (errno) containing the cause of the error.

Can't log trace message. Invalid format or parameter number.

Internal error. Please report this to your HP Response Center.

Can't write trace file.

The reporting process is unable to write trace information to the current output file. This message is qualified by a system error message (errno) containing the cause of the error.

54 Chapter 2

OpC20-0704

OpC20-0705

OpC20-0706

OpC20-0750

OpC20-0751

OpC20-0752

OpC20-0800

OpC20-0801

OpC20-0960

ITO Error Messages

Error messages of public routines

Initializing tracing failed.

Internal error. Please report this to your HP Response Center.

Tracing is enabled on the management server.

Set OPC_TRACE FALSE in the opcsvinfo file to disable tracing.

Tracing is enabled on the managed node.

Set OPC_TRACE FALSE in the opcinfo/nodeinfo file to disable tracing.

Empty logfile name.

Internal error. Please report this to your HP Response Center.

Can't open logfile '<

x1

>'.

The reporting process is unable to open the specified file as ITO logfile.

This message is qualified by a system error message (errno) containing the cause of the error.

Can't check size of logfile '<

x1

>' using lseek.

Internal error. Please report this to your HP Response Center.

Internal error: Illegal operation code <

x1

>.

Internal error. Please report this to your HP Response Center.

IP address '<

x2

>' configured for node '<

x1

>' could not be found in the name service database.

The specified nodename - IP address is configured in ITO but could not be found in this combination in the name service database. The used name service database is either the /etc/hosts file, or the DNS or NIS database, depending on the current system configuration. This may be caused by the modification of the name or the IP address of the reported host. Solution: Fix the ITO configuration for this host to match the name service representation.

Cannot initialize OV License Manager.

The OVLicenseMgr process is probably not running. Please (re-) start it.

For more information see the ITO Installation Guide.

Chapter 2 55

OpC20-0961

OpC20-0962

OpC20-0964

OpC20-0966

OpC20-0967

OpC20-0968

ITO Error Messages

Error messages of public routines

OV License Manager returned

LS_LICENSE_SYS_NOT_AVAILABLE.

There has been a problem while doing the license check. This might be due to networking problems or license server problems. Please make sure the license server is running and accessible. Otherwise you may not be able to use this product. For more information see the ITO

Installation Guide.

OV License Manager returned LS_NO_SERVER_CONNECTION.

The connection to the netlsd daemon does not work. Please check if your license server is running and you have access to it. For more information see the ITO Installation Guide.

OV License Manager returned LS_NO_LICENSES_AVAILABLE.

There are no/not enough ITO licenses available on your license server. If you have installed license passwords on the license server, this may due to problems accessing the license server.

If you have not installed a license, please contact your HP sales representative or channel partner to purchase a license for this product.

OV License Manager returned LS_SOFT_NO_LICENSE.

There has been a problem while doing the license check. This might be due to networking problems or license server problems. Please make sure the license server is running and accessible. Otherwise you may not be able to use this product. For more information see the ITO

Installation Guide.

OV License Manager returned LS_HARD_NO_LICENSE.

There has been a problem while doing the license check. This might be due to networking problems or license server problems. Please make sure the license server is running and accessible. Otherwise you may not be able to use this product. For more information see the ITO

Installation Guide.

OV License Manager returned LS_UNKNOWN_STATUS.

56 Chapter 2

OpC20-0969

OpC20-0970

OpC20-0971

OpC20-0972

ITO Error Messages

Error messages of public routines

A problem has occurred while performing the license check. This may be due to networking or license server problems. Please make sure the license server is running and accessible. Otherwise you may not be able to use this product. For more information see the appropriate ITO

Installation Guide.

OV License Manager returned LS_BAD_PARAMETER.

A problem has occurred while performing the license check. This may be due to networking or license server problems. Please make sure the license server is running and accessible. Otherwise you may not be able to use this product. For more information see the appropriate ITO

Installation Guide.

There are no licenses available from the license server for this product. If you have installed license passwords on the license server, this may be due to problems accessing the license server.

This is the last time you will be allowed to run this product without installing a license or correcting access to the license server.

There are no licenses available from the license server for this product. If you have installed license passwords on the license server, this may be due to problems accessing the license server.

This is the last time you will be allowed to run this product without installing a license or correcting access to the license server.

** Cannot get an ITO server license.

There are no/not enough ITO Server licenses available on your license server. If you have installed license passwords on the license server, this may be due to problems accessing the license server.

If you have not installed license passwords, please contact your HP sales representative or channel partner to purchase a license for this product.

** ITO Temporary Server License: > expires TODAY

Chapter 2 57

OpC20-0973

OpC20-0974

OpC20-0975

OpC20-0976

OpC20-0977

ITO Error Messages

Error messages of public routines

You are currently running with a temporary license. You will not be able to run this product after the specified date. Please contact your HP sales representative or channel partner to purchase a license for this product.

If you have installed license passwords on the license server, this may be due to problems accessing the license server.

** ITO Temporary Server License: > expires in <

x1

> days

You are currently running with a temporary license. You will not be able to run this product after the specified date. Please contact your HP sales representative or channel partner to purchase a license for this product.

If you have installed license passwords on the license server, this may be due to problems accessing the license server.

** Cannot get '<

x1

>' ITO managed node licenses

There are no/not enough ITO Managed Nodes licenses available on your license server. If you have installed license passwords on the license server, this may be due to problems accessing the license server.

If you have not installed license passwords, please contact your HP sales representative or channel partner to purchase a license for this product.

** ITO Temporary Managed Node License: > expires TODAY

You are currently running with a temporary license. You will not be able to run this product after the specified date. Please contact your HP sales representative or channel partner to purchase a license for this product.

If you have installed license passwords on the license server, this may be due to problems accessing the license server.

** ITO Temporary Managed Node License: > expires in <

x1

> days

You are currently running with a temporary license. You will not be able to run this product after the specified date. Please contact your HP sales representative or channel partner to purchase a license for this product.

If you have installed license passwords on the license server, this may be due to problems accessing the license server.

*****************************************************

** HP IT/Operations cannot get an ITO server license.

** If you have installed license passwords on the

58 Chapter 2

OpC20-0978

OpC20-0979

OpC20-0980

ITO Error Messages

Error messages of public routines

**license server, this may be due to problems

**accessing the license server.

*****************************************************

There are no/not enough ITO Server licenses available on your license server. If you have installed license passwords on the license server, this may be due to problems accessing the license server.

If you have not installed license passwords, please contact your HP sales representative or channel partner to purchase a license for this product.

**************************************************

** HP IT/Operations Temporary Server License:

** > expires TODAY

**************************************************

You are currently running with a temporary license. You will not be able to run this product after the specified date. Please contact your HP sales representative or channel partner to purchase a license for this product.

If you have installed license passwords on the license server, this may be due to problems accessing the license server.

**************************************************

** HP IT/Operations Temporary Server License:

** > expires in <

x1

> days

**************************************************

You are currently running with a temporary license. You will not be able to run this product after the specified date. Please contact your HP sales representative or channel partner to purchase a license for this product.

If you have installed license passwords on the license server, this may be due to problems accessing the license server.

Cannot get '<

x1

>' additional ITO managed node license(s). If you have installed license passwords on the license server, this may be due to problems accessing the license server.

There are no/not enough ITO Managed Nodes licenses available on your license server. If you have installed license passwords on the license server, this may be due to problems accessing the license server.

If you have not installed license passwords, please contact your HP sales representative or channel partner to purchase a license for this product.

Chapter 2 59

OpC20-1011

OpC20-1051

OpC20-1052

OpC20-1053

OpC20-1054

OpC20-1055

OpC20-1056

OpC20-1057

OpC20-1081

ITO Error Messages

Error messages of public routines

Can't close socket.

The reporting process could not close a socket. This message is qualified by an system error text.

Invalid mutex.

Internal error. Please report this to your HP Response Center.

Can't initialize mutex '<

x1

>'.

The reporting process could not initialize the mutex <mutex name>. This message is qualified by an error text from the mutex subsystem (DCE).

Can't destroy mutex '<

x1

>'.

The reporting process could not remove the mutex<mutex name>. This message is qualified by an error text from the mutex subsystem (DCE).

Can't lock mutex '<

x1

>'.

The reporting process could not lock the mutex <mutex name>. This message is qualified by an error text from the mutex subsystem (DCE).

Can't unlock mutex '<

x1

>'.

The reporting process could not unlock the mutex <mutex name>. This message is qualified by an error text from the mutex subsystem (DCE).

Can't create attributes of mutex '<

x1

>'.

The reporting process could not create a mutex attribute requested for the mutex <mutex name>. This message is qualified by an error text from the mutex subsystem (DCE).

Can't set type of mutex '<

x1

>'.

The reporting process could not change the mutex type of <mutex name>.

This message is qualified by an error text from the mutex subsystem

(DCE).

Can't create signal handler thread.

The reporting process could not create a special thread responsible for signal handling. This message is qualified by an error text from the thread subsystem (DCE).

60 Chapter 2

OpC20-1082

OpC20-1083

OpC20-1100

OpC20-1102

OpC20-1103

OpC20-2001

ITO Error Messages

Error messages of public routines

Can't switch cancel request handling.

The reporting process could not set the current policy for handling thread cancel requests. This message is qualified by an error text from the thread subsystem (DCE).

Invalid signal <

x1

> - can't register handler.

The reporting process could not establish a signal handler for signal

<sig>. This signal is not supported to be caught asynchronously.

Could not open socket

A socket, needed for communication over the network, could not be opened. Please make sure that this machine and all its network connections are functioning properly. Maybe no more memory or file handles are available or the network connection has a problem. If you are quite sure that this problem has nothing to do with your machine's networking setup or operating system, then please report this to your HP

Response Center.

Could not send IP package to host with address <

x1

>.

Please check your local network interface.

It seems that this system is having major problems trying to communicate with other systems over the network. Please make sure that the network connection is working well. If this error message keeps coming even after you have carefully checked that the network connection is working well, then please report this to your HP Response

Center.

Could not send IP package to host with address <

x1

>.

No appropriate route statement.

The ITO software is having a problem contacting a system over the network. Please check error messages before or after this one to see which node could not be reached. It seems that routing on your network is not configured properly so that this no route could be found to this node (or a router or switch is down). If you cannot easily find out which node is affected then please report this to your HP Response Center.

Invalid statement found in distribution list file

'<

x1

>': '<

x2

>'.

Chapter 2 61

OpC20-2002

OpC20-2021

OpC20-2022

OpC20-2023

OpC20-2041

OpC20-2042

OpC20-2043

OpC20-2044

OpC20-2045

ITO Error Messages

Error messages of public routines

The reporting process could not read the distribution list file <fname> because the line <line> is in an incorrect format.

Can't write distribution list file. Name and path must not be empty.

Internal error. Please report this to your HP Response Center.

Registered processing function failed for directory element '<

x1

>'.

An operation to be executed on the directory element <element> failed.

This message is qualified by another message giving more information.

Invalid MPE directory format: '<

x1

>'. Must be group.account.

Internal error. Please report this to your HP Response Center.

Can't get list of files for MPE directory '<

x1

>'.

The reporting process could not read the MPE group <group>. This message is qualified by another message giving more information.

Cannot open MSI control pipe '<

x1

>'.

An OS routine reported an error; check that you have appropriate permissions to create / access the named file.

Cannot open MSI control queue '<

x1

>'.

An OS routine reported an error; check that you have appropriate permissions to create / access the named file.

mkfifo failed for '<

x1

>'.

An OS routine reported an error; check that you have appropriate permissions to create / access the named file.

Cannot open MSI read pipe '<

x1

>'.

An OS routine reported an error; check that you have appropriate permissions to access the named file.

Cannot open MSI read queue '<

x1

>'.

62 Chapter 2

OpC20-2046

OpC20-2047

OpC20-2048

OpC20-2151

OpC20-2152

OpC20-2153

OpC20-2154

OpC20-2155

OpC20-2181

ITO Error Messages

Error messages of public routines

An OS routine reported an error; check that you have appropriate permissions to access the named file.

Cannot open MSI write pipe '<

x1

>'.

An OS routine reported an error; check that you have appropriate permissions to access the named file.

Cannot open MSI write queue '<

x1

>'.

An OS routine reported an error; check that you have appropriate permissions to access the named file.

MSI instance '<

x1

>' already exists.

An MSI instance with this name already exists - the application that received this message must choose a different name.

Can't get file system status for path '<

x1

>'.

The statfs(2) system call failed to get file system information about the file system where <path> resides in. This message is qualified by a system error message (errno) containing the cause of the error.

Unknown file system type for path '<

x1

>'.

The type of the file system <path> resides in is not known. Verify the

/etc/mnttab file for the file system type.

Can't split NFS mount source into server host and path:

'<

x1

>'.

The /etc/mnttab entry <entry> could not be split into the server and the path portion of the NFS mount source.

Can't open mount table '<

x1

>'.

The reporting process could not open the mount table file <mnttab> to inquire detailed information about a file system.

Internal error: File system '<

x1

>' not found.

Internal error. Please report this to your HP Response Center.

Can't write control manager pipe.

Chapter 2 63

OpC20-2182

OpC20-2183

OpC20-2184

OpC20-2185

OpC20-2186

OpC20-2187

OpC20-2188

ITO Error Messages

Error messages of public routines

The reporting process could not pass a request to the ITO control manager due to a failure writing the control manager pipe. This message is qualified by another message giving more information.

Can't write request into control manager queue.

The reporting process could not pass a request to the ITO control manager due to a failure writing the control manager queue. This message is qualified by another message giving more information.

Can't read request from control manager queue.

The reporting process could not read a request from the ITO control manager queue. This message is qualified by another message giving more information.

Can't get name of control manager queue/pipe from config subsystem.

Internal error. Please report this to your HP Response Center.

Can't open control manager queue '<

x1

>'.

The reporting process could not open the ITO control manager queue

<qname>. This message is qualified by another message giving more information.

Can't create control manager pipe '<

x1

>'.

The reporting process could not create the ITO control manager pipe

<pname>. This message is qualified by a system error message (errno) containing the cause of the error.

Can't open control manager pipe '<

x1

>'.

The reporting process could not open the ITO control manager pipe

<pname>. This message is qualified by a system error message (errno) containing the cause of the error.

Can't close control manager pipe.

The reporting process could not close the ITO control manager pipe. This message is qualified by a system error message (errno) containing the cause of the error.

64 Chapter 2

OpC20-2189

OpC20-2258

OpC20-2290

OpC20-2291

OpC20-2310

OpC20-2400

ITO Error Messages

Error messages of public routines

No reading process at the control manager pipe - control manager down.

The ITO control manager is expected to run as a reading process at the control manager queue but it is not running. Restart the ITO server processes.

ITO license-process (distribution manager) is not running on the ITO license server.

The distribution manager is the responsible process on a management server to answer license requests from managed nodes. If the ITO server processes on the management server, which holds the license for a node, don't run, the license check fails. You can get the appropriate server by using the command: opcswlicsrv -get_license <managed-node>

Cannot get the ITO management server name from the opcinfo file.

It is not possible to get the ITO management server name from the opcinfo file. Check whether the opcinfo file contains the correct entry for the ITO management server. The opcinfo file has to contain a line

OPC_MGMT_SERVER <nodename of ITO management server>

If this line is not in the opcinfo file you should deinstall the ITO agent software and install it again from the ITO management server.

Cannot get the ITO management server name from the primary mgr data file.

An error occurred during the read of the primary mgr file. This error message is qualified by another message.

Problem occurred during encryption process.

Data encryption was not successful. Please check for a previous message showing more details. If this error is causing you problems then please report this to your HP Response Center.

Can't escalate ITO message <

x1

>.

The ITO message is on the target ITO manager <

x2

> already available.

The ITO message to escalate is already in the database of the target ITO manager. It is not possible to escalate the message a second time.

Chapter 2 65

OpC20-2401

OpC20-2402

OpC20-2403

OpC20-2404

OpC20-2405

OpC20-2406

ITO Error Messages

Error messages of public routines

Can't escalate ITO message <

x1

>.

Can't add the ITO message to the database on the target

ITO manager <

x2

>.

An error occurred during the add of the ITO message to the database.

This error message is qualified by another message giving more information.

Can't escalate ITO message <

x1

>.

Can't add the annotations of the ITO message to the database on the target ITO manager <

x2

>.

An error occurred during the add of annotations to the database. This error message is qualified by another message giving more information.

Can't escalate ITO message <

x1

>.

The source node <

x2

> is not configured as ITO managed node on the target ITO manager <

x3

>.

The source node of the ITO message is not configured as ITO managed on the ITO target system. The escalation of the message is not possible in this case. Solution: Configure the source node of the ITO message on the target ITO manager.

Can't escalate ITO message <

x1

>.

Can't check whether the source node <

x2

> is an ITO managed node on the target ITO manager <

x3

>.

An error occurred during the check of the ITO message. This error message is qualified by another message giving more information.

Can't escalate ITO message <

x1

>.

Can't add the escalation information to the database on the target ITO manager <

x2

>.

An error occurred during the add of the escalation information to the database. This error message is qualified by another message giving more information.

Error during escalation of ITO message <

x1

>.

Can't inform ITO operators about escalated message on the target ITO manager <

x2

>.

66 Chapter 2

OpC20-2413

OpC20-2500

OpC20-2501

OpC20-2502

OpC20-2503

OpC20-2504

ITO Error Messages

Error messages of public routines

It was not possible to inform operators about the escalated ITO message

This is not really a problem because the responsible operator will get the message the next time he/she logs in.

Can't execute the action.

It is not possible to connect to the ITO manager <

x1

>.

ITO failed to escalate a message to another Management Server due to communication problems. Make sure that the target manager is set up as managed node with the correct communication attributes on the local server and the ITO server processes are running on the remote node.

Empty input data.

The reporting process was requested to transfer some data to another management server but the specified data array is empty. This error message is qualified by another message giving more information.

The input file '<

x1

>' was modified during transfer to another management server system.

The reporting process was requested to transfer the file <file> to another management server and detected that the file became smaller during data transfer. Make sure that no other process modifies the file until the operation has completed.

Can't connect to communication manager on system '<

x1

>'.

The reporting process is not able to connect to the communication manager running on <node>. This error message is qualified by another message giving more information.

Can't send data through TCP socket to communication manager.

The reporting process is not able to send data to another management server via TCP socket. This error message is qualified by another message giving more information.

Invalid status returned from communication manager:

'<

x1

>'.

Internal error. Please report this to your HP Response Center.

Chapter 2 67

OpC20-2505

OpC20-2506

OpC20-2507

OpC20-2520

OpC20-2521

OpC20-2522

OpC20-2523

OpC20-2524

ITO Error Messages

Error messages of public routines

Invalid communication ID returned from communication manager: '<

x1

>'.

Internal error. Please report this to your HP Response Center.

Unknown error returned by ITO communication manager on system '<

x1

>'.

The management server system <node> failed receiving or processing data sent by the reporting process. Verify the ITO error logfiles on the target system.

Server error returned by ITO distribution manager on system '<

x1

>'.

The management server system <node> failed receiving or processing data sent by the reporting process. This error message is qualified by another message giving more information.

No communication manager running.

There is no ITO communication manager running on the target management server system and it could not be started. Verify the ITO error logfiles on the target system.

Can't initialize connection to communication manager.

The initialization of this connection failed on the target management server system. Verify the ITO error logfiles on the target system.

Can't send data to communication manager.

The ITO distribution manager on the target management server system could not initiate the data transfer to the communication manager.

Verify the ITO error logfiles on the target system.

Can't send action request to communication manager.

The ITO distribution manager on the target management server system could not initiate a requested action to the communication manager.

Verify the ITO error logfiles on the target system.

Can't close connection to communication manager.

68 Chapter 2

OpC20-2621

OpC20-2622

OpC20-2623

OpC20-2624

OpC20-2625

OpC20-2626

OpC20-2627

ITO Error Messages

Error messages of public routines

The ITO distribution manager on the target management server system could not close the connection to the communication manager. Verify the

ITO error logfiles on the target system.

Can't perform DCE login as '<

x1

>'. This principal does not exist: <

x2

>.

The reporting process could not log into DCE with the principal(name)

<princ>. The principal is not contained in the DCE registry. To create the required ITO configuration use the opc_sec_register.sh script.

Can't perform DCE login as '<

x1

>'. Can't reach security service: <

x2

>.

The reporting process failed to contact the DCE security service during logon. Use the DCE utility 'dce_config' to verify and start the DCE server processes.

Can't perform DCE login as '<

x1

>'. Generic error: <

x2

>.

The reporting process failed to log into DCE. A DCE error occurred:

<dce_err>.

Can't validate DCE login as '<

x1

>': <

x2

>.

The reporting process failed to validate it's login context. More details about the reason are in the DCE error text <dce_err>.

Can't certify DCE login. The consulted security service is unknown: <

x1

>.

The security service which was consulted during login seems not to be the DCE security service. See <dce_err> for more details.

Can't activate DCE login context as '<

x1

>': <

x2

>.

The established login context cannot be activated. See <dce_err> for more details.

Can't validate DCE login - the validating security service is not the DCE security service.

The security service which was consulted during login seems not to be the DCE security service. See <dce_err> for more details.

Chapter 2 69

OpC20-2628

OpC20-2629

OpC20-2630

OpC20-2631

OpC20-2632

OpC20-2633

OpC20-2634

ITO Error Messages

Error messages of public routines

Can't register authentication information as/for RPC server '<

x1

>': <

x2

>.

Initializing a RPC connection failed. This message can be reported by both RPC clients and servers. See <dce_err> for more details.

Can't get authentication information about calling RPC client: <

x2

>.

The reporting process could not extract authentication data out of the

RPC parameters. See <dce_err> for more details.

Can't log into DCE.

The reporting process failed to log into DCE. More information is contained in another part of the error message.

Can't get password for '<

x1

>' from key table file '<

x2

>':

<

x3

>.

The reporting process failed to load it's password from the keytab file

<keytab>. See <dce_err> for more details. Check the file permissions and use the DCE utility 'rgy_edit' to verify the contents of the keytab file.

Can't create password for '<

x1

>' in key table file

'<

x2

>': <

x3

>.

The reporting process failed to update the keytab file <keytab> to hold the new password for the principal <princ>. Check the file permissions and use the DCE utility 'rgy_edit' to verify the contents of the keytab file.

Can't convert password to DES key.

The reporting process failed to generate a DES key (as used by DCE as passwords). More information is contained in another part of the error message.

The calling RPC client is unauthenticated.

The reporting RPC server received an unauthenticated RPC from a client which is supposed to be authenticated. More information is contained in another part of the error message. Check the ITO error logfile on the client system. Verify the configuration on the client system for the correct security level.

70 Chapter 2

OpC20-2635

OpC20-2636

OpC20-2637

OpC20-2638

OpC20-2639

OpC20-2640

ITO Error Messages

Error messages of public routines

The calling RPC client has registered as another principal than required.

The reporting RPC server received an authenticated RPC from a client which logged on as another principal than expected. More information is contained in another part of the error message. This can happen if the name service on the client system delivers another value for the local host than on the server system.

The calling RPC client has bound to RPC server with another principal than required.

The reporting RPC server received an authenticated RPC from a client which is bound to another RPC server principal than expected. More information is contained in another part of the error message. This can happen if the name service on the client system delivers another value for the local host than on the server system.

The calling RPC client requests an insufficient security level.

The reporting RPC server received an authenticated RPC from a client but the selected security level is too low. More information is contained in another part of the error message. Verify the configuration on the client system for the correct security level.

The calling RPC client is not authenticated by the DCE security service.

The reporting RPC server received an authenticated RPC from a client but the consulted authentication service seems not to be the DCE security service. More information is contained in another part of the error message. Check the ITO error logfile on the client system.

Can't get expiration time of current DCE login context:

<

x1

>.

Internal DCE error. See <dce_err> for more details.

Can't get refresh current DCE login context of '<

x1

>':

<

x2

>.

The current DCE login context of the reporting process is about to expire but could not be refreshed. See <dce_err> for more details.

Chapter 2 71

OpC20-2641

OpC20-2642

OpC20-2643

OpC20-2644

OpC20-2645

OpC20-2646

OpC20-2647

OpC20-2648

ITO Error Messages

Error messages of public routines

Can't get delete current DCE login context of '<

x1

>':

<

x2

>.

Internal DCE error. See <dce_err> for more details.

The current DCE login context is invalid.

Internal error. Please report this to your HP Response Center.

Can't get current DCE login context: <

x1

>.

The reporting process failed to retrieve an inherited DCE login context.

See <dce_err> for more details. This may happen if the DCE security services have been restarted but the process maintaining (refreshing) the login context did not perform this operation. Restart the ITO manager or agent processes depending on the reporting process.

Can't get account information for current DCE login context: <

x1

>.

The reporting process failed to retrieve the account data from the DCE registry for the current login context. See <dce_err> for more details.

Can't bind to DCE security service: <

x1

>.

The reporting process could not establish a connection to the DCE security service. See <dce_err> for more details. Use the DCE utility

'dce_config' to verify and start the DCE server processes.

Can't update password in DCE registry for

'<

x1

>:<

x2

>:<

x3

>': <

x4

>.

The reporting process failed to change the password for the

<princ>:<group>:<org> triple. See <dce_err> for more details.

Can't close DCE security service: <

x1

>.

Internal DCE error. See <dce_err> for more details.

Can't get next password version for '<

x1

>': <

x2

>.

The reporting process failed to retrieve the latest password version for the principal <princ> during an attempt to update the password in the local key tab file. See <dce_err> for more details.

72 Chapter 2

OpC20-2649

OpC20-2650

OpC20-2651

OpC20-2652

OpC20-2653

OpC20-2701

OpC20-2702

ITO Error Messages

Error messages of public routines

Calling client: '<

x1

>'. Bound to server '<

x2

>'. Requested security level: '<

x3

>'.

Required is: Client: '<

x4

>'. Server: '<

x5

>'. Least security level: '<

x6

>'.

The RPC server detected a mismatch between the client's authentication information/security level and the expected values. The parameters in the error message show the actual and expected values.

The current DCE login context is the inherited default context: '<

x1

>'.

The reporting process detected that it's inherited login context is not self-established as an ITO principal. This can happen if the process maintaining the login context failed to log into DCE.

Can't get account information for principal '<

x1

>': <

x2

>.

The reporting process failed to get account information for the principal

<princ>. This happens during verification of the principal. Probably the principal does not exist. Use the DCE utilities to verify and the ITO utility opc_sec_register.sh to setup the required configuration.

Can't get server principal from client RPC handle:

'<

x1

>'.

The reporting RPC client failed to extract the server name out of the

RPC handle. See <dce_err> for more details. Possibly the server is not authenticated at all. Check the RPC server host for error messages.

Bound to unexpected RPC server: '<

x1

>'. Want: '<

x2

>'.

The reporting RPC client has bound to the RPC server logged on as

<srv> instead of the expected <exp srv>. Check the RPC server host for error messages. This is either an attempted security break or an internal error.

Ambiguous option: <

x1

>.

This abbreviated option matches at least two allowed options and cannot be resolved uniquely.

Option <

x1

> requires <

x2

> arguments.

The specified option <opt> must be specified with exactly <num> additional parameters.

Chapter 2 73

OpC20-2703

OpC20-2704

OpC20-2705

OpC20-2706

OpC20-2707

OpC20-2708

OpC20-2709

OpC20-2710

OpC20-2720

ITO Error Messages

Error messages of public routines

Option <

x1

> conflicts with previous option <

x2

> which requires <

x3

> arguments.

The specified option <opt1> appears at a place where an argument for

<opt2> is expected. For example -x -y where -x requires an argument and

-y is a legal option.

Option <

x1

> must not be specified more than once.

The specified option <opt> must not be specified more than once.

Option <

x1

> cannot be specified in conjunction with other options.

The specified option <opt> must not be specified in conjunction with other options.

Illegal option: <

x1

>.

The specified option <opt> is unknown and excessive arguments are not allowed.

Option <

x1

> cannot be specified in conjunction with any of:<

x2

>.

The specified option <opt1> must not be specified in conjunction with any of the specified options <opt2> ...

Option <

x1

> must be specified in conjunction with all of:<

x2

>.

The specified option <opt1> must be specified in conjunction with option(s) <opt2> ...

Option <

x1

> must be specified.

The option <opt> is mandatory but has not been specified.

Option <

x1

> does not allow unrecognized arguments.

The option <opt> does not allow excessive arguments which are not legal options or their arguments.

Version: <

x1

>.

The default ITO program version text.

74 Chapter 2

OpC20-2721

OpC20-2801

OpC20-2802

OpC20-2803

OpC20-2804

OpC20-2805

OpC20-2806

OpC20-2807

OpC20-2821

ITO Error Messages

Error messages of public routines

Usage: <

x1

> [ -help ] [ -version ]

The default ITO program help text.

Internal error: No number range defined.

Internal error. Please report this to your HP Response Center.

The specified range contains a nested sub-range near

<

x1

>.

The number set contains a construction like 10-20-30. Ranges may have the form 10-20 only.

The specified range contains an illegal character near

<

x1

>.

The number set contains an illegal character. Allowed are numbers, the comma and space character.

The specified range contains an illegal sequence near

<

x1

>.

The number set contains a range where the upper limit is smaller than the lower like 20-10.

Internal error: Syntax error in range.

General syntax error in number set. Legal are ranges and lists like "-10

20-30,40, 100-". Open ranges must appear at the begin and end of the set.

The specified range contains an illegal character near

<

x1

>.

The number set contains an illegal character. Allowed are numbers, the comma and space character.

End of range - no more elements.

No more possible numbers are contained in set while evaluation. Not enough numbers in set which can be used by reporting process.

Queue empty.

The memory queue was empty during an attempted read operation.

Chapter 2 75

OpC20-2822

OpC20-2831

OpC20-2832

OpC20-2833

OpC20-2834

OpC20-2835

OpC20-2836

ITO Error Messages

Error messages of public routines

Queue full.

The memory queue was full during an attempted write operation.

Can't get exit code of terminated process '<

x1

>'.

The reporting process was unable to retrieve the exit code of the terminated process <proc>. More information is contained in another part of the error message.

Process '<

x1

>' terminated by signal '<

x2

>'. Exit code is

<

x3

>.

The controlled subprocess <proc> terminated unrequested. If the terminating signal is not SIGTERM or SIGINT the subprocess probably went down due to an internal failure. Otherwise these signals may have been sent by external processes/users. Another indicator for internal failures is an exit code other than 0. Check the local ITO error logfile for more information logged by the terminated process.

Can't execute program '<

x1

>'. Check existence and permissions.

The reporting process was unable to start a program as <command>.

Check whether this command is a valid path, the file exists and has the appropriate permission required for execution. This can also happen due to insufficient system resources. More information is contained in another part of the error message.

Process '<

x1

>' terminated with exit code <

x2

>.

The controlled subprocess <proc> terminated unrequested. If the exit code is not 0 the subprocess probably went down due to an internal failure. Check the local ITO error logfile for more information logged by the terminated process.

Can't execute program '<

x1

>'.

The reporting process was unable to start a program as <command>.

Check whether this command is a valid path, the file exists and has the appropriate permission required for execution.

Can't get process ID of of process '<

x1

>'.

76 Chapter 2

OpC20-2837

OpC20-2838

OpC20-2839

OpC20-2881

OpC20-2882

OpC20-2883

OpC20-2884

OpC20-2885

OpC20-2887

OpC20-2889

ITO Error Messages

Error messages of public routines

The reporting process was unable to retrieve the process ID of the started process <proc>. More information is contained in another part of the error message.

Can't add process object to table. Table full.

Internal error. Please report this to your HP Response Center.

Process '<

x1

>' not found in table.

Internal error. Please report this to your HP Response Center.

Could not terminate all controlled processes.

The reporting process attempted to terminate all started subprocesses but at least one process did not exit. Check running ITO processes using system commands and terminate remaining processes manually.

Cannot compress file <

x1

>.

Cannot compress file with LZ 4.3 compression algorithm

Cannot uncompress file <

x1

>.

Cannot uncompress file with LZ 4.3 compression algorithm

Cannot compress file (<

x1

> -> <

x2

>).

Cannot compress file with LZ 4.3 compression algorithm

Cannot uncompress file (<

x1

> -> <

x2

>).

Cannot uncompress file with LZ 4.3 compression algorithm

The file to be uncompressed does not end with extension

.Z.

The uncompress-routine was used in a way that expects filenames ending with .Z as source

The file is either corrupted or not compressed.

The file to be uncompressed has not the right format; please check whether the file is empty or not yet compressed; the file may also be corrupted, what caused an unexpected termination of the decompression.

Can't compress a buffer.

Chapter 2 77

OpC20-2890

OpC20-2891

OpC20-2892

OpC20-2893

OpC20-2921

OpC20-2922

OpC20-2923

OpC20-2924

ITO Error Messages

Error messages of public routines

Internal error. Compression of a data structure failed. Maybe out of memory.

Can't uncompress a buffer.

Internal error. Uncompress of a data structure failed. Maybe out of memory, or data structure was garbled.

Can't uncompress the message from node '<

x1

>'.

Internal error. Maybe out of memory, or message was garbled during transport.

Can't uncompress the action request from node '<

x1

>'.

Internal error. Maybe out of memory, or action request was garbled during transport.

Can't uncompress the action response from node '<

x1

>'.

Internal error. Maybe out of memory, or action response was garbled during transport.

Can't open connection to node '<

x1

>' for bulk transfer.

The Message Agent is unable to establish a connection to the

Management Server. A qualifying message gives more information.

Can't send data to node '<

x1

>' during bulk transfer.

The Message Agent is unable to send a request to the Management

Server. A qualifying message gives more information.

The receiving server on node '<

x1

>' failed to process a bulk transfer request.

The Management Server refused this request. A qualifying message gives more information.

The receiving server on node '<

x1

>' failed to process a bulk transfer request. Unknown error.

The Management Server refused this request but did not return a valid error code. Check the ITO error logfile the Server for related error messages.

78 Chapter 2

OpC20-2930

OpC20-2931

OpC20-2932

ITO Error Messages

Error messages of public routines

Error occured with the request transfer.

Error occured with the request transfer.

Request from agent node with unknown server id.

There is no subserver registered on the Management Server with the server ID as specified in this request. Probably an internal error in the subagent sending this request or the according subserver is simply not yet configured.

Authentication failure.

The Management Server processes refused this requests to to an authentication failure. Make sure that the security level on Server and

Agent system match. Check the ITO error logfile on Agent and Server for related error messages.

Chapter 2 79

ITO Error Messages

Error messages of agent processes

OpC30-0001

OpC30-0002

OpC30-0003

OpC30-0004

OpC30-0005

OpC30-0007

OpC30-0008

OpC30-0010

Error messages of agent processes

Internal error: Invalid request to assemble.

Internal Error. Please report this to your HP Response Center.

Internal error: NULL pointer passed to forward message routine.

Internal Error. Please report this to your HP Response Center.

Communication failure to message receiver: <

x1

>.

Buffering messages.

The ITO message agent detected a communication problem to the ITO message receiver while attempting to send data to it. The message agent buffers all further incoming requests until it can reconnect to the message receiver. The NCS message <ncs-msg> gives more information.

Internal error: Unknown queue element.

Internal Error. Please report this to your HP Response Center.

There is a message agent running already.

The message agent should be started but there is an instance already running.

Can't check already running agents.

The message agent should be started but is unable to check whether a message agent is running already. This error message is qualified by another message.

Initializing server failed.

The reporting process failed to start up as NCS server. This error message is qualified by another message containing more information.

Server main loop terminated. Exiting.

80 Chapter 2

OpC30-0011

OpC30-0012

OpC30-0013

OpC30-0014

OpC30-0015

OpC30-0016

ITO Error Messages

Error messages of agent processes

The reporting process exits it's NCS server main loop and terminates.

This can happen due to receipt of a signal. A qualifying message gives more information.

Can't connect to ITO message receiver on system '<

x1

>'.

The ITO message agent failed to connect to the ITO message receiver running on the management server node <node>.

Can't unregister message agent.

The ITO message agent is unable to unregister at the NCS local location broker process llbd/rpcd running on the managed node. This action will be done by the message agent only on exit. The next time the message agent starts up it will overwrite the remained entry. Solution: Check whether the llbd/rpcd process is running on the managed node, using the lb_admin/rpccp tool.

Can't connect to ITO message receiver on system '<

x1

>'.

Probably either node or llbd/rpcd down.

This message is reported when the ITO message agent cannot connect to the message receiver on start-up, or when it detects a communication error and tries to reconnect. The message agent can not reach the llbd/rpcd on the node. It starts up and buffers all incoming requests.

Solution: Check whether the llbd/rpcd is running on the management server.

Internal error: Message buffer queue is empty.

Internal Error. Please report this to your HP Response Center.

Can't read buffered message.

The ITO message agent is unable to read a temporary buffered message or action response. This error message is qualified by another message giving more information.

Can't retrieve number of buffered messages.

The ITO message agent is unable to retrieve the number of messages/action responses currently contained in the buffer queue file.

This error message is qualified by another message giving more information.

Chapter 2 81

OpC30-0017

OpC30-0018

OpC30-0019

OpC30-0020

OpC30-0021

OpC30-0022

OpC30-0023

OpC30-0024

OpC30-0025

OpC30-0026

ITO Error Messages

Error messages of agent processes

Can't return message to buffer.

The ITO message agent is unable to return a temporarily unbuffered message/action response to the buffer queue file. This message is qualified by another message giving more information.

Initializing configuration failed.

The ITO message agent is unable to get required configuration information. This message is qualified by another message giving more information.

Can't retrieve local IP address.

The ITO message agent is unable to get the local IP address. This message is qualified by another message giving more information.

Can't get name of ITO management server.

Internal Error. Please report this to your HP Response Center.

Can't get name of action request queue.

Internal Error. Please report this to your HP Response Center.

Can't get name of message buffer.

Internal Error. Please report this to your HP Response Center.

Can't open action request queue.

The ITO queue file between message agent and action agent can not be opened. This error message is qualified by another message giving more information.

Can't open message buffer.

The ITO queue file used as message buffer can not be opened. This error message is qualified by another message giving more information.

Can't close action request queue.

Internal Error. Please report this to your HP Response Center.

Can't close message buffer.

Internal Error. Please report this to your HP Response Center.

82 Chapter 2

OpC30-0027

OpC30-0028

OpC30-0029

OpC30-0030

OpC30-0031

OpC30-0032

OpC30-0033

ITO Error Messages

Error messages of agent processes

Can't put action request into queue.

The ITO message agent is unable to forward an action request to the ITO action agent through the action request queue file. This error message is qualified by another message giving more information.

Can't put message/action response into message buffer.

The ITO message agent is unable to store a message/action response temporarily into the buffer queue file. This error message is qualified by another message giving more information.

There is no ITO message receiver registered on system

'<

x1

>'. Buffering messages.

The ITO message agent could not connect to the message receiver because there is no such ITO server running on the node. Solution:

Check whether the management server processes are running.

The ITO message receiver is not running on system '<

x1

>'.

Buffering messages.

The ITO message agent could not connect to the message receiver. The

ITO message receiver is registered on the node but not responding. This can also be caused by a crash of the message receiver. Solution: Check whether the management server processes are running.

Assembly of fragmented request failed.

Internal Error. Please report this to your HP Response Center.

Can't retrieve node control status. Assuming monitored only.

The ITO message agent is unable to retrieve the status of the managed node from the 'nodeinfo' configuration file. The status 'Monitored Only' is assumed. Solution: Check the managed-node-specific configuration file

'nodeinfo' for a statement such as OPC_NODE_TYPE <node_type>.

Can't get IP address of management server.

The ITO message agent is unable to convert the name of the management server to an IP address. Solution: Check the name of the management server system in the 'opcinfo' file to be correct and verify whether this name can be resolved to an IP address on the managed node.

Chapter 2 83

OpC30-0034

OpC30-0035

OpC30-0036

OpC30-0037

OpC30-0038

OpC30-0039

OpC30-0040

OpC30-0041

ITO Error Messages

Error messages of agent processes

Can't get IP address of action request.

Internal Error. Please report this to your HP Response Center.

Action request from node other than the management server arrived (<

x1

>).

The ITO message agent received an action request from a node other than the currently-assigned management server with the IP address

<address>. This might be caused by an assignment of this managed node to another management server. Solution: Check the ITO node configuration on the system with the specified IP address.

Forwarding message/action response to ITO message receiver failed due to server failure.

Internal Error. Please report this to your HP Response Center.

Can't retrieve RPC parameters for max. data array size and inter RPC delay.

Internal Error. Please report this to your HP Response Center.

Can't set signal handler for signal <

x1

>.

The ITO message agent could not set a signal handler. This message is qualified by a system error message (errno) containing the cause of the error.

Can't open the ITO message agent buffer file (<

x1

>).

An error occurred while opening the ITO message agent buffer file. This message is qualified by another message giving more information.

Can't initialize the alive check for the responsible ITO management servers.

An error occurred while initializing the ITO message agent. This message is qualified by another message giving more information.

Errors occurred during the read of the responsible manager configuration file <

x1

>.

An error occurred while reading the ITO responsible manager configuration. This message is qualified by another message giving more information.

84 Chapter 2

OpC30-0042

OpC30-0043

OpC30-0044

OpC30-0045

OpC30-0053

OpC30-0054

OpC30-0055

OpC30-0056

ITO Error Messages

Error messages of agent processes

Can't get IP address for ITO management server <

x1

>.

The ITO message agent is unable to convert the name of the management server to an IP address. Solution: Check the name of the management server system to be correct and verify whether this name can be resolved to an IP address on the managed node.

ITO action response with invalid IP address received.

The action response is ignored.

Internal Error. Please report this to your HP Response Center.

No ITO subagent found.

The ITO subagent must be specified in the subagent registration with the subagent-id 1.

Can't evaluate a manager for subagent-id <

x1

>. Drop message.

The message agent was not able to evaluate a manager for the given subagnet-id. Please check if a subagent with this number is registered.

Can't retrieve IP addresses.

The agent is unable to retrieve local IP-address(es) from the device list.

Cannot contact node <

x1

> via ping-module.

Trying to send packets to the node using "ping" failed. Networking services on the node may not be running properly or maybe the node is not configured correctly.

Can't get own identity from login context.

The ITO message agent failed to retrieve it's own identity from the inherited DCE login context. This login context is supposed to be established by the ITO Control agent. Check the ITO error logfile for error messages from the Control agent. This error message is qualified by another message giving more information.

Can't authenticate with DCE security service. Management server: '<

x1

>'.

Manager name: '<

x2

>'; own name: '<

x3

>'.

Sending data unauthenticated.

Chapter 2 85

OpC30-0057

OpC30-0058

OpC30-0059

OpC30-0060

ITO Error Messages

Error messages of agent processes

The ITO message agent failed to initialize an authenticated RPC connection to the management server <mgmt sv>. This error message is qualified by another message giving more information. The Message agent will send further data unauthenticated.

Authentication failure to message receiver: <

x1

>.

Retrying unauthenticated ...

The ITO message agent failed to send an ITO message/action response via authenticated RPC. This happens usually if the ITO message receiver does not run authenticated but the Message agent does. The

Message agent will send further data unauthenticated. Possibly the

Management server failed to initialize properly or the Management server has been unconfigured in the DCE security service. Verify the ITO management server error logfile for security related error messages.

Unable to obtain proper security context for <

x1

>.

Further security related error messages will be suppressed.

The ITO message agent could not set the security context for the reported system, or an error during encryption occurred. Please check if required session processes are running (opcsa/opcsm for public key), and the keys or certificates are installed on both systems.

ITO agents failed to write queue file '<

x1

>'. No space in file system.

The ITO message agent detected that a previous write operation attempted by another ITO agent failed due to lack of file system space.

The writing agent will retry the write operation. Nevertheless this is a critical condition and may limit the entire ITO functionality. Log on the managed node and free up file space in the file system where the queue file <queue> resides.

Can't get queue status of queue file '<

x1

>' or unknown status: <

x2

>.

The ITO message failed to verify the status of the queue file <queue> or and unknown status value was found. This error message is qualified by another message giving more information. To ensure correct operation move the queue away and re-start the ITO agent.

86 Chapter 2

OpC30-0095

OpC30-0096

OpC30-0101

OpC30-0102

OpC30-0103

OpC30-0104

ITO Error Messages

Error messages of agent processes

The message agent detected a corrupted queue-file

(<

x1

>). A backup for trouble-shooting purpose was stored at <

x2

>. The ITO agent processes will be restarted automatically.

A corrupted queue-file was detected. Queue-files are used in ITO to perform local inter-process communication. A queue-file can be corrupted e.g. since 'system panic' occurred. The message agent tries to repair things by renaming the queue-file (to be used for trouble-shooting), creating a new empty queue-file and triggering the restart of the agent processes.

The message agent detected a corrupted queue-file; it renamed the file created a new one, but failed to trigger the control agent to restart the ITO agent processes.

Please try to restart the agents manually.

The message agent was not able to trigger the control agent to restart the agent processes after a queue-file was corrupted. This may have been caused due to the fact, that the control agent wasn't registered as

RPC-server yet. Please try to restart the agents manually by using the

ITO server command opcragt or use the appropriate entry in the application desk-top.

Configuration file contains no source description.

The ITO logfile encapsulator found that it's configuration file does not contain any active logfiles. It will keep on running but won't monitor anything.

Configuration file contains no source description.

Continuing with old configuration.

Internal Error. Please report this to your HP Response Center.

Cannot create default message for source <

x1

>.

The ITO logfile encapsulator is unable to create a default message filled with globally configured values. This error message is qualified by another message giving more information.

Cannot set signal mask for SIGUSR1.

Internal Error. Please report this to your HP Response Center.

Chapter 2 87

OpC30-0105

OpC30-0106

OpC30-0107

OpC30-0108

OpC30-0109

OpC30-0110

OpC30-0111

OpC30-0112

ITO Error Messages

Error messages of agent processes

Cannot install signal handler for SIGUSR1.

Internal Error. Please report this to your HP Response Center.

Installation of new configuration failed. Continuing with old one.

The ITO logfile encapsulator is unable to install a new assigned configuration. The previously distributed configuration will be used furthermore. This error message is qualified by another message giving more information.

Command '<

x2

>' configured in source '<

x1

>' returns <

x3

>.

Ignoring this logfile.

The command configured in the logfile source exits with a code that the logfile encapsulator assumes that the command failed and ignores the corresponding logfile furthermore. Solution: Check whether the command is correct and restart the agent processes.

Logfile <

x1

> doesn't exist. Treating as empty.

The logfile doesn't exist. This message is reported only when the logfile encapsulator starts up and this feature is enabled for this logfile source.

Non-existent files are always treated as empty.

Node is no cluster member. Ignoring CDF specification in

<

x1

>.

Using <

x2

> instead.

The logfile is configured as CDF but the node is no cluster member. The logfile encapsulator maps the file path.

Cannot get context while expanding CDF name.

The ITO logfile encapsulator is unable to retrieve the HP-UX cluster configuration to expand a CDF logfile specification. This error message is qualified by a system error text (errno).

Internal error: Logfile is no CDF.

Internal Error. Please report this to your HP Response Center.

Can't get name of configuration file.

Internal Error. Please report this to your HP Response Center.

88 Chapter 2

OpC30-0113

OpC30-0114

OpC30-0115

OpC30-0116

OpC30-0117

OpC30-0118

OpC30-0119

OpC30-0120

OpC30-0121

OpC30-0122

ITO Error Messages

Error messages of agent processes

Can't read configuration file.

The configuration file of the reporting process could not be read correctly.

This error message is qualified by another message giving more information.

Can't convert configuration file.

Internal Error. Please report this to your HP Response Center.

Can't retrieve name of message logfile.

Internal Error. Please report this to your HP Response Center.

Can't create empty message.

The ITO logfile encapsulator is unable to create an empty ITO message.

This error message is qualified by another message giving more information.

Can't send message to ITO message agent.

The logfile encapsulator could not send a message to the message agent.

This error message is qualified by another message giving more information.

Can't log message.

The logfile encapsulator could not put a message into the local logfile.

This error message is qualified by another message giving more information.

Internal error: Can't set async flag of internal object.

Internal Error. Please report this to your HP Response Center.

Can't retrieve config flag file name.

Internal Error. Please report this to your HP Response Center.

Can't retrieve config flag file checking interval.

Internal Error. Please report this to your HP Response Center.

Installation of configuration failed.

Chapter 2 89

OpC30-0123

OpC30-0124

OpC30-0125

OpC30-0126

OpC30-0127

OpC30-0128

OpC30-0129

OpC30-0130

OpC30-0131

ITO Error Messages

Error messages of agent processes

The ITO logfile encapsulator is unable to install a configuration. This error message is qualified by another message giving more information.

Main loop terminated.

The ITO logfile encapsulator terminated due to an error. This error message is qualified by another message giving more information.

Can't get command status.

Internal Error. Please report this to your HP Response Center.

Can't set command status.

Internal Error. Please report this to your HP Response Center.

Can't get exit code of command.

Internal Error. Please report this to your HP Response Center.

Can't run command <

x1

>.

The command could not be executed. This error message is qualified by another message giving more information.

Can't kill command <

x1

>.

The ITO logfile encapsulator is unable to terminate a command started previously as configured file to be executed before logfile processing. This action has to be performed when the logfile configuration belonging to the command that is running has been modified. Solution: Check that processes having the PID of the logfile encapsulator as parent exist and display proper functionality. If there are hanging processes, kill them manually.

Can't remove config flag file.

Internal Error. Please report this to your HP Response Center.

Invalid CDF specification in <

x1

>.

The CDF logfile specification configured in template <logfile> is not valid.

Invalid interval for object <

x1

> specified. Using default (<

x2

>).

90 Chapter 2

OpC30-0132

OpC30-0133

OpC30-0134

OpC30-0135

OpC30-0136

OpC30-0137

OpC30-0138

ITO Error Messages

Error messages of agent processes

The ITO logfile encapsulator encountered an invalid interval configured for the logfile <logfile>. The logfile encapsulator proceeds with the specified default value. This is an internal Error. Please report this to your HP Response Center.

Logfile <

x1

> was removed but 'close' option is off.

Closing the file and treating as empty.

The logfile has been kept open by the logfile encapsulator but was removed by another process. The logfile encapsulator treats the file as empty. Only valid for UNIX systems.

Logfile <

x1

> was removed and re-created but 'close' option is off. Reopening the file.

The logfile has been kept open by the logfile encapsulator, but was removed and newly created by another process. The logfile encapsulator reopens the file. Only valid for UNIX systems.

Can't get default directory for conversion programs.

Internal Error. Please report this to your HP Response Center.

Can't get path from environment.

The ITO logfile encapsulator is unable to retrieve the execution path from the environment. This error message is qualified by a system error text (errno).

Can't set path in environment.

The ITO logfile encapsulator is unable to set the execution path in the environment. This error message is qualified by a system error text

(errno).

Can't append ITO default path for conversion programs.

The ITO logfile encapsulator is unable to modify the execution path in the environment to include the ITO path for monitoring scripts. This is necessary to start configured conversion scripts/programs from this default location. This error message is qualified by another message giving more information.

Can't convert logfile entry.

Chapter 2 91

OpC30-0139

OpC30-0140

OpC30-0141

OpC30-0142

OpC30-0143

OpC30-0144

ITO Error Messages

Error messages of agent processes

The ITO logfile encapsulator is unable to convert a logfile entry to the required character set. This error message is qualified by another message giving more information.

Logfile path for object <

x1

> is empty but no alternate file specified.

The ITO logfile encapsulator encountered an empty logfile path configured for the object <logfile>. This is only allowed if an alternate file to be read is specified.

CDF base directory <

x1

> not found for logfile or alternate file <

x2

>.

The ITO logfile encapsulator is unable to check whether a <*.node> specification refers to a CDF or has to be replaced by the host name because the next directory doesn't exist. The logfile encapsulator proceeds with the assumption that the <*.node> path component stands for the host name.

Environment variable '<

x1

>' requested for path '<

x2

>' not set. Replacing by empty string.

The ITO logfile encapsulator could not get the value of the environment variable <var> to replace in the logfile path <path>. The variable specifier will be left empty. This might cause the monitoring of a wrong path which doesn't exist. The logfile encapsulator treats non-existent files as if they ar empty. The variable must be set in the environment the

ITO processes are started in.

Can't expand environment variables in path '<

x1

>'.

The ITO logfile encapsulator could not substitute environment variables contained in the logfile specification <logfile>.

NT API <

x1

>: Can't open the NT Eventlog <

x2

>.

The NT API found a reference to the Eventlog, but was unable to open it.

Use the NT Registry Editor to investigate the problem.

NT API <

x1

>: Can't close the NT Eventlog <

x2

>.

An Internal Error has occurred. This warning is not serious and can safely be ignored.

92 Chapter 2

OpC30-0145

OpC30-0146

OpC30-0147

OpC30-0148

OpC30-0149

OpC30-0152

ITO Error Messages

Error messages of agent processes

NT API <

x1

>: Can't expand strings, message file = '<

x2

>'.

The NT API was unable to expand path variable. Investigate using the

NT control panel. Make sure that the variable exists and is correctly set.

NT API <

x1

>: Can't open message file '<

x2

>' of NT eventlog.

The NT API was unable to open the message file. Use the NT Registry

Editor to make sure the message file exists, and is in the path. Open a command shell and type "echo $PATH" to examine the default paths.

NT API <

x1

>: Can't find message for Event Id <

x2

> in message file <

x3

> for source <

x4

>.

The NT API was unable to find a message for a specific Windows NT

Event ID. This could happen if a third-party program created an Event

ID, but did not create any message text for that ID. In this case, the NT

API will record the default value "The description for the Event ID ### could not be found"

NT API <

x1

>: Can't close message file '<

x2

>' of NT eventlog.

An Internal Error has occurred. This warning is not serious and can suavely be ignored.

The NT Eventlog <

x1

> was changed (cleared) and the current position is no longer reachable. ITO starts reading from the beginning of the Eventlog.

Some records might be lost.

This warning indicates that a user has manually cleared an eventlog. If a user clears the event log, the NT API may not have recorded all the events before they were cleared.

Command '<

x2

>' configured in source '<

x1

>' cannot be executed. The system call exec(2) failed.

Ignoring this logfile.

The command configured in the logfile source could not be executed.

Check whether the configured path resolves to a valid executable and the permissions are correct. If this error message was reported by a HP-UX

Chapter 2 93

OpC30-0201

OpC30-0202

OpC30-0203

OpC30-0204

OpC30-0205

OpC30-0206

OpC30-0207

ITO Error Messages

Error messages of agent processes

or MPE/iX node this error relates to a intermediate shell instead of the command itself. The logfile encapsulator ignores the corresponding logfile furthermore.

Can't open SNMP session: <

x1

>.

The ITO event interceptor is unable to establish an SNMP session. This error message is qualified by another message from the SNMP subsystem giving more information.

Can't connect the OV daemon 'pmd' to open SNMP session:

<

x1

>.

The ITO event interceptor could not connect to the OV daemon 'pmd'.

The SNMP API message <snmp-msg> gives more information. Solution:

Check whether the OV processes 'ovtrapd' and 'pmd' are running using the ovstatus(1m) utility. Restart these services if necessary.

Select failed.

The ITO event interceptor failed executing the system call select(2). This error message is qualified by a system error text (errno).

Receiving SNMP PDU failed: <

x1

>. Trying to reinitialize.

The ITO event interceptor could not get a SNMP PDU although it was informed that there is one available. The SNMP API message

<snmp-msg> gives more information. The event interceptor tries to reconnect to pmd.

Can't close SNMP session: <

x1

>.

The ITO event interceptor is unable to close a SNMP session. This error message is qualified by another message from the SNMP subsystem giving more information.

Can't get hostname.

The ITO event interceptor is unable to retrieve the local hostname. This error message is qualified by a system error text (errno).

Configuration contains more than one source. Using first one (<

x1

>).

The administrator distributed multiple trap sources but the event interceptor expects only one. The first source is used.

94 Chapter 2

OpC30-0208

OpC30-0551

OpC30-0562

OpC30-0563

OpC30-0568

ITO Error Messages

Error messages of agent processes

Can't connect the OV daemon 'pmd' to open SNMP session:

<

x1

>.

Trying to open session directly.

The ITO event interceptor could not connect to the 'pmd' process. The event interceptor tries to open the SNMP trap port 162 directly. Solution:

Check whether the OV processes 'ovtrapd' and 'pmd' are running using the ovstatus(1m) utility. Restart these services if necessary.

The operator-initiated action to answer an MPE-request did not open an

X-display on the operators system to enter the reply. possible reasons: the used DISPLAY-variable, transferred to the MPE system cannot be resolved there. Check for name service entries on MPE and check for short/long hostnames in DISPLAY-variable. To fix this, set the

DISPLAY-variable on the operator's system appropriately and restart the GUI to get the value into the environment. The MPE-system is maybe not authorized to open a display on the operator's system as well.

ITO Account does not have the required privileges enabled.

Actions will not be allowed to switch user accounts.

The HP ITO user's account does not have the necessary privileges enabled. You can reinstall the account by running opcsetup.exe -s.

Could not register at the NT Local Security Authority.

Actions will not be allowed to switch user accounts.

This problem is usually caused by wrong user rights (not HP ITO

Account) or a removal of the security library (opcauth.dll) from the

%SystemRoot%\system32\ directory.

Actions are currently not allowed to switch the user account.

Please check for errors occurred during agent startup.

The action agent cannot start actions under certain user accounts. For instance if it cannot register at the NT LSA, if the NT version failed the verification, or if the HP ITO Account is not configured correctly.

Previous error messages may help in analyzing this situation.

Chapter 2 95

OpC30-0569

OpC30-0571

OpC30-0600

OpC30-0601

OpC30-0603

OpC30-0604

ITO Error Messages

Error messages of agent processes

Could not switch to user (<

x1

>).

There is no Domain Controller for logon authentication available.

The action agent failed to start an application under a certain user account. No NT Primary nor NT Backup Domain Controller was available to validate the logon request. Please verify that the network connections and Domain Controllers are up and running.

Switch to user (<

x1

>) failed.

There is no ITO agent installed on the active domain controller.

The action agent failed to start an application under a certain user account. This agent requires that the NT Domain Controllers for this system are running AND have an ITO agent installed. Please ensure that all currently active Domain Controllers have an installed ITO NT

Agent.

Can't get own IP-address; no monitoring of SNMP variables possible.

The ITO monitoring agent is unable to retrieve the IP address of the managed node. This information is required for monitoring of local MIB variables. The process will start up anyway, if any script or external monitors are defined. This error message is qualified by another message giving more information.

Can't establish SNMP session; no monitoring of SNMP variables possible.

The ITO monitor agent could not open a SNMP session. All configured objects with SNMP variables to be monitored are ignored.

Can't close SNMP session.

The ITO monitoring agent is unable to close an open SNMP session. This action is to be performed only on exit. This error message is qualified by another message from the SNMP subsystem giving more information.

Can't retrieve polling interval for managed node self-monitoring.

Internal Error. Please report this to your HP Response Center.

96 Chapter 2

OpC30-0605

OpC30-0606

OpC30-0607

OpC30-0608

OpC30-0609

OpC30-0610

ITO Error Messages

Error messages of agent processes

Can't install new configuration.

The ITO monitoring agent was unable to install a new configuration distributed to the managed node. This can happen either at start up or while runtime when re-distributing the configuration. The monitoring agent will terminate resp. continue with the previously installed configuration. This error message is qualified by another message giving more information.

Can't execute script for monitor <

x1

>.

The script for the monitor object could not be executed. This error message is qualified by another message giving more information.

Can't issue an SNMP GET request for monitor '<

x1

>'.

Suppressing further error messages.

The ITO monitor agent could not send an SNMP 'Get' request to retrieve the current value for the monitored object. Solution: Check whether the

SNMP daemon on the target node is reachable and the following entry exists in /etc/snmpd.conf: 'get-community-name:' or

'get-community-name: public'.

Can't retrieve value for monitor '<

x1

>'.

Suppressing further error messages.

The ITO monitoring agent could not read a required value for the configured monitor <mon_name>. This may occur if the monitor agent detects the completion of an initiated script or program and is not able to get the current value, which has to be passed by the monitor script using the opcmon(1) or opcmon(3) functionality. Solution: Check that the monitor script/program belonging to this correctly delivers a value. If not, or if there are any processes marked <defunct> having the monitoring agent as parent process, this might be an internal error.

Can't kill monitor script (Pid = <

x1

>).

The ITO monitoring agent is unable to kill a monitoring script/program that has been started. This action is performed if the running script belongs to a monitored object whose configuration must be modified. This error message is qualified by a system error text (errno).

Can't start monitor script for object '<

x1

>'. Script still running.

Chapter 2 97

OpC30-0611

OpC30-0612

OpC30-0613

OpC30-0615

OpC30-0616

OpC30-0617

OpC30-0618

ITO Error Messages

Error messages of agent processes

The monitor agent should start a monitor script for the object but the script started last time is still running. Probably either the interval is too short or the script hangs. Solution: Verify whether the script works correctly. Adapt the interval if necessary.

Can't install signal handler for SIGUSR1 signal.

Internal Error. Please report this to your HP Response Center.

Internal error: Object '<

x1

>' received unexpected event

'<

x2

>'.

Internal Error. Please report this to your HP Response Center.

Unknown monitor '<

x1

>'. Ignoring received value.

The monitor agent received a monitor value for the currently not configured object. The value will be discarded. Solution: Check whether the configured monitor scripts deliver correct object names. Verify whether other processes sending monitor values are active.

Can't get name of temporary directory. Using "." instead.

Internal Error. Please report this to your HP Response Center.

Can't open temporary file to save error messages of monitor '<

x1

>'.

The ITO monitoring agent is unable to open a temporary file to store the output of the monitoring script/program configured for the object

<mon_name>. This error message is qualified by a system error text

(errno).

Script for monitor '<

x1

>' failed, but cannot read stderr.

Suppressing further error messages.

The ITO monitoring agent is unable to read the file containing the stderr output generated by the script/program configured for the object

<mon_name>. The script/program exited with a non-zero exit code. This error message is qualified by a system error text (errno).

Script for monitor '<

x1

>' failed.

Error message: '<

x2

>'.

Suppressing further error messages.

98 Chapter 2

OpC30-0621

OpC30-0622

OpC30-0625

OpC30-0627

OpC30-0628

OpC30-0629

OpC30-0630

ITO Error Messages

Error messages of agent processes

The executed script for the object exits with a non-zero exit code. The monitor agent assumes that the script failed. <msg> contains the stderr output of the script. Solution: Verify whether the script works correctly.

A monitor script should contain an exit 0 statement.

Can't open monitor value queue file; no monitoring via scripts possible.

The ITO monitoring agent is unable to open the queue file used for reading the actual values from the opcmon(1|3) interface. This error message is qualified by another message giving more information.

Can't close monitor value queue file.

The ITO monitoring agent is unable to close the queue file used for reading the actual values from the opcmon(1|3) interface. This error message is qualified by another message giving more information.

Can't send a 'threshold exceeded' message for monitor

'<

x1

>'.

The ITO monitor agent could not send an ITO message but the threshold for the object is exceeded. This error message is qualified by another message giving more information.

Monitor agent exits due to exception.

The ITO monitoring agent exits, due to a received signal. This error message is qualified by another message giving more information.

Monitored SNMP variable of object '<

x1

>' is not of numeric type.

Suppressing further error messages.

The type of the SNMP variable configured for the object is not numeric.

Either an invalid variable was configured (for example, of type string) or the variable is unknown. Solution: Check whether the SNMP object ID of the variable is correct.

Monitor queue is empty.

Internal Error. Please report this to your HP Response Center.

Monitor value belongs to other object.

Internal Error. Please report this to your HP Response Center.

Chapter 2 99

OpC30-0631

OpC30-0632

OpC30-0633

OpC30-0634

OpC30-0635

OpC30-0636

OpC30-0637

OpC30-0638

OpC30-0639

ITO Error Messages

Error messages of agent processes

Reading monitor queue failed.

Internal Error. Please report this to your HP Response Center.

Can't get name of monitoring queue.

Internal Error. Please report this to your HP Response Center.

Can't update configuration. Continuing with old one.

The ITO monitoring agent is unable to install a newly distributed configuration. The process continues using the previously installed configuration. This can happen you you assigned a monitor and a scheduled action with the same name to a agent. Please use unique names for monitors and a scheduled actions.

Can't get monitoring script directory to append to path.

Internal Error. Please report this to your HP Response Center.

Can't get path environment variable.

The ITO monitoring agent is unable to retrieve the execution path from the environment. This error message is qualified by a system error text

(errno).

Can't update path environment variable.

The ITO monitoring agent is unable to add ITO related directories to the execution path in the environment.

Appending default path for monitoring scripts failed.

Using current path.

The ITO monitoring agent is unable to set the execution path in the environment. This error message is qualified by a system error text

(errno).

Can't get interval for checking external monitoring.

Internal Error. Please report this to your HP Response Center.

Invalid value for external monitoring interval. Using default (<

x1

>s).

Internal Error. Please report this to your HP Response Center.

100 Chapter 2

OpC30-0640

OpC30-0641

OpC30-0642

OpC30-0643

OpC30-0644

OpC30-0645

OpC30-0646

ITO Error Messages

Error messages of agent processes

Invalid monitoring interval for object '<

x1

>' specified.

Using default (<

x2

>s).

The ITO monitoring agent encountered a monitoring interval out of the valid range configured for the object <mon_name>. The default value of

<default> seconds will be used.

Can't get name of monitor pipe.

Internal Error. Please report this to your HP Response Center.

Can't create monitor pipe '<

x1

>'.

The ITO monitoring agent is unable to create the named pipe

<pipe_path> used to pass actual values by the opcmon(1|3) functionality.

This error message is qualified by a system error text (errno).

Can't open monitor pipe '<

x1

>'.

The ITO monitoring agent is unable to open the existing named pipe

<pipe_path> used to pass actual values by the opcmon(1|3) functionality.

This error message is qualified by a system error text (errno).

Number of valid monitored objects is zero.

The ITO monitoring agent's configuration contains no valid monitored object, or all the configured objects cannot be monitored due to other errors. The monitoring agent will exit.

Can't execute monitor script for object '<

x1

>'. System call exec(2) failed.

The ITO monitoring agent is unable to execute the script/program configured for object <mon_name>. This might happen if the script/program is not present at all or the required permissions are missing. This error message is qualified by a system error text (errno).

Can't execute a shell to start monitor script for object

'<

x1

>'. System call exec(2) failed.

The ITO monitoring agent is unable to execute a shell for subsequent execution of a script/program configured for object <mon_name>.

Possible only on HP-UX systems. This might happen if the program

/bin/ksh is not present at all or the required permissions are missing.

This error message is qualified by a system error text (errno).

Chapter 2 101

OpC30-0647

OpC30-0648

OpC30-0649

OpC30-0650

OpC30-0680

OpC30-0681

ITO Error Messages

Error messages of agent processes

Can't find required perfmon object for the monitor script '<

x1

>'

The agent was unable to find the object specified in a threshold monitor template. Please check to make sure that the software that produces the object is installed on the system and that the name of the object is exactly the same as the name specified in the corresponding threshold monitor template.

Can't find required perfmon counter for the monitor script '<

x1

>'

The agent was unable to find the counter specified in a threshold monitor template. Please check to make sure that the name of the object is exactly the same as the name specified in the corresponding threshold monitor template.

Can't find index/counter for the monitor script '<

x1

>'.

This could occur if the system software has been deinstalled or changed on the system.

Performance data cannot be monitored, check the local system to make sure that the system software is correctly installed.

Please ensure that this is not a problem with the intallation of System

Software on the Managed Node. Please also ensure that the name of the object to be monitored is correct. If this problem is then still a concern for you, please report this to your HP Response Center.

Can't find required perfmon instance for the monitor script '<

x1

>'

Please verify that the name of the instance and of the parent instance match the names in the corresponding threshold monitor template.

Usage: opcmon [-help] <

object name

>=<

value

> [-object

<

message object

>] [-option <

var

>=<

var_value

>]*.

The program opcmon(1) was called either with the option -help or any abbreviation or an invalid parameter list. Correct is opcmon

<name>=<value> where <name> is the name of the monitored object and

<value> the current value. Note that this pair must be passed as one parameter. Quote if necessary.

Invalid monitor value in '<

x1

>'.

102 Chapter 2

OpC30-0682

OpC30-0683

OpC30-0684

OpC30-0685

OpC30-0686

OpC30-0800

ITO Error Messages

Error messages of agent processes

The value passed to the opcmon(1) command is not in a numeric format.

Valid is any floating point representation recognized by scanf(3C).

Extra characters in monitor value '<

x1

>'.

Trailing non-numeric characters in the passed value are encountered by the opcmon(1) command. Valid is any floating point representation recognized by scanf(3C).

Invalid parameter: '<

x1

>'.

The name-value pair passed to the opcmon(1) command is invalid.

Correct is opcmon <name>=<value> where <name> is the name of the monitored object and <value> the current value. Note that this pair must be passed as one parameter. Quote if necessary.

Can't forward monitor value to ITO monitor agent.

The opcmon(1) command is unable to forward a passed value to the ITO monitoring agent. This error message is qualified by another message giving more information.

Usage: opcmon.bin.ovopc "[-help] <

object name

>=<

value

>

[-object <

message object

> [-option <

var

>=<

var_value

>]*"

The program opcmon(1) was called either with the -help option, or any abbreviation or an invalid parameter list. Correct is opcmon

<name>=<value> where <name> is the name of the monitored object and

<value> the current value. Note that this pair must be passed as one parameter.

The ITO monitor agent is not running. Can't forward value.

The opcmon(1) command is unable to forward a passed value to the monitoring agent, because this process is currently not running. Check whether monitoring is configured at all, and if so, whether the ITO monitoring agent is running, by using opcagt/opcragt(1).

Communication failure between Distribution Agent and

Distribution Manager.

Chapter 2 103

OpC30-0801

OpC30-0802

OpC30-0803

OpC30-0804

OpC30-0805

ITO Error Messages

Error messages of agent processes

Communication problem between distribution agent and distribution manager; the network might be down or too much network traffic has caused timeouts. Solution: Make sure that the network is performing appropriately. Afterwards, re-start the ITO agents on that managed node.

Distribution Manager too busy (after several retries).

Distribution Agent will stop requesting now.

Distribution agent will stop requesting now. The distribution manager on the management server system has to handle more requests in parallel than possible (max. 5 requests), so the distribution request of this distribution agent has not been accepted, however new data for transmission is available for that managed node. Solution: Re-start the

ITO agents on that managed node after you are sure that the distribution manager is accepting requests again.

Cannot get ITO version info from local opcinfo file.

Internal Error. The opcinfo file does not exist or does not contain the

OPC_INSTALLED_VERSION entry. The opcinfo file must have at least the following entries: OPC_INSTALLED_VERSION: <ITO_version>

OPC_MGMT_SERVER: <mgmt_server_hostname>

Distribution Agent has been stopped during access of new configuration or binary data; you have to re-enforce the distribution for consistent and complete data.

The distribution agent got an interrupt (for example, due to 'Stop Agents' call) and not all data available on the management server has been transmitted yet. Solution: Re-distribute the data once more, after the

ITO agents on the managed node are running.

Cannot set signal mask.

Internal error. Please report this to your HP Response Center. Re-start the management server processes and then re-distribute the selected components to that managed node. (This may not always work.)

Cannot install signal handler.

Internal error. Please report this to your HP Response Center. Re-start the management server processes and then re-distribute the selected components to that managed node. (This may not always work.)

104 Chapter 2

OpC30-0806

OpC30-0807

OpC30-0808

OpC30-0809

OpC30-0810

OpC30-0811

ITO Error Messages

Error messages of agent processes

Unexpected hardware <

x1

> found.

Distribution agent runs on a hardware/OS platform not yet supported.

Solution: Verify the hardware and OS version of the managed node: On

UN*X systems: uname -a On MPE/iX systems: showme Compare the result with the list of supported platforms and OS versions.

Got unexpected return value when calling Distribution

Manager.

Internal error. Please report this to your HP Response Center. Re-start the management server processes and then re-distribute the selected components to that managed node. (This may not always work.)

Invalid transmission mode specified: '<

x1

>'. Using TCP socket as default.

The ITO distribution agent encountered an invalid data transmission mode configured in the local nodeinfo/opcinfo file. Valid is DIST_RPC or

DIST_TCPSOCK. Using TCP socket mode.

Can't convert IP address of management server from NCS handle.

Internal NCS error. This error message is qualified by a message from the NCS subsystem giving more information.

Can't connect Distribution TCP socket server on system

'<

x1

>'.

The ITO distribution agent is unable to connect the TCP socket server process on the management server system <server>. This process will be started dynamically by the ITO distribution manager on demand. Check the opcerror logfile on the management server for a corresponding error message.

Receiving package from Distribution TCP socket server failed.

The ITO distribution agent is unable to receive expected distribution data from the TCP socket server running on the management server.

This error message is qualified by another message giving more information. Check the opcerror logfile on the management server for a corresponding error message.

Chapter 2 105

OpC30-0812

OpC30-0813

OpC30-0814

OpC30-0815

OpC30-0816

OpC30-0817

OpC30-0818

ITO Error Messages

Error messages of agent processes

Can't set TCP socket buffer size to value '<

x1

>' bytes.

Using default size.

The ITO distribution agent is unable to set the socket buffer size to the requested value of <size> bytes. The process continues with a default value.

Invalid number of busy-tries specified: '<

x1

>'. Value must be greater than zero. Trying infinitely.

The ITO distribution agent needed an invalid number of tries to get required data from the ITO distribution manager. This situation occurs when the number of parallel requesting distribution agents exceeds the configured limit. The number of tries can be specified in the nodeinfo/opcinfo file and must be greater than zero. The distribution agent will try until success or an error.

The following configuration information was successfully distributed:

<

x1

> <

x2

> <

x3

> <

x4

> <

x5

>

The ITO distribution agent on this managed node received the specified configuration information from the distribution manager.

Invalid maximum number of distribution files per package specified: '<

x1

>'. Valid is <

x2

> - <

x3

>. Using '<

x4

>' as default.

The ITO distribution manager encountered an invalid maximum number of files allowed per distribution package. This value may be in the specified range only.

Can't evaluate system uname values: sysname '<

x1

>', release '<

x2

>'.

The ITO distribution manager got malformed values from the uname(2) system call on the system <system>. The release string is not in the format V.##.##.

Too few entries in distribution info file '<

x1

>'.

The distribution date file <distfile> contains too few entries. Solution:

Remove the file. It will be generated when distributing next time.

Invalid line in distribution info file '<

x1

>': '<

x2

>';

106 Chapter 2

OpC30-0819

OpC30-0820

OpC30-0821

OpC30-0822

OpC30-0823

OpC30-0824

OpC30-0825

ITO Error Messages

Error messages of agent processes

The distribution date file <distfile> contains an entry in an incorrect format: <line>. Solution: Remove the file. It will be generated when distributing next time.

Invalid type in distribution info file '<

x1

>': '<

x2

>';

The distribution date file <distfile> contains an incorrect entry. Solution:

Remove the file. It will be generated when distributing next time.

Can't read distribution info file '<

x1

>'.

The ITO distribution agent could not read the distribution date file

<distfile>. Solution: Remove the file. It will be generated when distributing next time.

Can't write distribution info file '<

x1

>'.

The ITO distribution agent could not create the distribution date file

<distfile>. This error message is qualified by another message giving more information.

Can't read config directory '<

x1

>' to merge new distributed elements.

OBSOLETE.

Can't read template file '<

x1

>'.

The ITO distribution agent could not read the template file <file> to merge the newly distributed configuration with the already available.

This error message is qualified by another message giving more information.

Merge of new distributed and already present templates failed.

The ITO distribution agent could not merge the newly distributed configuration with the already available. This error message is qualified by another message giving more information.

Can't write template file '<

x1

>'.

The ITO distribution agent could not write the merged template file

<file>. This error message is qualified by another message giving more information.

Chapter 2 107

OpC30-0826

OpC30-0827

OpC30-0828

OpC30-0829

OpC30-0830

OpC30-0831

OpC30-0832

ITO Error Messages

Error messages of agent processes

Internal error: Unknown template type '<

x1

>'.

Internal Error. Please report this to your HP Response Center.

Can't get status of filesystem '<

x1

>'.

The ITO distribution agent could not get the status of the file system the path <path> belongs to. This error message is qualified by another message giving more information.

Cluster server '<

x3

>'(<

x4

>) reported by node '<

x1

>'(<

x2

>) unknown.

The ITO distribution manager received a distribution request from a cluster client <client> but the corresponding cluster server <server> is not configured as ITO managed node. The distribution request cannot be mapped to the cluster server. Solution: Configure the cluster server as an

ITO managed node.

Hostname to IP resolution for '<

x1

>' (mode='<

x2

>', preferred='<

x3

>') failed.

OBSOLETE.

Can't connect to distribution manager on '<

x1

>'.

The ITO distribution agent could not connect to the distribution manager on the management server system <node>. This error message is qualified by another message giving more information.

Can't resolve hostname '<

x1

>' (gethostbyname(3N) failed).

The ITO distribution agent could not resolve the name of the management server <node> using the gethostbyname(3N) call. Either the name is wrong or not configured or maybe the name service is not accessible. This message is qualified by a system error message (errno) giving more information.

Can't copy file '<

x1

> to '<

x2

>'.

The ITO distribution agent couldn't copy or link a action/command/monitor script which is expected to be present on the managed node. This might be caused by either a manual removal of the source file on the managed node or by a modification of the corresponding file on the management server in a way that the time of last modification

108 Chapter 2

OpC30-0835

OpC30-0836

OpC30-0837

OpC30-0862

ITO Error Messages

Error messages of agent processes

of the file is earlier than the last distribution of this type of script.

Solution: Verify whether the file stated as source file in the error message exists; if not re-distribute with the 'Force update' option.

Otherwise check the last modification time using ls -l on the management server and update the current time using the command touch(1).

Detected invalid template(s). Please re-distribute only the templates once again with force-update

(if not just happened).

This message is sent, since the current template files on a managed node are not valid any longer. This may happen if:

• the syntax version of a template changed

• templates were somehow corrupted on the managed node

Redistributing templates with force update should solve this.

Can't get own identity from login context.

The ITO distribution agent failed to retrieve it's own identity from the inherited DCE login context. This login context is supposed to be established by the ITO Control agent. Check the ITO error logfile for error messages from the Control agent. This error message is qualified by another message giving more information.

Can't authenticate with DCE security service. Management server: '<

x1

>'.

Manager name: '<

x2

>'; own name: '<

x3

>'.

The ITO distribution agent failed to initialize an authenticated RPC connection to the management server <mgmt sv>. This error message is qualified by another message giving more information. The Message agent will send further data unauthenticated.

Access to the MPE console messages was disabled by an other program. The ITO console interceptor will exit now.

The ITO console interceptor for MPE terminated, because it could not read further messages from the kernel data segment in which console messages are stored. There can be only one reader on that data segment.

Chapter 2 109

OpC30-0913

OpC30-0955

OpC30-1001

OpC30-1002

OpC30-1003

OpC30-1004

ITO Error Messages

Error messages of agent processes

If another application (e.g. SYSMAN or EASYTIME) captured the message queue, there is no chance to obtain further data for the console interceptor.

The ITO Message Command is not configured on this system.

Contact your ITO Administrator to configure it.

This problem occurs when the administrator has not assigned (i.e.

configured) an opcmsg template to the agent on the managed node.

Another possibility is that the distribution of one or more templates to the node was interrupted or failed or has been delayed for some other reason. To solve this problem the administrator must check to see that an opcmsg template is assigned to the node (directly or as a template in a group) and then distribute templates to the node, using force update if necessary. If it is still not possible to distribute the templates it may help to stop and restart the management server processes and then distribute again.

Empty ITO Message Interceptor configuration.

The ITO message interceptor found that it's configuration file does not contain any active logfiles. It will keep on running but won't process any messages.

Can't initiate ITO configuration distribution

Could not start sub-process to control the distribution agent. No new templates, scripts or programs were distributed. The problem may be caused due to missing system resources (memory or process table). Try to distribute configuration data once again.

Can't open pipe to distribution agent

Can't open communication pipe between control agent and distribution agent. This may e.g. happen, if system resources (file descriptors) are exhausted. Distribution of new templates, scripts and programs failed.

Try to distribute the data once again.

Can't delete file <

x1

>

Internal error. Please contact your HP Response Center.

Can't fork process

110 Chapter 2

OpC30-1005

OpC30-1006

OpC30-1007

OpC30-1008

OpC30-1009

OpC30-1010

OpC30-1011

OpC30-1012

OpC30-1013

ITO Error Messages

Error messages of agent processes

No further process can be initiated, because system resources (process table or memory) are exhausted. Check, how much processes run on the appropriate node; maybe some of them are obsolete.

Can't lock file <

x1

>

Internal error. Please contact your HP Response Center.

Can't create directory <

x1

>

Internal error. Please contact your HP Response Center. Maybe the appropriate file system is full.

Can't move <

x1

> to <

x2

>

Internal error. Please contact your HP Response Center.

Can't move <

x1

> to <

x2

>

Internal error. Please contact your HP Response Center.

Can't open directory <

x1

>

Internal error. Please contact your HP Response Center. There is probably a resource problem (no further file descriptors available).

Can't open file <

x1

>

Internal error. Please contact your HP Response Center. There is probably a resource problem (no further file descriptors available).

Can't read file <

x1

>

Internal error. Please contact your HP Response Center.

Can't initiate reconnect of ITO Message Agent to the ITO

Message Receiver

The control agent cannot contact its message agent via RPC-call.

Therefore the message agent won't be informed, that it should forward buffered messages to the management station. Check, if the message agent or local location broker aborted on the managed node. Maybe it helps to restart the agent processes.

Can't set sid

Internal error. Please contact your HP Response Center.

Chapter 2 111

OpC30-1014

OpC30-1015

OpC30-1016

OpC30-1017

OpC30-1018

OpC30-1019

OpC30-1020

OpC30-1021

ITO Error Messages

Error messages of agent processes

Can't start ITO Control Agent

The control agent cannot fork itself, because system resources (memory or process table) are probably exhausted. Please check, if there are processes on the node, which are obsolete and could be killed.

Can't stat file <

x1

>

Internal error. Please contact your HP Response Center.

Can't stop all ITO Agent processes

Internal error. Please contact your HP Response Center. Please check, which ITO process could not be stopped. Try to stop the agents once again or do it manually.

Can't unlock ITO distribution lock file.

Internal error. Please contact your HP Response Center.

Can't write file <

x1

>

Internal error. Please contact your HP Response Center.

Errors occurred during the add of new configuration files for ITO.

Solve the problems and distribute the configuration again.

It was probably impossible, to move away current configuration data to backup location, because some files there, which are still accessed

(textfile busy), could not be overwritten. Refer to the trouble shooting section in the administrator's guide.

Can't add the new configuration for ITO.

It was probably impossible, to move away current configuration data to backup location, because some files there, which are still accessed

(textfile busy), could not be overwritten. Refer to the trouble shooting section in the administrator's guide.

Errors occurred during the replace of configuration files for ITO.

Solve the problems and distribute the configuration again.

112 Chapter 2

OpC30-1022

OpC30-1023

OpC30-1025

OpC30-1026

OpC30-1027

OpC30-1028

ITO Error Messages

Error messages of agent processes

It was probably impossible, to move away current configuration data to backup location, because some files there, which are still accessed

(textfile busy), could not be overwritten. Refer to the trouble shooting section in the administrator's guide.

Can't replace the configuration for ITO.

It was probably impossible, to move away current configuration data to backup location, because some files there, which are still accessed

(textfile busy), could not be overwritten. Refer to the trouble shooting section in the administrator's guide.

Can't connect to the ITO Message Agent

After starting the message agent, the control agent checks, if it came up successfully. Check, if the local location broker is running. Maybe it helps, to restart the agents.

Can't stop all ITO Agent processes

Internal error. Please contact your HP Response Center. Please check, which ITO process could not be stopped. Try to stop the agents once again or do it manually.

The ITO Distribution Agent reported an unexpected error.

The distribution agent aborted with an error. Check the error logfile for messages produced by the distribution agent. Try to distribute once again. Possibly the distribution agent couldn't be executed at all - check location and permissions.

The ITO Distribution Agent aborted.

The distribution agent aborted with an error. Check the error logfile for messages produced by the distribution agent. Try to distribute once again.

Errors occurred during distribution of the actions.

Solve the problems and distribute the actions again.

It was probably impossible, to move away current 'actions' to backup location, because some files there, which are still accessed (textfile busy), could not be overwritten. Refer to the trouble shooting section in the administrator's guide.

Chapter 2 113

OpC30-1029

OpC30-1030

OpC30-1031

OpC30-1032

OpC30-1033

OpC30-1034

OpC30-1035

OpC30-1036

OpC30-1037

ITO Error Messages

Error messages of agent processes

Errors occurred during distribution of the commands.

Solve the problems and distribute the commands again.

It was probably impossible, to move away current 'commands' to backup location, because some files there, which are still accessed (textfile busy), could not be overwritten. Refer to the trouble shooting section in the administrator's guide.

Errors occurred during distribution of the monitors.

Solve the problems and distribute the monitors again.

It was probably impossible, to move away current 'monitors' to backup location, because some files there, which are still accessed (textfile busy), could not be overwritten. Refer to the trouble shooting section in the administrator's guide.

Could not start ITO Distribution Agent

Could not start ITO distribution agent, because there are probably too little system resources (memory or process table).

Invalid directory name <

x1

> for delete directory.

Internal error. Please contact your HP Response Center.

Can't copy ITO nodeinfo file

Internal error. Please contact your HP Response Center.

Can't distribute the nodeinfo file for ITO.

Internal error. Please contact your HP Response Center.

Can't read pipe

Internal error. Please contact your HP Response Center. Distribute the configuration data once again.

Initialize of the ITO Control Agent failed.

Internal error. Please contact your HP Response Center.

Can't start ITO Agents

114 Chapter 2

OpC30-1038

OpC30-1039

OpC30-1040

OpC30-1041

OpC30-1042

OpC30-1043

OpC30-1044

ITO Error Messages

Error messages of agent processes

There are probably too little system resources (memory or process table), to start the ITO agents. Please check, how many processes are running on the appropriate node. Maybe some are obsolete and can be killed. Try to restart the ITO agents once again.

Unexpected data received from the ITO Distribution Agent

Internal error. Please contact your HP Response Center. Please check appropriate logfiles for errors produced by distribution agent and manager.

Can't inform the ITO Agents about the new configuration.

Internal error. Please contact your HP Response Center. A sub-process of the control agent could not get the process ids of the ITO agents. The agents could not be informed, that new configuration is available.

<

x1

> of subagent <

x2

> aborted; process did an exit <

x3

>

The process monitoring of the control agent found an agent process which has aborted due to an exit(2) call.

<

x1

> of subagent <

x2

> aborted; process got signal <

x3

>

The process monitoring of the control agent found an agent process which has aborted due to a kill(2) call.

<

x1

> (<

x2

>) aborted on MPE-node

Internal error. Please contact your HP Response Center. The process monitoring of the control agent found an agent process on MPE which has aborted. Please check the error logfile for messages produced by the aborted agent. Please check the output spool file of the ITO agents' job for program stack dumps.

cannot start self-monitoring on MPE-node

Could not start a sub-process of the control agent on an MPE-node, which does the self-monitoring. This may have been caused by missing system resources. Please, try to start the agents once again.

Can't connect to the ITO control agent. Check whether the local location broker runs on the node.

Chapter 2 115

OpC30-1045

OpC30-1046

OpC30-1047

OpC30-1048

OpC30-1049

OpC30-1050

OpC30-1055

ITO Error Messages

Error messages of agent processes

Can't connect to the ITO control agent. Check whether the local location broker is running on the node. Without the llbd/rpcd, the ITO-agents cannot work correctly.

The ITO control agent is currently not running.

The ITO control agent is currently not accessible via its RPC-interface.

Maybe, the agent is just initializing itself. Maybe, it isn't running. Try to connect to the control agent once again if you think that it is supposed to run. Especially on MPE-nodes, the init-phase can last some seconds.

Can't readlink file <

x1

>.

Problem since following a symbolic link. Please, check the concerning file and directories.

There are to many symbolic links in the link chain of file <

x1

>.

There are to many symbolic links in the link chain of the concerning file.

Cannot start ITO agent.

No Local Location Broker or DCE RPC Daemon is running on the system.

Cannot start ITO control agent. No Local Location Broker or DCE RPC

Daemon is running on the system. Please start the appropriate service.

Otherwise, the ITO-agents cannot work correctly.

Cannot start ITO agent.

Network communication problems occurred.

Cannot start ITO agent. Network communication problems occurred.

Please contact your system administrator. Maybe, the loopback interface of the concerning system is not running properly.

The opcagt command can not be used on this node.

It is not configured as ITO node.

The opcagt command can not be used on this node. The node is not configured as an ITO managed node.

The ITO control agent is currently not available but the agent job OPCAGTJ is running. Please try again later.

116 Chapter 2

OpC30-1056

OpC30-1057

OpC30-1058

OpC30-1059

OpC30-1060

OpC30-1071

ITO Error Messages

Error messages of agent processes

The ITO control agent is currently not available but the agent job

OPCAGTJ is running. Please try to connect once again later.

Could not generate temporary job-file from original file

<

x1

>.

Trying to use the original file to start the ITO agents

Internal error. Please contact your HP Response Center. Could not generate temporary job-file from original file opcagtj.bin.ovopc Trying to use the original jobfile to start the ITO-agents.

Job-stream of <

x1

> failed (used <

x2

> as job-stream facility).

<

x3

>

It failed to stream the ITO agents job with the customer defined job-stream facility. Tried to use the default facility instead.

Job-stream of <

x1

> probably failed (used <

x2

> as job-stream facility) (CI-warning <

x3

> <

x4

>).

run opcagt -status to check, whether the agents were started.

It probably failed to stream the ITO agents job with the customer defined job-stream facility. Run opcagt -status to check, whether the agents were started.

Directory <

x1

> could not be removed. Is it in use at the moment?

Please check to make sure that this directory is not being accessed from any shell or file manager and that no programs are running from this directory.

Directory <

x1

> could not be renamed to <

x2

>. Are they in use at the moment?

Please check to make sure that this directory is not being accessed from any shell or file manager and that no programs are running from this directory.

Can't initialize DCE security as '<

x1

>'. Security level:

'<

x2

>'.

Chapter 2 117

OpC30-1072

OpC30-1073

OpC30-1074

OpC30-1075

ITO Error Messages

Error messages of agent processes

The ITO control agent failed to initialize the DCE security related components. This includes a process login and RPC server initialization.

This error message is qualified by another message giving more information. Use the opc_sec_verify.sh utility on the managed node to verify a proper DCE configuration.

Can't login as agent administrator principal '<

x1

>'.

The ITO control agent could not log into DCE with it's primary identity and tried to use the administrative principal to recover the primary account. This login operation failed, too. If the account 'opc-agt'adm' is disabled, automatic password generation for the primary account cannot be performed. This error message is qualified by another message giving more information. Use the opc_sec_verify.sh utility on the managed node to verify a proper DCE configuration.

Can't recover primary account '<

x1

>'. Password generation failed.

The ITO control agent could not log into DCE with it's primary identity and tried to use the administrative principal to recover the primary account. This operation failed even if the login as 'opc-agt-adm' succeeded. This error message is qualified by another message giving more information. Use the opc_sec_verify.sh utility on the managed node to verify a proper DCE configuration.

Can't resolve local hostname '<

x1

>' with name service.

Using hostname for authentification.

The primary identity of an ITO agent within DCE contains the fully qualified hostname of the managed node. The ITO control agent failed to resolve the local hostname with the name service and will use the simple hostname. Possibly the login operation itself will fail. Always make sure that the local hostname can be resolved with the name service n any ITO node.

Authentication failure - the calling RPC client on host

'<

x1

>' requested incorrect security attributes.

Check error logfile on this host for more details.

The ITO control agent received an RPC request with insufficient security attributes and refused the request. This can happen if the known security level on the managed node doesn't match the one configured on

118 Chapter 2

OpC30-1094

OpC30-1095

OpC30-1096

OpC30-1097

OpC30-1100

ITO Error Messages

Error messages of agent processes

the management server - possibly due to a distribution failure. Also make sure that the calling management server is configured correctly in the opcinfo resp. mgrinfo file.

output of kill -0 differs from internal pids-table for index <

x1

>

Internal error. Please contact your HP Response Center. The buffer containing agents' process ids does not correspond to actual status. The mentioned index has following meaning: if it contains a 1, stored message agent pid doesn't correspond to reality, if it contains a 2, stored action agent pid doesn't correspond to reality, if it contains a 3, stored monitor agent pid doesn't correspond to reality, if it contains a 4, logfile encapsulator pid doesn't correspond to reality, if it contains a 5, stored

SNMP agent pid doesn't correspond to reality, if it contains a 6, stored msg interceptor pid doesn't correspond to reality.

copy of file <

x1

> to <

x2

> failed (cierr <

x3

>, add. info

<

x4

>)

Could not copy source-file to target-file on MPE. The reason for that is, that target-file could not be overwritten, because it is accessed.

Target-file keeps in place.

purge of file <

x1

> failed (cierr <

x2

>, add. info <

x3

>)

Could not purge file on MPE. The reason for that is, that the file is still accessed. It remains as it is.

The following files could not be replaced during

ITO distribution because they were accessed

(textfile busy). The old files will be used furthermore

List of files couldn't be replaced during configuration distribution. The files were still in access and therefor they were write-protected. These files remain unchanged. If it is really necessary to replace them, stop the agents and than do the distribution once again. This should help in most cases.

Can't execute action on node <

x1

>. The ITO management server sending the action request is not an authorized

ITO management server for the managed node.

Chapter 2 119

OpC30-1110

OpC30-1111

OpC30-1193

OpC30-1200

OpC30-1201

OpC30-1202

ITO Error Messages

Error messages of agent processes

The ITO control agent received an action request from an ITO management server not configured as 'action allowed' ITO manager.

Because only 'action allowed' ITO managers can execute actions on an

ITO agent the action request is ignored. Solution: Check the configured

'action allowed' ITO managers. This can be done by checking the mgrconf and opcinfo file of the ITO agent.

Can't copy ITO responsible manager configuration file.

An error occurred during the copy of the ITO responsible managers configuration file. This error message is qualified by another message giving more information.

Can't get name of ITO responsible manager configuration file.

Internal error. Please contact your HP Response Center.

Couldn't reconfigure subagent with ID <

x1

>.

The ITO Control agent failed to reinitialize the subagent <subagt>. This error message is qualified by another message giving more information.

Errors occurred during the read of the

ITO responsible manager configuration.

During the read of the ITO responsible manager configuration file some errors occurred. This error message is qualified by another message giving more information.

The ITO responsible manager configuration file <

x1

> contains more than one configuration. The configuration file is ignored.

The ITO responsible manager configuration file contains more than one configuration. Solution: Check the configuration file in the respmgrs directory on the ITO management system and correct the configuration.

Errors occurred during the convertion of the ITO responsible manager configuration file <

x1

>. The configuration file is ignored.

Internal error. Please contact your HP Response Center.

120 Chapter 2

OpC30-1203

OpC30-1300

OpC30-1301

OpC30-1302

OpC30-1303

OpC30-1304

OpC30-1305

ITO Error Messages

Error messages of agent processes

Warnings occurred during the read of the

ITO responsible manager configuration.

During the read of the ITO responsible manager configuration file some warnings occurred. This error message is qualified by another message giving more information.

Pipe control failed, error <

x1

>.

The fcntl(2) call to control the ECS agent pipe failed. This message is qualified by a system error message (errno) containing the cause of the error.

Pipe read failed, error <

x1

>.

The read(2) call to read the ECS agent pipe failed. This message is qualified by a system error message (errno) containing the cause of the error.

Select MSI queue file failed, error <

x1

>.

The select(2) system call for the ECS MSI queue file failed. This message is qualified by a system error message (errno) containing the cause of the error.

Cannot load data store <

x1

>.

The ECS data store file could not be loaded. Probably the fopen(3) call to open the data store file failed. This message is qualified by a system error message (errno) containing the cause of the error. Otherwise it is an HP internal ECS library error, in this case please contact your HP

Response Center.

Cannot load fact store <

x1

>.

The ECS fact store file could not be loaded. Probably the fopen(3) call to open the fact store file failed. This message is qualified by a system error message (errno) containing the cause of the error. Otherwise it is an HP internal ECS library error, in this case please contact your HP Response

Center.

Cannot open ECS engine log file <

x1

>.

The ECS engine log file could not be opened. This error message is qualified by another message providing more information.

Chapter 2 121

OpC30-1306

OpC30-1307

OpC30-1308

OpC30-1309

OpC30-1310

OpC30-1311

OpC30-1350

OpC30-1351

ITO Error Messages

Error messages of agent processes

Cannot open ECS engine trace file <

x1

>.

The ECS engine trace file could not be opened. This error message is qualified by another message providing more information.

Cannot open ECS engine event input log file <

x1

>.

The ECS engine event input log file could not be opened. This error message is qualified by another message providing more information.

Cannot open ECS engine event output log file <

x1

>.

The ECS engine event output logfile could not be opened. This error message is qualified by another message providing more information.

Cannot put message into EC event log file <

x1

>.

Put an ITO message into an ECS event logfile failed. This error message is qualified by another message providing more information.

No event types found to register.

The retrieved input event type value contains no event types for register.

Check the used circuit.

Non string type event found for register.

Non-string type events could not register, because ITO messages are strings. If it is not a string, it will be ignored.

MSI output is not enabled.

No event correlation can be done.

The MSI output is not enabled. This means that the opcecm/opceca cannot receive from the Message Stream Interface. Check that the

Server/Agent MSI is enabled in the ITO GUI. This can be done in the

[Actions:Server:Configure(Advanced Options)] or

[Actions:Node:Modify(Advanced Options...)] window, respectively.

Cannot open MSI. Return error code <

x1

>.

The opcif_open(3) call to open ECS MSI instance failed. Check that the event correlation MSI files in the OV temporary ITO directory do not exist; if necessary, remove them reported by opcecm: rm

/var/opt/OV/share/tmp/OpC/mgmt_sv/opceca[pq] reported by opceca: rm

/var/opt/OV/tmp/OpC/opceca[pq]

122 Chapter 2

OpC30-1352

OpC30-1353

OpC30-1354

OpC30-1355

OpC30-1356

OpC30-1357

OpC30-1358

OpC30-1359

OpC30-1360

OpC30-1400

ITO Error Messages

Error messages of agent processes

Cannot close MSI. Return error code <

x1

>.

The opcif_close(3) call to close the MSI instance failed.

Cannot get MSI pipe file descriptor. Return error code

<

x1

>.

The opcif_get_pipe(3) call to get the MSI pipe file descriptor failed.

Cannot register for ITO messages from the MSI.

The opcif_register(3) call to register for ITO messages from the MSI failed.

Cannot unregister for ITO messages from the MSI.

The opcif_unregister(3) call to unregister for ITO messages from the MSI failed.

Cannot create a registration condition.

The opcreg_create(3) call to initialize a registration condition failed.

Cannot set message type of registration condition.

The opcreg_set_str(3) call to set the message type field of a registration condition failed.

Cannot create empty ITO data type structure.

The opcdata_create(3) call to initialize an empty ITO data type structure failed.

Cannot read a message from the MSI. Return error code

<

x1

>.

The opcif_read(3) call to read a message from the MSI failed.

Cannot write a message back to MSI. Return error code

<

x1

>.

The opcif_write(3) call to write a message back to the MSI failed.

Cannot initialize the EC engine.

Chapter 2 123

OpC30-1403

OpC30-1410

OpC30-1420

OpC30-1421

OpC30-1422

OpC30-1430

OpC30-1431

OpC30-1401

OpC30-1402

ITO Error Messages

Error messages of agent processes

Internal ECS library error. If this occurs after a distribution, try to restart the ITO agent or distribute again. Otherwise please contact your

HP Response Center.

Cannot unload the EC engine.

Internal ECS library error. Please contact your HP Response Center.

Cannot create a new circuit from file <

x1

>.

Internal ECS library error. Probably a incorrect circuit was used. This can be checked by using the EventFlow Circuit Simulator. If no error is found, please contact your HP Response Center.

Cannot create event.

Internal ECS library error. Please contact your HP Response Center.

Cannot retrieve circuit variable "<

x1

>".

Internal ECS library error. Please contact your HP Response Center.

Wrong engine value type code. Type code: <

x1

>.

Internal error. Please contact your HP Response Center.

Cannot create engine value object of type <

x1

>.

Internal ECS library error. Please contact your HP Response Center.

Cannot copy engine value object.

Internal ECS library error. Please contact your HP Response Center.

Cannot input event to ECS circuit (ECS err code <

x1

>).

Internal ECS library error. Please contact your HP Response Center.

Event was rejected by the ECS circuit. It's probably older than specified in the circuit's maximum transit delay.

The message was rejected by the ECS engine because no circuit was interested in it. By the time the message was delivered to the engine, the message was probably older than specified in the circuit's maximum transit delay (an indicator for this is the difference between the messages creation time and its receive time).

124 Chapter 2

OpC30-1440

OpC30-1441

OpC30-1442

OpC30-1443

OpC30-1444

OpC30-1445

OpC30-1446

OpC30-1450

OpC30-1451

OpC30-1452

OpC30-1453

ITO Error Messages

Error messages of agent processes

Cannot create and initialize a new log message buffer.

Internal ECS library error. Please contact your HP Response Center.

Cannot create and initialize a new trace message buffer.

Internal ECS library error. Please contact your HP Response Center.

Cannot register an EC engine logging message buffer.

Internal ECS library error. Please contact your HP Response Center.

Cannot register an EC engine trace buffer.

Internal ECS library error. Please contact your HP Response Center.

Cannot set the EC engine log mask.

Internal ECS library error. Please contact your HP Response Center.

Cannot set the EC engine global trace mask.

Internal ECS library error. Please contact your HP Response Center.

Cannot set the EC engine global component mask.

Internal ECS library error. Please contact your HP Response Center.

Cannot initialize the encode/decode libraries internal data structures.

Internal ECS library error. Please contact your HP Response Center.

Encode/decode library has not been initialized.

Internal ECS library error. Please contact your HP Response Center.

Cannot register a "<

x1

>" event encoding and decoding module.

Internal ECS library error. Please contact your HP Response Center.

Encode/decode library has not been initialized or the module type "<

x1

>" was not known.

Internal ECS library error. Please contact your HP Response Center.

Chapter 2 125

OpC30-1454

OpC30-1455

OpC30-1456

OpC30-1457

OpC30-1458

OpC30-1459

OpC30-1460

OpC30-1462

OpC30-2000

OpC30-2050

ITO Error Messages

Error messages of agent processes

Module type "<

x1

>" already known by the encode/decode library.

Internal ECS library error. Please contact your HP Response Center.

Cannot initialize an encode/decode library event workspace.

Internal ECS library error. Please contact your HP Response Center.

Cannot set the default workspace pointer.

Internal ECS library error. Please contact your HP Response Center.

Cannot get event structure from the internal events memory pool.

Internal ECS library error. Please contact your HP Response Center.

Cannot extract a raw event from an encode/decode event object.

Internal ECS library error. Please contact your HP Response Center.

Cannot delete all allocated events.

Internal ECS library error. Please contact your HP Response Center.

Cannot add a type entry to the encode/decode type table.

Internal ECS library error. Please contact your HP Response Center.

Annotate request ("<

x1

>") timed out.

The ECS annotate node executed a command but it was not possible to pass back the results to the circuit due to a timeout. You can modify the timeout by changing the time-limit value for annotate-node definitions in the ECS designer.

NT API <

x1

>: WIN32API_ERROR; Thread ID <

x2

>.

Internal NT API error. Please contact your HP Response Center. Report the API function name and Thread ID.

Could not open the NT window sockets.

Internal NT API error. Please contact your HP Response Center.

126 Chapter 2

OpC30-2100

OpC30-2101

OpC30-2120

OpC30-2121

OpC30-2122

OpC30-2123

OpC30-2130

OpC30-2131

OpC30-2140

OpC30-2141

ITO Error Messages

Error messages of agent processes

NT API <

x1

>: Could not get a valid handle.

Internal NT API error. Please contact your HP Response Center. Report the API function name.

NT API <

x1

>: The handle for <

x2

> could not be closed.

Internal NT API error. Please contact your HP Response Center. Report the API function name and the resource.

NT API <

x1

>: Thread with Id <

x2

> failed to suspend.

Internal NT API error. Please contact your HP Response Center. Report the API function name and Thread ID.

NT API <

x1

>: Thread with Id <

x2

> failed to terminate.

Internal NT API error. Please contact your HP Response Center. Report the API function name and Thread ID.

NT API <

x1

>: Thread could not be created.

The system might have been overloaded when the API tried to create the thread. If this error reoccurs, Please contact your HP Response Center.

Report the API function name.

NT API <

x1

>: Thread with Id <

x2

> failed to resume.

Internal NT API error. Please contact your HP Response Center. Report the API function name and Thread ID.

NT API <

x1

>: Failed to get Mutex for <

x2

>.

Internal NT API error. Please contact your HP Response Center. Report the API function name.

NT API <

x1

>: Failed to release Mutex for <

x2

>.

Internal NT API error. Please contact your HP Response Center. Report the API function name.

NT API <

x1

>: Event <

x2

> could not be created.

Internal NT API error. Please contact your HP Response Center. Report the API function name and event name.

NT API <

x1

>: Event <

x2

> failed to be set.

Chapter 2 127

OpC30-2142

OpC30-2143

OpC30-2150

OpC30-2151

OpC30-2152

OpC30-2160

OpC30-2161

OpC30-2170

OpC30-2171

ITO Error Messages

Error messages of agent processes

Internal NT API error. Please contact your HP Response Center. Report the API function name and event name.

NT API <

x1

>: Event <

x2

> failed to be reset.

Internal NT API error. Please contact your HP Response Center. Report the API function name and event name.

NT API <

x1

>: Event <

x2

> does not exist.

Internal NT API error. Please contact your HP Response Center. Report the API function name and event name.

NT API <

x1

>: Can't create security descriptor.

Internal NT API error. Please contact your HP Response Center. Report the API function name.

NT API <

x1

>: Can't init security descriptor.

Internal NT API error. Please contact your HP Response Center. Report the API function name.

NT API <

x1

>: Can't set security descriptor.

Internal NT API error. Please contact your HP Response Center. Report the API function name.

NT API <

x1

>: Process could not be created.

Internal NT API error. Please contact your HP Response Center. Report the API function name.

NT API <

x1

>: Process with Id <

x2

> failed to terminate.

Internal NT API error. Please contact your HP Response Center. Report the API function name and process ID.

NT API <

x1

>: Can't open NT Registry Key <

x2

>.

Internal NT API error. Please contact your HP Response Center. Report the API function name and NT Registry Key name.

NT API <

x1

>: Can't query NT Registry Key <

x2

>.

Internal NT API error. Please contact your HP Response Center. Report the API function name and NT Registry Key name.

128 Chapter 2

ITO Error Messages

Error messages of manager processes

OpC40-0001

OpC40-0002

OpC40-0003

OpC40-0004

OpC40-0005

OpC40-0006

OpC40-0007

OpC40-0008

Error messages of manager processes

Can't open pipe <

x1

>.

Either the action manager pipe or the message manager pipe could not be opened. This message is qualified by a system error message (errno) giving more information.

Can't create pipe <

x1

>.

Either the action manager pipe or the message manager pipe could not be created. This message is qualified by a system error message (errno) giving more information.

Retrieving names of queues/pipes failed.

Internal Error. Please report this to your HP Response Center.

Opening of queues/pipes failed.

The ITO message receiver could not open a queue or pipe to the action manager or message manager. More information is contained in another part of the error message.

Can't close message queue.

The ITO message receiver is unable to close the message queue file used to pass messages to the ITO message manager. This error message is qualified by another message giving more information.

Can't write message queue.

The ITO message receiver is unable to pass a message through the message queue file to the ITO message manager. This error message is qualified by another message giving more information.

Internal error: Invalid request to assemble.

Internal Error. Please report this to your HP Response Center.

Initializing server failed.

Chapter 2 129

OpC40-0009

OpC40-0011

OpC40-0012

OpC40-0013

OpC40-0014

OpC40-0015

OpC40-0016

OpC40-0017

ITO Error Messages

Error messages of manager processes

The ITO message receiver encountered a problem during initialization as

RPC server. This error message is qualified by another message giving more information.

Server main loop terminated. Exiting.

The ITO message receiver's RPC main loop terminated abnormally. This error message is qualified by another message giving more information.

Assembly of fragmented request failed.

Internal Error. Please report this to your HP Response Center.

Can't close action request queue.

Internal Error. Please report this to your HP Response Center.

Can't put action request into queue.

The ITO message receiver is unable to pass a action response through the message queue file to the ITO action manager. This error message is qualified by another message giving more information.

Can't unregister message receiver.

The ITO message receiver couldn't unregister during shutdown. This error message is qualified by another message giving more information.

Can't create server thread.

The ITO message receiver couldn't start a thread executing the Sun RPC server loop. This error message is qualified by another message giving more information.

Sun RPC server main loop terminated.

The ITO message receiver's Sun RPC server loop terminated abnormally.

This error message is qualified by another message giving more information.

Initializing Sun RPC server failed.

The ITO message receiver encountered a problem during initialization as

Sun RPC server. This error message is qualified by another message giving more information.

130 Chapter 2

OpC40-0018

OpC40-0019

OpC40-0101

OpC40-0102

OpC40-0103

OpC40-0104

OpC40-0105

ITO Error Messages

Error messages of manager processes

Can't register Sun RPC server.

The ITO message receiver couldn't register at the Sun RPC portmapper.

This error message is qualified by another message giving more information.

Can't read server registration file.

The ITO message receiver couldn't read the Common Agent server registration file. Check existence and permissions of this file. This error message is qualified by another message giving more information.

Inconsistent distribution package data.

Internal error. Please report this to your HP Response Center.

Re-distribution of the selected components may help.

Invalid distribution type <

x1

> got from Distribution

Agent.

Internal error. Please report this to your HP Response Center.

Re-distribution of the selected components may help.

No more free entries of package table.

More than five distribution agents are trying to access the new configuration simultaneously. The distribution agents will retry several times; if they fail, a corresponding message will also be sent. In the latter case, you have to re-start the agents on that managed node (re-starting triggers the distribution agent, too).

Distribution package for system <

x1

> cleaned, because no new data request of the Distribution

Agent for more than 10 minutes.

The distribution agent on managed node did not retrieve all provided distribution packages. It might have terminated due to unexpected interrupt or the network connection has been broken. Solution: Verify the network connection is okay; then re-distribute the entire configuration (and monitor/actions/commands binaries) to the managed node.

No ITO version found in file <

x1

> supporting

OS version <

x2

> of Managed Node <

x3

>.

Chapter 2 131

OpC40-0106

OpC40-0107

OpC40-0108

OpC40-0109

ITO Error Messages

Error messages of manager processes

The managed node has an ITO version installed which is no longer available on the Management server. An appropriate ITO version cannot be found which supports the OS version of the Managed node. Solutions: a. Re-install the appropriate ITO version on the management server using ovinstall(1).

b. Update/downgrade the OS of the managed node to an OS version currently supported by ITO.

ITO version related directory <

x1

> not found, even if it is mentioned in corresponding requirements file.

Internal error. Please report this to your HP Response Center. The requirements file contains information that is not installed on the management server. Remove the corresponding entry from the requirements file

/usr/OV/databases/OpC/mgd_node/vendor/<arch>/require.dat.

Invalid link-ID <

x1

> got from Distribution Agent;

Note, link-ID range 0 - <

x2

>.

Internal error. Please report this to your HP Response Center.

Re-distribution of the selected components may help.

Installed ITO version <

x1

> on Managed Node

<

x3

> (architecture <

x4

>) adapted to <

x2

> to get vendor's actions/cmds/monitor data.

The ITO version installed on the managed node is no longer available on the management server, but another ITO version also supports the OS version of the managed node. Therefore the related ITO information will be used instead. Solution: Update the installed ITO version on that managed node to avoid this warning.

Managed Node <

x1

> (architecture <

x2

>) stops current distribution request due to interrupt; therefore packages will be cleaned up.

The distribution agent got an interrupt in the middle of the distribution sequence and exited appropriately (for example, 'Stop ITO Agents' issued). The remaining data will be distributed when re-starting the ITO agents.

132 Chapter 2

OpC40-0110

OpC40-0111

OpC40-0112

OpC40-0113

OpC40-0114

OpC40-0115

ITO Error Messages

Error messages of manager processes

Too few table entries are available to save data for

Managed Node <

x1

>; new entries have been made in the meantime in the action/cmd/monitor directories which have not been counted during the distribution init phase.

During the distribution request new files have been placed in

/usr/OV/databases/OpC/mgd_node/customer/<arch>/{actions/commands/ monitor} directories. Solution: Re-distribute the selected components once more.

Terminated due to signal. Possibly some data has not been transmitted to requesting nodes.

The distribution managers stopped due to a receipt signal. If the distribution manager was currently submitting data to the distribution agents, a corrupted version will be left on the managed nodes. The distribution agents will also generate an error message that the distribution manager has been gone. Solution: After restarting the ITO managers, re-distribute the selected components to those managed nodes which issued the warning about the distribution agent.

Maybe ITO fileset no longer installed on the Management

Server supporting the architecture of Managed Node <

x1

>.

The ITO distribution manager is unable to determine the system requirements for a managed node. The requirement specification file was not found. Check whether the corresponding fileset is still installed.

Can't update node status after distribution.

The ITO distribution manager is unable to update the status of the managed node in the database after a successful distribution. This error message is qualified by another message giving more information.

Can't add node to IP address mapping table.

The ITO distribution manager is unable to add a newly configured managed node to the IP address mapping table. This error message is qualified by another message giving more information.

Invalid limit for parallel distribution requests specified: '<

x1

>'. Valid id <

x2

> - <

x3

>. Using <

x4

> as limit.

Chapter 2 133

OpC40-0116

OpC40-0117

OpC40-0118

OpC40-0119

OpC40-0120

OpC40-0121

ITO Error Messages

Error messages of manager processes

Internal Error. Please report this to your HP Response Center.

Can't execute ITO distribution TCP socket server '<

x1

>'.

The exec(2) system call failed.

The ITO distribution manager is unable to start the TCP socket server process to serve a requesting distribution agent. Check whether the program opctss exists in the ITO management server binary, and whether the program is executable.

ITO distribution TCP socket server failed with exit code

'<

x1

>'.

The TCP socket server subprocess made an unexpected exit. Check the opcerror logfile for an corresponding entry reported by the opctss program.

Can't kill ITO distribution TCP socket server.

The ITO distribution manager is unable to terminate the TCP socket server after successful configuration distribution to a managed node.

This error message is qualified by a system error text (errno). Internal

Error. Please report this to your HP Response Center.

Can't create pipe.

The ITO distribution manager is unable to create a pipe to communicate with the TCP socket server subprocess. The pipe(2) system call failed.

This error message is qualified by a system error text (errno).

Waiting for port number to be returned by ITO distribution TCP socket server timed out.

The ITO distribution manager receives no response from the started

TCP socket server subprocess. Check whether a process executing

'opctss' or <defunct> exists, having the ITO distribution manager

'opcdistm' as the parent process. Check the opcerror logfile for a corresponding entry reported by the opctss program. Please report this to your HP Response Center.

ITO distribution TCP socket server didn't return port number.

Internal Error. Please report this to your HP Response Center.

134 Chapter 2

OpC40-0122

OpC40-0123

OpC40-0124

OpC40-0125

OpC40-0126

OpC40-0127

OpC40-0128

ITO Error Messages

Error messages of manager processes

ITO distribution TCP socket server didn't return a valid port number: '<

x1

>'.

Internal Error. Please report this to your HP Response Center.

Internal error: Reading TSS pipe returns 0.

Internal Error. Please report this to your HP Response Center.

Can't write distribution file name to ITO distribution

TCP socket server.

The ITO distribution manager is unable to pass data to the TCP socket server subprocess through a pipe. Probably the TCP socket server aborted. Check the opcerror logfile for a corresponding entry reported by the opctss program.

Can't terminate ITO distribution TCP socket server.

The ITO distribution manager is unable to terminate the TCP socket server subprocess. This error message is qualified by another message giving more information.

Can't start ITO distribution TCP socket server.

The ITO distribution manager is unable to start the TCP socket server subprocess. This error message is qualified by another message giving more information.

Can't inform ITO distribution TCP socket server about next package.

The ITO distribution manager is unable to pass controlling data to the

TCP socket server subprocess. This error message is qualified by another message giving more information.

Managed Node <

x1

> (architecture <

x2

>) aborts current distribution request. Distribution agent could not connect to ITO distribution TCP socket server.

The ITO distribution agent running on the managed node <mgd_node> aborts a requested configuration distribution. The distribution agent could not connect the TCP socket server running on the management server. Check the opcerror logfile for an corresponding entry reported by the opctss program. Check the opcerror logfile on the managed node for a corresponding entry reported by the distribution agent.

Chapter 2 135

OpC40-0129

OpC40-0130

OpC40-0131

OpC40-0132

OpC40-0133

OpC40-0134

ITO Error Messages

Error messages of manager processes

Managed Node <

x1

> (architecture <

x2

>) aborts current distribution request due to an unknown failure.

The ITO distribution agent running on the managed node <mgd_node> aborts a requested configuration distribution. An RPC execution by the distribution manager failed for unknown reason. Check the opcerror logfile for a corresponding entry reported by the distribution manager.

Can't read distribution list file '<

x1

>'.

The ITO distribution manager could not read the distribution list file

<distlist> containing information about the data to distribute. This error message is qualified by another message giving more information.

Rejecting distribution request from an ITO 1.* agent

'<

x1

>'.

The ITO distribution manager received a distribution request from a managed node running an older ITO version. Due to configuration file syntax enhancements the old agents will not be able to process the new configuration data, But they will continue to work with the old configuration. To distribute new configuration you have to upgrade the managed node to the latest version using the ITO admin GUI.

Can't pass distribution request to ovoareqsdr - not running.

The ITO distribution manager could not redirect a distribution request a managed node running on a cluster client to the cluster server because it could not send a distribution request to the control manager. Check the local error logfile for a reason why the control manager is down and restart the ITO server processes.

Can't pass distribution request to ovoareqsdr - can't write queue.

The ITO distribution manager could not redirect a distribution request a managed node running on a cluster client to the cluster server because it could not send a distribution request to the control manager. This error message is qualified by another message giving more information.

Can't open ovoareqsdr queue.

136 Chapter 2

OpC40-0135

OpC40-0136

OpC40-0137

OpC40-0138

OpC40-0139

OpC40-0140

OpC40-0141

ITO Error Messages

Error messages of manager processes

The ITO distribution manager could not connect to the control manager at start-up. Check the local error logfile for a reason why the control manager is down and restart the ITO server processes.

Can't pass request to ITO communication manager.

The ITO distribution manager could not forward a command to the communication manager. This error message is qualified by another message giving more information.

Can't execute ITO communication manager '<

x1

>'. The exec(2) system call failed.

The ITO distribution manager could not start the communication manager. This error message is qualified by another message giving more information.

ITO communication manager failed with exit code '<

x1

>'.

The ITO communication manager terminated abnormally with the exit code <ecode>. Check the local error logfile for a reason why the communication manager aborted. It will be restarted on demand later.

Can't start ITO communication manager.

The ITO distribution manager could not start the communication manager. This error message is qualified by another message giving more information.

Can't set heartbeat polling status of managed node

'<

x1

>'.

The reporting process could not modify the heartbeat polling behavior for the managed node <node>. This error message is qualified by another message giving more information.

Invalid agent status command arrived for node '<

x1

>':

<

x2

>.

Internal error. Please report this to your HP Response Center.

Agent status command arrived for unknown node

'<

x1

>'(<

x2

>).

Chapter 2 137

OpC40-0142

OpC40-0201

OpC40-0202

OpC40-0203

OpC40-0204

ITO Error Messages

Error messages of manager processes

The distribution manager received a request to update the ITO agent status for the managed node <node>. This node is not configured in ITO.

First add the node to the ITO node bank using the admin GUI. If the node is already contained in the node bank the manager processes were not informed automatically. In this case restart the ITO manager processes.

Agent '<

x1

>' requested configuration but authentication checks failed. Distributing only node configuration file if available.

The distribution manager received a distribution request from a managed node with insufficient security attributes. If available only the managed node's internal configuration has been distributed to allow the agent to reconfigure and try again. This can happen if this was the first distribution request after increasing the node's security level.

Can't connect to the ITO Management Server processes.

Check whether the processes are running.

Check whether the processes are running. It is not possible to connect the ITO display manager. Check whether the processes are running, the llbd or rpcd is running and there are no network problems. Restart the

ITO managers if necessary.

Connection to the ITO Management Server lost.

Check whether the processes are running.

Check whether the processes are running. A process lost the connection the ITO display manager. Check whether the processes are running, the llbd or rpcd is running and there are no network problems. Restart the

ITO managers if necessary.

NCS / DCE RPC error in ITO Display Manager.

<

x1

>

An error occurred during the rpc connection to the ITO display manager.

More information is contained in another part of the error message.

The ITO Action Manager is not running.

The ITO action manager is currently not running but it should. Check the error log file to get more information and restart the ITO manager processes.

138 Chapter 2

OpC40-0205

OpC40-0206

OpC40-0207

OpC40-0208

OpC40-0209

OpC40-0210

OpC40-0211

OpC40-0212

ITO Error Messages

Error messages of manager processes

The ITO Control Manager is not running.

The ITO control manager is currently not running but it should. Check the error log file to get more information and restart the ITO manager processes.

Get operator information from database failed.

An error occurred during the database access to get information about

ITO operators. More information is contained in another part of the error message.

Get ITO node configuration from database failed.

An error occurred during the database access to get information about the ITO node configuration. More information is contained in another part of the error message.

Get message information from database failed.

An error occurred during the database access to get information about an

ITO message. More information is contained in another part of the error message.

Get operator configuration from database failed.

An error occurred during the database access to get information about the ITO operator configuration. More information is contained in another part of the error message.

Check operator change flag in database failed.

An error occurred during the database access to check the change flag of an ITO operator. More information is contained in another part of the error message.

Check realm change flag in nodebank failed.

An error occurred during the database access to check the realm change flag of an ITO operator. More information is contained in another part of the error message.

Check desktop change flag in nodebank failed.

Chapter 2 139

OpC40-0213

OpC40-0214

OpC40-0215

OpC40-0216

OpC40-0217

OpC40-0218

OpC40-0219

OpC40-0220

ITO Error Messages

Error messages of manager processes

An error occurred during the database access to check the desktop change flag of an ITO operator. More information is contained in another part of the error message.

Cannot open queue <

x1

>.

Can not open an ITO display manager queue. More information is contained in another part of the error message.

Cannot create pipe <

x1

>. mkfifo(2) failed.

Can not create an ITO display manager pipe. This message is qualified by a system error message (errno) giving more information.

Cannot open pipe <

x1

>. open(2) failed.

Can not open an ITO display manager pipe. This message is qualified by a system error message (errno) giving more information.

Cannot write to queue <

x1

>.

Can not write to ITO display manager queue. More information is contained in another part of the error message.

Can't connect to the ITO Management Server processes on node <

x1

>. Check whether the processes are running.

The reporting process failed to connect to the ITO management server processes. Verify that all processes are running using the opcsv(1m) command. If necessary re-start the server processes by opcsv -start.

Display receiver of user <

x1

> is not reachable and will be logged off.

The display manager has lost the connection to the operator user interface. The reason was probably an abnormal abort of the UI.

License check for node <

x1

> failed.

The ITO management server processes couldn't satisfy a managed node license request for node <node> due to database problems. This error message is qualified by another message giving more information.

Number of entries in MCE queue exceeds max_entries; disconnecting <

x1

>.

140 Chapter 2

OpC40-0221

OpC40-0222

OpC40-0223

OpC40-0256

OpC40-0257

OpC40-0258

ITO Error Messages

Error messages of manager processes

A connected ITO message stream interface client associated with the interface <if> is registered to receive ITO message change events but the action response queue contains the maximum number of entries. Make sure the application works properly and restart it.

MSI client exited without disconnect from interface

<

x1

>.

A connected ITO message stream interface client associated with the interface <if> terminated without disconnecting properly. Possibly the application crashed.

Cannot read user domain of registered user condition for user <

x1

> of MSI instance <

x2

>.

A connected ITO message stream interface client associated with the interface <if> is registered as user <user>. The corresponding conditions could not be loaded from the database.

Number of entries in Application Response queue exceeds max_entries; disconnecting <

x1

>.

A connected ITO message stream interface client associated with the interface <if> is registered to receive ITO action responses but the action response queue contains the maximum number of entries. Make sure the application works properly and restart it.

<

x1

> aborted; process did an exit <

x2

>.

The ITO self monitoring detected that an ITO manager process did an unexpected abort. Check the errorlog file to get more error information and restart the ITO manager processes.

<

x1

> aborted; process got signal <

x2

>.

The ITO self monitoring detected that an ITO manager process did an unexpected abort because it got a signal. Check the errorlog file to get more error information and restart the ITO manager processes.

Connect to database failed.

An ITO process is not able to connect to the database. Check whether the database is running. If you have set database environment variables

(Oracle: ORACLE_HOME, ORACLE_SID, NLS_LANG), check if they

Chapter 2 141

OpC40-0259

OpC40-0260

OpC40-0261

OpC40-0263

OpC40-0264

OpC40-0265

OpC40-0266

ITO Error Messages

Error messages of manager processes

are correct. If the environment variables are not set, the values in the

OpenView database configuration file /etc/opt/OV/share/conf/ovdbconf are used. Check, if they are correct.

The database server is probably down; cannot connect;

An ITO process is not able to connect to the database. Check whether the database is running. If you have set database environment variables

(Oracle: ORACLE_HOME, ORACLE_SID, NLS_LANG), check if they are correct. If the environment variables are not set, the values in the

OpenView database configuration file /etc/opt/OV/share/conf/ovdbconf are used. Check, if they are correct.

Main controlling loop aborted.

The ITO control manager's main loop terminated unexpectedly. This error message is qualified by another message giving more information.

Contents of control manager queue is corrupt.

The ITO control manager queue contains corrupt data information. Stop the ITO manager processes on the management server, delete the control manager queue ( /usr/OV/tmp/OpC/mgmt_sv/ctrlq ) and restart the ITO manager processes.

Can't load nodebank.

An error occurred during the access to the database to get information about the configured ITO nodes. More information is contained in another part of the error message.

Can't update internal object table.

An error occurred during the update of the heart beat polling configuration. More information is contained in another part of the error message.

Get database maintenance information failed.

An error occurred during the access to the database to get information about the configured ITO database maintenance. More information is contained in another part of the error message.

Download history messages failed.

142 Chapter 2

OpC40-0267

OpC40-0268

OpC40-0269

OpC40-0270

OpC40-0271

OpC40-0272

OpC40-0273

ITO Error Messages

Error messages of manager processes

An error occurred during the download of the history messages. More information is contained in another part of the error message.

Download audit messages failed.

An error occurred during the download of the audit log. More information is contained in another part of the error message.

Check number of messages in the database failed.

An error occurred during the access to the database to check the number of entries in the message and audit log tables. More information is contained in another part of the error message.

Download of history messages started.

The ITO administrator can schedule the download of history messages to flat files. Every day at the specified time the history messages will be downloaded.

Download of audit messages started.

The ITO administrator can schedule the download of audit entries to flat files. Every day at the specified time the audit entries will be downloaded.

Invalid time specified to download history messages; download history messages will not be done.

The database contains an invalid time for download history messages of the ITO database maintenance. Check the time on the window in the

ITO admin GUI and set it to a correct value.

Invalid time specified to download audit messages; download audit messages will not be done.

The database contains an invalid time for download audit log of the ITO database maintenance. Check the time on the window in the ITO admin

GUI and set it to a correct value.

Invalid interval specified to check number of messages in the database.

The database contains an invalid interval. Check the interval for the node in the ITO admin GUI and set it to a correct value.

Chapter 2 143

OpC40-0274

OpC40-0275

OpC40-0280

OpC40-0281

OpC40-0282

OpC40-0283

ITO Error Messages

Error messages of manager processes

History messages downloaded.

The history messages were successfully downloaded to flat files and can now be archived.

Audit messages downloaded.

The audit entries were successfully downloaded to flat files and can now be archived.

Number of <

x1

> messages in active-message-table is near to limit <

x2

>.

A lot of messages in the active messages table leads to a bad performance. You should acknowledge some no longer needed messages.

This error is generated when the number of messages reaches 95% of the maximum value that is set in Actions->Utilities->Database

Maintenance.

Number of <

x1

> messages in active-message-table reached limit <

x2

>.

A lot of messages in the active messages table leads to a bad performance. You should acknowledge some no longer needed messages.

This error is generated when the number of messages reaches the maximum value that is set in Actions->Utilities->Database

Maintenance.

Number of <

x1

> messages in history-message-table is near to limit <

x2

>.

A lot of messages in the history messages table consumes a lot of disk space and leads to a long time when loading the history messages browser. You should download the history messages on a regular basis.

The download of history messages can be scheduled in the administrator user interface from the Actions->Utilities->Database Maintenance...

menu.

Number of <

x1

> messages in history-message-table reached limit <

x2

>.

A lot of messages in the history messages table consumes a lot of disk space and leads to a long time when loading the history messages browser. You should download the history messages on a regular basis.

144 Chapter 2

OpC40-0284

OpC40-0285

OpC40-0290

OpC40-0291

OpC40-0292

OpC40-0293

OpC40-0294

ITO Error Messages

Error messages of manager processes

The download of history messages can be scheduled in the administrator user interface from the Actions->Utilities->Database Maintenance...

menu.

Number of <

x1

> messages in audit-message-table is near to limit <

x2

>.

A lot of entries in the audit table consumes a lot of disk space and leads to a long time when generating an audit report. You should download the audit entries on a regular basis. The download of audit entries can be scheduled in the administrator user interface from the

Actions->Utilities->Database Maintenance... menu.

Number of <

x1

> messages in audit-message-table reached limit <

x2

>.

A lot of entries in the audit table consumes a lot of disk space and leads to a long time when generating an audit report. You should download the audit entries on a regular basis. The download of audit entries can be scheduled in the administrator user interface from the

Actions->Utilities->Database Maintenance... menu.

Reading name for <

x1

> from configuration failed.

Internal Error. Please report this to your HP Response Center.

Cannot open queue <

x1

>.

Can not open the ITO control manager queue. More information is contained in another part of the error message.

Cannot read from control manager queue.

Can not read from the ITO control manager queue. More information is contained in another part of the error message.

Cannot create pipe <

x1

>. mkfifo(2) failed.

Can not create the ITO control manager pipe. This message is qualified by a system error message (errno) giving more information.

Cannot open pipe <

x1

>. open(2) failed.

Can not open the ITO control manager pipe. This message is qualified by a system error message (errno) giving more information.

Chapter 2 145

OpC40-0307

OpC40-0308

OpC40-0331

OpC40-0362

OpC40-0363

OpC40-0364

ITO Error Messages

Error messages of manager processes

Can't connect to the DCE rpcd/dced. The daemon doesn't seem to run.

Cannot start the ITO manager processes on the management server. No llbd or rpcd is running. Start one of the daemons.

Can't connect to the DCE rpcd/dced.

Can not start the ITO manager processes on the management server.

There are some network communication problems. More information is contained in another part of the error message.

Can't connect to OpenView daemons. Starting up standalone.

The ITO control manager could not connect to the OpenView daemons.

Verify whether the OV processes are running using the ovstatus(1m) command. The ITO processes start-up in standalone mode. The controlling OV commands like ovstop(1m) and ovstatus(1m) won't work then. Before re-starting the ITO server processes using these commands or opcsv(1m) first shut down the running processes using opcctlm -stop.

Cannot become primary manager. Please check mgrconf of the node.

The ITO control agent received a request to change the primary ITO manager from an ITO management server not configured as secondary

ITO manager. Because only secondary ITO managers are allowed to become the primary ITO manager for an ITO agent the request is ignored. Solution: Check the configured secondary ITO managers. This can be done by checking the mgrconf and opcinfo file of the ITO agent.

ITO Server Initialization Complete. All processes started.

This message is written to the logfile, when the control manager has successfully passed all steps to initialize the ITO server processes. The message can be used as time-stamp for an ITO server start-up.

ITO servers terminated.

This message is written to the logfile, since the control manager finishes an ITO session on the management server. The message can be used as time-stamp for an ITO server shutdown.

146 Chapter 2

OpC40-0369

OpC40-0370

OpC40-0371

OpC40-0372

OpC40-0373

OpC40-0374

ITO Error Messages

Error messages of manager processes

Internal error: Can't read job from queue. Status: <

x1

>.

Internal error. Please report this to your HP Response Center.

Internal error: Can't write job into queue. Status: <

x1

>.

Internal error. Please report this to your HP Response Center.

Execution of job failed.

Processing of an internal DB maintenance request (history or audit download) or process handling request (like server start and stop) or config change request (like informing the managers about changing or adding a node, setting up a notification service etc.) failed. In case of an

DB maintenance request, check, if the opchistdwn or opcauddwn programs exist and have right permissions. In the other cases, restarting the management server processes manually may help. This error message is qualified by another message giving more information.

Can't connect to OpenView process manager daemon.

The ITO control manager could not connect to the OpenView process manager daemon and will start up independently. This will prevent commands like ovstop and ovstatus from operating on ITO processes correctly.

Can't resolve local hostname '<

x1

>' with name service.

Using hostname for authentification.

The primary identity of an ITO management server within DCE contains the fully qualified hostname of the managed node. The ITO control manager failed to resolve the local hostname with the name service and will use the simple hostname. Possibly the login operation itself will fail.

Always make sure that the local hostname can be resolved with the name service on any ITO node.

There are <

x1

> nodes configured with a security level higher than <

x2

>.

This requires the control manager to run in authenticated mode but it is not logged into DCE.

The ITO control manager detected that the current nodebank contains some managed nodes configured for authenticated RPC. The control manager failed to determine whether it's own principal is configured at all which indicates whether any DCE security is desired. If

Chapter 2 147

OpC40-0404

OpC40-0405

OpC40-0416

OpC40-0424

OpC40-0433

OpC40-0436

ITO Error Messages

Error messages of manager processes

authenticated RPC is desired certain ITO configuration within the DCE security service is required. Use the opc_sec_register.sh utility to configure the ITO management server.

Message agent on node <

x1

> is not running.

The self-monitoring detected that the ITO message agent on the managed node <node> terminated unexpectedly. Check the ITO error logfile on that node and re-start the agents using the GUI or opcragt(1m).

Control agent on node <

x1

> isn't running.

The self-monitoring detected that the ITO control agent on the managed node <node> does not run. This can happen if the managed node has been added to the ITO node bank without installing the agent software.

Otherwise check the ITO error logfile on that node and re-start the agents using opcagt -start. You cannot access the ITO agent remotely if the Control agent is down.

Update configuration for monitor loop failed.

Internal Error. Please report this to your HP Response Center.

Cannot perform configuration request for subagents

(index <

x2

>) on node <

x1

>.

If the node is an NT node that you have just installed this is no error. The agent will download this configuration data after the installation during the startup.

The llbd/rpcdaemon on node <

x1

> is down.

The request sender detected that the llbd/rpcd on the target node is down. Check the llbd/rpcd on the target node and restart it if necessary.

Node <

x1

> is probably down. Even to contact it with ping-packages failed.

The request sender was unable to perform the heartbeat monitoring.

Check for network problems between the Management Server and the target node. Additional causes may be a very short HBP interval, high work load or a congested network.

148 Chapter 2

OpC40-0437

OpC40-0462

OpC40-0463

OpC40-0464

OpC40-0465

OpC40-0489

ITO Error Messages

Error messages of manager processes

Heartbeat-monitoring for the following nodes could not be done in time:

<

x1

>

The request sender could not perform the required heartbeat monitoring as configured for the listed nodes. This can be caused by a very short

HBP interval and high work load causing the request sender to be unable to execute the HBP operation in the configured interval.

Configure the HBP interval as small as necessary but as long as possible for performance improvement.

Control agent on node <

x1

> is now running.

The request sender detected that the ITO control agent on the target node is up again. You can acknowledge all messages reporting communication problems related to this node.

General Common Agent error. Check agent and server logfile for more info.

The ITO control agent returned an error condition when executing this request. Check the Managed Node ITO error log file for related error messages.

Agent authorization error. The ITO Control agent refused this request.

The ITO control agent rejected this request. Probably the local

Management server is not configured to be responsible. Verify the opcinfo and mgrconf file on the managed node.

General error during Common Agent bulk transfer.

Check agent and server logfile for more info.

A general error occurred during processing of a Common Agent bulk transfer. Most likely it is related to file access or socket transfer problems. Check the Managed Node as well as the Management Server

ITO error log file for related error messages.

The request was cancelled before its execution.

A request was not sent to an ITO managed node but cancelled on theserver instead. For example, this can happen, if the stop_action button was pressed, and the request could be caught on the server.

Chapter 2 149

OpC40-0498

OpC40-0499

OpC40-0568

OpC40-0570

OpC40-0600

OpC40-0601

OpC40-0602

ITO Error Messages

Error messages of manager processes

Could not send this request as the agent

'<

x1

>' was not found in the ITO node bank or it does not have an ITO agent installed.

The request sender could not forward a request to the target node

<node> because the node could not be found in internal tables. This can happen if this node has been added using the GUI but no agent software has been installed from this Management Server. If the managed node has agent software installed from another server you can mark this node as installed by executing opcsw -i <node>.

Could not send this request to node '<

x1

>' as operation type is unsupported.

Internal Error. Please report this to your HP Response Center.

execution of notification service <

x1

> failed

The program or script that you configured for the trouble ticket or notification service interface could not be started. Please check if the file exists and has sufficient permissions (need execute permission at least for opc_op). If it is a shell-script, you may need to add a line at the top such as #!/usr/bin/sh to tell the shell which shell to run the script in.

notification service <

x1

> aborted; it did an exit <

x2

>

The notification service script has exited with an exit code greater than

256. The exact exit code is shown in the error message.

Can't add ITO message to the database.

It is not possible to add an ITO message to the database. More information is contained in another part of the error message.

Can't get message groups from the database.

An error occurred during the database access to get information about the configured ITO message groups. More information is contained in another part of the error message.

Can't get regroup conditions from the database.

An error occurred during the database access to get information about the configured ITO regroup conditions. More information is contained in another part of the error message.

150 Chapter 2

OpC40-0603

OpC40-0604

OpC40-0605

OpC40-0606

OpC40-0607

OpC40-0608

OpC40-0609

OpC40-0613

ITO Error Messages

Error messages of manager processes

Can't convert the regroup conditions into internal form.

An error occurred during the conversion of the regroup conditions from the database into an internal form. More information is contained in another part of the error message.

Can't get nodebank configuration from the database.

An error occurred during the database access to get information about the configured ITO nodes. More information is contained in another part of the error message.

Can't get trouble ticket configuration from the database.

An error occurred during the database access to get information about the configured ITO trouble ticket interface. More information is contained in another part of the error message.

Can't get notification configuration from the database.

An error occurred during the database access to get information about the ITO notification configuration. More information is contained in another part of the error message.

Can't get node configuration from the database.

An error occurred during the database access to get information about an

ITO node. More information is contained in another part of the error message.

Can't add annotation for ITO message to the database.

An error occurred during the database access to add an annotation. More information is contained in another part of the error message.

Can't acknowledge ITO message in the database.

An error occurred during the database access to acknowledge an ITO message. More information is contained in another part of the error message.

Cannot open queue <

x1

>.

Can not open an ITO message manager queue. More information is contained in another part of the error message.

Chapter 2 151

OpC40-0614

OpC40-0615

OpC40-0616

OpC40-0617

OpC40-0621

OpC40-0622

OpC40-0630

OpC40-0631

ITO Error Messages

Error messages of manager processes

Cannot read from queue <

x1

>.

Can not read from an ITO message manager queue. More information is contained in another part of the error message.

Cannot create pipe <

x1

>. mkfifo(2) failed.

Can not create an ITO message manager pipe. This message is qualified by a system error message (errno) giving more information.

Cannot open pipe <

x1

>. open(2) failed.

Can not open an ITO message manager pipe. This message is qualified by a system error message (errno) giving more information.

Cannot write to queue <

x1

>.

Can not write to ITO message manager queue. More information is contained in another part of the error message.

MSI client exited without disconnect from interface

<

x1

>.

A client application accessing the MSI terminated without closing the interface instance. ITO noticed this and has closed the instance.

Number of entries in MSI queue exceeds max_entries; disconnecting <

x1

>.

The maximum number of entries allowed for the MSI queue (specified in the max_entries parameter in opcif_open()) was exceeded. The application that is connected to the Message Stream Interface still can read messages until the queue is empty; it then needs to close (and maybe reopen, if desired) the MSI.

Could not load the message forwarding template

(msgforw).

This error occurs, when the message forwarding template stored at

/etc/opt/OV/share/conf/OpC/mgmt_sv/respmgrs/msgforw is not accessible correctly. It will be continued, as if there is no template at all.

Messages will not be forwarded.

Problems detected while reading the message forwarding template.

152 Chapter 2

OpC40-0632

OpC40-0633

OpC40-0634

OpC40-0635

OpC40-0636

OpC40-0637

ITO Error Messages

Error messages of manager processes

This error occurs, when the message forwarding template stored at

/etc/opt/OV/share/conf/OpC/mgmt_sv/respmgrs/msgforw contains syntax errors. It will be continued, as if there is no template at all. Messages will not be forwarded. You can use the check-tool opcmomchk to verify the template in advance.

Could not convert data from the message forwarding template (msgforw) into an internal format.

An internal error occurred, when converting the message forwarding data.

The target manager <

x1

> for message forwarding is not in the nodebank. Trying to continue with default values for security- and communication protocols.

All ITO management servers, that get in contact with each other, should know the opposite's security level and communication type. Otherwise, default values will be taken (security=off, comm.type=DCE), that may not fit. Therefore you should add the target manager to the nodebank of the source manager, as well as the source manager to the target manager's nodebank, and setup the communication parameters.

Could not get needed message attributes from the database.

Problem, when contacting the database. Concerned database-tables are the active- or history_messages.

Could not set message attribute (<

x1

>) in the database.

Problem, when contacting the database. Concerned database-tables are the active- or history_messages.

Could not convert distribution lists used for message forwarding.

Internal error; either there is not enough memory or the distribution list was damaged during transfer or processing.

Could not store distribution lists for message forwarding in the database.

Chapter 2 153

OpC40-0638

OpC40-0639

OpC40-0651

OpC40-0670

OpC40-0671

ITO Error Messages

Error messages of manager processes

Problem when contacting the database. Concerned database-tables are the active- or history_messages and the forw_msg_table.

Could not read distribution list for message forwarding from the database.

Problem, when contacting the database. Concerned database-table is the forw_msg_table.

Line <

x1

> of msi conf file <

x2

> was skipped due to syntax errors or order number out of range.

Check the msi conf file for syntax errors or out-of-range order numbers.

Didn't start <

x1

> <

x2

> on node <

x3

>.

The ITO management server processes have been restarted since this request was entered (For more information see online help, error 40-651).

An action request was not executed, cause the ITO server was restarted since the request was entered. you can change this behaviour by adding the line OPC_EXEC_ACTIONS_AT_STARTUP TRUE to the opcsvinfo file. For more granularity you can additionally add the line

OPC_MAX_AGE_OF_ACTIONS_AT_STARTUP <age_in_seconds> to opcsvinfo. The server processes must be restarted to activate the changes.

Can't find MSI instance '<

x1

>'.

Reconnect to an MSI instance is not possible. The ITO server processes were successfully started but the applications using the MSI must reconnect to the server. ITO can reconnect to MSI instances when the instance process was not stopped when the server processes were stopped. Was the MSI instance process also stopped the MSI instance will be removed from the database.

Can't find MSI registration condition.

This error can be safely ignored. If it occurs frequently, report it to your

HP Response Center.

154 Chapter 2

OpC40-0674

OpC40-0675

OpC40-0676

OpC40-0700

ITO Error Messages

Error messages of manager processes

A message arrived from node '<

x1

>'.

The required security level is '<

x2

>' but the agent is logged on as '<

x3

>' and has set security level '<

x4

>'.

No more authentication failures will be reported for this node.

The ITO management server received the previous message from a managed node with insufficient security attributes. This message will be processed normally but automatic and operator-initiated actions have been set to FAILED if configured. Check the managed node's error logfile for additional information. Verify the DCE security related configuration on the management server and managed node using the opc_sec_verify.sh utility.

Can't start <

x1

> <

x2

> on node <

x3

>.

The message failed authentication checks - this message has possibly been sent by an untrusted source.

The action bound to this message has been disabled because the message failed authentication checks. This message will be processed normally but automatic and operator-initiated actions have been set to FAILED if configured. Check the managed node's error logfile for additional information. Verify the DCE security related configuration on the management server and managed node using the opc_sec_verify.sh

utility.

Discarded <

x1

> <

x2

> for node <

x3

>

The message failed authentication checks - this message has possibly been sent by an untrusted source.

Nevertheless it is possible to start this operator-initiated action.

The operator-initiated action bound to this message has been set to

FAILED because the message failed authentication checks. If desired the action can be started again - this annotation is intended to notify you about possible security problems. Check the managed node's error logfile for additional information. Verify the DCE security related configuration on the management server and managed node using the opc_sec_verify.sh utility.

Initializing configuration failed.

Internal Error. Please report this to your HP Response Center.

Chapter 2 155

OpC40-0701

OpC40-0702

OpC40-0703

OpC40-0704

OpC40-0705

OpC40-0706

ITO Error Messages

Error messages of manager processes

Usage: opcragt [ -help ]

[ [ ( -start | -stop | -status | -primmgr ) [-id

<

subagent_id

>] ]

| [ -update ]

| [ -init_install <

inst_server

> <

architecture

> <

version

>

<

account_password

> <

inst_drive

> ]

| [ -distrib [ -templates ] [ -actions ] [ -monitors ] [

-commands ]

[ -force ] ] ]

[ -all | [ -nodegrp <

group

>... ] <

node

>... ]

The opcragt(1) command was called either with the -help option or with an incorrect parameter list. Correct is: opcragt -help or opcragt [ -start |

-stop | -update ] [ -all | <nodelist> ] where the first alternative specifies the command to be executed remotely. No command option returns the status on the managed node. The second alternative is either a list of managed nodes, or -all for all ITO configured nodes. For more information, see the opcragt(1) man page.

Can't connect to ITO control agent.

The opcragt command is unable to connect the ITO control agent running on a managed node displayed previously. This error message is qualified by another message giving more information.

Can't start ITO services.

The opcragt command is unable to execute the 'start' option on the managed node. This error message is qualified by another message giving more information.

Can't stop ITO services.

The opcragt command is unable to execute the 'stop' option on the managed node. This error message is qualified by another message giving more information.

Can't reconfigure ITO services.

The opcragt command is unable to execute the 'update' option on the managed node. This error message is qualified by another message giving more information.

Can't get local IP address.

156 Chapter 2

OpC40-0707

OpC40-0708

OpC40-0709

OpC40-0710

OpC40-0711

OpC40-0712

OpC40-0714

ITO Error Messages

Error messages of manager processes

The opcragt command is unable to obtain the local IP address. This error message is qualified by another message giving more information.

Command failed.

The opcragt command is unable to execute the requested operation. This error message is qualified by another message giving more information.

The gethostbyname(3N) call failed.

The opcragt command is unable to resolve a passed node name to an IP address. The node name is displayed previously. Check whether the node name is correct.

This node is not accessible via IP network.

The opcragt command is unable to execute a requested operation on the specified managed node because it is configured in ITO with another network type than IP. Check the configuration of that node in ITO using the administrator's GUI.

Retrieving list of configured nodes failed.

The opcragt command is unable to obtain the set of configured managed node from the database. This error message is qualified by another message giving more information.

Command not allowed. Node is neither controlled nor monitored.

The opcragt command is unable to execute a requested operation on the specified managed node because it is not configured in ITO as 'controlled' or 'monitored'. Check the configuration of that node in ITO using the administrator's GUI.

Node <

x1

>:

This node is not contained in the domain.

The opcragt command is unable to execute a requested operation on the specified managed node, because it is not configured in ITO at all. Check the managed node configuration in ITO using the administrator's GUI.

You must be root to use this command.

The opcragt command may be used by a user with the effective user id 0 only.

Chapter 2 157

OpC40-0715

OpC40-0716

OpC40-0717

OpC40-0718

OpC40-0719

OpC40-0720

OpC40-0721

ITO Error Messages

Error messages of manager processes

Invalid IP address specification: <

x1

>.

A managed node specification passed as IP address is invalid. The address is displayed previously. Valid is an IP address in the format

#n.n.n.n where n is a numeric value.

Can't display ITO status.

The opcragt command is unable to display current status of the managed node. This error message is qualified by another message giving more information.

Can't get list of all configured ITO node groups from the database.

It was not possible to get required ITO information from the database.

This error message is qualified by another message giving more information.

<

x1

> used as node group name with the option -nodegrp is not configured within ITO as ITO node group.

The used node group name is not configured in ITO. Solution: Check whether you used the correct name.

Can't get the ITO management server name from the database.

It was not possible to get required ITO information from the database.

This error message is qualified by another message giving more information.

Can't get IP addresses for the ITO management server

<

x1

>.

It was not possible to convert the name of the management server to an

IP address. Solution: Check the name of the management server system to be correct and verify whether this name can be resolved to an IP address on the managed node.

The managed node requires authenticated RPC but the opcragt command is not logged into DCE.

158 Chapter 2

OpC40-0722

OpC40-0723

OpC40-0780

OpC40-0782

OpC40-0783

OpC40-0784

ITO Error Messages

Error messages of manager processes

If there was no previous error message about a failed login operation either the DCE security service was unavailable or the DCE principal used by the management server is not configured at all. Refer to the installation manual for more information about required DCE setup.

No node left for processing.

The job could not be done for any node because the specified nodes or node groups were invalid. The command exited with exit code 1. If not all specified nodes or node groups are invalid, only a warning will be written to stderr for each invalid node or node group but the program still continues with the other nodes and exits with 0.

The command is not supported by the agent platform or the agent type of this node.

The opcragt command is unable to execute a requested operation on the specified managed node because the requested operation is not supported on this node platform.

New ITO manager configuration download to directory <

x1

>.

A new ITO manager configuration was distributed to your Management

Server. It resides normally in /usr/OV/tmp/OpC_appl/cfgdwn on HP-UX

9.x nodes or in /var/opt/OV/share/tmp/OpC_appl/cfgdwn on HP-UX 10.x

nodes. You should use 'opccfgupld' to upload the new configuration.

Target server node '<

x1

>' is not configured in the local ITO database. You must configure other management servers as regular nodes in the ITO node bank.

To distribute configuration to another Management Server you must configure the target node as regular node in ITO. Use the 'Node Add' functionality of the Administrator's GUI to perform this task.

Cannot read target of symbolic link '<

x1

>'.

The command cannot get information of a symbolic link. Check, that the symbolic link exists and that the directory of the symbolic link and the parent directories have sufficient permissions.

Cannot send symbolic link '<

x1

>' to target manager.

Chapter 2 159

OpC40-0785

OpC40-0786

OpC40-0850

OpC40-0851

OpC40-0852

OpC40-0853

OpC40-0854

ITO Error Messages

Error messages of manager processes

An error occured, when sending a symbolic link to another manager.

Check, if the communication was broken or if the opccmm process on the target node aborted. If the target manager cannot receive symbolic links, use the

• no_symlink option. If the communication was broken, send the data again.

Received invalid data for creating a symbolic link:

'<

x1

>'

A symbolic link was sent, but the received data is invalid. Check, if the communication was broken and send the data again.

Cannot create symbolik link '<

x1

>'.

A symbolic link that was received from opcmgrdist could not be created.

Check, if the previous command to create the directory failed and check for operating system errors. Probably the permissions of one of the parent directories are insufficient.

Cannot open queue <

x1

>.

Can not open the ITO display receiver. More information is contained in another part of the error message.

Cannot create pipe <

x1

>. mkfifo(2) failed.

Can not create the ITO display receiver pipe. This message is qualified by a system error message (errno) giving more information.

Cannot open pipe <

x1

>. open(2) failed.

Can not open the ITO display receiver pipe. This message is qualified by a system error message (errno) giving more information.

Cannot write to queue <

x1

>.

Can not write to the ITO display receiver queue. More information is contained in another part of the error message.

Cannot start ITO display receiver. fork(2) failed.

Start of the ITO display receiver failed. This message is qualified by a system error message (errno) giving more information.

160 Chapter 2

OpC40-0855

OpC40-0856

OpC40-0900

OpC40-0901

OpC40-0902

OpC40-0903

OpC40-0904

OpC40-0905

ITO Error Messages

Error messages of manager processes

Cannot start ITO display receiver. exec(2) failed.

Start of the ITO display receiver failed. This message is qualified by a system error message (errno) giving more information.

Did not get necessary information from display receiver.

Start of the ITO display receiver failed. This message is qualified by a system error message (errno) giving more information.

Cannot start the tss server.

The 'opctss' process is unable to create a server connection. This message is qualified by a system error message (errno) containing the cause of the error.

Error during transfer of package file <

x1

>.

An error during the data transfer to the managed node occurred. This message is qualified by a system error message (errno) containing the cause of the error.

Cannot write to socket.

The 'opctss' process is unable to write to a socket. This message is qualified by a system error message (errno) containing the cause of the error.

Cannot write socket number.

The 'opctss' process can not deliver its socket number to the distribution manager. This message is qualified by a system error message (errno) containing the cause of the error.

Cannot get filename.

The 'opctss' process is unable to read a temporary filename from the distribution manager. This message is qualified by a system error message (errno) containing the cause of the error. This error may be caused by the termination of the distribution manager during a distribution or if an abnormally terminated distribution left the current instance of the TSS process.

Init of config file failed.

Chapter 2 161

OpC40-0906

OpC40-0907

OpC40-0950

OpC40-0951

OpC40-0952

OpC40-0953

OpC40-0954

OpC40-0955

ITO Error Messages

Error messages of manager processes

The 'opctss' process is unable to open the opcinfo file. This message is qualified by a system error message (errno) containing the cause of the error.

Pipe to opcdistm is broken.

The pipe between the distribution manager and the 'opctss' process is broken. This message is qualified by a system error message (errno) containing the cause of the error.

Cannot unlink file <

x1

>. Continuing with processing.

The 'opctss' process is unable to remove a temporary file This message is qualified by a system error message (errno) containing the cause of the error.

Communication manager can't accept connection on TCP socket.

The ITO communication manager could not start as TCP socket server.

The accept(2) system call failed.

Communication manager can't open output file '<

x1

>'.

The ITO communication manager could not open the requested output file <file> to write data into. This message is qualified by a system error message (errno) containing the cause of the error.

Communication manager can't receive data on TCP socket.

The ITO communication manager failed to receive data from a remote management server. This error message is qualified by another message giving more information.

Communication manager can't write output file '<

x1

>'.

The ITO communication manager could not write the requested output file <file> to write data into. This message is qualified by a system error message (errno) containing the cause of the error.

Internal error: Invalid command parameters.

Internal Error. Please report this to your HP Response Center.

Internal error: Invalid connection ID.

162 Chapter 2

OpC40-0956

OpC40-0957

OpC40-0958

OpC40-0959

OpC40-1111

OpC40-1200

OpC40-1201

ITO Error Messages

Error messages of manager processes

Internal Error. Please report this to your HP Response Center.

Internal error: Invalid command.

Internal Error. Please report this to your HP Response Center.

Can't initialize as TCP server.

The ITO communication manager could not initialize as TCP socket server. This error message is qualified by another message giving more information.

Lost connection to ITO distribution manager.

The ITO communication manager lost the connection to the distribution manager. Probably the distribution manager terminated. Check the error log file to get more information and restart the ITO manager processes.

Communication manager can't send data via TCP socket.

OBSOLETE.

Cannot write NNM license file to save license information.

The file '<

x1

>' is not writable.

The managed node to operate on is configured in ITO to use a higher security level than SEC_NONE. This requires the calling RPC client to be logged into DCE. This login operation failed. This error message is qualified by another message giving more information.

No distribution manager registered on management server node.

The ITO distribution manager is not registered on the local management server system. This will prevent the ITO DCE agent manager from forwarding distribution requests. Check the error log file to get more information and restart the ITO manager processes.

No distribution manager running on management server node.

Chapter 2 163

OpC40-1202

OpC40-1203

OpC40-1204

OpC40-1205

OpC40-1206

OpC40-1207

ITO Error Messages

Error messages of manager processes

The ITO distribution manager is registered on the local management server system but not responding. This will prevent the ITO DCE agent manager from forwarding distribution requests. Check whether the ITO manager processes are running. If not examine the error log file to get more information and restart the ITO manager processes.

Can't connect to distribution manager - can't reach rpcd/llbd.

The ITO DCE agent manager could not connect the ITO distribution manager on the local management server system because it could not reach the llbd/rpcd. This will prevent the ITO DCE agent manager from forwarding distribution requests. Check whether the llbd/rpcd and the

ITO manager processes are running. If not restart the llbd/rpcd, examine the error log file to get more information and restart the ITO manager processes.

Can't connect to distribution manager.

The ITO DCE agent manager could not connect the distribution manager. This error message is qualified by another message giving more information.

Can't forward RPC call.

The ITO DCE agent manager could not forward an RPC call to either the

ITO distribution manager on the local management server system or to a control agent on a managed node. This error message is qualified by another message giving more information.

Unsupported RPC call.

Internal Error. Please report this to your HP Response Center.

Can't retrieve value from config subsystem for number of server threads.

Using default value.

Internal Error. Please report this to your HP Response Center.

Invalid number of server threads specified: <

x1

>. Using default value <

x2

>.

164 Chapter 2

OpC40-1252

OpC40-1300

OpC40-1301

OpC40-1302

OpC40-1303

OpC40-1304

OpC40-1305

ITO Error Messages

Error messages of manager processes

The configured number <num> of RPC threads to be started by the ITO

DCE agent manager is out of range. Valid is 1 - <maxnum>. The process will use <maxnum> as default. Fix this value in your opcinfo file.

Can't obtain name of current DCE user. You must be logged into DCE when running this command.

The installation of a password into the DCE registry requires a valid login context as a privileged user. You need to log into DCE before running the opcpwd command.

Could not read configuration data.

Internal error

Could not initialize internal data structures (<

x1

>).

Internal error or no more memory available.

Could not set registration condition to catch message-change events.

Internal error or no more memory available.

Could not open message-stream interface <

x1

>.

The ITO forward manager cannot open a link to the ITO display manager via message-stream interface to get message-change events.

Error causes may be a failed file operation or insufficient memory.

The ITO message reciever on the target manager

(<

x1

>) is registered at the location broker, but it's not reachable.

The ITO message receiver (opcmsgr) on the target manager is registered in the location broker (rpcd/dced),of the target system but it's not running. This can happen, when the message receiver terminated abnormally; it has no time to unregister itself. Cleanup the location broker with the control program rpccp or by restarting the ITO services on the target system.

The ITO message receiver on the target manager

(<

x1

>) isn't running. Probably, ITO isn't up on the target system.

Chapter 2 165

OpC40-1306

OpC40-1307

OpC40-1308

OpC40-1309

OpC40-1310

OpC40-1311

OpC40-1313

ITO Error Messages

Error messages of manager processes

The ITO message receiver on the target manager is not running.

Probably, ITO does not run there.

Could not connect to target manager <

x1

>.

Could not connect to ITO target manager. Either the node is not running or there are network problems or the location broker on the node is not running.

Could not forward data to ITO management server on system <

x1

>.

Summary-message; cannot forward any data to target manager.

Could not register to catch message change events.

It was not possible to forward an registration condition to the ITO display manager; error causes may be a failed file operation or insufficient memory.

Read invalid data from communication queue.

Read invalid data from communication queue. The data is not in the expected format; maybe it was damaged during transport or processing.

It's very likely an internal error.

Could not generate distribution list for message forwarding.

Internal error or insufficient memory.

Could not read data from communication queue.

Could not read data from communication queue. Error causes are a failed file operation or insufficient memory.

Can't authenticate with DCE security service.

Management server: '<

x1

>'.

Manager name: '<

x2

>'; own name: '<

x3

>'.

Sending data unauthenticated.

166 Chapter 2

OpC40-1314

OpC40-1400

OpC40-1401

OpC40-1402

OpC40-1403

OpC40-1404

ITO Error Messages

Error messages of manager processes

The ITO Forward Manager failed to initialize an authenticated RPC connection to the Management Server <mgmt sv>. This error message is qualified by another message giving more information. The forward manager will send further data unauthenticated and try to recover an authenticated connection later.

Authentication failure during RPC to message receiver on

'<

x1

>': <

x2

>.

Retrying unauthenticated ...

The ITO Forward Manager failed to send an ITO message via authenticated RPC. This can happen if the target ITO Message Receiver does not run authenticated but the sending Forward Manager does. The

Forward Manager will send further data unauthenticated and try to recover an authenticated connection later. Possibly the Management

Server failed to initialize properly or the Management Server has been unconfigured in the DCE security service. Verify the ITO Management

Server error logfile for security related error messages.

The Mid-Level-Manager is running on the node.

The RPC-server of the Mid-Level-Manager is running and is ready to receive RPC-calls.

The Mid-Level-Manager isn't running.

The RPC-server of the Mid-Level-Manager is not running, or the

RPC-connection is not possible because of an RPC-error.

The Mid-Level-Manager specified for this node could not be found.

The node is configured to be managed via a Mid-Level-Manager, but the

Mid-Level-Manager specified for this node could not be found in the Node

Bank. Agent type and Mid-Level-Manager can be specified in the

[Actions:Node:Modify] window.

The request is not supported by the agent platform or the agent type of this node.

Some request are not supported on specific platforms or they are not supported on a specific Agent Type. Agent type and Mid-Level-Manager can be specified in the [Actions:Node:Modify] window.

The Mid-Level-Manager isn't running on node <

x1

>.

Chapter 2 167

OpC40-1405

OpC40-1406

OpC40-1407

OpC40-1408

OpC40-1409

OpC40-1500

OpC40-1502

OpC40-1503

ITO Error Messages

Error messages of manager processes

The RPC-server of the Mid-Level-Manager is not running, or the

RPC-connection is not possible because of an RPC-error.

The Mid-Level-Manager on node <

x1

> is registered at the llbd or rpcdaemon but it is not running.

Restart the RPC-server of the Mid-Level-Manager.

The Message Forwarding component of the

Mid-Level-Manager on node <

x1

> is not running.

The Message Forwarding component of the Mid-Level-Manager is not running. You cannot receive any messages from the Mid-Level-Manager or any of its managed nodes while this component is not running.

The Mid-Level-Manager on node <

x1

> is now running.

The request sender detected that the Mid-Level-Manager on the target node is up again.

The Message Agent on node <

x1

> is now running.

The request sender detected that the Message Agent on the target node is up again.

The Message Forwarding component of the

Mid-Level-Manager on node <

x1

> is now running.

The request sender detected that the Message Forwarding component of the Mid-Level-Manager on the target node is up again.

opcwall failed. Cannot inform users.

The command opcwall failed. See previous errors for the reason.

Cannot connect to database.

The program could not connect to the database. See the server error logfile for more details.

Cannot connect to display manger.

168 Chapter 2

OpC40-1504

OpC40-1505

OpC40-1551

OpC40-1553

ITO Error Messages

Error messages of manager processes

The program could not connect to the ITO display manager. Probably the

ITO server processes are not running and no users need to be informed.

See the server error logfile for more details.

Cannot do an API connect. opc_connect() failed with error <

x1

>.

The program could not connect to the ITO API. See the server error logfile for more details.

The API function <

x1

> failed with error <

x2

>.

The specified API function failed. See the server error logfile for more details.

Cannot assign hierarchy of user <

x1

> to user <

x2

>.

Hierarchy of the source user could not be assigned to the target user. See previous error messages for the reason.

Could not read password.

The program could not read the password because getpass() failed.

Chapter 2 169

ITO Error Messages

Error messages of DB access

OpC50-0001

OpC50-0002

OpC50-0003

OpC50-0004

Error messages of DB access

Database inconsistency detected (<

x1

>).

The entries in the two tables belong together. But actually there is only an entry in one table.

The corresponding information is placed in more than one database table. But there is only an entry in one table. This error can occur if the administrator has changed an operator configuration but the operator is still logged in, or if the database installation was not successful. Delete the affected object or rerun the database initialization program, using the clear option (all data in the database will be deleted!).

Could not connect to database <

x1

>.

Please look if the database processes are running.

The application cannot connect to the database. This may have several reasons: 1. The database environment variables are not set correctly. If you have set database environment variables (Oracle: ORACLE_HOME,

ORACLE_SID, NLS_LANG), check if they are correct. If the environment variables are not set, the values in the OpenView database configuration file /etc/opt/OV/share/conf/ovdbconf are used. Check, if the values in this file are still correct. 2. The database is not running.

Restart it as described in the Administrator's Reference Guide. 3. You have resource problems. Check, if the number of open files or the available swap space is near the maximum and reconfigure it if needed.

No according data found in the database.

There is no corresponding data available in the database. This may not be an error. It may be you have not yet set up the object. Other reasons for this message may be: The administrator has deleted an object, but an operator who has this object is still logged in. When the operator exits and again logs in, the error no longer occurs, as the operator now has the new configuration. Another possible reason, is that the database installation was not successful. Re-running the database initialization program with the clear option (does delete all data from the database tables!) solves this problem.

Login failed.

170 Chapter 2

OpC50-0006

OpC50-0007

OpC50-0008

OpC50-0009

OpC50-0010

OpC50-0011

OpC50-0012

OpC50-0013

ITO Error Messages

Error messages of DB access

In order to logon to the ITO application, user name and password must be entered. The entered user name is not yet configured or the entered password is incorrect. Your ITO administrator defines the user name, along with the password, to give you access to your capabilities within

ITO.

Invalid browser identifier received.

Internal Error. Please report this to your HP Response Center.

Invalid annotation identifier received.

Internal Error. Please report this to your HP Response Center.

Invalid application identifier received.

Internal Error. Please report this to your HP Response Center.

Invalid instruction identifier received.

The instruction to a message is no longer available. This occurs if you delete the message condition that matched the message.

Invalid message identifier <

x1

> received.

This error occurs if a old message is not in the database or a new message is already in the database.

This may not be a error. The message can have two reasons. Either the response of an automatic action has arrived before the message itself, or a message is no longer in the active- or history-table, and is referenced.

Invalid node identifier <

x1

> received.

ITO identifies nodes internally by node IDs. There exists no entry for this node ID in the opc_node_names, opc_node_pattern or opc_nodes table.

Either the node ID is corrupted or the node was deleted. See also the instructions to the error 50-91 for more information.

Invalid user identifier received.

May be the user <

x1

> is no longer in the user bank.

The User does not (or no longer) exist. Probably an operator who was still logged-in was removed by the administrator from the user bank.

Invalid session identifier received. A UI process might have died.

Chapter 2 171

OpC50-0014

OpC50-0015

OpC50-0016

OpC50-0017

ITO Error Messages

Error messages of DB access

Each operator has a session identifier for the current session. The session identifier is not (or no longer) valid. Probably an operator who is still logged in was removed by the administrator from the user bank. If this error message appears in the admin GUI, it is very likely that the admin's user interface process has been terminated unexpectedly. Exit the program via the OpenView Exit menu and restart ITO.

Invalid view filter received.

The filters for the view browser or the filters for the history browser are not valid.

Database: <

x1

>

This message contains the message text which was returned by the database system. The message following this message will tell if this message is an informative message or if a real problem occurred. A possible database message is:

'Database: ORA-00054: resource busy and acquire with NOWAIT specified' for an Oracle RDBMS: Another process has taken a lock on a database table. As several users and processes work on the database at the same time this may occur sometimes. ITO will try to repeat the transaction several times. This is indicated by the ITO message 'Retry.'.

In this case the timeout has no influence on the system. Only if several retries were without success, the database transaction will be aborted. In this cases another error message will follow the generic database message and will tell which transaction was not successful.

A possible reason for this problem is a user who accesses the ITO tables with a interactive database query tool. This user should commit his transactions or exit the query tool. Repeating the action now will work.

For more details about the generic database messages, ask your database administrator.

The user is already logging into the system.

Previously somebody logged in but did not complete the user interface startup. This error is only for information. The login process will continue.

The user is already logged on.

172 Chapter 2

OpC50-0018

OpC50-0019

OpC50-0020

OpC50-0021

OpC50-0022

OpC50-0025

ITO Error Messages

Error messages of DB access

This message is caused because someone is already logged on as the same user. ITO allows only one logged user for a single user name. If this message appears but the login is still successful, you can ignore this error. This means that an user interface session was not properly ended but ITO detected this and thus allowed the new login. If nobody is logged in for the affected user name and you are not able to log in, please contact your HP Response Center.

Can not acknowledge message in database.

A possible reason for this error is that the database tables are locked.

Perhaps somebody is accessing the tables with a interactive database query tool. This user should commit his transactions or exit the query tool. Repeating the action now will work.

Can not unacknowledge message in database.

A possible reason for this error is that the database tables are locked.

Perhaps somebody is accessing the tables with an interactive database query tool. This user should commit his transactions or exit the query tool. Repeating the action now will work.

Error in access to file (<

x1

>).

Check that the file exists and that it has the right permissions. The administrator user interface generally runs as user root, the operator user interface runs as user opc_op.

Error during delete of file (<

x1

>).

Check that the file exists and that the directory where the file resides has write permissions. The administrator user interface generally runs as user root, the operator user interface as user opc_op.

Invalid node name received (<

x1

>).

An external node was used for an operation where only normal nodes

(real nodes) are allowed.

Duplicate object detected (<

x1

>).

There are two entries with the same Key in the database in the specified table. This may occur if you run the database initialization program a second time without the clear option. It may also occur after you issue a copydb without previously clearing the database tables. You should

Chapter 2 173

OpC50-0027

OpC50-0028

OpC50-0029

OpC50-0030

OpC50-0031

OpC50-0032

OpC50-0033

OpC50-0034

ITO Error Messages

Error messages of DB access

delete the non-unique object with an interactive database query tool or re-run the database initialization program with the clear option (all data in the database will be deleted!).

Node is not managed.

The node is not in the nodebank.

Invalid symbol type identifier received.

Internal Error. Please report this to your HP Response Center.

Invalid node name or IP address received.

A node with this IP address or hostname is not in the database. If the node is new, add it to the node bank. If the node is in the node bank, check that all its IP addresses and aliases can be resolved by the name service. Hidden IP addresses may be added to the opc.hosts file.

Can't convert node name to IP address (<

x1

>).

The IP-Address of the node can not be determined. Check if the name service is running.

Duplicate node name detected (<

x1

>).

Two different nodes have the same node name. The message contains the affected node IDs of the two nodes. opcdbidx(1m) can fix some of this problems. If opcdbidx fails to correct the problem, please report this to your HP Response Center.

Invalid nodegroup identifier received.

The internal used nodegroup ID for the node group does not exist. If you recently did an opccfgupld, restart the user interface and the ITO server processes to re-read the configuration from the database. If the error still occurs, please report this to your HP Response Center.

Invalid password.

The password may not contain control characters.

The specified password contains unallowed characters or the password is too long. Unallowed characters are control characters and space characters.

Invalid condition ID.

174 Chapter 2

OpC50-0035

OpC50-0036

OpC50-0037

OpC50-0039

OpC50-0040

OpC50-0041

OpC50-0042

OpC50-0043

OpC50-0045

ITO Error Messages

Error messages of DB access

Internal Error. Please report this to your HP Response Center.

Invalid application type.

Internal Error. Please report this to your HP Response Center.

Invalid application group id received.

Internal Error. Please report this to your HP Response Center.

Invalid distribution status received.

Internal Error. Please report this to your HP Response Center.

Invalid desktop type.

Internal Error. Please report this to your HP Response Center.

Node not processed (<

x1

>).

A node of a list of nodes can not be processed. The other nodes are processed normal. Check the previous error messages for the reason.

Invalid tree fork type (operator desktop) received.

Internal Error. Please report this to your HP Response Center.

Error in read-access to file (<

x1

>).

Check that the file exists, and that it has read permissions. Check also that the directory where the file resides has read permissions. The administrator user interface generally runs as user root, the operator user interface, as user opc_op.

Invalid crypted password received.

The password has errors in crypt. Please change the password for the affected application or operator. If this does not work or the administrator password is the problem password, please report this to your HP Response Center.

Invalid password.

If this error occurs for the database connection, there is currently no password set or it is empty. You can set the database password with opcdbpwd. If this error occurs when changing the own password of an user, the old password is not correct.

Chapter 2 175

OpC50-0046

OpC50-0047

OpC50-0048

OpC50-0049

OpC50-0050

OpC50-0051

OpC50-0052

ITO Error Messages

Error messages of DB access

Error while reading report file: <

x1

>.

Check that the file exists, and that it has read permissions. Check also that the directory where the file resides has read permissions. The administrator user interface generally runs as user root, the operator user interface as user opc_op.

Error while reading report file or file is empty.

Check that the file exists, and that it has read permissions. Check also that the directory where the file resides has read permissions. The administrator user interface generally runs as user root, the operator user interface as user opc_op.

Node name (<

x1

>) is not valid for IP address (<

x2

>).

The node can not be resolved correctly. Check that the name service is running.

Can not get correct node name (invalid: <

x1

>) for IP address (<

x2

>).

Please check node (<

x3

>).

The node is already in the database but with different values and the correct values can not be resolved. Check that the name service is running correctly.

There are two identical nodes (<

x1

>, <

x2

>) for the same IP address (<

x3

>) configured in the nodebank.

Please remove one of the nodes.

The name service returns the same IP-Address for both nodes. ITO however requires that the IP-Address must be unique in the database.

Check that the name service is running correctly, and try the action again. If this does not work, delete one of the two entries manually.

The node <

x1

> is member of the ITO Nodebank.

You tried to add a node to the nodebank that is already in the node bank or you wanted to modify the node address of a node to the values of another node that is already in the node bank. Check the values returned by the name service and modify the existing node if necessary.

Can't convert IP address to node name (<

x1

>).

176 Chapter 2

OpC50-0053

OpC50-0054

OpC50-0055

OpC50-0056

OpC50-0057

ITO Error Messages

Error messages of DB access

The node name of the node can not be determined. Check that the name service is running.

A timeout occurred during database access.

Please try again later.

Another process has taken a lock on a database table. Several attempts to repeat this transaction were without success. The transaction can not be made. A possible reason for this error is a user who accesses the ITO tables with an interactive database query tool. This user should commit his transactions or exit the query tool. Repeating the action now will work.

Node name (<

x1

>) has assigned two IP-Addresses (<

x2

>,

<

x3

>).

Please check node.

A node has two different IP-Addresses assigned. This means no error.

The node is recognized but in the database, only one node address of a node can be kept. It may also be that the node is not set up correctly in the name service. Check the node.

Can't resolve node (circular IP-Addresses with nodes

<

x1

>, <

x2

>).

Please check nodes.

The IP-Address of the modified node is wrong and belongs to a node which itself has a wrong IP-Address and so on. This might end in a loop and can not be handled. Try to modify the nodes from the end of this chain.

Management server configuration is missing in database

(table opc_mgmtsv_config).

Configuration data for the management server system is missing in the database. Probably the database initialization did not work correctly.

The reason for this could be that the node address of the management server system can not be resolved. Please check that the name service is running correctly and re-run the database initialization program with the clear option (this will clear all your data in the database!) or re-run the database upgrade program.

Can't get name of Management Server, please check with

'hostname'.

Chapter 2 177

OpC50-0058

OpC50-0059

OpC50-0060

OpC50-0061

OpC50-0062

OpC50-0063

ITO Error Messages

Error messages of DB access

The system call, gethostname, which delivers the name of the actual system, failed. Check that the networking is set up correctly.

Can't get node entry of Management Server (<

x1

>), please check the node bank.

The node address of the management server system can not be resolved correctly. Check that the name service is running correctly, and re-run the database initialization program, using the clear option (this will delete all your data in the database!) or re-run the database upgrade program.

Invalid node pattern type received.

Internal Error. Please report this to your HP Response Center.

Can not call the compress program for file <

x1

> because number of processes reached system limit.

Please either stop some processes or increase the kernel parameter for the maximum number of processes per user (maxuprc) and the maximum number of processes on the system (nproc). Refer to the prerequisites in the installation manual for appropriate values.

Can not call the compress program for file <

x1

> because physical or reserved swap memory reached system limit.

Please either stop some processes or increase the swap space on the system. Refer to the prerequisites in the installation manual for appropriate values.

Error while compressing file <

x1

>.

During the distribution of templates, a file could not be compressed.

Check, if the directory has wrong permissions or if the file does not exist.

Distributing with force update may help.

Error while calling or executing the compress program for file <

x1

>.

During the distribution of templates, a file could not be compressed because the exec call to compress failed. Check, if the compress command exists and has execute permissions.

178 Chapter 2

OpC50-0065

OpC50-0066

OpC50-0068

OpC50-0069

OpC50-0070

OpC50-0071

ITO Error Messages

Error messages of DB access

Connection to database server processes lost.

Please restart the database server processes if they are not running.

Please check if the database server processes are running correct. For an

Oracle database at least the following processes must run: ora_dbwr_openview, ora_smon_openview, ora_d000_openview, ora_lgwr_openview, ora_pmon_openview, ora_ckpt_openview and ora_s000_openview. If you use another ORACLE_SID, the processes will have a different end. Restart the database server processes if the processes are not running correct. If you use SQL*Net, this error might also be caused by network problems. For SQL*Net, the tnslsnr process must also run on the database server.

File error (<

x1

>): <

x2

>.

An error occurred when trying to create a file. The file name is in brackets, the reason for the error is behind the colon. Check, if the directory exists and has right permissions.

Wrong parent ID for nodebank group <

x1

>.

Please use modify nodebank group to assign another parent to the nodebank group.

The parent nodebank group of the nodebank group is invalid. Please assign the nodebank group to another parent nodebank group.

Wrong parent ID for node <

x1

>. Please use modify node to assign another parent to the node.

The nodebank group of the node is invalid. Please assign the node to another parent nodebank group.

Nonexisting MSI ID (<

x1

>) received.

A process which is registered at the message processing interface uses a wrong ID. The IDs are registered when connecting to the Message

Stream Interface.

Platform family <

x1

> already exists with different values.

Chapter 2 179

OpC50-0072

OpC50-0073

OpC50-0074

OpC50-0084

OpC50-0086

ITO Error Messages

Error messages of DB access

The referenced platform family already exists with different values. A platform family is specified in the agent platform file. Edit the agent platform file of the currently loaded platform to fit to the other platforms.

Platform family name may not be empty.

A platform family is specified in the agent platform file. The name of the platform family may not be empty. Edit the agent platform file of the currently loaded platform to fit to the other platforms.

Cannot delete platform. Node for this platform still exist.

A agent platform may not be deleted from the database as long as nodes of this platform are in the nodebank. Delete the affected nodes from the database or set the platform of the nodes to the correct value before removing the platform.

Platform family <

x1

> does not exist. Platform family must be added before platform of this platform family can be added.

The platform family does not exist. Platform family must be added before a platform of this platform family can be added. Please first load another platform of this platform family which contains a definition of the platform family.

ORACLE_HOME parameter does not exist in configuration file <

x1

>.

The ORACLE_HOME parameter is needed to connect to the database. If this variable is not set in the environment, it is read from the configuration file /usr/OV/conf/ovdbora. This file is written after a successful database configuration. If the database configuration failed, you should again run opcdbsetup.

Cannot update node address in database.

The opcchgaddr(1m) program cannot change the node address of the specified node. Check for previous errors to see the reason. If the changed address cannot be resolved by the name service, check if the specified values are correct and if the name service is up and running.

180 Chapter 2

OpC50-0087

OpC50-0088

OpC50-0089

OpC50-0090

OpC50-0091

OpC50-0095

ITO Error Messages

Error messages of DB access

Invalid network type (<

x1

>) specified.

Valid types are: IP, SNA, DEC, NOVELL, OTHER and

UNKNOWN.

The specified word for the network type is invalid. Allowed words are 'IP' for the network type IP and 'OTHER' for non IP network types. See also the opcchgaddr(1m) man page for more information on the allowed node address formats.

Node name may not be empty.

The Node name may not be empty. See the opcchgaddr(1m) man page for information on the node address format.

IP address for IP node must be specified.

The IP address for an IP node must be specified. See the opcchgaddr(1m) man page for information on the node address format.

New address is different than values from name service. Following values have been used:

Network type <

x1

>, IP address <

x2

>, Node name '<

x3

>'.

When -force is not used, opcchgaddr(1m) always checks the specified values with the values from the name service. If the values from the name service differ, the values from the name service will be used. For example, opcchgaddr(1m) will always use the fully qualified hostname.

The used values are displayed together with the error message. If you want opcchgaddr(1m) to use the specified values, you have to use -force.

Node <

x1

> is not in the node bank.

Check if the affected node is in the node bank. This error can also occur if the affected managed node has (also) an IP address which is not known on the management server. To solve the problem, update your name service to know all IP-Addresses of the affected managed node. See chapter 9, 'Tuning, Troubleshooting, Security and Maintenance' of the

Administrator's Reference guide, subchapter 'ITO Installation Problems of Multi-homed Hosts' for more information about troubleshooting nodes with multiple IP-Addresses.

ECS template '<

x1

>' cannot be distributed as it is unverified. The template will be skipped.

Chapter 2 181

OpC50-0096

OpC50-0098

OpC50-0107

OpC50-0108

OpC50-0109

OpC50-0110

ITO Error Messages

Error messages of DB access

An unverified event correlation circuit is assigned to a node or to the management server to which configuration is distributed. Only verified event correlation circuits can be distributed. Please verify the ECS circuit prior distributing it with the ECS designer or de-assign it from the node/management server.

Error while trying to distribute more than one circuit to a node.

More than one circuit is assigned to distribute. Please undo the surplus assignments.

Could not fix inconsistency in opc_nodes_in_group.

opcdbidx could not fix an inconsistency. A node group contains a node that is not in the node bank. See previous error messages to see the reason why this not worked. If SQL errors like a timeout were the reason, you can start opcdbidx again. If this still does not work, call your

HP Response Center.

Setting software and configuration distribution status flags to modified.

This step allows to set the software and configuration distribution status flags to modified. This means, that even though nothing was changed, everything is again distributed like if force update was pressed during the distribution.

Template '<

x1

>' is already locked by user '<

x2

>'.

The Template is already locked by another template administrator or by the administrator (see error message for the user name). Please contact the user to finish the work on this template. This will release the lock.

No such template.

You tried to lock/unlock a template which does not exist. Probably your user interface is not in sync with the database and the template was meanwhile deleted by another user. To get the current state, exit and restart the user interface. This will load the data again from the database.

Could not remove duplicate entries in opc_node_names.

182 Chapter 2

OpC50-0112

OpC50-0113

OpC50-0114

OpC50-0115

OpC50-0116

ITO Error Messages

Error messages of DB access

See the previous errors to see the reason why opcdbidx(1m) could not remove the duplicate entries. If an SQL Error like timeout occured, you can run opcdbidx again. If this still does not work, call your HP Response

Center.

Template '<

x1

>' exists already in the database.

The template could not be added to the database because the database returned an non unique object error. Either a template with this name already exists (e.g. because another template administrator added it).

Please use another name to avoid this error. The other reason is, that the used UUID is already in use. In this case, try it again and another UUID will be generated.

Template '<

x1

>' will be skipped.

The named template will be skipped from distribution because of previous errors. But the other templates will be distributed.

Cannot remove old ECS files.

The opendir(3) call failed for directory '<

x1

>'.

Could not get the files in the old ECS configuration directory. When event correlation templates are distributed to the management server, first the old ECS configuration file and the old ECS circuits are deleted. This files reside in the directory <OV_CONF>/OpC/mgmt_sv/ec. Please check that the directory exists and has proper rights.

Cannot remove old ECS files.

The stat(2) call failed for file '<

x1

>'.

Could not get status of an old event correlation file. When event correlation templates are distributed to the management server, first the old ECS configuration file and the old ECS circuits are deleted. This files reside in the directory <OV_CONF>/OpC/mgmt_sv/ec. Please check that the directory exists and has proper rights.

Cannot remove old ECS files.

The remove(3) call failed for file '<

x1

>'.

Could not remove an old event correlation file. When event correlation templates are distributed to the management server, first the old ECS configuration file and the old ECS circuits are deleted. This files reside in the directory <OV_CONF>/OpC/mgmt_sv/ec. Please check that the directory exists and has proper rights.

Chapter 2 183

OpC50-0117

OpC50-0118

OpC50-0119

OpC50-0120

OpC50-0121

ITO Error Messages

Error messages of DB access

Cannot remove old ECS files.

The readdir(3) call failed for directory '<

x1

>'.

Could not get the files in the old ECS configuration directory. When event correlation templates are distributed to the management server, first the old ECS configuration file and the old ECS circuits are deleted. This files reside in the directory <OV_CONF>/OpC/mgmt_sv/ec. Please check that the directory exists and has proper rights.

Cycle detected while resolving template group with ID '<

x1

>'. This operation would result in a cycle. It was aborted.

A database function encountered a loop when it tried to generate all resulting templates. This also includes templates contained in subsequent template groups of a template group. Probably a certain template group contains itself or a subsequent template group contains the template group. This creates a loop. Template groups may not contain loops. For this reason, the operation was aborted.

Could not modify config status flag

(No entry for node_id '<

x1

>').

The configuration distribution status update of the node with the specified node_id failed. If the node_id consists of only zeros, the update in the opc_mgmtsv_config table for the management server failed.

Otherwise, no entry for this node_id was found in the opc_node_names table.

Message with ID '<

x1

>' is already forwarded to manager

'<

x2

>'.

The Message with the given ID was already forwarded to the specified target manager. Probably you have set up duplicate rules for message forwarding.

Cycle detected while resolving template group '<

x1

>'.

This operation would result in a cycle. It was aborted.

A database function encountered a loop when it tried to generate all resulting templates. This also includes templates contained in subsequent template groups of a template group. Probably a certain template group contains itself or a subsequent template group contains the template group. This creates a loop. Template groups may not contain loops. For this reason, the operation was aborted.

184 Chapter 2

OpC50-0123

OpC50-0124

OpC50-0125

OpC50-0126

OpC50-0127

OpC50-0128

ITO Error Messages

Error messages of DB access

Templates of type <

x1

> are not allowed for the agent platform of node <

x2

>.

Not all types of templates are allowed for all platforms. E.g. Console templates are only allowed on MPE/iX. When distributing, the resulting templates for a node are calculated (including templates assigned to template groups and node groups). For each of this templates a check is done, if the template can be assigned to this platform. If not, the template is not distributed and this error message is written. Only those templates for which such an error appeared are skipped. All other templates are distributed.

Templates of type <

x1

> are not allowed for the management server.

Not all types of templates are allowed for assignment to the management server (not the agent of the management server). With ITO 4.0 only ECS templates can be assigned. The not allowed templates will be skipped.

But if some valid templates were assigned, they will still be activated.

Monitor Condition '<

x1

>' already exists.

The description of a monitor condition must be unique.

The description of a Monitor Condition already exists within the same monitor template. The description of a monitor condition must be unique.

Please change the description of the new condition.

There are more than one applications with name '<

x1

>' and group '<

x2

>' for this user.

There are more than one applications with a given name and group for the user. The first application returned will be used. To avoid problems, you should rename the duplicates.

Condition '<

x1

>' was skipped due to error.

A condition was skipped because of a previous error for this condition.

The error before this error tells the reason for this problem. Probably a database inconsistency is the reason for the error. The other conditions are not affected from this error if they have not an error, too.

Cannot determine database variable <

x1

>. It is not set and cannot be read from the ovdbconf file.

Chapter 2 185

OpC50-0129

OpC50-0143

OpC50-0144

OpC50-0147

OpC50-0148

ITO Error Messages

Error messages of DB access

The specified database environment variable cannot be determined. The variable is either read from the environment or from the OV database configuration file /etc/opt/OV/share/conf/ovdbconf. You can either set the variable in the environment or you can add a line to the config file in the form '<name> <value>' before starting the process. For example:

NLS_LANG american_america.WE8ISO8859P1 If the file does not exist, probably something went wrong when installing the database. If you already configured the database, you can re-run opcdbsetup and let opcdbsetup use the existing database. This will create the file and other missing database objects. But it will probably abort later on because database tables or configuration information already exists.

Management area does not exist (ID: <

x1

>, name: <

x2

>).

The specified management area ID (for the specified management area name) does not exist. Probably the UI is out of sync with the database and the management area was meanwhile deleted. Please unmark this management area. If the management area name is "Parent", the database is inconsistent. No management area with the management area ID of the parent_id DB field exists.

Checking for orphans (unused entries) in opc_node_names.

ITO stores all node names in the opc_node_names table. As different tables refer to this table, entries are not automatically deleted when they are no longer used. This may leed to a lot of unused entries in the opc_node_names table and thus to performance problems. opcdbidx

-orphan removes such unused entries. This message tells, that this check and removal is currently in progress.

Error occured when checking and removing orphans in opc_node_names.

The program could not fix all orphans in the opc_node_names table. See the previous errors for more details about the reason. opcdbidx can be called again.

Could not create temporary table <

x1

>.

The temporary table could not be created. Check previous error messages for the reason. Check, if there is enough space left on disk.

Removed <

x1

> unused entries from the opc_node_names table.

186 Chapter 2

OpC50-0153

OpC50-0154

OpC50-0155

OpC50-0156

OpC50-0157

OpC50-0159

OpC50-0162

OpC50-0163

ITO Error Messages

Error messages of DB access

ITO stores all node names in the opc_node_names table. As different tables refer to this table, entries are not automatically deleted when they are no longer used. This may leed to a lot of unused entries in the opc_node_names table and thus to performance problems. opcdbidx

-orphan removes such unused entries. This message tells, that such entries were removed and the number of removed entries.

The audit level is already locked. Nothing changed.

The program opc_audit_secure can only be called once. If the audit level has been locked, you can no longer change the audit level and the audit and history download directory. To unlock, you have to re-initialize the database (opcdbinit -c).

Cannot read database maintenance information from database.

See the previous errors for details why this error occurred.

Cannot update database maintenance information in database.

See the previous errors for details why this error occurred.

Cannot get the audit level from the database.

See the previous errors for details why this error occurred.

Cannot update the audit level in the database.

See the previous errors for details why this error occurred.

Path name is too long: '<

x1

>'.

The path name is longer than the maximum allowed length of the platform. On UNIX this is PATH_MAX.

The subpath '<

x1

>' exists but is no directory.

A part of the complete path is not a directory (e.g. a normal file or a special file). This prevents, that a directory bellow this path can be used.

Please choose a different path or remove the file.

The subpath '<

x1

>' exists but is owned by user '<

x2

>' instead of user root or <

x3

>.

Chapter 2 187

OpC50-0164

OpC50-0167

OpC50-0168

OpC50-0169

OpC50-0170

OpC50-0172

ITO Error Messages

Error messages of DB access

The program checks, that the specified directory and any parent directory is only writable by root (or bin). This prevents, that the directory can be moved and therefore the security can be bypassed.

The subpath '<

x1

>' exists but it has wrong (too open) permissions: <

x2

>.

The program checks, that the specified directory and any parent directory is only writable by root (or bin). This prevents, that the directory can be moved and therefore the security can be bypassed.

Aborting program due to error. The audit level was not changed.

Errors occurred. Because of this errors, the program stops. The reasons for the abort are in previous errors. Please fix this problems and run the program again.

Option -file is not possible because audit level is locked.

The audit level has been locked using opc_audit_secure. This means, that the audit level and also the audit and history download directories cannot be changed anymore for security reasons. For security reasons, in this case the -file option of opcauddwn and opchistdwn is disabled.

The configured download path is no directory. Because the audit level is locked, the download path must be a directory.

To avoid, that old download files are overwritten, the configured download path must be a directory if the audit level has been locked.

Cannot modify node label. But node address has been changed.

Probably the modified node is not contained in the node bank.

Node group <

x1

> does not exist.

The node group with the specified name does not exist. Check if the name is written correct. If the administrator deleted the node group, restart the process to get the current list of node groups.

188 Chapter 2

OpC50-0173

OpC50-0174

OpC50-0175

OpC50-0185

OpC50-0200

OpC50-0201

OpC50-0202

ITO Error Messages

Error messages of DB access

Error in time conversion. localtime_r(3C) for <

x1

> failed.

The conversion of the time in seconds since the epoch to the string representation in local time needed for the database failed. Please check the the environment variable setting (e.g. TZ and LANG).

Cannot add audit entry. <

x1

> tries to find unique audit_nr failed.

The primary key of audit entries is audit_nr. Several tries failed to find a unique audit_nr. If a lot of concurrent processes work, another try may work. Another reason could be, that the maximum number is reached. In this case, you can download all audit entries with opcauddwn(1M). This ensures that the numbers will again start with 1.

Audit entry with number <

x1

> skipped because it already exists.

An audit entry could not be uploaded from file because an audit entry with this number already exists in the database. This probably occured because the same file has already been uploaded once. The affected audit entry is skipped, but the audit upload will continue.

Could not determine database.

The program could not determine the access to the used RDBMS (name,

SQL*Net parameters, ...). See the previous error messages for the detailed reason.

Cannot delete message <

x1

> from <

x2

> table.

Check the previous errors for the reason, why the message could not be deleted. If a timeout or deadlock occured, trying it again may work.

Cannot move message <

x1

> to opc_hist_messages.

Message with the same ID exists already.

You can download the current history messages with opchistdwn -older

0s. Then it should be possible to move the message to the history message table.

Message <

x1

> does not exist.

Chapter 2 189

OpC50-0203

OpC50-0204

OpC50-0205

OpC50-0206

OpC50-0284

OpC50-0287

ITO Error Messages

Error messages of DB access

The message can have several reasons. Either the response of an automatic action has arrived before the message. Or a message is referenced that is no longer in the active- or history-table because it was for example already downloaded. Or a wrong message number was specified to an API program.

A Message with ID <

x1

> is already in the history table.

The message could not be inserted into the history message table opc_hist_messages because a message with this message number already exists. Probably history messages were uploaded a second time.

Cannot add annotation for message <

x1

>.

An annotation could not be added. Check previous errors to see the reason for this problem. The message for the annotation may not exist.

Message <

x1

> could not be added.

A message could not be added to the database. See the previous errors for the details why this message could not be added.

Could not move messages that are marked acknowledged to history tables.

To improve the acknowledgement of messages, ITO first marks a message as acknowledged, but keeps it in the active message tables. In regular intervalls, the program opcdbmsgmv moves all marked messages to the history tables. This move of messages failed for some or all messages. See previous error messages for the reason. If this failed because of a timeout, you can run opcdbmsgmv manually again or wait until it is scheduled the next time. Except of a worse performance for new messages, this problem has no impact on the work of ITO.

Could not add missing nodes to node hierarchies.

opcdbidx tries to fix inconsistencies between the node bank and the node hierarchies. If a node is not in a hierarchy, it is added. The previous messages give more information, why this could not be done. If a lot of changes have to be done, the Oracle rollback segment may run out of space. Run opcdbidx again when you fixed the problem.

Removing duplicate applications ...

190 Chapter 2

ITO Error Messages

Error messages of DB access

ITO offers different message load policies to reduce the time needed to load the messages from the database. This policy can be changed by the system administrator in the opcsvinfo file. It is not supported to use external nodes in the node filter when using the ALLMSGS or

NO_EXT_NO_MISC policy.

Chapter 2 191

ITO Error Messages

Internal Database messages

OpC51-0022

OpC51-0023

Internal Database messages

Retry.

Another process has taken a lock on a database table. ITO tries several times to perform the transaction. The retry itself is not an error, it simply indicates that ITO has tried to repeat the transaction. If the retries are not successful, the transaction can not be made. A possible reason for this error is a user who accesses the ITO tables with an interactive database query tool. This user should commit his transactions or exit the query tool. Repeating the action now will work.

Invalid software status received for updating all nodes.

Internal Error. Please report this to your HP Response Center.

192 Chapter 2

ITO Error Messages

Message set used by the application integration program

OpC53-0001

OpC53-0020

OpC53-0100

OpC53-0150

OpC53-0200

Message set used by the application integration program

Usage: opcdbupload [ -h[elp] ] [ -v[verbose] ]

[ -r[eplace] ] [ -a[pplications] ]

[ -e[xecutables] ] [ -t[emplates] ] <

application

> opcdbupload is a subprogram of the application integration program opcupload. For details, see the man page opcupload(1m) or the

Administrator's Reference Guide, Appendix C.

Cannot find the ITO administrator.

Cannot add applications.

The database contains no administrator user. Uploaded applications belong to the administrator user. Please ensure that an administrator user exists. This problem may be caused because the database initialization was not successful. To reinitialize the database run opcdbinit -c -v. Warning: this will delete the contents of all tables.

Usage: opcdownload [ -h[elp] ] [ -v[erbose] ]

[ -a[pplication] <

application

> ]...

[ -g[roup] <

application_group

> ]...

[ -t[emplate] <

template

> ]... <

directory

>

Program for downloading message- and monitor-templates to an ASCII file. For details, see the manual page opcdownload(1m) or the

Administrator's Reference Guide, Appendix C.

Usage: opchistupl <

filename

>

Upload program for history messages. For details see the man page opchistupl(1m) or the Administrator's Reference Guide, Appendix C.

Usage: opcaudupl <

filename

>

Upload program for audit information. For details see the man page opcaudupl(1m) or the Administrator's Reference Guide, Appendix C.

Chapter 2 193

OpC53-0452

OpC53-0453

OpC53-0461

OpC53-0462

OpC53-0463

OpC53-0464

ITO Error Messages

Message set used by the application integration program

Cannot send message through message interceptor.

Message: <

x1

>.

The Oracle tablespace monitor creates messages which are sent to the

ITO message interceptor. Please check, that a template for the message interceptor is assigned to that node and that the message interceptor agent (opcmsgi) is running on that node.

Tablespace <

x1

> does not exist. Please adapt the tablespace monitor template and redistribute it.

The tablespace which was specified in the Oracle tablespace monitor template does not exist. Please adapt the arguments of the tablespace monitor executable in the tablespace monitor template.

Could not open configuration file <

x1

>.

The configuration file for the Oracle tablespace extension program opcaddbf is missing. It contains information about where the new file of the tablespace should be located and what size it should have. For each tablespace the configuration file should contain lines of the following format: <tablespace name> SIZE <size of new file> <directory of new file>

Specification for tablespace <

x1

> not found in <

x2

>.

The Oracle tablespace extension program opcaddbf was called for a tablespace which does not exist. For each tablespace the configuration file should contain lines of the following format: <tablespace name> SIZE

<size of new file> <directory of new file>

Size specification for tablespace <

x1

> not found in <

x2

>.

The size specification for the tablespace was not found in the tablespace extension configuration file. For each tablespace the configuration file should contain lines of the following format: <tablespace name> SIZE

<size of new file> <directory of new file>

Directory specification for tablespace <

x1

> not found in

<

x2

>.

The directory specification for the tablespace was not found in the tablespace extension configuration file. For each tablespace the configuration file should contain lines of the following format:

<tablespace name> SIZE <size of new file> <directory of new file>

194 Chapter 2

OpC53-0465

OpC53-0466

OpC53-0467

ITO Error Messages

Message set used by the application integration program

SQL command '<

x1

>' failed.

The printed SQL command of the Oracle tablespace extension program opcaddbf failed. The previous error messages give more information about the reason of the failure.

Datafile '<

x1

>' of size <

x2

>K added to tablespace <

x3

>.

A new datafile has been successfully added to an full tablespace from the program opcaddbf. The tablespace should now have enough space for further operations. If the tablespace is a roll back tablespace (RBS1) you must create and activate new rollback segments. Contact your Oracle database administrator to do this.

Adding datafile to tablespace <

x1

> failed.

The Oracle tablespace extension program opcaddbf could not add a datafile to the tablespace. The previous error messages give more information about the reason of the failure.

Chapter 2 195

ITO Error Messages

Upload/Download feature messages

OpC54-0001

OpC54-0002

OpC54-0003

OpC54-0004

OpC54-0005

OpC54-0006

OpC54-0007

OpC54-0008

OpC54-0009

Upload/Download feature messages

You must be user root to run this program.

This program must be called with the effective user id of 'root'.

Unknown option '<

x1

>'.

An illegal option for this program was specified.

Cannot create directory '<

x1

>'.

The program failed to create a filesystem directory. Use the system error message which is printed out as a hint.

Cannot determine working directory.

The current working directory could not be determined. Use the system error message which is printed out as a hint.

Cannot change working directory to '<

x1

>'.

The specified directory could not be made the current working directory.

Use the system error message which is printed out as a hint.

Cannot stat entry '<

x1

>'.

The status of the specified file system object (file, directory, link) could not be determined. Use the system error message which is printed out as a hint.

Cannot change owner of '<

x1

>'.

The ownership of the specified file system object could not be changed.

Use the system error message which is printed out as a hint.

Cannot change mode of '<

x1

>'.

The access mode of the specified file system object could not changed.

Use the system error message which is printed out as a hint.

Cannot remove file '<

x1

>'.

196 Chapter 2

OpC54-0010

OpC54-0011

OpC54-0012

OpC54-0013

OpC54-0014

OpC54-0015

OpC54-0016

OpC54-0017

OpC54-0018

ITO Error Messages

Upload/Download feature messages

The specified file could not be removed. Use the system error message which is printed out as a hint.

Registration file '<

x1

>' not linked to directory '<

x2

>'.

The symbolic link for the specified application registration file does point to an expected target directory. This happens only if the uploaded data is changed while 'opccfgupld' is running or the registration files used by

IT/O are changed while 'opccfgdwn' is in progress.

Cannot execute command '<

x1

>'.

No instruction

Cannot get information for file '<

x1

>' (lstat).

No information about the specified file system object could be obtained.

Use the system error message which is printed out as a hint.

Cannot read from file/command '<

x1

>'.

An error occurred while reading from the specified file. Use the system error message which is printed out as a hint.

Cannot determine destination of symbolic link '<

x1

>'

(readlink).

The target location for the specified symbolic link could not be determined. Use the system error message which is printed out as a hint.

Cannot make symbolic link '<

x1

>' (symlink).

The specified symbolic link could not be created. Use the system error message which is printed out as a hint.

Unknown character set.

The internal character set is not supported by either 'opccfgupld' or

'opccfgdwn'.

Cannot initialize configuration handling.

The configuration file handling of the reporting process could not be initialized correctly.

Cannot find administrator.

Chapter 2 197

OpC54-0050

OpC54-0051

OpC54-0052

OpC54-0053

OpC54-0054

OpC54-0055

ITO Error Messages

Upload/Download feature messages

The configuration download 'opccfgdwn' could not find the administrator in the IT/O database. Verify if you are trying to download a not properly initialized configuration (administrator present). The configuration upload 'opccfgupld' tried to upload applications into the application bank but could not find the administrator in the IT/O database. Verify if you are trying to upload applications to a properly initialized configuration

(administrator present).

usage: opccfgdwn [-help] |

[-silent] [-force] [-v<

version number

>]

<

specification file

> <

target directory

>

There is an error in the calling sequence of 'opccfgdwn'.

Internal error [<

x1

>].

This is an internal error. Please report this message to your HP

Response Center.

Cannot access specification file '<

x1

>'.

The configuration download 'opccfgdwn' could not access the download specification file. Use the system error message which is printed out as a hint.

Cannot open specification file '<

x1

>'.

The configuration download 'opccfgdwn' could not open the download specification file. Use the system error message which is printed out as a hint.

Target filetree is not empty and option '-force' is not specified.

Remove the filetree manually and restart the download.

(use command 'rm -r <

x1

>').

The directory tree which was specified for the configuration download is not empty. Since the option '-force' was not specified, the existent files are not modified. Use the option '-force' or remove the directory tree manually. You may use the command mentioned in the error message.

File '<

x1

>' removed from target filetree.

198 Chapter 2

OpC54-0056

OpC54-0057

OpC54-0058

OpC54-0059

OpC54-0060

OpC54-0061

OpC54-0062

ITO Error Messages

Upload/Download feature messages

This is an informational message indicating the removal of an existent file from the download directory. Files are removed only if the option

'-force' was specified for 'opccfgdwn'.

Cannot create index file '<

x1

>'.

The configuration download could not create the index file which used by

'opccfgupld'. Use the system error message which is printed out as a hint.

Syntax error in specification file '<

x1

>'.

The download specification file had syntax errors. If this specification file was created using the administrator GUI, please report this message to your HP Response Center. If you created this file manually, check the according line and correct the error.

Cannot create data file '<

x1

>'.

The configuration download could not create the specified data file. Use the system error message which is printed out as a hint.

Illegal user name pattern for registration file destination (<

x1

>).

This is an internal error. Please report this to your HP Response Center.

Error writing to file '<

x1

>'.

An error occurred while the configuration download was writing to the specified file. Use the system error message which is printed out as a hint.

Options for <

x1

>:

-help : Displays this message.

-silent : Perform silent download, report only warnings and errors.

If not specified, verbose progress messages are generated.

This message gives a short description for the options of 'opccfgdwn'.

-force : Overwrite existing files.

<

specification file

> : Name of file containing the

download specification. If no path is specified, the

Chapter 2 199

OpC54-0063

OpC54-0064

OpC54-0065

OpC54-0100

OpC54-0101

ITO Error Messages

Upload/Download feature messages

file

is searched for in a subdirectory <

target dir

>

of the default application data directory.

No instruction

<

target directory

> : Name of the directory under which the file

tree of downloading data will start. If no path is speci-

fied, the directory is used/created in the directory

<

x1

>.

No instruction

Warning:

Since not 'All Configuration Data' was selected for the download, the

upload may result in unexpected database contents.

Try 'man 1m <

x1

>' for details.

This warning occurs only if not the complete IT/O configuration was downloaded. Uploading partial configuration data may result in lost references (since the referenced data was not downloaded, too) or deleted data (since before replacing the node bank, say, the node group bank is deleted, too). See the manual page for 'opccfgupld' for more details

(section RESTRICTIONS).

Logfile output has been stored in '<

x1

>'

The configuration upload writes a logfile which basename is reported in this message. This file is stored in '/var/opt/OV/log/OpC/mgmt_sv'.

Internal error [<

x1

>].

This is an internal error. Please report this message to your HP

Response Center.

Cannot open index file '<

x1

>'.

The index file, which controls 'opccfgupld', could not be opened. Verify that the index file is located in the language specific subdirectory of your upload path, and that it has the same name as the last component of the specified upload directory (truncated to eight characters) with extension

'.idx'. The index file is written by 'opccfgdwn' while downloading.

200 Chapter 2

OpC54-0102

OpC54-0103

OpC54-0104

OpC54-0106

OpC54-0107

OpC54-0108

OpC54-0109

ITO Error Messages

Upload/Download feature messages

Syntax error(s) in index file '<

x1

>'.

The index file, which controls 'opccfgupld', contains syntax errors. If you used an index file created by 'opccfgdwn', please report this message to your HP Response Center. If you created your own index file, use the specific error messages which were printed before the current message and correct the error.

usage: <

x1

> [-help] | [-contents] | [-silent | -verbose]

[-check] |

[-silent] [-verbose] [-installed] [-configured]

[-no_license]

[-add | -replace] [-subentity] [-trace]

[-heartbeat { on | off | keep | data }]

[-layout]

[-index <

index file

>] <

upload directory

>

There is an error in the calling sequence of 'opccfgupld'.

Character set of download data not compatible with installed set.

The character set which was installed on the downloaded server is not compatible with the character set installed on the current management server.

Synchronize mode requires download of all data.

The synchronize mode is allowed only if a download of all configuration data is used for uploading.

Cannot open data file '<

x1

>'.

The specified data file could not be opened for reading. Use the system error message which is printed out as a hint.

Syntax error in data file '<

x1

>'

The specified data file contains a syntax error. If you are uploading a previous download from 'opccfgdwn', please report this message to your

HP Response Center. If you used a manually created data file, locate the error using the error messages which were printed before this message and correct the error.

Database modifications are skipped from now on.

Chapter 2 201

OpC54-0110

OpC54-0111

OpC54-0112

OpC54-0113

ITO Error Messages

Upload/Download feature messages

After an error occurred during the upload process, all database modifications are skipped from now on. However, the remaining data files are parsed and errors are reported.

Options for <

x1

>:

-help : Displays this message.

-contents : Show entities which are available in the data files.

-check : Check the syntax of the data files.

-silent : Perform silent upload, report only warnings and errors.

If not specified, verbose progress messages are generated.

-installed : Set software status flag of new nodes to

'active'.

This message gives a short description for the options of 'opccfgupld'.

-configured: Do not set config change flag if templates are changed

or newly assigned to a managed node.

-no_license: Do not set flag to indicate license checking for new nodes.

This option may only be used for configuration of Backup

Servers, otherwise it violates the license agreements.

No instruction

-subentity : Specifies the behaviour in add or replace mode.

-trace : Add SQL-execution info to our logfile <

x1

>.log.

-add : Insert data in addition to existing configuration.

-replace : Insert data and replace existing configuration.

No instruction

-index : Read upload specification from this index file.

-heartbeat : Set the Heartbeat flag for nodes to ON,

OFF, KEEP the value or take the value of the DATA files (default).

-layout : Upload also the operator layouts when

202 Chapter 2

OpC54-0150

OpC54-0151

OpC54-0152

OpC54-0153

OpC54-0154

OpC54-0155

OpC54-0156

OpC54-0157

OpC54-0158

ITO Error Messages

Upload/Download feature messages

uploading ITO 4.x

operator data and convert them to node hierarchies.

<

upload directory

> : Name of the directory under which the file tree of

the upload data is located.

If no path is specified, the directory is searched

for in the directory <

x1

>.

No instruction line <

x1

> "<

x2

>": error in application login.

This is a specific error message concerning a syntax error in a data file.

line <

x1

> "<

x2

>": error in 'APPLICATION' entity.

This is a specific error message concerning a syntax error in a data file.

line <

x1

> "<

x2

>": error in 'APPLICATION_GROUP' entity.

This is a specific error message concerning a syntax error in a data file.

line <

x1

> "<

x2

>": node address or 'PATTERN_OTHER <

string

>' expected.

This is a specific error message concerning a syntax error in a data file.

line <

x1

> "<

x2

>": condition node address or pattern expected.

This is a specific error message concerning a syntax error in a data file.

line <

x1

> "<

x2

>": condition severity expected.

This is a specific error message concerning a syntax error in a data file.

line <

x1

> "<

x2

>": error in 'CONSOLE_TEMPLATE' entity.

This is a specific error message concerning a syntax error in a data file.

line <

x1

> "<

x2

>": error in 'INTERFACE_TEMPLATE' entity.

This is a specific error message concerning a syntax error in a data file.

line <

x1

> "<

x2

>": 'DOWNLOAD_DATA <

entity

>' expected.

This is a specific error message concerning a syntax error in a data file.

Chapter 2 203

OpC54-0163

OpC54-0164

OpC54-0165

OpC54-0166

OpC54-0167

OpC54-0168

OpC54-0159

OpC54-0160

OpC54-0161

OpC54-0162

OpC54-0169

OpC54-0170

ITO Error Messages

Upload/Download feature messages

line <

x1

> "<

x2

>": error in 'INSTRUCTION_INTERFACE' entity.

This is a specific error message concerning a syntax error in a data file.

line <

x1

> "<

x2

>": error in 'LOGFILE_TEMPLATE' entity.

This is a specific error message concerning a syntax error in a data file.

line <

x1

> "<

x2

>": error in 'MONITOR_TEMPLATE' entity.

This is a specific error message concerning a syntax error in a data file.

line <

x1

> "<

x2

>": error in template message condition entry.

This is a specific error message concerning a syntax error in a data file.

line <

x1

> "<

x2

>": error in 'MESSAGE_GROUP' entity.

This is a specific error message concerning a syntax error in a data file.

line <

x1

> "<

x2

>": error in 'NODE_GROUP' entity.

This is a specific error message concerning a syntax error in a data file.

line <

x1

> "<

x2

>": error in 'NODE' entity.

This is a specific error message concerning a syntax error in a data file.

line <

x1

> "<

x2

>": node address expected.

This is a specific error message concerning a syntax error in a data file.

line <

x1

> "<

x2

>": error in 'NODE_DEFAULTS' entity.

This is a specific error message concerning a syntax error in a data file.

line <

x1

> "<

x2

>": error in 'LAYOUT' entry of managed node.

This is a specific error message concerning a syntax error in a data file.

line <

x1

> "<

x2

>": name of node template expected.

This is a specific error message concerning a syntax error in a data file.

line <

x1

> "<

x2

>": error in 'NOTIFICATION_SERVICE' entity.

204 Chapter 2

OpC54-0171

OpC54-0172

OpC54-0173

OpC54-0174

OpC54-0175

OpC54-0176

OpC54-0177

OpC54-0178

OpC54-0179

OpC54-0180

OpC54-0181

ITO Error Messages

Upload/Download feature messages

This is a specific error message concerning a syntax error in a data file.

line <

x1

> "<

x2

>": error in notification schedule entry.

This is a specific error message concerning a syntax error in a data file.

line <

x1

> "<

x2

>": error in 'OPERATOR' entity.

This is a specific error message concerning a syntax error in a data file.

line <

x1

> "<

x2

>": error in application group entity of operator desktop.

This is a specific error message concerning a syntax error in a data file.

line <

x1

> "<

x2

>": error in operator geometry entry.

This is a specific error message concerning a syntax error in a data file.

line <

x1

> "<

x2

>": error in operator node 'LAYOUT' entry.

This is a specific error message concerning a syntax error in a data file.

line <

x1

> "<

x2

>": 'NODE <

address

>' expected for operator layout.

This is a specific error message concerning a syntax error in a data file.

line <

x1

> "<

x2

>": error in operator responsibility entry

'NODE_GROUP'

This is a specific error message concerning a syntax error in a data file.

line <

x1

> "<

x2

>": error in 'REGROUP_CONDITIONS' entity.

This is a specific error message concerning a syntax error in a data file.

line <

x1

> "<

x2

>": error in 'TRAP_TEMPLATE' entity.

This is a specific error message concerning a syntax error in a data file.

line <

x1

> "<

x2

>": error in snmp variable entry.

This is a specific error message concerning a syntax error in a data file.

line <

x1

> "<

x2

>": error in trap template message condition entry.

Chapter 2 205

OpC54-0182

OpC54-0183

OpC54-0184

OpC54-0250

OpC54-0251

OpC54-0252

OpC54-0253

OpC54-0254

OpC54-0255

OpC54-0256

ITO Error Messages

Upload/Download feature messages

This is a specific error message concerning a syntax error in a data file.

line <

x1

> "<

x2

>": character set is not compatible with installed set.

This is a specific error message concerning a syntax error in a data file.

line <

x1

> "<

x2

>": error in operator scope entry.

This is a specific error message concerning a syntax error in a data file.

line <

x1

> "<

x2

>": error in management area entry.

This is a specific error message concerning a syntax error in a data file.

line <

x1

> "<

x2

>": error in application specification.

This is a specific error message concerning a syntax error in a data file.

line <

x1

> "<

x2

>": error in application group specification.

This is a specific error message concerning a syntax error in a data file.

line <

x1

> "<

x2

>": error in condition specification.

This is a specific error message concerning a syntax error in a data file.

line <

x1

> "<

x2

>": error in instruction interface specification.

This is a specific error message concerning a syntax error in a data file.

line <

x1

> "<

x2

>": error in monitor template spec. (string expected).

This is a specific error message concerning a syntax error in a data file.

line <

x1

> "<

x2

>": error in message group specification.

This is a specific error message concerning a syntax error in a data file.

line <

x1

> "<

x2

>": error in network/machine type specification.

This is a specific error message concerning a syntax error in a data file.

206 Chapter 2

OpC54-0257

OpC54-0258

OpC54-0259

OpC54-0260

OpC54-0261

OpC54-0262

OpC54-0263

OpC54-0264

OpC54-0265

OpC54-0266

OpC54-0267

ITO Error Messages

Upload/Download feature messages

line <

x1

> "<

x2

>": error in node specification.

This is a specific error message concerning a syntax error in a data file.

line <

x1

> "<

x2

>": error in node address specification.

This is a specific error message concerning a syntax error in a data file.

line <

x1

> "<

x2

>": error in node group specification.

This is a specific error message concerning a syntax error in a data file.

line <

x1

> "<

x2

>": error in notification service specification.

This is a specific error message concerning a syntax error in a data file.

line <

x1

> "<

x2

>": error in operator specification.

This is a specific error message concerning a syntax error in a data file.

line <

x1

> "<

x2

>": error in operator configuration specification.

This is a specific error message concerning a syntax error in a data file.

line <

x1

> "<

x2

>": error in operator responsibility specification.

This is a specific error message concerning a syntax error in a data file.

line <

x1

> "<

x2

>": error in template specification.

This is a specific error message concerning a syntax error in a data file.

line <

x1

> "<

x2

>": error in template specification (string expected).

This is a specific error message concerning a syntax error in a data file.

line <

x1

> "<

x2

>": error in template condition specification.

This is a specific error message concerning a syntax error in a data file.

line <

x1

> "<

x2

>": error in header section.

This is a specific error message concerning a syntax error in a data file.

Chapter 2 207

OpC54-0268

OpC54-0269

OpC54-0270

OpC54-0271

OpC54-0300

OpC54-0301

OpC54-0302

OpC54-0500

OpC54-0501

OpC54-0502

OpC54-0503

ITO Error Messages

Upload/Download feature messages

line <

x1

> "<

x2

>": error in template group specification.

This is a specific error message concerning a syntax error in a data file.

line <

x1

> "<

x2

>": error in operator scope specification.

This is a specific error message concerning a syntax error in a data file.

line <

x1

> "<

x2

>": error in ec template specification.

This is a specific error message concerning a syntax error in a data file.

line <

x1

> "<

x2

>": error in schedule template specification.

This is a specific error message concerning a syntax error in a data file.

line <

x1

> "<

x2

>": error in entity specification.

This is a specific error message concerning a syntax error in a data file.

line <

x1

> "<

x2

>": error in operator configuration specification.

This is a specific error message concerning a syntax error in a data file.

line <

x1

> "<

x2

>": error in operator desktop specification.

This is a specific error message concerning a syntax error in a data file.

No data specified for insertion (<

x1

>)

No depot node was specified in the node defaults section. This is a warning only, the remaining data is processed.

No required data specified for insertion (<

x1

>)

Internal error. Please report this to your HP Response Center.

Illegal structure passed (<

x1

>)

Internal error. Please report this to your HP Response Center.

Illegal parameter passed (<

x1

>)

Internal error. Please report this to your HP Response Center.

208 Chapter 2

OpC54-0504

OpC54-0505

OpC54-0506

OpC54-0507

OpC54-0508

OpC54-0509

OpC54-0510

ITO Error Messages

Upload/Download feature messages

Warning during Add - Regroup Condition already exists

(<

x1

>)

The specified regroup condition exists and replace mode was not selected.

Warning - Instruction Interface not found (<

x1

>)

The specified instruction interface was referenced but does not exist in the database. This happens if a downloaded template used an instruction interface but the interface was not selected for the download and is not available at upload time.

Warning - Message Group not found (<

x1

>)

The specified message group was referenced but does not exist in the database. This happens if an operator was downloaded which is responsible for that group but the group was not selected for the download and is not available at upload time.

Warning - Node Group not found (<

x1

>)

The specified node group was referenced but does not exist in the database. This happens if an operator was downloaded which is responsible for that group but the group was not selected for the download and is not available at upload time.

Warning - Platform missing for node defaults.

Please check platforms on source system and reinstall on destination system.

The platform for a set of node default data does not exist in the database.

Check the platforms available on the source system and reinstall missing platforms on the destination system.

Warning - Platform missing (net/machine=<

x1

>).

The platform for the specified network/machine type is missing. Check the platforms available on the source system and reinstall missing platforms on the destination system.

Warning - Platform missing for node "<

x1

>".

Please check platforms on source system and reinstall on destination system.

Chapter 2 209

OpC54-0511

OpC54-0512

OpC54-0513

OpC54-0514

OpC54-0515

OpC54-0516

OpC54-0517

ITO Error Messages

Upload/Download feature messages

The platform for the specified node is missing. Check the platforms available on the source system and reinstall missing platforms on the destination system.

Warning - trouble ticket already existing, not being replaced

The trouble ticket information already exists in the database and is not going to be replaced (add mode selected).

Warning - management server configuration already existing, not being replaced

The management server configuration already exists in the database and is not going to be replaced (add mode selected).

Warning - DB maintenance already existing, not being replaced

The database maintenance information already exists in the database and is not going to be replaced (add mode selected).

Please wait cleaning up unused references in table "<

x1

>"

...

This is a progress message from 'opccfgupld' if the option '-cleanup' is used to remove orphan database objects introduced with versions before

IT/O A.04.x. Because the cleanup may consume a rather large amount of processing time, a message indicating the beginning of the process is printed.

** DONE ** processed <

x1

> entries

This is an information indicating the completed cleanup of one database table.

Node <

x1

> found in database with different IP address

The specified node already exists in the database but the IP address is different. The reference to this node is skipped. A database entry for a node is not only made if a node is added to the node bank, but also if a message is received for this node (whatever occurs first).

Management Area "<

x1

>" not found in database (path is

"<

x2

>")

210 Chapter 2

OpC54-0604

OpC54-0605

OpC54-0606

OpC54-1001

OpC54-1002

OpC54-1003

ITO Error Messages

Upload/Download feature messages

The specified management area is referenced from within an operators scope, but the area does not exist in the database. This happens if an operator was downloaded which is responsible for that area but the management areas were not selected for the download are not available at upload time.

Assignment to template group '<

x1

>' will be skipped.

Cannot assign template (group) to template group because it is not or several times in the database. If the template (group) is not in the database, then create or upload it, or remove the assignment from the template group. If the template (group) is several times in the database, then delete or rename it, to have unique template (group) names. Then you can upload the assignment by uploading the template group with opccfgupld(1m).

Assignment to node '<

x1

>' will be skipped.

Cannot assign template (group) to node because it is not or several times in the database. If the template (group) is not in the database, then create or upload it, or remove the assignment from the node. If the template (group) is several times in the database, then delete or rename it, to have unique template (group) names. Then you can upload the assignment by uploading the node with opccfgupld(1m).

Assignment to node group '<

x1

>' will be skipped.

Cannot assign template (group) to node group because it is not or several times in the database. If the template (group) is not in the database, then create or upload it, or remove the assignment from the node group. If the template (group) is several times in the database, then delete or rename it, to have unique template (group) names. Then you can upload the assignment by uploading the node group with opccfgupld(1m).

+ downloading nodegroup "<

x1

>"

This is a progress message of the configuration download.

+ downloading managed node "<

x1

>"

This is a progress message of the configuration download.

+ downloading node defaults for <

x1

>/<

x2

>

This is a progress message of the configuration download.

Chapter 2 211

OpC54-1004

OpC54-1005

OpC54-1006

OpC54-1007

OpC54-1008

OpC54-1009

OpC54-1010

OpC54-1011

OpC54-1012

OpC54-1013

OpC54-1014

OpC54-1015

ITO Error Messages

Upload/Download feature messages

+ downloading message group "<

x1

>"

This is a progress message of the configuration download.

+ downloading application group "<

x1

>"

This is a progress message of the configuration download.

+ downloading operator data

This is a progress message of the configuration download.

+ downloading operator responsibility

This is a progress message of the configuration download.

+ downloading operator layout

This is a progress message of the configuration download.

+ downloading layout "<

x1

>"

This is a progress message of the configuration download.

+ downloading operator desktop

This is a progress message of the configuration download.

+ downloading <

x1

> "<

x2

>"

This is a progress message of the configuration download.

+ downloading template "<

x1

>"

This is a progress message of the configuration download.

+ reading node groups from DB

This is a progress message of the configuration download.

+ reading managed nodes from DB

This is a progress message of the configuration download.

+ reading node defaults from DB

This is a progress message of the configuration download.

212 Chapter 2

OpC54-1016

OpC54-1017

OpC54-1018

OpC54-1019

OpC54-1020

OpC54-1021

OpC54-1022

OpC54-1023

OpC54-1024

OpC54-1025

OpC54-1026

OpC54-1027

ITO Error Messages

Upload/Download feature messages

+ reading message groups from DB

This is a progress message of the configuration download.

+ reading applications from DB

This is a progress message of the configuration download.

+ reading operators from DB

This is a progress message of the configuration download.

+ reading <

x1

> templates from DB

This is a progress message of the configuration download.

+ reading notification services from DB

This is a progress message of the configuration download.

+ downloading service "<

x1

>"

This is a progress message of the configuration download.

+ reading regroup conditions from DB

This is a progress message of the configuration download.

+ downloading regroup condition "<

x1

>"

This is a progress message of the configuration download.

+ reading administrator configuration from DB

This is a progress message of the configuration download.

+ reading database maintenance data from DB

This is a progress message of the configuration download.

+ downloading database maintenance data

This is a progress message of the configuration download.

+ reading management server configuration from DB

This is a progress message of the configuration download.

Chapter 2 213

OpC54-1028

OpC54-1029

OpC54-1030

OpC54-1031

OpC54-1032

OpC54-1033

OpC54-1034

OpC54-1035

OpC54-1036

OpC54-1037

OpC54-1038

OpC54-1039

ITO Error Messages

Upload/Download feature messages

+ downloading management server configuration

This is a progress message of the configuration download.

+ reading trouble ticket data from DB

This is a progress message of the configuration download.

+ downloading trouble ticket data

This is a progress message of the configuration download.

+ reading instruction text interfaces from DB

This is a progress message of the configuration download.

+ downloading instruction text interface "<

x1

>"

This is a progress message of the configuration download.

+ uploading node defaults

This is a progress message of the configuration upload.

+ uploading message groups

This is a progress message of the configuration upload.

+ uploading managed nodes

This is a progress message of the configuration upload.

+ uploading management server configuration

This is a progress message of the configuration upload.

+ uploading node groups

This is a progress message of the configuration upload.

+ uploading <

x1

> templates

This is a progress message of the configuration upload.

+ uploading regroup conditions

This is a progress message of the configuration upload.

214 Chapter 2

OpC54-1040

OpC54-1041

OpC54-1042

OpC54-1043

OpC54-1044

OpC54-1045

OpC54-1046

OpC54-1047

OpC54-1048

OpC54-1049

OpC54-1050

OpC54-1051

ITO Error Messages

Upload/Download feature messages

+ uploading applications

This is a progress message of the configuration upload.

+ uploading operators

This is a progress message of the configuration upload.

+ uploading administrator configuration

This is a progress message of the configuration upload.

+ uploading management server configuration

This is a progress message of the configuration upload.

+ uploading trouble ticket information

This is a progress message of the configuration upload.

+ uploading notification services

This is a progress message of the configuration upload.

+ uploading instruction interface

This is a progress message of the configuration upload.

+ verifying target filetree

This is a progress message of the configuration download.

+ parsing download specification file "<

x1

>"

This is a progress message of the configuration download.

+ starting download

This is a progress message of the configuration download.

+ of all configuration data

This is a progress message of the configuration download.

+ of selected configuration data

This is a progress message of the configuration download.

Chapter 2 215

OpC54-1052

OpC54-1053

OpC54-1054

OpC54-1055

OpC54-1056

OpC54-1057

OpC54-1058

OpC54-1059

OpC54-1060

OpC54-1061

OpC54-1062

OpC54-1063

ITO Error Messages

Upload/Download feature messages

+ parsing index file "<

x1

>"

This is a progress message of the configuration upload.

+ parsing data file "<

x1

>"

This is a progress message of the configuration upload.

+ starting upload

This is a progress message of the configuration upload.

+ skipping upload of node defaults

This is a progress message of the configuration upload.

+ skipping upload of message groups

This is a progress message of the configuration upload.

+ skipping upload of managed nodes

This is a progress message of the configuration upload.

+ skipping upload of management server configuration

This is a progress message of the configuration upload.

+ skipping upload of nodegroups

This is a progress message of the configuration upload.

+ skipping upload of <

x1

> templates

This is a progress message of the configuration upload.

+ skipping upload of regroup conditions

This is a progress message of the configuration upload.

+ skipping upload of applications

This is a progress message of the configuration upload.

+ skipping upload of operators

This is a progress message of the configuration upload.

216 Chapter 2

OpC54-1064

OpC54-1065

OpC54-1066

OpC54-1067

OpC54-1068

OpC54-1069

OpC54-1070

OpC54-1071

OpC54-1072

OpC54-1073

OpC54-1074

OpC54-1075

ITO Error Messages

Upload/Download feature messages

+ skipping upload of administrator configuration

This is a progress message of the configuration upload.

+ skipping upload of db maintenance

This is a progress message of the configuration upload.

+ skipping upload of trouble ticket information

This is a progress message of the configuration upload.

+ skipping upload of notification services

This is a progress message of the configuration upload.

+ skipping upload of instruction interface data

This is a progress message of the configuration upload.

+ copying "<

x1

>"

This is a progress message of the configuration upload.

+ downloading file "<

x1

>"

This is a progress message of the configuration download.

+ uploading file "<

x1

>"

This is a progress message of the configuration upload.

+ <

x1

> terminated with <

x2

> warning(s)/error(s)

Configuration download terminated with warnings or errors.

+ <

x1

> finished

Configuration download terminated without warnings and errors.

+ <

x1

> terminated with <

x2

> warning(s)/error(s)

Configuration upload terminated with warnings or errors.

+ <

x1

> finished

Configuration upload terminated without warnings and errors.

Chapter 2 217

OpC54-1076

OpC54-1077

OpC54-1078

OpC54-1079

OpC54-1080

OpC54-1081

OpC54-1082

OpC54-1083

OpC54-1084

OpC54-1090

OpC54-1091

OpC54-1092

ITO Error Messages

Upload/Download feature messages

+ downloading executables

This is a progress message of the configuration download.

+ uploading executables

This is a progress message of the configuration upload.

+ downloading escalation manager configuration

This is a progress message of the configuration download.

+ uploading escalation manager configuration

This is a progress message of the configuration upload.

+ downloading responsible manager configuration

This is a progress message of the configuration download.

+ uploading responsible manager configuration

This is a progress message of the configuration upload.

+ downloading node configuration

This is a progress message of the configuration download.

+ uploading node configuration

This is a progress message of the configuration upload.

+ skipping upload of node configuration

This is a progress message of the configuration upload.

+ downloading ec circuit files for template "<

x1

>"

This is a progress message of the configuration download.

+ uploading ec circuit files for template "<

x1

>"

This is a progress message of the configuration upload.

+ downloading ec libraries

This is a progress message of the configuration download.

218 Chapter 2

OpC54-1093

OpC54-1094

OpC54-1095

OpC54-1100

OpC54-1101

OpC54-1102

OpC54-1103

OpC54-1104

OpC54-1105

OpC54-1106

OpC54-1107

OpC54-1132

ITO Error Messages

Upload/Download feature messages

+ uploading ec libraries

This is a progress message of the configuration upload.

+ downloading ec modules

This is a progress message of the configuration download.

+ uploading ec modules

This is a progress message of the configuration upload.

+ downloading template group "<

x1

>"

This is a progress message of the configuration download.

+ reading template groups from DB

This is a progress message of the configuration download.

+ uploading template groups

This is a progress message of the configuration upload.

+ downloading operator scope

This is a progress message of the configuration download.

+ reading management areas from DB

This is a progress message of the configuration download.

+ downloading toplevel management area "<

x1

>"

This is a progress message of the configuration download.

+ skipping upload of management area information

This is a progress message of the configuration upload.

+ uploading management areas

This is a progress message of the configuration upload.

+ skipping the adjustment of node hierarchies with the node bank

Chapter 2 219

ITO Error Messages

Upload/Download feature messages

The alignment of the node hierarchies with the node bank has been skipped because database actions are skipped. If there is the need to align the node hierarchies with the node bank, you can call opcdbidx

-hierarchy.

220 Chapter 2

ITO Error Messages

Database installation/upgrade messages

OpC55-0004

OpC55-0005

OpC55-0006

OpC55-0007

OpC55-0008

OpC55-0009

Database installation/upgrade messages

Could not initialize error handling.

This error is because the program has too little free memory or the gethostname(2) system call failed.

Not enough resources to continue installation.

The Operating System Resources required by the database system, such as memory or temporary disk space, have been exceeded. The previous error message contains the error message delivered by the database system which may describe the error in more detail.

Error in communication with database.

Check that the database server processes are running. The previous error message contains the error message delivered by the database system, which may describe the error in more detail.

Severe error in database server.

A severe error occurred which has terminated the session. The previous error message contains the error message delivered by the database system which may describe the error in more detail.

Timeout or deadlock had occurred.

Make sure you are the only user working on ITO tables.

Another process has taken a lock on a database table. This does not mean any error if the next error message is 'Retry.' as the transaction will be repeated several times. If the retries still are not successful, the transaction can not be made. A possible reason for this error is a user who accesses the ITO tables with an interactive database query tool.

This user should commit his transactions or exit the query tool.

Repeating the action now will work.

Trying to reconnect to database server...

Chapter 2 221

OpC55-0010

OpC55-0011

OpC55-0020

OpC55-0025

OpC55-0026

OpC55-0027

ITO Error Messages

Database installation/upgrade messages

The connection to the database system has been lost. The application is trying to reconnect to database system. If this is successful the application can go on to work.

Reconnect to database server was successful.

The connection to the database system was lost, but the application has reconnected to the database system successfully and is able to continue.

Reconnect to database server failed.

The connection to the database system has been lost. The application tried to reconnect to database system without success. The application can not continue. Check that the database servers are running. If not, restart the database servers and run the application again.

All retries failed.

Another process has taken a lock on a database table. Repeating the transaction was without success. The transaction can not be made. A possible reason for this error is a user who accesses the ITO tables with an interactive database query tool. This user should commit his transactions or exit the query tool. Repeating the action now will work.

Could not get message from message catalog.

Check that the message catalog exists and has read permissions for all users. The file is: '/opt/OV/lib/nls/<lang>/opcsv.cat where lang is your set language (default: C). Check also that the directory where the message catalog resides is readable for all users.

Retry last action.....

Another process has taken a lock on a database table. ITO tries several times to perform the transaction. The retry itself is not an error, it is simply an indication that ITO has tried to repeat the transaction. If the retries are not successful, the transaction can not be made. A possible reason for this error is a user who accesses the ITO tables with an interactive database query tool. This user should commit his transactions or exit the query tool. Repeating the action now will work.

Usage: opcdbinst [-v][-r|-c|-ac|-rc]

-v : verbose

-r : remove all ITO tables from database

222 Chapter 2

OpC55-0028

OpC55-0029

OpC55-0030

OpC55-0031

OpC55-0032

OpC55-0036

OpC55-0037

ITO Error Messages

Database installation/upgrade messages

-c : clear tables

-ac : add constraints (foreign keys)

-rc : remove constraints (foreign keys)

ITO database installation program. This program creates the ITO database scheme in the OpenView database. For more details, see the manual page opcdbinst(1m) or the Administrator's Reference Guide,

Appendix C.

Error while creating table <

x1

>.

The database table <table> could not be created. The previous error messages will describe the reason in more detail. Probably a lock is the reason.

Error while creating secondary index <

x1

>.

The secondary index <index> for a table could not be created. The previous error messages will describe the reason in more detail.

Error while modifying storage structure of table <

x1

>.

The storage structure of the database table <table> could not be changed.

The previous error messages describe the reason in more detail.

Probably a lock is the reason.

Error while modifying storage structure of secondary index <

x1

>.

The storage structure of the secondary index <index> could not be changed. The previous error messages describe the reason in more detail.

Error while writing startup data into table <

x1

>.

The database table <table> could not be filled with startup data. The previous error messages describe the reason in more detail. Probably a lock is the reason.

Error while deleting table <

x1

>.

The database table <table> could not be deleted. The previous error messages describe the reason in more detail. Probably a lock is the reason.

Error while deleting secondary index <

x1

>.

Chapter 2 223

OpC55-0040

OpC55-0043

OpC55-0099

OpC55-0100

OpC55-0103

OpC55-0104

OpC55-0105

ITO Error Messages

Database installation/upgrade messages

The secondary index <index> for a database table could not be deleted.

The previous error messages describe the reason in more detail.

Error while removing contents of table <

x1

>.

The database table <table> could not be cleared. The previous error messages describe the reason in more detail. Probably a lock is the reason.

Error while removing table <

x1

>.

The database table <table> could not be deleted. The previous error messages describe the reason in more detail. Probably a lock is the reason.

Error in access to directory (<

x1

>):

<

x2

>

The directory <dir> could not be accessed or created. The error number of the previous system call was <errno>. Check that the parent directory of the directory exists.

Usage: opc_dbinit [-v] [-s]

-v : verbose

-s : use Shiftjis as managment server character set

ITO database initialization program. This program fills the ITO database tables with the default configuration. For more details, see the manual page opcdbinit(1m) or the Administrator's Reference Guide,

Appendix C.

<

x1

> contains a wrong key word.

The file <file> which contains the default configuration data, has incorrect syntax. Please use the original defaults file or use the same syntax used in the original defaults file.

<

x1

> contains a wrong value for <

x2

>.

The file <file> which contains the default configuration data, contains a wrong value. Check the values or use the original defaults file.

<

x1

>: end of file reached before value of <

x2

>.

224 Chapter 2

OpC55-0106

OpC55-0107

OpC55-0111

OpC55-0125

OpC55-0126

OpC55-0250

OpC55-0257

ITO Error Messages

Database installation/upgrade messages

The file <file> which contains the default configuration data, has incorrect syntax. Use the original defaults file or use the same syntax used in the original defaults file.

File error (<

x1

>): <

x2

>.

An error occurred while accessing the file <file>. The system call used, delivered the error number <error_num>. Check that the file <file> exists, and that the file and the directory where the file resides have correct permissions.

File <

x1

> contains invalid node <

x2

>.

The file <file> which contains the default configuration data, contains a wrong value. Please check the values or use the original defaults file.

Node <

x1

> is not configured for ITO.

The node <node> does not have a configuration file. Create one, or delete the node from the NODE_NAMES file.

Unknown template <

x1

> specified in node configuration file <

x2

>.

The template <template> does not have a configuration file. Create one, or remove the template from the node configuration file <file>.

Error in template configuration file <

x1

>.

The file <file> which contains default configuration data, has incorrect syntax. Use the original defaults file or use the same syntax used in the original defaults file.

Usage: opcdbupgr [-h] [-v] [-l] [<

upgrdef_file

>]

-h: help

-v: verbose

-l: write logfile

<

upgrdef_file

>: upgrade definition file

ITO database upgrade program. This program does the upgrade of the database fields from ITO version 1.0 to version 1.1. For details, see the manual page opcdbupgr(1m), or the Administrator's Reference Guide,

Appendix C.

Can not create or modify object <

x1

>.

Chapter 2 225

OpC55-0260

OpC55-0261

OpC55-0269

OpC55-0309

ITO Error Messages

Database installation/upgrade messages

The database object <object> for a table could not be created. The previous error messages describes the reason in more detail.

Error while changing columns of table (<

x1

>).

The columns of the table <table> could not be adapted to the new layout.

The previous error messages will describe the reason in more detail.

Database successful upgraded.

The database upgrade from the previous version of ITO was successfully finished. The database tables are now in the new database layout.

Aborting upgrade of ITO tables.

The program has been terminated due to earlier errors. Earlier error messages describe the reason in more detail.

You must be user root to run this program.

This program must be called as superuser root.

226 Chapter 2

ITO Error Messages

Error messages of user interface

OpC60-0005

OpC60-0006

OpC60-0007

OpC60-0008

OpC60-0009

OpC60-0010

OpC60-0011

Error messages of user interface

User name must be entered.

In order to logon to ITO, the user name must be entered. Your ITO administrator defines your user name, along with the password, to give you access to your capabilities within ITO.

Password must be entered.

In order to logon to ITO, the password of the user must be entered. Your

ITO administrator defines your user name, along with the password, to give you access to your capabilities within ITO.

Error during open of the dialogfile (<

x1

>).

Program aborted.

The user interface specification file (file) was not found. Therefore, ITO could not be started. Check that the given file is available and has read permissions.

Could not set the environment (<

x1

>).

ITO has tried to set the environment variable specified. This problem can only occur if internal table limitations apply. Try to set the environment variable before you start ITO.

Could not execute the program with 'execlp'.

(path=<

x1

> pgm=<

x2

>).

System call inside ITO failed. Check UNIX error number for the function in HP-UX manpages.

Could not get the environment (<

x1

>).

The environment variable specified is expected by ITO. Due to internal table limitations, the variable was not available. Exit the program via the OpenView Exit menu and restart ITO.

Reentered password does not match the new password.

Chapter 2 227

OpC60-0015

OpC60-0030

OpC60-0031

OpC60-0032

OpC60-0033

OpC60-0042

ITO Error Messages

Error messages of user interface

You entered a different new password. In order to prevent typing problems, you have to reenter the new password again. Type in the correct new password again or cancel the action.

Error during login occurred.

The login procedure could not be completed. This may happen if some of the ITO server processes do not run properly, or the same user has logged in at the same time from another display station. Exit the program via the OpenView Exit menu, and try to login again.

First finish the already started editing task, before new annotations can be loaded

You have already started an add or modify task for an annotation. You must finish or cancel this task before you are able to load annotations for another message.

Only the creator of the annotation is allowed to perform this action.

You are not allowed to modify or delete annotations created by another author. These actions can only be performed by the creator of the annotation. However, you are allowed to add additional annotations to the message.

Field may not be empty.

In order to complete the editing task, the field which has the input focus may not be left empty.

No annotation was selected.

First select an annotation, then perform the task.

If you want to modify or delete an annotation, you must select one line belonging to the annotation in the listbox. You are then able to perform the required task.

Unable to link file <

x1

>.

ITO was not able to create the specified symbolic link (probably for an

Application Registration File). Either try to create the indicated symbolic link yourself or fix the problem in the affected directory and try again.

This problem can come up because you (or user opc_op) have no right to

228 Chapter 2

OpC60-0090

OpC60-0096

OpC60-0113

OpC60-0198

OpC60-0200

ITO Error Messages

Error messages of user interface

write to the directory or a file with that name already exists, which cannot be overwritten, or the file system is full, quota has been reached, etc.

Help cannot be provided.

The selected object does belong to another application.

ITO provides context-sensitive help. This may be invoked on editable fields by the use of <F1>. If the context-sensitive help has been invoked from the Help menu, the question mark cursor may be clicked on any object. In this case, ITO is only able to provide help for fields which belong to ITO windows, and which are non-map windows.

No instruction available!

No instruction could be found. If you are able to reproduce this problem then please report this to your HP Response Center.

OpenView Windows map is "Read Only" because either

- user is already logged in or

- map has no write permissions.

Please exit and log in again.

For several reasons (for example, shutdown of machine while the ITO

GUI is running, another user might have incorrectly called `ovw -map

<user_name>') the OV map for an ITO user will not have write permission; in this case the ITO user is not able to re-login into the ITO

GUI any more. If you are sure, that no other user has that OV map in access apply the following solution. Solution: /usr/OV/bin/ovwchmod +w

<user_name>

You have just made changes to a registered OpenView Application (e.g.

added a new one). To be able to use this application as ITO

Administrator, OpenView Windows must be restarted. Since ITO is integrated into OpenView Windows, you need to exit this ITO session and start a new one if you want to use the application (or menu items or whatever) that you just changed or added.

Unable to load messages due to database problems.

When a new browser is opened, messages are transferred from the database to the user interface. A message received from the user interface that is obviously corrupt would create an inconsistent state.

Chapter 2 229

OpC60-0202

OpC60-0203

OpC60-0205

OpC60-0208

OpC60-0211

OpC60-0212

ITO Error Messages

Error messages of user interface

Therefore the browser will not appear on the screen. Solution: Try to open the browser again, or if the main `Message Browser' does not appear, restart the user interface.

Could not load the saved browser geometry.

The browser's geometry of the last ITO session could not be queried from the database. The browser will be opened with default geometry.

Could not invoke display receiver.

The display receiver is a child process of the user interface. For some reason it could not be started. See the error messages following this message for a detailed description of the reasons of this fault ( maybe maximum number of processes exceeded). See Solution of the more detailed error message and restart the user interface.

Attempt to read from display receiver failed.

ITO events (for example, a new message, successful end of action) are received from the display receiver and transmitted in a queue from the display receiver to the user interface. The user interface was unable to read the next event from this queue. Restart the user interface.

Unable to append message to internal message list.

Warning: this may cause inconsistencies during this session.

A message could not be stored in the internal message lists of the user interface. If this message appears when trying to open the `History

Message Browser' close and reopen this browser again. Otherwise, restart the user interface.

Cannot retrieve operator initiated action from database.

Open `Message Details' for this message, to review the predefined operator-initiated action. Try to start this action manually. If `Details' could not be opened, restart the user interface.

Warning: at least one of the selected messages does not contain the specified type of action.

The ITO operator pressed `Perform Action' for a message that has no predefined operator-initiated action.

230 Chapter 2

OpC60-0213

OpC60-0214

OpC60-0219

OpC60-0220

OpC60-0221

OpC60-0229

ITO Error Messages

Error messages of user interface

Warning: the specified type of action is currently running for at least one of the selected messages.

The ITO operator tried to start an action twice for the same message.

Wait until the first operator-initiated action is completed. This is indicated by the `O'-flag in the message browser. This field must be `S' for successful or `F' for failed. Then the action can be performed again.

Perform action failed:

Display Manager reports Error on action request.

Display Manager reports error on action request. Look for a more detailed description following this error message. Verify that the ITO management server processes are running. If not, restart the ITO management server processes. Do this either from the administrator user interface or execute the command: /usr/OV/bin/OpC/opcsv -start If the action was invoked from the Message Details window, try to start it directly from the Message Browser.

Unable to perform action since management server is down

Restart the ITO management server processes. Do this either from the administrator user interface, or execute the command:

/usr/OV/bin/OpC/opcsv -start

Unable to (un)acknowledge message(s).

The database could not serve a request to (un)acknowledge the selected message(s). If more than one message should be acknowledged, try to acknowledge them in smaller portions. If a single message cannot be acknowledged, restart the user interface.

Unable to unacknowledge message

The database could not serve a request to unacknowledge the selected messages. If more than one message should be acknowledged, try to acknowledge them in smaller portions. If a single message cannot be acknowledged restart the user interface.

Unable to inform Display Manager about acknowledge request

Displays of other users will not be updated

Chapter 2 231

OpC60-0230

OpC60-0231

OpC60-0235

OpC60-0236

ITO Error Messages

Error messages of user interface

Connection to display manager lost. The display manager is informed about the acknowledge request in order to update the displays of other

ITO operators. Verify that the ITO management server processes are running. If not, restart the ITO management server processes. Do this either from the administrator user interface, or execute the command:

/usr/OV/bin/OpC/opcsv -start

Unable to inform Display Manager about action start

Displays of other users will not be updated

Connection to display manager lost. The display manager is informed about the start of an action in order to update the displays of other ITO operators. Verify that the ITO management server processes are running. If not, restart the ITO management server processes. Do this either from the administrator user interface, or execute the command:

/usr/OV/bin/OpC/opcsv -start

Unable to inform Display Manager about unacknowledge request

Displays of other users will not be updated

Connection to display manager lost. The display manager is informed about the unacknowledge request in order to update the displays of other

ITO operators. Verify that the ITO management server processes are running. If not, restart the ITO management server processes. Do this either from the administrator user interface, or execute the command:

/usr/OV/bin/OpC/opcsv -start

Error in message filter: filtering of message failed.

In most cases the specified message text pattern is syntactically incorrect. Look for a more detailed description following this error message. Simplify the message filter (for example, don't use or use simple message patterns) in order to find the component that is causing the troubles.

Message with unknown node attribute "<

x1

>" found.

Update of status colors for this node failed.

May be caused by a change in the configuration of your

"Managed Nodes".

Update of status colors for this node failed. May be caused by a change in the configuration of your 'Managed Nodes'. A message contains a node attribute that does not correspond to any of the ITO operators' managed

232 Chapter 2

OpC60-0250

OpC60-0255

OpC60-0261

OpC60-0292

ITO Error Messages

Error messages of user interface

nodes. For this reason the color of a node on the OpenView submaps could not be set according to the severity of the message. This can happen if the ITO administrator has changed your configuration during the current ITO operator session. To get the new configuration, exit ITO and log on again.

Can't get message for the browser from database.

A message that has been unacknowledged by another ITO operator can not be written back into your main `Message Browser'. The attempt to retrieve it from the database failed. Another ITO operator should acknowledge the message and then unacknowledge it again. If the error appears again, restart the user interface.

Your acknowledge request can not be served.

Unable to compose an acknowledge list.

Try to perform the same acknowledge request again. If this does not work, try to acknowledge the messages in smaller portions.

Warning: Cannot disconnect from database.

This may cause troubles if ITO is not terminated properly (Display receiver process opcdispr hangs).

This may cause troubles if ITO is not terminated properly (display receiver process, opcdispr, hangs). To be sure that this does not lead to any further problems, exit ITO and log on again. If the ITO session can not be terminated properly, look for any remaining display receiver processes. Use the command: `ps -ef | grep opcdispr' to review the display receiver processes running. If a display receiver doesn't have an associated ITO parent process (third column is `1' (one)) kill this display receiver process: kill <process-id> (<process-id> = second column in `ps' output).

Cannot read the contents of the current working directory "<

x1

>". If you are using SQL*Net, the database connect may fail.

Under normal circumstances, you should set and export environment variable $OPC_HOME to a directory that you can change to, read from and write into. If you don't want to do that then ITO will try to change into $HOME. Failing that, ITO will change into /tmp. If you have insufficient permissions for even this directory you may well have problems when working with the GUI later on.

Chapter 2 233

OpC60-0293

OpC60-0300

OpC60-0301

OpC60-0302

OpC60-0303

OpC60-0304

ITO Error Messages

Error messages of user interface

Cannot write to the current working directory

"<

x1

>". When saving files you will have to specify a different directory.

Under normal circumstances, you should set and export environment variable $OPC_HOME to a directory that you can change to, read from and write into. If you don't want to do that then ITO will try to change into $HOME. Failing that, ITO will change into /tmp. If you have insufficient permissions for even this directory you may well have problems when working with the GUI later on.

First finish the editing task already started before beginning a new task.

You have already opened a sub window for another task. The opened window might be iconized or hidden by another window. You must finish or cancel this task before you are able to continue.

The syntax for specification of the Message Type is invalid.

A syntax error was detected in the message type pattern definition.

Check the syntax of the pattern by invoking context-sensitive help for the pattern field.

Invalid time format ( valid is "1h40m10s" ).

The specified time format is invalid. You may enter a number only, which is interpreted as seconds, or you may use 'h' for hours, 'm' for minutes and 's' for seconds. For example: 12h45m11s

Invalid Interval specified. A specification less than

<

x1

>s is not allowed.

The specified time interval is invalid or too short. There is a minimum value required. A value less then this minimum would make no sense, since the affected processes would probably encounter performance problems.

Too many separators defined. Not more than <

x1

> are allowed.

234 Chapter 2

OpC60-0305

OpC60-0306

OpC60-0307

OpC60-0308

OpC60-0309

OpC60-0310

ITO Error Messages

Error messages of user interface

You are not allowed to specify more than n separators. The default separators are blank and the tab character (specified as \t) if you leave the field empty. A valid specification would be '.\n \t' for the use of the separators, '.', carriage return, blank and tab.

Invalid timespan specified. A specification less than

<

x1

>s is not allowed.

The specified time interval is invalid, or too short. There is a minimum value required. A value less then this minimum would make no sense, since the value is used to detect duplicate messages. Use the option only for messages which might appear in a specific time period again, as an duplicate.

The re-send time specification must be 0, or greater than the time span.

The specified time interval is invalid or too short. The value must be greater then the time span, because it determines the time after which you want to re-send suppressed duplicate messages.

The Node (<

x1

>) is not defined within ITO yet.

The specified node is not known within ITO. You may only use nodes which are already defined within ITO (Node Bank), because it is not possible to perform actions on nodes which are not managed by ITO.

First define the node in the Node Bank or in one of the Node Groups.

The syntax for specification of the text pattern is invalid.

A syntax error was detected in the message text pattern definition.

Check the syntax of the pattern by invoking context-sensitive help for the pattern field.

The content of the field is invalid or contains a reference to an unknown parameter.

You may only use reference parameters which are reserved words for

ITO, or user-defined parameters.

The syntax for the specification of the Enterprise is invalid.

Chapter 2 235

OpC60-0311

OpC60-0312

OpC60-0313

OpC60-0314

OpC60-0315

OpC60-0321

ITO Error Messages

Error messages of user interface

The format of the specified enterprise is invalid. The enterprise has the format of A.B.C.D..., where A, B, C, and D are subidentifiers in decimal notation. For example, a valid enterprise is 1.3.6.1.4.1.11.2.3

The syntax for the list is invalid. Multiple values must be separated with the use of the "|" character.

A list of elements can be only specified by the use of '|' (bar) as the separator.

The syntax for the node list is invalid. Multiple nodes must be separated with the use of the "|" character.

A list of elements can be only specified by the use of '|' (bar) as the separator.

The field contains an invalid node name or a reference to an unknown variable.

The specified node is not known within ITO or you used an invalid reference parameter ( reserved word for ITO or user-defined parameter ).

You may only use nodes which are already defined within ITO (Node

Bank), because it is not possible to perform actions on nodes which are not managed by ITO.

A template with the same name already exists. Use a unique name for the template.

There already exists a template with the same name. Make sure that the name is unique, because the name will be used later, to assign the template to nodes.

Message Group "Misc" is a reserved group and may not be used.

The message group (Misc) has a special meaning, and may not be used here. It is used to hold all messages which are assigned to a message group which is not yet defined within ITO.

An instruction interface with the same name already exists. Use a unique name for the instruction interface.

236 Chapter 2

OpC60-0323

OpC60-0326

OpC60-0327

OpC60-0329

OpC60-0330

OpC60-0331

OpC60-0332

ITO Error Messages

Error messages of user interface

There already exists an instruction interface with the same name. Make sure that the name is unique, because the name will be used later, to assign the instruction interface to templates or conditions.

A condition with the same description already exists.

Please use a unique description for the condition.

You are not allowed to use the same description text for two different conditions. Please use a unique description.

Unable to delete download specification file <

x1

>.

ITO could not delete the old Download Specification File. You gave the

OK to delete this file before writing a new one, but for some reason, ITO could not delete it. Perhaps it is on a read-only file system.

Please specify a path for the download directory.

This is an information message. ITO successfully wrote the desired

Download Specification File into the specified directory.

ITO Download Configuration

Watch this window for messages on the progress of the Configuration

Download that you just started.

A node must be selected for the requested report.

A report was requested for a specific node, but no node was previously selected. Select a single node on one of the HP OpenView map windows, and activate the report again.

A nodegroup must be selected for the requested report.

A report was requested for a specific nodegroup, but no nodegroup was previously selected. Select a nodegroup from the Node Group Bank map and activate the report again.

A messagegroup must be selected for the requested report.

A report was requested for a specific message group, but no message group was previously selected. Select a message group from the Message

Group map, and activate the report again. The report can only be invoked for a single message group at a time.

Chapter 2 237

OpC60-0333

OpC60-0334

OpC60-0335

OpC60-0336

OpC60-0337

ITO Error Messages

Error messages of user interface

An application must be selected for the requested report.

A report was requested for a specific application, but no application was previously selected. Open the Application Desktop window. Select a single application, and activate the report again. The report can only be invoked for one application at a time.

A user must be selected for the requested report.

A report was requested for a specific operator, but no operator was previously selected. Open the User Bank window first. Select one operator and activate the report again. The report can only be invoked for a single operator at a time.

Please select one or more messages in the corresponding browser before trying to run this report.

A report was requested for a specific message in the Message Browser, but no message was previously selected. Open the Message Browser window first. Select one message and activate the report again. The report can only be invoked for a single message at a time.

An error occurred during generation of the report.

The specified report generation failed, due to an error with the database report writer. Check that the report specification file for the requested report is available and accessible for user root and opc_op. The report specification files are in following directories: HP-UX 9.x:

/usr/OV/conf/OpC/mgmt_sv/reports/<LANG> HP-UX 10.x:

/etc/opt/OV/share/conf/OpC/mgmt_sv/reports/<LANG> You might also be able to issue the report directly, by using the report writer in the form:

$ INGRES: report openview

-i/usr/OV/conf/OpC/mgmt_sv/reports/C/<filename> ORACLE, as user opc_op: runrep20 userid=/@P:openview module=/usr/OV/conf/OpC/mgmt_sv/reports/C/<filename>

Could not open runtime file (<

x1

>) with report information.

The configuration file for the ITO reporting utility is not accessible.

Check that the listed file for the report configuration is available and has read permission for everyone. If the file is not available, create, at least, an empty file.

238 Chapter 2

OpC60-0338

OpC60-0339

OpC60-0340

OpC60-0341

OpC60-0342

OpC60-0343

ITO Error Messages

Error messages of user interface

Could not open report output file (<

x1

>).

The report output file could not be opened by the ITO reporting facility.

Check that the file path is set correctly, and that the current user is allowed to open the file listed. The ITO Administrator generally accesses files as the user root. ITO Operators create all files as user opc_op.

Could not create report output file (<

x1

>).

The report output file could not be created by the ITO reporting facility.

Check that the file path is set correctly, and that the current user is allowed to create the listed file. The ITO Administrator generally accesses files as user root. ITO Operators create all files as user opc_op.

A template must be selected for the requested report.

A report was requested for a specific template, but no template was previously selected. Open the Message Source Templates window first.

Select one template from the list, and activate the report again. The report can only be invoked for a single template at a time.

An error occurred during generation of the report.

The execution of the report program (<

x1

>) failed.

The report generation for a report of type (PGM) failed due to an error with the configured report program. Check that the listed UNIX program file is available and executable. The ITO Administrator generally accesses files as user root. ITO Operators create all files as user opc_op.

Check that the program is executable by the UNIX users listed above, and creates valid output.

Could not open output file.

The report output file could not be opened by the ITO reporting facility.

Check that the file permissions are set correctly, and that the current user is allowed to read the file. The ITO administrator generally accesses files as user root. ITO Operators create all files as user opc_op.

Could not write output file.

The report output file could not be generated by the ITO reporting facility. Check that the file permissions are set correctly, and that the current user is allowed to write to the file. The ITO Administrator generally access files as user root. ITO Operators create all files as user opc_op.

Chapter 2 239

OpC60-0345

OpC60-0348

OpC60-0350

OpC60-0351

OpC60-0352

OpC60-0409

ITO Error Messages

Error messages of user interface

No report selected.

No report was selected in the report list. Select a report from the list, and activate the report again.

The report writer call returned an error: <

x1

>

To produce an Oracle report writer report, ITO calls the Oracle report writer program runrep20. This report writer program returned an error.

You could check following things:

• Do you use the correct Oracle Reports version (see installation guide)

• Are the permissions of the report writer program correct. The user opc_op must be able to execute the report writer binary.

• Is the environment variable ORACLE_HOME set correct (see installation guide).

Invalid number of entries specified.

The entered value is invalid. It must be a numeric value greater than 0.

Only whole numbers are allowed. Clear the field and enter a valid numeric value again.

File (<

x1

>) could not be opened.

The reference testfile either does not exist, or is not readable by the

UNIX user, root. Check that the file listed has the corresponding permissions, and that user root is able the read it.

File (<

x1

>) was not found or is not an executable program or script.

The given file either does not exist, or is not executable by the UNIX user root. Check that the file listed has the corresponding permissions, and that the user root is able to execute it.

Unable to automatically determine the node type for node <

x1

>.

The method to automatically determine the node type is SNMP GET. In order for SNMP GET to work, make sure that

• the snmp daemon is working on the affected node and

240 Chapter 2

OpC60-0410

OpC60-0460

OpC60-0520

OpC60-0521

ITO Error Messages

Error messages of user interface

• the following entry exists (for HP-UX) on the node in file

/etc/snmpd.conf: 'get-community-name:' or 'get-community-name: public'.

Unable to automatically determine the node type for node <

x1

>, since SNMP OPEN fails.

The method to automatically determine the node type is SNMP GET. In order for SNMP GET to work make sure that

• the snmp daemon is working on the affected node and

• the following entry exists (for HP-UX) on the node in file

/etc/snmpd.conf: 'get-community-name:' or 'get-community-name: public'.

Invalid node specification found.

The value in the node field of the action specification is neither an ITO managed node nor a valid parameter. To get more information about the node specification syntax, click on the node field and press <F1>.

ITO could not find an Application Registration File for the integrated

OpenView Application that you have specified in your ITO configured OV

Application or Action. Without this Application Registration File, ITO will not be able to start the Action or Application you have specified. So you must find out where the Application Registration File for your new

OV Application/Action is and copy it to the given location. Also, you must rename the copied file to the name given in the error message or else change the symbolic link (i.e. delete it and create a new one) that ITO created to point to the copied file.

Cannot open hpterm or run script/program

(/usr/bin/X11/hpterm or the desired shell script or program returned an error).

ITO could not start a terminal on your display. This would be hpterm for an HP system or xterm for another system. Perhaps you don't have enough free memory or too many processes or open files. Possibly the terminal could be started but the program or script that was called returned an error-status.

Chapter 2 241

OpC60-0544

OpC60-0545

OpC60-0613

OpC60-0614

ITO Error Messages

Error messages of user interface

Could not find the application registration file for the integrated application "<

x1

>" under the directory "<

x2

>".

For ITO Motif GUI users to be able to use the application, the ITO Administrator must add a symbolic link to the correct application registration file. For example:

# ln -s /opt/OV/NewApplication/registration/C/NewApplArf

\

/etc/opt/OV/share/conf/OpC/mgmt_sv/appl/registration/C

After the symbolic link has been added you must restart your GUI if you want to use this ovw-integrated application.

The ITO administrator must add a symbolic link to the correct application registration file that contains an 'Application: <applname>' line, under the

/etc/opt/OV/share/conf/OpC/mgmt_sv/appl/registration/<lang> directory.

Ask the system administrator of the management server to check that a valid entry for 'opcgrp' exists in the system group file /etc/group or

/etc/logingroup.

Unable to activate management server.

Connection to display manager lost. Verify that the ITO management server processes are running. If not, restart them. Do this either from the administrator user interface, or execute the command:

/usr/OV/bin/OpC/opcsv -start

Unable to acknowledge all active messages of node <

x1

>.

The message cannot be escalated to another management server, because no configured message target rule fits the current date/time and/or message attribute criteria.

242 Chapter 2

ITO Error Messages

NT installation messages

NT installation messages

OpC130-0001

OpC130-0002

OpC130-0003

OpC130-0004

OpC130-0005

OpC130-0006

OpC130-0007

OpC130-0008

E-> Error from <

x1

>.

An internal error has occurred. Report the function name and error number to your HP Response Center.

E-> Error from <

x1

> for <

x2

>.

An internal error has occurred. Report the function name and error number to your HP Response Center.

U-> Unknown return value from <

x1

>. errno=<

x2

>.

An internal error has occurred. Report the function name and error number to your HP Response Center.

E-> Unable to convert <

x1

>.

An internal error has occurred. Report the function name and error number to your HP Response Center.

U-> Invalid parameter for <

x1

>. nr=<

x2

>.

An internal error has occurred. Report the function name and error number to your HP Response Center.

T-> Tracing information: <

x1

> <

x2

> <

x3

>.

This is a tracing message from the NT setup program.

U-> Unknown return value from <

x1

> for <

x3

>. errno=<

x2

>.

An internal error has occurred. Report the function name and error number to your HP Response Center.

usage: <

x1

> [-n|-u|-s||-h|[-p <

drive

>] [-f]]

-n complete interactive Installation (initiated from remote)

-u uninstall complete installation

-s setup the ITO Agents

(User/Service/Path/Filepermissions)

Chapter 2 243

OpC130-0010

OpC130-0011

OpC130-0012

OpC130-0013

OpC130-0020

OpC130-0021

OpC130-0022

OpC130-0023

ITO Error Messages

NT installation messages

-p <

drive

> setup the ITO Agents

(User/Service/Path/Filepermissions) in pre-installed mode on <

drive

>

-f force removal of user accounts and profiles

-h display help

The Logfile can be found in <

x2

>

The setup program for the NT agent was called with the wrong command line.

I-> Setup program started (preinit).

Informational message that the setup on NT was started.

I-> Setup program started at <

x1

>. It may need some time.

Informational message that the setup on NT was started.

I-> Setup program successfully finished.

Informational message that the setup on NT has finished.

E-> Setup program aborted.

There was a problem during the installation. Look into the tracefile to find out more about the problem.

I-> Installing HP ITO Agent on drive <

x1

>.

Informational message that the setup on NT is installing the agent on the said drive.

I-> Starting to remove the HP ITO Agent from drive <

x1

>.

Informational message that the setup on NT is removing the agent from the said drive.

I-> Starting the reinstallation of the HP ITO Agent on drive <

x1

>.

Informational message that the setup on NT is re-installing the agent on the said drive.

I-> Configuration installed.

244 Chapter 2

OpC130-0024

OpC130-0025

OpC130-0026

OpC130-0028

OpC130-0030

OpC130-0031

OpC130-0032

OpC130-0033

OpC130-0034

ITO Error Messages

NT installation messages

Informational message that the setup has finished installing the configurational data.

I-> The opcinfo file was updated.

The opcinfo file was successfully updated by the NT installation program.

I-> From opcsetup.inf found destination drive <

x1

>.

Informational message that the setup found the given drive as installation drive in the opcsetup.inf file.

I-> Installed source for event log messages <

x1

>.

Informational message telling that the source for the NT installation message that are written into the NT eventlog are registered with the

NT eventlog service.

I-> Writing this information into the opcinfo file.

Management Server is <

x1

>. Installation Time is <

x2

>.

Informational message that tells which management server is written into the opcinfo file.

I-> Found backup domain controller <

x1

>.

This is just an informational message that lists the first found backup domain controller in the domain the node is in.

I-> No backup controller in domain <

x1

>.

Informational message that there was no backup domain controller found in the domain the node is in.

I-> This system is standalone.

Informational message stating that the node is a standalone system.

I-> This system is a primary controller in domain <

x1

>.

Informational message stating that the node is a primary domain controller.

I-> This system is a backup controller in domain <

x1

>.

Chapter 2 245

OpC130-0035

OpC130-0040

OpC130-0041

OpC130-0042

OpC130-0043

OpC130-0045

OpC130-0046

OpC130-0047

OpC130-0048

ITO Error Messages

NT installation messages

Informational message stating that the node is a backup domain controller.

I-> This system is a workstation in domain <

x1

>.

Informational message stating that the node is a workstation in a domain.

I-> No installed version of ITO found.

Informational message that no ITO agent was found on this node.

Perhaps because there was no agent installed before.

I-> An installed version of ITO was found on drive <

x1

>.

The setup program for NT found an agent already installed on the named drive.

I-> Will check all drives on system.

Informational message that all drives are searched.

I-> Checking Drive <

x1

>.

Status message of the setup program saying that the named drive is checked.

I-> Filesystem on drive <

x1

> is not NTFS.

The checked filesystem is not an NTFS filesystem, but may be a FAT or

HPFS filesystem.

I-> Not enough free space on drive <

x1

>.

The free space used to install the NT agent is not sufficient on the named drive.

I-> Destination for the setup is drive <

x1

>.

Informational message stating which drive is the target drive for the installation.

W-> The volume <

x1

> does not contain a recognized file system.

The checked filesystem is not an NTFS filesystem.

246 Chapter 2

OpC130-0050

OpC130-0051

OpC130-0052

OpC130-0053

OpC130-0054

OpC130-0055

OpC130-0056

OpC130-0060

OpC130-0061

ITO Error Messages

NT installation messages

I-> Copied file <

x1

>.

Status message of the setup program stating that the given file was successfully copied.

I-> Set rights on <

x1

>.

Status message of the setup program stating that the file rights for the given file were successfully set.

I-> Finished transfering files.

Status message of the setup program stating that the transfer of the NT agent files has finished successfully.

I-> Finished deleting source files.

Status message of the setup program stating that the deletion of the NT agent files has finished successfully.

I-> Finished setting file rights

Status message of the setup program stating that the setting of the file rights has finished successfully.

I-> The file <

x1

> could not be copied to its target <

x3

>.

Therefore it is copied to <

x2

> for the moment and will be moved to the correct place after the next reboot when the targetfile is not locked.

A file could not be copied at the moment. It is scheduled to be moved in place after the next reboot.

E-> The architecture string <

x1

> is invalid.

The architecture string could not be used to access the software package on the installation server.

I-> Created new user account <

x1

>.

A new user account was created on the NT node. This account is used for the NT ITO agent.

I-> Added privileges for user account <

x1

>.

Privileges were added to the given user account.

Chapter 2 247

OpC130-0062

OpC130-0071

OpC130-0072

OpC130-0073

OpC130-0074

OpC130-0075

OpC130-0076

OpC130-0077

OpC130-0078

OpC130-0080

ITO Error Messages

NT installation messages

I-> Installed service <

x1

>.

The given service was registered with the NT service manager.

I-> Removed all privileges of <

x1

>.

All privileges for the given user were removed by the setup program.

I-> Removed the user account <

x1

>.

The user account was successfully removed.

I-> Account <

x1

> not removed because it may be needed on the other domain controller(s).

The account was note removed although a de-installation is taking place, because the account might still be used by domain controllers.

I-> Service <

x1

> does not exist. No need to delete it.

The de-installation tried to delete an ITO service, that was not existing.

This is not an error.

I-> Service <

x1

> was deleted.

The service was deleted successfully.

W-> Unable to delete user profile for user <

x1

>.

The user profile for the given user cannot be deleted. If you encounter this problem with Windows NT 4.0, please remove the profile manually with the Control Panel 'System'.

W-> Unable to delete user profile for user <

x1

> (SID

<

x2

>).

The user profile for the given user cannot be deleted. If you encounter this problem with Windows NT 4.0, please remove the profile manually with the Control Panel 'System'.

I-> Successfully deleted the user profile for user <

x1

>

(SID <

x2

>).

Informational message that the user profile was successfully deleted.

E-> Trouble registering the event source <

x1

>.

248 Chapter 2

OpC130-0081

OpC130-0082

OpC130-0085

OpC130-0090

OpC130-0100

OpC130-0101

OpC130-0102

OpC130-0103

ITO Error Messages

NT installation messages

The installation program was not able to register the given event source.

HP ITO Agent Messages sent to the Eventlogging mechanism will not be resolvable.

E-> Trouble accessing the system event log.

The System Event log could not be opened. Please check with the NT

Eventviewer for problems.

E-> System event log is full. Please clean up System event log or change Event logfile size or wrapping mode.

The System Event log is full. Setup messages of the HP ITO Agent will not be sent to the System Event log.

E-> The Schedule service is disabled. Please call the script <

x1

> manually to remove the HP ITO agent completely.

The Scheduler is disabled. The remove script could not be run automatically. Please run the given script manually in a Command

Prompt to remove the HP ITO Agent files.

I-> Backing up HP ITO agent file <

x1

> to <

x2

>.

This is just an informational message. The backup of the agent files is done each time a new agent is installed. This backup will be used to restore the agent files in case the installation of the new files failed.

W-> Could not find opcsetup.inf file.

The installation program was unable to find the opcsetup.inf file that contains information about the installation parameters.

W-> Didn't find an acceptable drive for the HP ITO Agent.

None of the drives available to this machine could be used for the ITO agent. The ITO agent requires 10MB of free space on a local NTFS formatted disk.

I-> Didn't find an installed HP ITO Agent.

There was no ITO agent found.

W-> Don't know the version of the agents.

Chapter 2 249

OpC130-0104

OpC130-0150

OpC130-0151

ITO Error Messages

NT installation messages

There is an ITO agent installed, but the installation program is unable to retrieve the version of that.

I-> NOTE: ITO software, version <

x1

> installed on system

<

x2

>, will be reinstalled.

There was already an agent installed, but it will be reinstalled.

W-> No password specified. Generating a random one.

This message is not an error, but is provided for your information.

W-> Generating a random password for the account on this node. Since this is a primary domain controller you will have to change it to a known password when you want to install the agent to a Backup Domain Controller in this domain.

This message is not an error, but is provided for your information.

OpC130-0152

OpC130-0153

OpC130-0154

OpC130-0156

OpC130-0157

This message is not an error, but is provided for your information.

W-> The given password is too long. It will be cut after the first <

x1

> characters.

This message is not an error, but is provided for your information.

E-> Decrypting the password returns an error. Will generate a random password and continue.

There was an internal error in the password encryption/decryption functionality.

E-> Encountered an unknown NT error code <

x1

> while calling NT API function '<

x2

>'.

A call to an NT API function failed with an error, but the error code cannot be resolved to an NT error message.

E-> The call to the NT API function '<

x2

>' failed with the following system error: <

x1

>

A call to an NT API function failed with the given error.

250 Chapter 2

OpC130-0158

OpC130-0200

OpC130-0210

OpC130-0211

OpC130-0221

OpC130-0222

OpC130-0223

OpC130-0224

OpC130-0230

ITO Error Messages

NT installation messages

E-> The call to the NT API function '<

x2

>' for '<

x3

>' failed with the following system error: <

x1

>

A call to an NT API function failed with the given error.

E-> More than one primary domain controller in domain

<

x1

>.

Make sure your domain is set up correctly.

E-> Timeout from startup <

x1

>.

The service could not be started. Check if the user for the service exists and if the password is correct. Check for additional tracing of the service program.

E-> The Control Agent didn't register at the RPC Server or has already terminated!

There was an error starting up the control agent. Check for additional tracing of the agent.

E-> File <

x1

> exists and can not be overwritten.

There was an error copying the file. Verify that the file exists, is not currently being used, and has the correct permissions.

E-> File <

x1

> can not be copied (File not found).

There was an error copying the file. Verify that the file exists, is not currently being used, and has the correct permissions.

E-> File <

x1

> can not be copied (Access denied).

There was an error copying the file. Verify that the file exists, is not currently being used, and has the correct permissions.

E-> File <

x1

> can not be copied because it is in use by another process.

There was an error copying the file. Verify that the file exists, is not currently being used, and has the correct permissions.

E-> Couldn't lookup account <

x1

>.

Check to make sure that the user account actually exists. Check for previous error messages during the installation.

Chapter 2 251

OpC130-0231

OpC130-0232

OpC130-0233

OpC130-0234

OpC130-0235

OpC130-0240

OpC130-0241

OpC130-0242

OpC130-0243

OpC130-0244

ITO Error Messages

NT installation messages

E-> Group <

x1

> not found.

Check to make sure that the group actually exists. Check for previous error messages during the installation.

E-> User <

x1

> does not exist.

Check to make sure that the user account actually exists. Check for previous error messages during the installation.

E-> Invalid account type of user <

x1

>.

Check to make sure that the user account actually exists. Check for previous error messages during the installation.

E-> Access denied while adding user <

x1

> to group <

x2

>.

Check to make sure that the installation program runs with the appropriate administrative rights.

E-> Access denied while installing the user <

x1

>.

Check to make sure that the installation program runs with the appropriate administrative rights.

E-> No Password for the new user. Can't install user

<

x1

>.

Check for previous error messages.

E-> No Password for user <

x1

>. Can't install service

<

x2

>.

Check for previous error messages.

E-> User <

x1

> exists though it could not be looked up before.

An internal error has occurred. Report to your HP Response Center.

E-> Password too short or too long.

This may be caused by special settings in your password policy. Use a different password.

E-> Password Check: User <

x1

> not found.

252 Chapter 2

OpC130-0252

OpC130-0254

OpC130-0255

OpC130-0256

OpC130-0257

OpC130-0260

OpC130-0261

ITO Error Messages

NT installation messages

Check to make sure that the user account actually exists. Check for previous error messages during the installation.

E-> Failed to stop service <

x1

>.

There was an error stopping the service. Check for additional tracing of the agent.

E-> Invalid user account <

x1

>.

Check to make that the user account actually exists. Check for previous error messages during the installation.

E-> The service <

x1

> has been marked for deletion.

The service seems to be still running. Shut it down manually and retry. If this happens again report to your HP Response Center.

E-> Failed to install service <

x1

>.

The service was not successfully installed. Check for previous error messages.

E-> The Schedule service is disabled on node <

x1

>.

The Schedule service may not be disabled because it is used to execute programs on other nodes. Re-enable the Schedule service on the NT node and try again.

E-> This is a backup controller. The user <

x1

> does not exist in the domain <

x2

>. Please install the HP ITO

Agents on the primary domain controller <

x3

> first.

Since a backup domain controller does not have local users it has to use the domain HP ITO account with the password setting that was created on the primary domain controller. This must be done before the backup domain controller can be installed.

E-> This is a backup controller. The password given for user <

x1

> is wrong. Please reinstall and give the password that is set on the primary domain controller

<

x2

> for this user.

Chapter 2 253

OpC130-0262

OpC130-0270

OpC130-0271

OpC130-0272

OpC130-0275

OpC130-0276

OpC130-0277

OpC130-0278

ITO Error Messages

NT installation messages

Since a backup domain controller does not have local users it has to use the domain HP ITO account with the password setting that was created on the primary domain controller. This must be done before the backup domain controller can be installed.

E-> This is a primary controller. The password given for user <

x1

> is wrong. Please reinstall and give the password that is set for the agent on the backup domain controller <

x2

> for this user.

See message.

E-> Can't find out my managment server's name.

The installation program cannot report to the management server about the installation. Check for previous error messages.

E-> Connection error to management server <

x1

>.

Make sure that all server processes are running on the management server.

E-> Agent status could not be reported to management server <

x1

>.

Make sure that all server processes are running on the management server.

E-> Don't know which version was installed before.

The installation process found an old ITO agent, but cannot resolve its version. Deinstall the old agent before installing the new one.

E-> Don't know the version of the new agents.

This is an internal error message. Please look for previous errors.

E-> NOTE: ITO software, version <

x1

> installed on system

<

x2

>, belongs to Management Server <

x3

>.

The node may not be reinstalled from that management server. Use the named management server to reinstall the agent software.

I-> NOTE: ITO software, version <

x1

> installed on system

<

x2

>, will be replaced by version <

x3

>.

254 Chapter 2

OpC130-0280

OpC130-0281

OpC130-0282

OpC130-0283

OpC130-0284

ITO Error Messages

NT installation messages

A previous version of the agents were already installed and will be overwritten now.

E-> Unable to retrieve the domain controllers of the current domain <

x1

>. Maybe the PDC is down or unreachable. Please check and try again.

The setup program was not able to retrieve the domain controllers for the domain the node is in. Please check if the domain configuration is correct and if the computer browser service is working.

E-> The retrieval of the domain controllers was denied, because of insufficient access rights. Please check and try again.

The setup program was not able to retrieve the domain controllers for the domain the node is in. Please check if the domain configuration is correct and if the computer browser service is working.

E-> The retrieval of the domain controllers failed, because the remote computer is not available. Please check and try again.

The setup program was not able to retrieve the domain controllers for the domain the node is in. Please check if the domain configuration is correct and if the computer browser service is working.

E-> The retrieval of the domain controllers failed, because the remote computer currently handles as much requests as the computer can accept. Please check and try again.

The setup program was not able to retrieve the domain controllers for the domain the node is in. Please check if the domain configuration is correct and if the computer browser service is working.

E-> The retrieval of the domain controllers failed, because the needed service is not started. Please check and retry.

The setup program was not able to retrieve the domain controllers for the domain the node is in. Please check if the domain configuration is correct and if the computer browser service is working.

Chapter 2 255

OpC130-0285

OpC130-0300

OpC130-0301

OpC130-0302

OpC130-0303

OpC130-0304

OpC130-0305

ITO Error Messages

NT installation messages

E-> The retrieval of the domain controllers failed, because the password is invalid. Please check and retry.

The setup program was not able to retrieve the domain controllers for the domain the node is in. Please check if the domain configuration is correct and if the computer browser service is working.

I-> Installation Server: Initiating the startup of the setup program on node <

x1

> (NT name is <

x2

>).

The installation server will start the installation of the new node.

I-> Installation Server: Setup program is scheduled on node <

x1

>.

The setup program will be started on the new node.

E-> Installation Server: Tracing of EventLog for node

<

x1

> aborted.

There was an internal error during the tracing of the installation of the new node. There won't be any more progress messages about the installation of that node.

E-> Installation Server: Timed out while waiting for the end of the installation program on node <

x1

>. Probably aborted. Please look on the node directly.

It took too long to install the new node. The installation program has probably aborted without informing the installation server. Check in the installation tracefile on the new node for errors.

<

x1

>

This is a progress message of the installation.

I-> Installation Server: The local reinstallation of new

ITO Agent Software will be started. There won't be any progress messages during the installation because the old agents have to be shut down. One of the next messages of the new node will be '...successfully

distributed...'. After that you can look into the installation log for the status of the setup.

See message text.

256 Chapter 2

OpC130-0306

OpC130-0310

OpC130-0311

OpC130-0312

OpC130-0313

OpC130-0314

OpC130-0320

ITO Error Messages

NT installation messages

E-> Installation Server: The local reinstallation failed, because the installation program could not be found under <

x1

> or <

x2

>. Please shutdown the agent on your managed node and call the installation program opc_inst.bat from your local FTP directory on your managed node.

See message text.

E-> Installation Server: Access denied from node <

x1

>.

Verify the trust relationship between both domains.

Verify the trust relationship between both domains.

E-> Installation Server: The Schedule service is disabled and cannot be started on node <

x1

>.

The Schedule service may not be disabled because it is used to execute programs on other nodes.

E-> Installation Server: Could not find out remote time of node <

x1

>.

The management server could not get the remote time of the node. Check to make sure that <node name> is really a Windows NT system.

E-> The Schedule service was not started correctly on node <

x1

>.

The Schedule service must be running on the new node because it is used to execute programs. Check locally on the node if there are problems.

W-> Installation Server: Increasing the delay counter for node <

x1

>. It seems to be a slow connection. Not really a problem.

The connection between the installation server and the new node is slower than expected. This is not an error, but a notification of a problematic connection.

E-> Installation Server: The Installation Server service is not configured on this node. Therefore it cannot initiate the installation to node <

x1

>.

This machine cannot be used as an installation server because it is not a primary domain controller.

Chapter 2 257

OpC130-0321

OpC130-0322

OpC130-0323

OpC130-0324

OpC130-0325

OpC130-0326

OpC130-0327

ITO Error Messages

NT installation messages

E-> Installation Server: Startup of the Installation

Server service failed. Therefore it cannot initiate the installation to node <

x1

>.

Is the password in the service startup screen the same as the one given for the account?

Make sure that in the User Properties neither the 'User

Must Change Password at Next Logon' nor the 'Account

Disabled' fields are marked.

Make sure that in the User Properties neither the 'User Must Change

Password at Next Logon' nor the 'Account Disabled' fields are marked.

E-> Installation Server: The configuration files for the installation of node <

x1

> could not be created.

There was an internal error during the creation of the configuration files of the new node. Check for additional tracing of the program.

E-> Installation Server: The agent package for the installation of node <

x1

> could not be copied to this node.

There was an internal error during the transfer of the software package of the new node. Check for additional tracing of the program.

E-> Installation Server: Don't know the remote node <

x1

>.

The installation server does not know the new node. Verify that your

Windows NT environment is set up correctly.

E-> Installation Server: The administrative share <

x1

> does not exist on remote node <

x2

>.

The installation server uses the administrative share to access the remote disk. If this does not exist in your environment (in violation of the

Microsoft standard), report to the HP Response Center.

E-> Installation Server: Path <

x1

> does not exist on remote node <

x2

> on network name <

x3

>.

Check for the existence of the path on the new node. Create it manually if it does not exist.

W-> Installation Server: The configuration files for the installation of node <

x1

> could not be deleted.

258 Chapter 2

OpC130-0328

OpC130-0329

OpC130-0330

OpC130-0331

OpC130-0400

OpC130-0401

OpC130-0500

ITO Error Messages

NT installation messages

There was an internal error deleting the configuration files for the new node. Check for additional tracing of the program.

E-> Installation Server: Cannot match the HostName <

x1

> to an NT name and therefore cannot access the remote NT node.

The IP hostname and the NETBIOS name cannot be matched. Please check the network settings for this node.

E-> Installation Server: Local Path <

x1

> does not exist.

The given path could not be found.

E-> Installation Server: Unable to copy file to <

x1

> on remote node <

x2

> on network name <

x3

>: Unknown network error occurred.

The installation server was not able to copy the given file, because an network error occurred.

E-> Installation Server: Transfer of default configuration files to new node failed. See previous error messages for details.

The transfer of the configuration files failed. Please see previous error message for details.

I-> Deinstall: Deinstalling node <

x1

>. In case of success there won't be any more messages from this node.

This message is provided for your information, and does not denote an error.

E-> Deinstall: The Schedule service is disabled and cannot be started on node <

x1

>.

The Schedule service may not be disabled because it is used to execute programs on other nodes.

The Host Name that is configured in the TCP/IP Protocol settings is <

x1

>. This name does not match the name <

x2

> returned from the DNS.

Chapter 2 259

OpC130-0501

OpC130-0502

OpC130-0510

ITO Error Messages

NT installation messages

For the moment we will try to continue with this setting but you should make sure that this is correctly configured.

For the moment we will try to continue with this setting but you should make sure that this is correctly configured.

The Computer Name that is configured in the Network settings is <

x1

>. This name does not match the name <

x2

> returned from the DNS.

For the moment we will try to continue with this setting but you should make sure that this is correctly configured.

This error may occur if you have changed the name of a Windows NT system. If you have changed the name of the computer you must reinstall the ITO agent.

The Host Name that was returned from the DNS during the installation is <

x1

>. This name does not match the name

<

x2

> that is now returned from the DNS.

If you have changed the name of the computer you have to reinstall the ITO agent.

This error may occur if you have changed the name of a Windows NT system. If you have changed the name of the computer you must reinstall the ITO agent.

Not all agents terminated in time.

One or more of the agent processes didn't terminate. Kill them manually or reboot the system.

260 Chapter 2

ITO Error Messages

Security related messages (commands and modules)

Security related messages (commands and modules)

OpC140-0100

OpC140-0101

OpC140-0102

OpC140-0103

OpC140-0104

OpC140-0105

OpC140-0106

Can't init Security API.

This error could indicate out of memory, a corrupted skey.sdb file or a database problem (check qualifying error message).

Can't get the security session.

This error could indicate out of memory, that a secret key was not found although configured, or the public key session negotiation returned a communication error.

Can't set the security session.

This error could indicate out of memory, that a secret key was not found although configured, or the public key session negotiation returned a communication error.

Error during message encryption/compression.

A message could not compressed and/or encrypted. This could indicate out of memory.

Error during message decryption/decompression.

A message could not decrypted and/or uncompressed. This could indicate out of memory, or data corruption (check more qualifying error message).

Error during action request encryption/compression.

An action request could not compressed and/or encrypted. This could indicate out of memory.

Error during action request decryption/decompression.

An action request could not decrypted and/or uncompressed. This could indicate out of memory, or data corruption (check more qualifying error message).

Chapter 2 261

OpC140-0107

OpC140-0108

OpC140-0109

OpC140-0110

OpC140-0111

OpC140-0113

OpC140-0114

OpC140-0115

OpC140-0116

ITO Error Messages

Security related messages (commands and modules)

Error during action response encryption/compression.

An action response could not compressed and/or encrypted. This could indicate out of memory.

Error during action response decryption/decompression.

An action response could not decrypted and/or uncompressed. This could indicate out of memory, or data corruption (check more qualifying error message).

Error during message operation encryption/compression.

A message operation could not compressed and/or encrypted. This could indicate out of memory.

Error during message operation decryption/decompression.

A message operation could not decrypted and/or uncompressed. This could indicate out of memory, or data corruption (check more qualifying error message).

Can't read nodeinfo parameters for security type and version.

Error reading network security protocol parameter OPC_NSP_TYPE and OPC_NSP_VERSION from nodeinfo file.

The generation of the hash value failed.

Internal Error. A hash value could not generated.

Invalid cookie after uncompression of data!

The data could not successfully uncompressed. Data seems to be corrupted.

The received MAC differs from the calculated. Data was modified!

A generated hash value over the data differs from the received one. The data seems to be corrupted.

Secret key info for '<

x1

>' not found!

The secret key for the specified host was not found in the secret key store

'skey.sdb'.

262 Chapter 2

OpC140-0117

OpC140-0118

OpC140-0119

OpC140-0120

OpC140-0121

OpC140-0131

OpC140-0132

OpC140-0133

OpC140-0134

OpC140-0135

OpC140-0136

ITO Error Messages

Security related messages (commands and modules)

Can't connect to session process '<

x1

>'

Communications error occurred during public key session establishment.

Check more qualifying error message.

Remote procedure call for setting a session failed!

Communications error occurred during public key session establishment.

Check more qualifying error message.

Remote procedure call for getting a session failed!

Communications error occurred during public key session establishment.

Check more qualifying error message.

Error during encryption of a data block.

Could indicate out of memory.

Error during decryption of a data block.

The received data block could not decrypted. This indicates out of memory, or corruption (check more qualifying error message).

Can't create the pre master secret

Internal error.

Can't load public keys for client and server from certificate store

Could indicate a corrupted certificate store (certs.sdb).

Can't create the Client Hello

Internal protocol error.

Can't create hash for Server Hello and Server

Certificate message

Internal protocol error.

Can't create hash for Client Verify message

Internal protocol error.

Can't create hash for Finished message

Chapter 2 263

OpC140-0137

OpC140-0138

OpC140-0139

OpC140-0140

OpC140-0141

OpC140-0142

OpC140-0143

OpC140-0144

OpC140-0145

OpC140-0146

ITO Error Messages

Security related messages (commands and modules)

Internal protocol error.

Received an invalid server id in Server Hello

(Got:'<

x1

>', Have:'<

x2

>')

Could indicate a corrupted reply packet of a Client Hello. The expected value was not part of the received data.

Can't find certificate for '<

x1

>' in certificate store

This error could indicate a corrupted certificate store. Check 'certs.sdb' on both, the Management Server and Managed Node.

Certificate mismatch! The received certificate is different from the one stored in the certificate store

This error could indicate a corrupted certificate store. Check 'certs.sdb' on both, the Management Server and Managed Node.

Server Certificate hash mismtch! The received Server

Certificate hash differs from the locally generated one

Could indicate corrupted data. Re-start the agent.

Can't parse Server Hello and Server Certificate message

Internal protocol error.

Can't create Client Key Exchange message

Internal protocol error.

Can't create Client Verify message

Internal protocol error.

Can't connect to session process '<

x1

>'

Communications error occurred during public key session establishment.

Check more qualifying error message.

Remote procedure call for phase 1 failed!

Communications error occurred during public key session establishment.

Check more qualifying error message.

Phase 1 of the session establishment failed!

264 Chapter 2

OpC140-0147

OpC140-0148

OpC140-0149

OpC140-0150

OpC140-0151

OpC140-0152

OpC140-0153

OpC140-0154

OpC140-0155

OpC140-0156

ITO Error Messages

Security related messages (commands and modules)

Communications error occurred during public key session establishment.

Check more qualifying error message.

Can't read my private key!

Check public key store 'pkey.sdb' for corruption.

Can't create reply messsage of phase 1 to client

Internal protocol error.

Invalid protocol received: <

x1

>

Internal protocol error.

Can't parse Client Hello

Internal protocol error.

Remote procedure call for phase 2 failed!

Communications error occurred during public key session establishment.

Check more qualifying error message.

Client rejected! No handshake info found for '<

x1

>' in phase 2

Internal protocol error.

Client Verify hash mismtch! The received Client Verify hash differs from the locally generated one

Internal protocol error.

Finished message mismatch! The received Finish message is different from the locally generated

Internal protocol error.

Can't parse Phase 2 from client

Internal protocol error.

Can't create Finish message

Internal protocol error.

Chapter 2 265

OpC140-0171

OpC140-0172

OpC140-0173

OpC140-0174

OpC140-0181

OpC140-0182

OpC140-0183

OpC140-0184

OpC140-0185

OpC140-0186

OpC140-0187

OpC140-0188

ITO Error Messages

Security related messages (commands and modules)

Error during phase 1 handshaking from '<

x1

>'

Internal protocol error.

Error during phase 2 handshaking from '<

x1

>'

Internal protocol error.

Can't set the session to '<

x1

>'

Internal protocol error.

Can't get the session to '<

x1

>'

Internal protocol error.

Can't create RSA signature

Internal error.

Signature verification failed

Internal error.

Can't create RSA public and private key

Internal error.

Public key encryption failed

Internal error.

Public key decryption failed

Internal error.

Private key encryption failed

Internal error.

Private key decryption failed

Internal error.

DES encryption failed

Internal error.

266 Chapter 2

OpC140-0189

OpC140-0201

OpC140-0202

ITO Error Messages

Security related messages (commands and modules)

DES decryption failed

Internal error.

Can't set the session context

Internal error.

Can't get the session context

Internal error.

Chapter 2 267

Was this manual useful for you? yes no
Thank you for your participation!

* Your assessment is very important for improving the work of artificial intelligence, which forms the content of this project