openview operations error messages

HP OpenView IT/OperationsError Message Reference

Edition 2

B6941-90005

HP OpenView IT/Operations

Version A.05.00

February 1999

Legal NoticesHewlett-Packard makes no warranty of any kind with regard to thismanual, including, but not limited to, the implied warranties ofmerchantability and fitness for a particular purpose. Hewlett-Packardshall not be held liable for errors contained herein or direct, indirect,special, incidental or consequential damages in connection with thefurnishing, performance, or use of this material.

Warranty. A copy of the specific warranty terms applicable to yourHewlett-Packard product and replacement parts can be obtained fromyour local Sales and Service Office.

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

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

The information provided here constitutes a Year 2000 ReadinessDisclosure for purposes of the Year 2000 Information and ReadinessDisclosure Act.

Restricted Rights Legend. All rights are reserved. No part of thisdocument may be photocopied, reproduced, or translated to anotherlanguage without the prior written consent of Hewlett-PackardCompany. The information contained in this document is subject tochange without notice.

Use, duplication or disclosure by the U.S. Government is subject torestrictions as set forth in subparagraph (c) (1) (ii) of the Rights inTechnical Data and Computer Software clause at DFARS 252.227-7013

2

for DOD agencies, and subparagraphs (c) (1) and (c) (2) of theCommercial Computer Software Restricted Rights clause at FAR 52.227-19 for other agencies.

HEWLETT-PACKARD COMPANY3404 E. Harmony RoadFort 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 copiesof the programs may be made for security and back-up purposes only.Resale of the programs in their present form or with alterations, isexpressly prohibited.

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

Reproduction, adaptation, or translation of this document without priorwritten permission is prohibited, except as allowed under the copyrightlaws.

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

This software is based in part on the Fourth Berkeley SoftwareDistribution under license from the Regents of the University ofCalifornia.

©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 UnitedStates and other countries, licensed exclusively through X/OpenCompany Limited.

3

X Window System is a trademark of the Massachusetts Institute ofTechnology.

OSF/Motif is a trademark of the Open Software Foundation, Inc. in theU.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 ofOracle 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 areU.S. trademarks of Netscape Communications Corporation.

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

4

Printing HistoryThe manual printing date and part number indicate its current edition.The printing date will change when a new edition is printed. Minorchanges may be made at reprint without changing the printing date. Themanual part number will change when extensive changes are made.

Manual updates may be issued between editions to correct errors ordocument product changes. To ensure that you receive the updated ornew editions, you should subscribe to the appropriate product supportservice. See your HP sales representative for details.

First Edition: August 1997

Second Edition: February 1999

5

In This BookThis book provides a copy of all ITO error messages that have additionalinstructional text available. This book contains no information that isnot also available from the user interface.

For information on how to install ITO on the management server, see theHP OpenView IT/Operations Installation Guide for the ManagementServer.

For a description of the ITO administrator’s daily setup andconfiguration tasks, see the HP ITO Administrator’s Guide to OnlineInformation.

For information about upgrading an earlier version of ITO , see the HPOpenView IT/Operations Software Release Notes.

For information about ITO concepts, see the HP OpenView IT/Operations Concepts Guide.

7

ConventionsThe following typographical conventions are used in this manual.

Font Type What the Font Type Represents Example

Italic Book or manual titles, and man pagenames

Refer to the HP OpenView IT/Operations Administrator’sReference and the opc(1M) manpagefor more information.

Provides emphasis You must follow these steps.

Specifies a variable that you mustsupply when entering a command

At the prompt type:rlogin your_name where yousupply your login name.

Parameters to a function The oper_name parameter returnsan integer response.

Bold New terms The monitor agent observes...

Computer Text and items on the computerscreen

The system replies: Press Enter

Command names Use the grep command ...

Function names Use the opc_connect() function toconnect ...

File and directory names /opt/OV/bin/OpC /

Process names Check to see if opcmona is running.

Window/dialog box names In the Add Logfile window...

Computer Bold

Text that you must enter At the prompt, type: ls -l

9

Keycap Keyboard keys Press Return .

[Button] Buttons on the user interface. Click [Operator] .Click on the [Apply] button.

MenuItems

A menu name followed by a colon (:)means that you select the menu,then the item. When the item isfollowed by an arrow (-> ), acascading menu follows.

Select Actions:Utilities->Reports …

Font Type What the Font Type Represents Example

10

The IT/Operations Documentation MapITO provides a set of manuals and online help which aim to assist you inusing ITO and improve your understanding of the underlying concepts.This section illustrates what information is available and where you canfind it.

HP OpenView IT/Operations Printed Manuals

This section provides an overview of the printed manuals and theircontents.

The HP OpenView IT/Operations Concepts Guideprovides you with an understanding of ITO on twolevels. As an operator, you can learn about ITO's basicstructure; as an administrator, you can use this book togain an insight into the setup and configuration of ITOin your own environment.

The HP OpenView IT/Operations Installation Guide for the ManagementServer

is for administrators who install ITO software on themanagement 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 Referenceis for people who install ITO on the managed nodes andare responsible for the administration andtroubleshooting of ITO in general.

The HP OpenView IT/Operations Error Message Referenceis for administrators involved in ITO problem solving.It provides a copy of all ITO error messages that haveadditional instructional text available. This bookcontains no information that is not also available fromthe user interface.

11

Managing Your Networks with HP OpenView Network Node Manageris for administrators and operators. It describes thebasic functionality of HP OpenView Network NodeManager which is an embedded part of ITO.

The HP OpenView ServiceNavigator Concepts and Configuration Guideprovides information for administrators who areresponsible for installing, configuring, maintaining,and troubleshooting the HP OpenViewServiceNavigator. It also contains a high-leveloverview of the concepts behind service management.

The HP OpenView IT/Operations Reporting and Database Schemacontains a detailed description of the ITO databasetables and provides examples for generating reportsfrom the ITO database.

The HP OpenView IT/Operations Software Release Notesgive a description of new features. In addition, theyprovide information to help you:

• compare the current software’s features with thoseavailable 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 Informationis a context-sensistive help system and containsdetailed help for each window of the ITO administratorGUI as well as step-by-step instructions for performingadministrative tasks.

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

The HP ITO Java-based GUI Online Documentationis available in HTML-format for the ITO Java-basedoperator GUI and the ServiceNavigator, and containsdetailed information about general ITO and

12

ServiceNavigator concepts and tasks for the ITOoperator, as well as reference and troubleshootinginformation.

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

HP OpenView IT/Operations Developer’s Toolkit

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

The HP OpenView IT/Operations Application Integration Guidesuggests several ways in which external applicationscan be integrated into ITO.

The HP OpenView IT/Operations Developer’s Referenceprovides an overview of all available applicationprogramming 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 Designerdocumentation set including the title:

HP OpenView ECS Configuring Circuits for NNM and ITOwhich contains information you need to use the ECSDesigner 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 HPOpenView IT/Operations , you receive the following additionaldocumentation:

Advanced Network Security for HP OpenView IT/Operationsprovides information for administrators who areresponsible for installing, configuring, maintaining,and troubleshooting ANS.

Electronic Version of the Manuals

All manuals except the HP OpenView IT/Operations Software ReleaseNotes are also included as Portable Document Format (PDF) files in theappropriate documentation software bundle. See the HP OpenView

13

IT/Operations Installation Guide for the Management Server for generalinstallation instructions using swinstall . The manuals are installedinto the following directory on the management server:

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

Alternatively, you can download the manuals from the following website:

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 onlineformat based on DynaText. DynaText is an application for viewing,searching, printing, and annotating your online library. The browser andthe manuals are available in the appropriate ITO documentationsoftware bundle. See the HP OpenView IT/Operations Installation Guidefor the Management Server for general installation instructions usingswinstall . Once the bundle is installed, you can open the library byselecting Online Manuals from the Help menu of any primary ITOwindow.

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 themain operator windows. Both volumes include:

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

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

❏ information about errors displayed in the ITO-Error Informationwindow. You can get help either when the error occurs or by using themessage number provided to perform a keyword search within thehelp 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 informationsystems

❏ a printing facility, which allows you to print any or all topics in thehelp 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 theHelp menu

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

15

You can also get context sensitive help in the Message Browser andMessage Source Templates window. After selecting Help: OnContext from the menu, the cursor changes into a question mark whichyou can then position over the area on which you want help. When youclick the mouse button, the required help page is displayed in its helpwindow.

The ITO Java-based GUI and OV ServiceNavigator Online Documentation

The ITO Java-based GUI online documentation helps operators tobecome familiar with and use the ITO product. The followinginformation is included:

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

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

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

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

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

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

Access the help system by selecting Help: Contents from the mainmenu of the Java GUI. A web browser opens and displays the helpcontents. Note that you must first configure ITO to use your preferredbrowser, see the HP OpenView IT/Operations Installation Guide for theManagement 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

IntroductionAbout this Book

About this BookThis book provides a copy of all ITO error messages for which additionalinstructional text is available. The content of this book is identical to theerror message help text available from the user interface.

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

You can also use the command line tool opcerrget to get theinstructional 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 arepresented in the following format:

OpC10-0001 The text of the error message.

The explanatory help text for the error.

Chapter 1 21

IntroductionFiltering ITO Internal Error Messages

Filtering ITO Internal Error MessagesITO internal error messages can be extracted from or filtered out of theinternal MSI so that automatic and operator-initiated actions may beattached and the message treated as if it were a normal, visible ITOmessages. This functionality may be enabled both on the managed nodeand on the ITO management server. Depending on where thefunctionality is enabled, all ITO internal messages will be sent back tothe local message interceptor either on the ITO management server oron the managed node, where they will be seen and treated in the sameway as any other ITO message. The user enables this feature by addingthe string OPC_INT_MSG_FLT TRUE to either the opcsvinfo file on themanagement server or the opcinfo file on the managed node.

NOTE You should set up at least one condition for the ITO internal errormessages in the opcmsg (1/3) template (using message group OpC) andset 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 MessagesInternal error messages

Internal error messages

OpC10-0001 Insufficient memory

The process cannot allocate enough memory. This could be an internalerror, 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.

OpC10-0002 Unexpected function return value < x1> of function < x2>.

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

OpC10-0011 Illegal NULL parameter (function < x1>)


OpC10-0012 Illegal index < x1> (function < x2>)


OpC10-0013 Illegal value < x1> (function < x2>)


OpC10-0014 Illegal case mark (function < x1>)


OpC10-0018 Critical return code < x1> (function < x2>)


OpC10-0020 Invalid list.


OpC10-0030 Internal RLS cleanup.


Chapter 2 25


OpC10-0031 Internal num srv.


OpC10-0032 Cannot uname(2).

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

OpC10-0033 Cannot gethostname(2).

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

OpC10-0034 File < x1> not found.

The required file <filename> could not be found.

OpC10-0036 Cannot compress file < x1>.

The file is not compressible or another compressing error has beendetected. Solution: Compress the file manually, if possible. MPE/iXspecial: use the file /usr/OV/bin/OpC/install/mpecmpr on themanagement server.

OpC10-0037 Cannot uncompress file < x1>.

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

OpC10-0040 Unexpected value < x1> in switch statement of function<x2>.


OpC10-0050 Size of array < x1> too small.

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

OpC10-0052 Problems using strftime(3).

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

26 Chapter 2


OpC10-0053 Problems using localtime(3).

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

OpC10-0055 Invalid date format < x1>.

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

OpC10-0056 Invalid time format < x1>.


Chapter 2 27

ITO Error MessagesError messages of public routines

Error messages of public routines

OpC20-0001 Invalid queue descriptor '< x1>'.


OpC20-0002 Invalid queue file '< x1>' (qd = < x2>, fd = < x3>).

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

OpC20-0003 Can't open queue file '< x1>'.

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

OpC20-0004 Can't close queue file '< x1>' (qd = < x2>, fd = < x3>).


OpC20-0005 Can't seek queue file '< x1>' (qd = < x2>, fd = < x3>).


OpC20-0006 Can't read queue file '< x1>' (qd = < x2>, fd = < x3>).


OpC20-0007 Can't write queue file '< x1>' (qd = < x2>, fd = < x3>).


OpC20-0008 Can't truncate queue file '< x1>' (qd = < x2>, fd = < x3>).


OpC20-0009 Can't lock queue file '< x1>' (qd = < x2>, fd = < x3>).


28 Chapter 2


OpC20-0010 Can't unlock queue file '< x1>' (qd = < x2>, fd = < x3>).


OpC20-0011 Can't open queue file '< x1>' due to full system table.

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

OpC20-0012 Can't lock queue file '< x1>' (qd = < x2>, fd = < x3>) dueto full system table.

There are two possibilities:

a. The ITO queue file can't be locked by the reporting process becausethe system lock table is full.

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

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

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

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

OpC20-0013 Can't write queue file '< x1>' (qd = < x2>, fd = < x3>). Nofile space.

The reporting process can't append an element to the ITO queue filebecause 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 thefile'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 mightbe an internal error, in which case it should be reported to your HPResponse Center.

OpC20-0014 Queue '< x1>' is empty (qd = < x2>).


OpC20-0015 Read buffer is too small.


Chapter 2 29


OpC20-0016 Unread operation on queue file '< x1>' already done (qd =<x2>).


OpC20-0020 You must be superuser < x1> to run this service.

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

OpC20-0021 Cannot read password file entry.

The password file /etc/passwd does not exist, or there is no entry for theeffective user-ID of the execution user. Solution: Check the existence of/etc/passwd and verify that an appropriate entry for the calling user isavailable.

OpC20-0025 Cannot open directory < x1>.

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

OpC20-0026 Cannot read entry of directory < x1>.

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

OpC20-0027 Cannot close directory < x1>.

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


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


30 Chapter 2


The reporting process was not able to compress the file <file>. On UNIXsystems this happens usually using the program compress(1). Checkwhether this program is present, executable and contained in the PATHvariable of the execution environment of the reporting process.

OpC20-0030 No configuration installed.


OpC20-0031 Invalid object definition for object < x1>.


OpC20-0032 Invalid object list.


OpC20-0033 Multiple objects with name '< x1>' defined.

This can happen you you assigned a monitor and a scheduled action withthe same name to a agent. Please use unique names for monitors and ascheduled actions. If this error has an other reason it is in internal error.Please report it then to your HP Response Center.

OpC20-0034 Select call failed.

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

OpC20-0035 Check callback of object < x1> returns invalid value.


OpC20-0036 Processing callback of object < x1> returns not OK forevent < x2>.

Qualifying error message. More information is contained in another partof the message.

OpC20-0037 Can't find object '< x1>' to set async. flag.

Qualifying error message. More information is contained in another partof the message.

OpC20-0038 Statistics option not compiled into module.


Chapter 2 31


OpC20-0039 Can't open trace file < x1>.


OpC20-0040 Can't write trace file < x1>.


OpC20-0054 Could not find entry for 'opcgrp' in the systemgroup file. You must be a member of this groupto start a Motif GUI or run a database report.

The Unix Group 'opcgrp' is vital for the operation of ITO Motif GUIs anddatabase reports. Please check why this group is no longer configured in'/etc/group' and/or '/etc/logingroup'! After adding the group you must alsoensure that /opt/OV/bin/OpC/opc is owned by this group and has the setgroup ID bit set (if at all possible, use the group ID of this file as alreadyset).

OpC20-0056 You currently have no 'opcgrp' rights. Pleasecheck with your ITO administrator why you do nothave these rights. You may also check '/etc/group'and '/etc/logingroup' to see if you are listed asa member of 'opcgrp'.Without 'opcgrp' rights you will not be able to starta Motif GUI or run a database report unless you are aroot user.

For normal operation of ITO Motif GUIs, the set group ID bit must be setfor file /opt/OV/bin/OpC/opc, for group opcgrp. If you do not want this, theITO Administrator must ensure that ALL operators have rights foropcgrp. Users using CDE on the management server (directly orremotely) can do an 'su - <user_name>' in a shell before starting ITO orhave the system administrator install an appropriate CDE patch fixingthe logingroups() problem. To have rights for opcgrp, '/etc/group' and'/etc/logingroup' MUST have the users listed as members of opcgrp. Afteradding a login name into '/etc/group' the user needs to log out of VUE orCDE and login again to get the group rights.

OpC20-0060 Cannot get temporary file name.

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

32 Chapter 2


OpC20-0061 Unable to get status of file < x1>.

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

OpC20-0062 Unable to unlink/erase file < x1>.

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

OpC20-0063 Cannot open file < x1>.

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

OpC20-0064 Cannot read contents of file < x1>.

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

OpC20-0065 Cannot write to file < x1>.

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

OpC20-0066 Cannot close file < x1>.

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

OpC20-0067 Cannot create directory < x1>.

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

OpC20-0068 Cannot change permission of < x1>.

Chapter 2 33


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

OpC20-0069 Cannot change ownership of < x1>.

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

OpC20-0070 Cannot seek file < x1>.

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

OpC20-0071 File < x1> is empty.

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

OpC20-0073 Cannot lock file < x1>.

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

OpC20-0074 Cannot unlock file < x1>.

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

OpC20-0075 Cannot truncate file < x1>.

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

OpC20-0076 Cannot access file < x1>.

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

OpC20-0080 Environment variable < x1> not set.

34 Chapter 2


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

OpC20-0083 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.

OpC20-0084 Can't create named pipe < x1>.

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

OpC20-0085 Select failed.

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

OpC20-0086 Can't create anonymous pipe.

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

OpC20-0090 Can't initialize mutex.

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

OpC20-0091 Can't lock mutex.

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

OpC20-0092 Can't unlock mutex.

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

OpC20-0093 No pipe reader.

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

Chapter 2 35


OpC20-0094 No pipe writer.

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

OpC20-0095 Can't write into pipe.

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

OpC20-0096 Can't read from pipe.

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

OpC20-0097 Can't open pipe.

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

OpC20-0098 Read operation on pipe timed out.

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

OpC20-0099 Can't copy binding: < x1>.

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

OpC20-0100 Server is already initialized.


OpC20-0101 Can't get protocol family: < x1>.


OpC20-0102 Can't check protocol family: < x1>.


36 Chapter 2


OpC20-0103 Can't inquire binding: < x1>.


OpC20-0104 Can't bind to server: < x1>.


OpC20-0105 Can't set short timeout: < x1>.


OpC20-0106 Checking server failed: < x1>.


OpC20-0107 Can't shutdown server: < x1>.


OpC20-0108 Can't lookup servers: < x1>.

The reporting process could not lookup a desired server process becausethe 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 ofserver and the node are contained in another part of the error message.

OpC20-0109 Can't use protocol family: < x1>.


OpC20-0110 Setting shutdown check routine failed: < x1>.

Chapter 2 37



OpC20-0111 Server not initialized.


OpC20-0112 Server already registered.


OpC20-0113 Server already running.

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

OpC20-0114 Can't register manager: < x1>.

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

OpC20-0115 Can't register object ID: < x1>.

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

OpC20-0116 Can't register manager at location broker: < x1>.

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

OpC20-0117 Can't unregister manager: < x1>.


OpC20-0118 Can't unregister manager at location broker: < x1>.

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

OpC20-0119 Exception caught: < x1>.

38 Chapter 2


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

OpC20-0120 Server listening failed: < x1>.


OpC20-0121 Can't convert location to numeric name: < x1>.


OpC20-0122 Can't convert location: < x1>.

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

OpC20-0123 Invalid server type.


OpC20-0124 No such server registered.

This is a qualifying message generated when an ITO process could notconnect another ITO server process because the server is not running.More information is contained in another part of the error message.

OpC20-0125 No such server running.

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

OpC20-0126 Last request.


OpC20-0127 Duplicated request.


Chapter 2 39


OpC20-0128 Unexpected request.


OpC20-0129 Invalid client ID.


OpC20-0130 Can't convert IP address.


OpC20-0131 Communication failure.


OpC20-0132 Invalid limit for RPC open arrays specified: < x1> Validis < x2> - < x3>. Using < x4> bytes.

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

OpC20-0133 Invalid inter RPC delay specified: < x1>. Valid is < x2> -<x3>. Using < x4> seconds.

The delay between two RPCs specified in the managed node's nodeinfofile is out of the valid range. The process continues with the reporteddefault value.

OpC20-0134 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 outof the valid range. The process continues with the reported default value.

OpC20-0135 Can't get value from pbconf module.


OpC20-0136 Invalid alternate IP address specified: < x1>.

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

OpC20-0137 Can't extract port number from location: < x1>.

40 Chapter 2



OpC20-0138 Can't set port number in location: < x1>.


OpC20-0142 Can't free string: < x1>.


OpC20-0143 Can't initialize server lookup operation at rpcd: < x1>.

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

OpC20-0144 Can't terminate server lookup operation at rpcd: < x1>.


OpC20-0145 Can't free RPC binding: < x1>.


OpC20-0146 Can't generate UUID: < x1>.


OpC20-0147 Can't generate NIL UUID: < x1>.


OpC20-0148 Can't convert UUID to string representation: < x1>.


OpC20-0149 Can't set object ID in RPC binding: < x1>.


Chapter 2 41


OpC20-0150 Communication failure to message agent.

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

OpC20-0151 Can't open message logfile < x1>.

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

OpC20-0152 Can't write message logfile < x1>.

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

OpC20-0155 Can't get message keyword from message catalog. Usingdefault values.

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

OpC20-0156 Execution of request failed due to server failure.


OpC20-0157 Invalid logging reason specified.


OpC20-0158 Can't get keyword from message catalog for key < x1>.


OpC20-0160 <x2> service not registered at Local Location Broker orDCE 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 theinstalled agent software. Especially this is important when adding nodesinstalled by another Management Server.

42 Chapter 2


OpC20-0161 <x2> service registered at Local Location Broker or DCERPC Daemon on system < x1>,but is not responding.

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

OpC20-0162 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 processterminated or it is not reachable due to network communication failures.This message will be qualified by another message giving moreinformation.

OpC20-0163 RPC service '< x2>' on system '< x1>' not reachable due toa failed lookup operation.

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

OpC20-0164 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 orfailed to execute it. See the local error log file on the server system<node>.

OpC20-0165 The UDP/IP protocol sequence is not supported onthe local host. RPC server can't register at llbd/rpcd.

The system where the reporting process is running on doesn't supportUDP as networking protocol. This will prevent the ITO processes fromusing DCE/UDP as communication type and also from communicatingwith NCS processes.

OpC20-0166 The communication type < x1> is currently not supported tosend control agent requests.

Chapter 2 43


The reporting process was requested to send a request to a control agentrunning on a managed node but the configured communication of thisnode cannot be used to inform the control agent. Currently only NCS orDCE communication types are supported.

OpC20-0167 All ports in range '< x1>' are in use. Performing dynamicallocation 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, orthe range is too small for all ITO processes. The RPC server is nowstarted with a port outside the specified range. Communication errorscould occur if this port is blocked by a firewall.

OpC20-0168 RPC service '< x2>' on system '< x1>' returns anauthentication 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 theclient requests authentication. See the local error log file on the serversystem <node>.

OpC20-0172 The file < x2>/< x3> targeted for platform < x1> has invalidfile 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 areais ".Z".

OpC20-0201 Can't open configuration file '< x1>' for writing.

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

OpC20-0202 Can't open configuration file '< x1>' for reading.

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

OpC20-0203 Write error writing msg source '< x1>'.

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

44 Chapter 2


OpC20-0204 Syntax error in dot string '< x1>'.

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

OpC20-0205 Syntax error in interval string '< x1>'.

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

OpC20-0206 Configuration file '< x1>' contains syntax errors.

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

OpC20-0209 Template < x1> mixes old and new monitor template syntax.

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

OpC20-0210 line < x1> "< x2>": message source or 'DESCRIPTION'expected.

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

OpC20-0211 line < x1> "< x2>": Logfile default / option or'MSGCONDITION' expected.


OpC20-0212 line < x1> "< x2>": unknown character set or chsetconflicts with the internal node chset.


OpC20-0213 line < x1> "< x2>": SNMP default / option or'MSGCONDITIONS' expected.

Chapter 2 45



OpC20-0214 line < x1> "< x2>": Console default / option or'MSGCONDITIONS' expected.


OpC20-0215 line < x1> "< x2>": opcmsg default / option or'MSGCONDITIONS' expected.


OpC20-0216 line < x1> "< x2>": Monitor option expected.


OpC20-0217 line < x1> "< x2>": MsgCondition or 'SUPPRESSCONDITIONS'expected.


OpC20-0218 line < x1> "< x2>": SuppressCondition expected.


OpC20-0219 line < x1> "< x2>": Condition expected.


OpC20-0220 line < x1> "< x2>": SNMP MsgCondition or'SUPPRESSCONDITIONS' expected.

46 Chapter 2



OpC20-0221 line < x1> "< x2>": SNMP SuppressCondition expected


OpC20-0222 line < x1> "< x2>": SNMP Condition expected.


OpC20-0223 line < x1> "< x2>": Set expression or 'SUPPRESSCONDITIONS'expected.


OpC20-0224 line < x1> "< x2>": Severity expected.


OpC20-0225 line < x1> "< x2>": Regroup condition expected.


OpC20-0226 line < x1> "< x2>": MSGGRP "< MsgGroup>" expected.


OpC20-0227 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 Monitor name "< x1>" contains invalid characters

ITO allows only alphanumeric characters, '-' and '_' for monitor names.Remove the invalid characters from the string.

OpC20-0229 Message type "< x1>" contains invalid characters or is toolong

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

OpC20-0230 Can't open rgrp file "< x1>" for reading.

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

OpC20-0231 Rgrp file "< x1>" contains syntax errors.

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

OpC20-0234 Template contains obsolete / invalid syntax version

The syntax of the template (specified with SYNTAX_VERSION<number>) is either incompatible with the currently required ITOsyntax or invalid.

OpC20-0235 Syntax error in pattern definition "< x1>".

The pattern contains syntax errors. See the "Administrator's OnlineHelp" or "Concepts Guide" for a description of the ITO pattern matchingsyntax.

OpC20-0236 Too many separators "< x1>"; using default separatorsinstead.

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

OpC20-0240 Dot string too long "< x1>".


OpC20-0241 Unknown trap variable type: < x1>.


48 Chapter 2


OpC20-0243 Replaced string too long: "< x1>".


OpC20-0260 String < x1> contains invalid multibyte characters.

The string contains invalid multibyte characters; check the string andremove the invalid characters.

OpC20-0270 Can't convert string from "< x1>" to "< x2>".

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

OpC20-0271 Can't get iconv table size to convert string from "< x1>"to "< x2>".

You may not have enough system resources, for example, too many filesmay be open, or the requested character conversion may not besupported on your system. Check your system parameters for themaximum number of open files. Check the character set defined for themanaged node, and the character set defined for the logfile. Checkwhether your operating system supports both character sets, by usingthe iconv command.

OpC20-0272 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 characterset defined for the logfile. Check that your operating system supportsboth character sets, by using the iconv command.

OpC20-0273 Output buffer is too small for iconv conversion.

Internal ITO error.

OpC20-0274 Bad input character converting string from "< x1>" to"< x2>".

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

OpC20-0275 Can't close iconv table.

Chapter 2 49


Internal ITO error.

OpC20-0280 Can't set locale to "< x1>".

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

OpC20-0281 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.

OpC20-0282 The language LANG="< x1>" is invalid.

Change your LANG setting. For more information, see the ITOdocumentation.

OpC20-0283 The codeset "< x1>" is invalid.

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

OpC20-0284 The codeset "< x1>" is incompatible to the codeset "< x2>".

The two given codesets are incompatible. This is a generic error whichcan be caused by several conditions. Please report this to your HPResponse Center.

OpC20-0285 Cannot get the database codeset.

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

OpC20-0286 Cannot get codesets from nodeinfo file.

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

OpC20-0411 fork(2) failed; no more memory

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

OpC20-0415 semget(2) failed; cannot create semaphore

50 Chapter 2


This problem is may cause by to small kernel parameters forsemaphores.

OpC20-0431 The process '< x1>' could not be started.

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

OpC20-0432 The process '< x1>' terminated with a non-zero exit code.

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

OpC20-0650 Can't retrieve local IP address.


OpC20-0651 The gethostbyname(3N) call failed.

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

OpC20-0652 Can't open SNMP session: < x1>.

The reporting process failed to open an SNMP session. This message isqualified by an error message originating from the SNMP subsystemcontaining the cause of the error.

OpC20-0653 Can't close SNMP session: < x1>.

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

OpC20-0654 Can't create SNMP pdu: < x1>.

The reporting process failed to create an SNMP PDU. This message isqualified by an error message originating from the SNMP subsystemcontaining the cause of the error.

OpC20-0655 Can't bind SNMP variable to pdu: < x1>.

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

Chapter 2 51


OpC20-0656 Can't send SNMP pdu: < x1>.

The reporting process failed to send an SNMP PDU. This message isqualified by an error message originating from the SNMP subsystemcontaining the cause of the error.

OpC20-0657 Can't get SNMP variable < x1>.

The reporting process failed to extract an SNMP variable from a receivedPDU because the PDU contained fewer variables than the requestednumber.

OpC20-0658 Unsupported request type to be sent via SNMP.


OpC20-0659 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 theSNMP subsystem containing the cause of the error. This is a MPE/iXspecific error.

OpC20-0660 Maximum number of variables reached. Can't bindvariable.


OpC20-0661 Object ID too long.

A specified object ID exceeds the maximum possible length. This is anMPE/iX specific error.

OpC20-0662 Unsupported variable type.


OpC20-0663 Can't get response file descriptor.

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

OpC20-0664 Can't clear SNMP variable list.

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

52 Chapter 2


OpC20-0665 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.

OpC20-0666 Unexpected SNMP response received: id = < x1>.

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

OpC20-0667 Can't get next SNMP variable from response.

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

OpC20-0668 Unsupported MIB variable type.

The reporting process received a SNMP variable of an unsupported type.This is a SNI specific error.

OpC20-0669 Select call to retrieve PDU failed.

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

OpC20-0670 All retries for PDU GET exhausted.

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

OpC20-0671 PDU receive call failed: < x1>

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

OpC20-0672 Error at MIB variable in response PDU: < x1>

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

OpC20-0673 SNMP request timed out.

The ITO Monitor Agent received no reply to an SNMP GET requestwhich was sent because a MIB monitor is configured. Most likely theSNMP agent is down.

OpC20-0674 SNMP request too big.

Chapter 2 53


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

OpC20-0675 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 areloaded or an invalid MIB variable was defined in the ITO monitor.

OpC20-0676 Invalid SNMP Value.

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

OpC20-0677 SNMP Vlaue is defined as READ ONLY.

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

OpC20-0678 General SNMP error.

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

OpC20-0700 Can't get name of trace file.


OpC20-0701 Can't open trace file '< x1>'.

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

OpC20-0702 Can't log trace message. Invalid format or parameternumber.


OpC20-0703 Can't write trace file.

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

54 Chapter 2


OpC20-0704 Initializing tracing failed.


OpC20-0705 Tracing is enabled on the management server.

Set OPC_TRACE FALSE in the opcsvinfo file to disable tracing.

OpC20-0706 Tracing is enabled on the managed node.

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

OpC20-0750 Empty logfile name.


OpC20-0751 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) containingthe cause of the error.

OpC20-0752 Can't check size of logfile '< x1>' using lseek.


OpC20-0800 Internal error: Illegal operation code < x1>.


OpC20-0801 IP address '< x2>' configured for node '< x1>' couldnot be found in the name service database.

The specified nodename - IP address is configured in ITO but could notbe found in this combination in the name service database. The usedname service database is either the /etc/hosts file, or the DNS or NISdatabase, depending on the current system configuration. This may becaused by the modification of the name or the IP address of the reportedhost. Solution: Fix the ITO configuration for this host to match the nameservice representation.

OpC20-0960 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 OV License Manager returnedLS_LICENSE_SYS_NOT_AVAILABLE.

There has been a problem while doing the license check. This might bedue to networking problems or license server problems. Please makesure the license server is running and accessible. Otherwise you may notbe able to use this product. For more information see the ITOInstallation Guide.

OpC20-0962 OV License Manager returned LS_NO_SERVER_CONNECTION.

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

OpC20-0964 OV License Manager returned LS_NO_LICENSES_AVAILABLE.

There are no/not enough ITO licenses available on your license server. Ifyou have installed license passwords on the license server, this may dueto problems accessing the license server.

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

OpC20-0966 OV License Manager returned LS_SOFT_NO_LICENSE.


OpC20-0967 OV License Manager returned LS_HARD_NO_LICENSE.


OpC20-0968 OV License Manager returned LS_UNKNOWN_STATUS.

56 Chapter 2


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

OpC20-0969 OV License Manager returned LS_BAD_PARAMETER.

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

OpC20-0970 There are no licenses available from the licenseserver for this product. If you have installedlicense passwords on the license server, this maybe due to problems accessing the license server.

This is the last time you will be allowed to runthis product without installing a license orcorrecting access to the license server.

There are no licenses available from the license server for this product. Ifyou have installed license passwords on the license server, this may bedue to problems accessing the license server.

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

OpC20-0971 ** Cannot get an ITO server license.

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

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

OpC20-0972 ** ITO Temporary Server License: > expires TODAY

Chapter 2 57


You are currently running with a temporary license. You will not be ableto run this product after the specified date. Please contact your HP salesrepresentative or channel partner to purchase a license for this product.If you have installed license passwords on the license server, this may bedue to problems accessing the license server.

OpC20-0973 ** ITO Temporary Server License: > expires in < x1> days


OpC20-0974 ** Cannot get '< x1>' ITO managed node licenses

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


OpC20-0975 ** ITO Temporary Managed Node License: > expires TODAY


OpC20-0976 ** ITO Temporary Managed Node License: > expires in < x1>days


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

** If you have installed license passwords on the

58 Chapter 2


**license server, this may be due to problems**accessing the license server.*****************************************************

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


OpC20-0978 **************************************************** HP IT/Operations Temporary Server License:** > expires TODAY**************************************************


OpC20-0979 **************************************************** HP IT/Operations Temporary Server License:** > expires in < x1> days**************************************************


OpC20-0980 Cannot get '< x1>' additional ITO managed nodelicense(s). If you have installed license passwordson the license server, this may be due to problemsaccessing the license server.

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


Chapter 2 59


OpC20-1011 Can't close socket.

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

OpC20-1051 Invalid mutex.


OpC20-1052 Can't initialize mutex '< x1>'.

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

OpC20-1053 Can't destroy mutex '< x1>'.

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

OpC20-1054 Can't lock mutex '< x1>'.

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

OpC20-1055 Can't unlock mutex '< x1>'.

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

OpC20-1056 Can't create attributes of mutex '< x1>'.

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

OpC20-1057 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).

OpC20-1081 Can't create signal handler thread.

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

60 Chapter 2


OpC20-1082 Can't switch cancel request handling.

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

OpC20-1083 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.

OpC20-1100 Could not open socket

A socket, needed for communication over the network, could not beopened. Please make sure that this machine and all its networkconnections are functioning properly. Maybe no more memory or filehandles are available or the network connection has a problem. If youare quite sure that this problem has nothing to do with your machine'snetworking setup or operating system, then please report this to your HPResponse Center.

OpC20-1102 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 tocommunicate with other systems over the network. Please make surethat the network connection is working well. If this error message keepscoming even after you have carefully checked that the networkconnection is working well, then please report this to your HP ResponseCenter.

OpC20-1103 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 thenetwork. Please check error messages before or after this one to seewhich node could not be reached. It seems that routing on your networkis not configured properly so that this no route could be found to thisnode (or a router or switch is down). If you cannot easily find out whichnode is affected then please report this to your HP Response Center.

OpC20-2001 Invalid statement found in distribution list file'< x1>': '< x2>'.

Chapter 2 61


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

OpC20-2002 Can't write distribution list file. Name and path mustnot be empty.


OpC20-2021 Registered processing function failed for directoryelement '< x1>'.

An operation to be executed on the directory element <element> failed.This message is qualified by another message giving more information.

OpC20-2022 Invalid MPE directory format: '< x1>'. Must begroup.account.


OpC20-2023 Can't get list of files for MPE directory '< x1>'.

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

OpC20-2041 Cannot open MSI control pipe '< x1>'.

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

OpC20-2042 Cannot open MSI control queue '< x1>'.


OpC20-2043 mkfifo failed for '< x1>'.


OpC20-2044 Cannot open MSI read pipe '< x1>'.

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

OpC20-2045 Cannot open MSI read queue '< x1>'.

62 Chapter 2



OpC20-2046 Cannot open MSI write pipe '< x1>'.


OpC20-2047 Cannot open MSI write queue '< x1>'.


OpC20-2048 MSI instance '< x1>' already exists.

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

OpC20-2151 Can't get file system status for path '< x1>'.

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

OpC20-2152 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.

OpC20-2153 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 thepath portion of the NFS mount source.

OpC20-2154 Can't open mount table '< x1>'.

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

OpC20-2155 Internal error: File system '< x1>' not found.


OpC20-2181 Can't write control manager pipe.

Chapter 2 63


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

OpC20-2182 Can't write request into control manager queue.

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

OpC20-2183 Can't read request from control manager queue.

The reporting process could not read a request from the ITO controlmanager queue. This message is qualified by another message givingmore information.

OpC20-2184 Can't get name of control manager queue/pipe from configsubsystem.


OpC20-2185 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 moreinformation.

OpC20-2186 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.

OpC20-2187 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.

OpC20-2188 Can't close control manager pipe.

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

64 Chapter 2


OpC20-2189 No reading process at the control manager pipe - controlmanager down.

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

OpC20-2258 ITO license-process (distribution manager) isnot running on the ITO license server.

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

OpC20-2290 Cannot get the ITO management server name from theopcinfo file.

It is not possible to get the ITO management server name from theopcinfo file. Check whether the opcinfo file contains the correct entry forthe 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 agentsoftware and install it again from the ITO management server.

OpC20-2291 Cannot get the ITO management server name from theprimary mgr data file.

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

OpC20-2310 Problem occurred during encryption process.

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

OpC20-2400 Can't escalate ITO message < x1>.The ITO message is on the target ITO manager < x2> alreadyavailable.

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

Chapter 2 65


OpC20-2401 Can't escalate ITO message < x1>.Can't add the ITO message to the database on the targetITO manager < x2>.

An error occurred during the add of the ITO message to the database.This error message is qualified by another message giving moreinformation.

OpC20-2402 Can't escalate ITO message < x1>.Can't add the annotations of the ITO message to thedatabase on the target ITO manager < x2>.

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

OpC20-2403 Can't escalate ITO message < x1>.The source node < x2> is not configured as ITO managednode on the target ITO manager < x3>.

The source node of the ITO message is not configured as ITO managedon the ITO target system. The escalation of the message is not possiblein this case. Solution: Configure the source node of the ITO message onthe target ITO manager.

OpC20-2404 Can't escalate ITO message < x1>.Can't check whether the source node < x2> is an ITOmanaged node on the target ITO manager < x3>.

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

OpC20-2405 Can't escalate ITO message < x1>.Can't add the escalation information to the database onthe target ITO manager < x2>.

An error occurred during the add of the escalation information to thedatabase. This error message is qualified by another message givingmore information.

OpC20-2406 Error during escalation of ITO message < x1>.Can't inform ITO operators about escalated messageon the target ITO manager < x2>.

66 Chapter 2


It was not possible to inform operators about the escalated ITO messageThis is not really a problem because the responsible operator will get themessage the next time he/she logs in.

OpC20-2413 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 tocommunication problems. Make sure that the target manager is set upas managed node with the correct communication attributes on the localserver and the ITO server processes are running on the remote node.

OpC20-2500 Empty input data.

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

OpC20-2501 The input file '< x1>' was modified during transfer toanother management server system.

The reporting process was requested to transfer the file <file> to anothermanagement server and detected that the file became smaller duringdata transfer. Make sure that no other process modifies the file until theoperation has completed.

OpC20-2502 Can't connect to communication manager on system '< x1>'.

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

OpC20-2503 Can't send data through TCP socket to communicationmanager.

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

OpC20-2504 Invalid status returned from communication manager:'< x1>'.


Chapter 2 67


OpC20-2505 Invalid communication ID returned from communicationmanager: '< x1>'.


OpC20-2506 Unknown error returned by ITO communication manager onsystem '< x1>'.

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

OpC20-2507 Server error returned by ITO distribution manager onsystem '< x1>'.

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

OpC20-2520 No communication manager running.

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

OpC20-2521 Can't initialize connection to communication manager.

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

OpC20-2522 Can't send data to communication manager.

The ITO distribution manager on the target management server systemcould not initiate the data transfer to the communication manager.Verify the ITO error logfiles on the target system.

OpC20-2523 Can't send action request to communication manager.

The ITO distribution manager on the target management server systemcould not initiate a requested action to the communication manager.Verify the ITO error logfiles on the target system.

OpC20-2524 Can't close connection to communication manager.

68 Chapter 2


The ITO distribution manager on the target management server systemcould not close the connection to the communication manager. Verify theITO error logfiles on the target system.

OpC20-2621 Can't perform DCE login as '< x1>'. This principal doesnot 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 therequired ITO configuration use the opc_sec_register.sh script.

OpC20-2622 Can't perform DCE login as '< x1>'. Can't reach securityservice: < x2>.

The reporting process failed to contact the DCE security service duringlogon. Use the DCE utility 'dce_config' to verify and start the DCE serverprocesses.

OpC20-2623 Can't perform DCE login as '< x1>'. Generic error: < x2>.

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

OpC20-2624 Can't validate DCE login as '< x1>': < x2>.

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

OpC20-2625 Can't certify DCE login. The consulted security serviceis unknown: < x1>.

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

OpC20-2626 Can't activate DCE login context as '< x1>': < x2>.

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

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

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

Chapter 2 69


OpC20-2628 Can't register authentication information as/for RPCserver '< x1>': < x2>.

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

OpC20-2629 Can't get authentication information about calling RPCclient: < x2>.

The reporting process could not extract authentication data out of theRPC parameters. See <dce_err> for more details.

OpC20-2630 Can't log into DCE.

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

OpC20-2631 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 anduse the DCE utility 'rgy_edit' to verify the contents of the keytab file.

OpC20-2632 Can't create password for '< x1>' in key table file'< x2>': < x3>.

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

OpC20-2633 Can't convert password to DES key.

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

OpC20-2634 The calling RPC client is unauthenticated.

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

70 Chapter 2


OpC20-2635 The calling RPC client has registered as anotherprincipal than required.

The reporting RPC server received an authenticated RPC from a clientwhich logged on as another principal than expected. More information iscontained in another part of the error message. This can happen if thename service on the client system delivers another value for the localhost than on the server system.

OpC20-2636 The calling RPC client has bound to RPC server withanother principal than required.

The reporting RPC server received an authenticated RPC from a clientwhich is bound to another RPC server principal than expected. Moreinformation is contained in another part of the error message. This canhappen if the name service on the client system delivers another valuefor the local host than on the server system.

OpC20-2637 The calling RPC client requests an insufficient securitylevel.

The reporting RPC server received an authenticated RPC from a clientbut the selected security level is too low. More information is contained inanother part of the error message. Verify the configuration on the clientsystem for the correct security level.

OpC20-2638 The calling RPC client is not authenticated by the DCEsecurity service.

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

OpC20-2639 Can't get expiration time of current DCE login context:<x1>.

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

OpC20-2640 Can't get refresh current DCE login context of '< x1>':<x2>.

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

Chapter 2 71


OpC20-2641 Can't get delete current DCE login context of '< x1>':<x2>.


OpC20-2642 The current DCE login context is invalid.


OpC20-2643 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 securityservices have been restarted but the process maintaining (refreshing)the login context did not perform this operation. Restart the ITOmanager or agent processes depending on the reporting process.

OpC20-2644 Can't get account information for current DCE logincontext: < x1>.

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

OpC20-2645 Can't bind to DCE security service: < x1>.

The reporting process could not establish a connection to the DCEsecurity service. See <dce_err> for more details. Use the DCE utility'dce_config' to verify and start the DCE server processes.

OpC20-2646 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.

OpC20-2647 Can't close DCE security service: < x1>.


OpC20-2648 Can't get next password version for '< x1>': < x2>.

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

72 Chapter 2


OpC20-2649 Calling client: '< x1>'. Bound to server '< x2>'. Requestedsecurity level: '< x3>'.Required is: Client: '< x4>'. Server: '< x5>'. Leastsecurity level: '< x6>'.

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

OpC20-2650 The current DCE login context is the inherited defaultcontext: '< x1>'.

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

OpC20-2651 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 theprincipal does not exist. Use the DCE utilities to verify and the ITOutility opc_sec_register.sh to setup the required configuration.

OpC20-2652 Can't get server principal from client RPC handle:'< x1>'.

The reporting RPC client failed to extract the server name out of theRPC handle. See <dce_err> for more details. Possibly the server is notauthenticated at all. Check the RPC server host for error messages.

OpC20-2653 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 forerror messages. This is either an attempted security break or an internalerror.

OpC20-2701 Ambiguous option: < x1>.

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

OpC20-2702 Option < x1> requires < x2> arguments.

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

Chapter 2 73


OpC20-2703 Option < x1> conflicts with previous option < x2> whichrequires < 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.

OpC20-2704 Option < x1> must not be specified more than once.

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

OpC20-2705 Option < x1> cannot be specified in conjunction with otheroptions.

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

OpC20-2706 Illegal option: < x1>.

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

OpC20-2707 Option < x1> cannot be specified in conjunction with anyof:< x2>.

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

OpC20-2708 Option < x1> must be specified in conjunction with allof:< x2>.

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

OpC20-2709 Option < x1> must be specified.

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

OpC20-2710 Option < x1> does not allow unrecognized arguments.

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

OpC20-2720 Version: < x1>.

The default ITO program version text.

74 Chapter 2


OpC20-2721 Usage: < x1> [ -help ] [ -version ]

The default ITO program help text.

OpC20-2801 Internal error: No number range defined.


OpC20-2802 The specified range contains a nested sub-range near<x1>.

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

OpC20-2803 The specified range contains an illegal character near<x1>.

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

OpC20-2804 The specified range contains an illegal sequence near<x1>.

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

OpC20-2805 Internal error: Syntax error in range.

General syntax error in number set. Legal are ranges and lists like "-1020-30,40, 100-". Open ranges must appear at the begin and end of theset.

OpC20-2806 The specified range contains an illegal character near<x1>.

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

OpC20-2807 End of range - no more elements.

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

OpC20-2821 Queue empty.

The memory queue was empty during an attempted read operation.

Chapter 2 75


OpC20-2822 Queue full.

The memory queue was full during an attempted write operation.

OpC20-2831 Can't get exit code of terminated process '< x1>'.

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

OpC20-2832 Process '< x1>' terminated by signal '< x2>'. Exit code is<x3>.

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

OpC20-2833 Can't execute program '< x1>'. Check existence andpermissions.

The reporting process was unable to start a program as <command>.Check whether this command is a valid path, the file exists and has theappropriate permission required for execution. This can also happen dueto insufficient system resources. More information is contained inanother part of the error message.

OpC20-2834 Process '< x1>' terminated with exit code < x2>.

The controlled subprocess <proc> terminated unrequested. If the exitcode is not 0 the subprocess probably went down due to an internalfailure. Check the local ITO error logfile for more information logged bythe terminated process.

OpC20-2835 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 theappropriate permission required for execution.

OpC20-2836 Can't get process ID of of process '< x1>'.

76 Chapter 2


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

OpC20-2837 Can't add process object to table. Table full.


OpC20-2838 Process '< x1>' not found in table.


OpC20-2839 Could not terminate all controlled processes.

The reporting process attempted to terminate all started subprocessesbut at least one process did not exit. Check running ITO processes usingsystem commands and terminate remaining processes manually.


Cannot compress file with LZ 4.3 compression algorithm


Cannot uncompress file with LZ 4.3 compression algorithm

OpC20-2883 Cannot compress file (< x1> -> < x2>).

Cannot compress file with LZ 4.3 compression algorithm

OpC20-2884 Cannot uncompress file (< x1> -> < x2>).

Cannot uncompress file with LZ 4.3 compression algorithm

OpC20-2885 The file to be uncompressed does not end with extension.Z.

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

OpC20-2887 The file is either corrupted or not compressed.

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

OpC20-2889 Can't compress a buffer.

Chapter 2 77


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

OpC20-2890 Can't uncompress a buffer.

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

OpC20-2891 Can't uncompress the message from node '< x1>'.

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

OpC20-2892 Can't uncompress the action request from node '< x1>'.

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

OpC20-2893 Can't uncompress the action response from node '< x1>'.

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

OpC20-2921 Can't open connection to node '< x1>' for bulk transfer.

The Message Agent is unable to establish a connection to theManagement Server. A qualifying message gives more information.

OpC20-2922 Can't send data to node '< x1>' during bulk transfer.

The Message Agent is unable to send a request to the ManagementServer. A qualifying message gives more information.

OpC20-2923 The receiving server on node '< x1>' failed to process abulk transfer request.

The Management Server refused this request. A qualifying messagegives more information.

OpC20-2924 The receiving server on node '< x1>' failed to process abulk transfer request. Unknown error.

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

78 Chapter 2


OpC20-2930 Error occured with the request transfer.

Error occured with the request transfer.

OpC20-2931 Request from agent node with unknown server id.

There is no subserver registered on the Management Server with theserver ID as specified in this request. Probably an internal error in thesubagent sending this request or the according subserver is simply notyet configured.

OpC20-2932 Authentication failure.

The Management Server processes refused this requests to to anauthentication failure. Make sure that the security level on Server andAgent system match. Check the ITO error logfile on Agent and Server forrelated error messages.

Chapter 2 79

ITO Error MessagesError messages of agent processes

Error messages of agent processes

OpC30-0001 Internal error: Invalid request to assemble.


OpC30-0002 Internal error: NULL pointer passed to forward messageroutine.


OpC30-0003 Communication failure to message receiver: < x1>.Buffering messages.

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

OpC30-0004 Internal error: Unknown queue element.


OpC30-0005 There is a message agent running already.

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

OpC30-0007 Can't check already running agents.

The message agent should be started but is unable to check whether amessage agent is running already. This error message is qualified byanother message.

OpC30-0008 Initializing server failed.

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

OpC30-0010 Server main loop terminated. Exiting.

80 Chapter 2


The reporting process exits it's NCS server main loop and terminates.This can happen due to receipt of a signal. A qualifying message givesmore information.

OpC30-0011 Can't connect to ITO message receiver on system '< x1>'.

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

OpC30-0012 Can't unregister message agent.

The ITO message agent is unable to unregister at the NCS local locationbroker process llbd/rpcd running on the managed node. This action willbe done by the message agent only on exit. The next time the messageagent starts up it will overwrite the remained entry. Solution: Checkwhether the llbd/rpcd process is running on the managed node, using thelb_admin/rpccp tool.

OpC30-0013 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 tothe message receiver on start-up, or when it detects a communicationerror and tries to reconnect. The message agent can not reach thellbd/rpcd on the node. It starts up and buffers all incoming requests.Solution: Check whether the llbd/rpcd is running on the managementserver.

OpC30-0014 Internal error: Message buffer queue is empty.


OpC30-0015 Can't read buffered message.

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

OpC30-0016 Can't retrieve number of buffered messages.

The ITO message agent is unable to retrieve the number ofmessages/action responses currently contained in the buffer queue file.This error message is qualified by another message giving moreinformation.

Chapter 2 81


OpC30-0017 Can't return message to buffer.

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

OpC30-0018 Initializing configuration failed.

The ITO message agent is unable to get required configurationinformation. This message is qualified by another message giving moreinformation.

OpC30-0019 Can't retrieve local IP address.

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

OpC30-0020 Can't get name of ITO management server.


OpC30-0021 Can't get name of action request queue.


OpC30-0022 Can't get name of message buffer.


OpC30-0023 Can't open action request queue.

The ITO queue file between message agent and action agent can not beopened. This error message is qualified by another message giving moreinformation.

OpC30-0024 Can't open message buffer.

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

OpC30-0025 Can't close action request queue.


OpC30-0026 Can't close message buffer.


82 Chapter 2


OpC30-0027 Can't put action request into queue.

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

OpC30-0028 Can't put message/action response into message buffer.

The ITO message agent is unable to store a message/action responsetemporarily into the buffer queue file. This error message is qualified byanother message giving more information.

OpC30-0029 There is no ITO message receiver registered on system'< x1>'. Buffering messages.

The ITO message agent could not connect to the message receiverbecause there is no such ITO server running on the node. Solution:Check whether the management server processes are running.

OpC30-0030 The ITO message receiver is not running on system '< x1>'.Buffering messages.

The ITO message agent could not connect to the message receiver. TheITO message receiver is registered on the node but not responding. Thiscan also be caused by a crash of the message receiver. Solution: Checkwhether the management server processes are running.

OpC30-0031 Assembly of fragmented request failed.


OpC30-0032 Can't retrieve node control status. Assuming monitoredonly.

The ITO message agent is unable to retrieve the status of the managednode from the 'nodeinfo' configuration file. The status 'Monitored Only' isassumed. Solution: Check the managed-node-specific configuration file'nodeinfo' for a statement such as OPC_NODE_TYPE <node_type>.

OpC30-0033 Can't get IP address of management server.

The ITO message agent is unable to convert the name of themanagement server to an IP address. Solution: Check the name of themanagement server system in the 'opcinfo' file to be correct and verifywhether this name can be resolved to an IP address on the managednode.

Chapter 2 83


OpC30-0034 Can't get IP address of action request.


OpC30-0035 Action request from node other than the managementserver arrived (< x1>).

The ITO message agent received an action request from a node otherthan the currently-assigned management server with the IP address<address>. This might be caused by an assignment of this managed nodeto another management server. Solution: Check the ITO nodeconfiguration on the system with the specified IP address.

OpC30-0036 Forwarding message/action response to ITO messagereceiver failed due to server failure.


OpC30-0037 Can't retrieve RPC parameters for max. data array sizeand inter RPC delay.


OpC30-0038 Can't set signal handler for signal < x1>.

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

OpC30-0039 Can't open the ITO message agent buffer file (< x1>).

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

OpC30-0040 Can't initialize the alive check for the responsible ITOmanagement servers.

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

OpC30-0041 Errors occurred during the read of the responsiblemanager configuration file < x1>.

An error occurred while reading the ITO responsible managerconfiguration. This message is qualified by another message giving moreinformation.

84 Chapter 2


OpC30-0042 Can't get IP address for ITO management server < x1>.

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

OpC30-0043 ITO action response with invalid IP address received.The action response is ignored.


OpC30-0044 No ITO subagent found.

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

OpC30-0045 Can't evaluate a manager for subagent-id < x1>. Dropmessage.

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

OpC30-0053 Can't retrieve IP addresses.

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

OpC30-0054 Cannot contact node < x1> via ping-module.

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

OpC30-0055 Can't get own identity from login context.

The ITO message agent failed to retrieve it's own identity from theinherited DCE login context. This login context is supposed to beestablished by the ITO Control agent. Check the ITO error logfile forerror messages from the Control agent. This error message is qualifiedby another message giving more information.

OpC30-0056 Can't authenticate with DCE security service. Managementserver: '< x1>'.Manager name: '< x2>'; own name: '< x3>'.Sending data unauthenticated.

Chapter 2 85


The ITO message agent failed to initialize an authenticated RPCconnection to the management server <mgmt sv>. This error message isqualified by another message giving more information. The Messageagent will send further data unauthenticated.

OpC30-0057 Authentication failure to message receiver: < x1>.Retrying unauthenticated ...

The ITO message agent failed to send an ITO message/action responsevia authenticated RPC. This happens usually if the ITO messagereceiver does not run authenticated but the Message agent does. TheMessage agent will send further data unauthenticated. Possibly theManagement server failed to initialize properly or the Managementserver has been unconfigured in the DCE security service. Verify the ITOmanagement server error logfile for security related error messages.

OpC30-0058 Unable to obtain proper security context for < x1>.Further security related error messages will besuppressed.

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

OpC30-0059 ITO agents failed to write queue file '< x1>'. No space infile system.

The ITO message agent detected that a previous write operationattempted by another ITO agent failed due to lack of file system space.The writing agent will retry the write operation. Nevertheless this is acritical condition and may limit the entire ITO functionality. Log on themanaged node and free up file space in the file system where the queuefile <queue> resides.

OpC30-0060 Can't get queue status of queue file '< x1>' or unknownstatus: < x2>.

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

86 Chapter 2


OpC30-0095 The message agent detected a corrupted queue-file(< x1>). A backup for trouble-shooting purpose wasstored at < x2>. The ITO agent processes will berestarted automatically.

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

OpC30-0096 The message agent detected a corrupted queue-file;it renamed the file created a new one, but failed totriggerthe 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 restartthe agent processes after a queue-file was corrupted. This may have beencaused due to the fact, that the control agent wasn't registered asRPC-server yet. Please try to restart the agents manually by using theITO server command opcragt or use the appropriate entry in theapplication desk-top.

OpC30-0101 Configuration file contains no source description.

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

OpC30-0102 Configuration file contains no source description.Continuing with old configuration.


OpC30-0103 Cannot create default message for source < x1>.

The ITO logfile encapsulator is unable to create a default message filledwith globally configured values. This error message is qualified byanother message giving more information.

OpC30-0104 Cannot set signal mask for SIGUSR1.


Chapter 2 87


OpC30-0105 Cannot install signal handler for SIGUSR1.


OpC30-0106 Installation of new configuration failed. Continuingwith old one.

The ITO logfile encapsulator is unable to install a new assignedconfiguration. The previously distributed configuration will be usedfurthermore. This error message is qualified by another message givingmore information.

OpC30-0107 Command '< x2>' configured in source '< x1>' returns < x3>.Ignoring this logfile.

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

OpC30-0108 Logfile < x1> doesn't exist. Treating as empty.

The logfile doesn't exist. This message is reported only when the logfileencapsulator starts up and this feature is enabled for this logfile source.Non-existent files are always treated as empty.

OpC30-0109 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. Thelogfile encapsulator maps the file path.

OpC30-0110 Cannot get context while expanding CDF name.

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

OpC30-0111 Internal error: Logfile is no CDF.


OpC30-0112 Can't get name of configuration file.


88 Chapter 2


OpC30-0113 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 moreinformation.

OpC30-0114 Can't convert configuration file.


OpC30-0115 Can't retrieve name of message logfile.


OpC30-0116 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 moreinformation.

OpC30-0117 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 moreinformation.

OpC30-0118 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 moreinformation.

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


OpC30-0120 Can't retrieve config flag file name.


OpC30-0121 Can't retrieve config flag file checking interval.


OpC30-0122 Installation of configuration failed.

Chapter 2 89


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

OpC30-0123 Main loop terminated.

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

OpC30-0124 Can't get command status.


OpC30-0125 Can't set command status.


OpC30-0126 Can't get exit code of command.


OpC30-0127 Can't run command < x1>.

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

OpC30-0128 Can't kill command < x1>.

The ITO logfile encapsulator is unable to terminate a command startedpreviously as configured file to be executed before logfile processing. Thisaction has to be performed when the logfile configuration belonging tothe command that is running has been modified. Solution: Check thatprocesses having the PID of the logfile encapsulator as parent exist anddisplay proper functionality. If there are hanging processes, kill themmanually.

OpC30-0129 Can't remove config flag file.


OpC30-0130 Invalid CDF specification in < x1>.

The CDF logfile specification configured in template <logfile> is notvalid.

OpC30-0131 Invalid interval for object < x1> specified. Usingdefault (< x2>).

90 Chapter 2


The ITO logfile encapsulator encountered an invalid interval configuredfor the logfile <logfile>. The logfile encapsulator proceeds with thespecified default value. This is an internal Error. Please report this toyour HP Response Center.

OpC30-0132 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 wasremoved by another process. The logfile encapsulator treats the file asempty. Only valid for UNIX systems.

OpC30-0133 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 wasremoved and newly created by another process. The logfile encapsulatorreopens the file. Only valid for UNIX systems.

OpC30-0134 Can't get default directory for conversion programs.


OpC30-0135 Can't get path from environment.

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

OpC30-0136 Can't set path in environment.

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

OpC30-0137 Can't append ITO default path for conversion programs.

The ITO logfile encapsulator is unable to modify the execution path inthe environment to include the ITO path for monitoring scripts. This isnecessary to start configured conversion scripts/programs from thisdefault location. This error message is qualified by another messagegiving more information.

OpC30-0138 Can't convert logfile entry.

Chapter 2 91


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

OpC30-0139 Logfile path for object < x1> is empty but no alternatefile specified.

The ITO logfile encapsulator encountered an empty logfile pathconfigured for the object <logfile>. This is only allowed if an alternate fileto be read is specified.

OpC30-0140 CDF base directory < x1> not found for logfile oralternate 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 namebecause the next directory doesn't exist. The logfile encapsulatorproceeds with the assumption that the <*.node> path component standsfor the host name.

OpC30-0141 Environment variable '< x1>' requested for path '< x2>' notset. Replacing by empty string.

The ITO logfile encapsulator could not get the value of the environmentvariable <var> to replace in the logfile path <path>. The variablespecifier will be left empty. This might cause the monitoring of a wrongpath which doesn't exist. The logfile encapsulator treats non-existentfiles as if they ar empty. The variable must be set in the environment theITO processes are started in.

OpC30-0142 Can't expand environment variables in path '< x1>'.

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

OpC30-0143 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.

OpC30-0144 NT API < x1>: Can't close the NT Eventlog < x2>.

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

92 Chapter 2


OpC30-0145 NT API < x1>: Can't expand strings, message file = '< x2>'.

The NT API was unable to expand path variable. Investigate using theNT control panel. Make sure that the variable exists and is correctly set.

OpC30-0146 NT API < x1>: Can't open message file '< x2>' of NTeventlog.

The NT API was unable to open the message file. Use the NT RegistryEditor to make sure the message file exists, and is in the path. Open acommand shell and type "echo $PATH" to examine the default paths.

OpC30-0147 NT API < x1>: Can't find message for Event Id < x2> inmessage file < x3> for source < x4>.

The NT API was unable to find a message for a specific Windows NTEvent ID. This could happen if a third-party program created an EventID, but did not create any message text for that ID. In this case, the NTAPI will record the default value "The description for the Event ID ###could not be found"

OpC30-0148 NT API < x1>: Can't close message file '< x2>' of NTeventlog.

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

OpC30-0149 The NT Eventlog < x1> was changed (cleared) and thecurrent position is no longer reachable. ITO startsreading from the beginning of the Eventlog.Some records might be lost.

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

OpC30-0152 Command '< x2>' configured in source '< x1>' cannot beexecuted. 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 thepermissions are correct. If this error message was reported by a HP-UX

Chapter 2 93


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

OpC30-0201 Can't open SNMP session: < x1>.

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

OpC30-0202 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 usingthe ovstatus(1m) utility. Restart these services if necessary.

OpC30-0203 Select failed.

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

OpC30-0204 Receiving SNMP PDU failed: < x1>. Trying to reinitialize.

The ITO event interceptor could not get a SNMP PDU although it wasinformed that there is one available. The SNMP API message<snmp-msg> gives more information. The event interceptor tries toreconnect to pmd.

OpC30-0205 Can't close SNMP session: < x1>.

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

OpC30-0206 Can't get hostname.

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

OpC30-0207 Configuration contains more than one source. Using firstone (< x1>).

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

94 Chapter 2


OpC30-0208 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. Theevent interceptor tries to open the SNMP trap port 162 directly. Solution:Check whether the OV processes 'ovtrapd' and 'pmd' are running usingthe ovstatus(1m) utility. Restart these services if necessary.

OpC30-0551

The operator-initiated action to answer an MPE-request did not open anX-display on the operators system to enter the reply. possible reasons:the used DISPLAY-variable, transferred to the MPE system cannot beresolved there. Check for name service entries on MPE and check forshort/long hostnames in DISPLAY-variable. To fix this, set theDISPLAY-variable on the operator's system appropriately and restartthe GUI to get the value into the environment. The MPE-system ismaybe not authorized to open a display on the operator's system as well.

OpC30-0562 ITO Account does not have the required privilegesenabled.Actions will not be allowed to switch user accounts.

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

OpC30-0563 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 ITOAccount) or a removal of the security library (opcauth.dll) from the%SystemRoot%\system32\ directory.

OpC30-0568 Actions are currently not allowed to switch the useraccount.Please check for errors occurred during agent startup.

The action agent cannot start actions under certain user accounts. Forinstance if it cannot register at the NT LSA, if the NT version failed theverification, or if the HP ITO Account is not configured correctly.Previous error messages may help in analyzing this situation.

Chapter 2 95


OpC30-0569 Could not switch to user (< x1>).There is no Domain Controller for logon authenticationavailable.

The action agent failed to start an application under a certain useraccount. No NT Primary nor NT Backup Domain Controller wasavailable to validate the logon request. Please verify that the networkconnections and Domain Controllers are up and running.

OpC30-0571 Switch to user (< x1>) failed.There is no ITO agent installed on the active domaincontroller.

The action agent failed to start an application under a certain useraccount. This agent requires that the NT Domain Controllers for thissystem are running AND have an ITO agent installed. Please ensurethat all currently active Domain Controllers have an installed ITO NTAgent.

OpC30-0600 Can't get own IP-address; no monitoring of SNMPvariables possible.

The ITO monitoring agent is unable to retrieve the IP address of themanaged node. This information is required for monitoring of local MIBvariables. The process will start up anyway, if any script or externalmonitors are defined. This error message is qualified by another messagegiving more information.

OpC30-0601 Can't establish SNMP session; no monitoring of SNMPvariables possible.

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

OpC30-0603 Can't close SNMP session.

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

OpC30-0604 Can't retrieve polling interval for managed nodeself-monitoring.


96 Chapter 2


OpC30-0605 Can't install new configuration.

The ITO monitoring agent was unable to install a new configurationdistributed to the managed node. This can happen either at start up orwhile runtime when re-distributing the configuration. The monitoringagent will terminate resp. continue with the previously installedconfiguration. This error message is qualified by another message givingmore information.

OpC30-0606 Can't execute script for monitor < x1>.

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

OpC30-0607 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 retrievethe current value for the monitored object. Solution: Check whether theSNMP daemon on the target node is reachable and the following entryexists in /etc/snmpd.conf: 'get-community-name:' or'get-community-name: public'.

OpC30-0608 Can't retrieve value for monitor '< x1>'.Suppressing further error messages.

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

OpC30-0609 Can't kill monitor script (Pid = < x1>).

The ITO monitoring agent is unable to kill a monitoring script/programthat has been started. This action is performed if the running scriptbelongs to a monitored object whose configuration must be modified. Thiserror message is qualified by a system error text (errno).

OpC30-0610 Can't start monitor script for object '< x1>'. Scriptstill running.

Chapter 2 97


The monitor agent should start a monitor script for the object but thescript started last time is still running. Probably either the interval is tooshort or the script hangs. Solution: Verify whether the script workscorrectly. Adapt the interval if necessary.

OpC30-0611 Can't install signal handler for SIGUSR1 signal.


OpC30-0612 Internal error: Object '< x1>' received unexpected event'< x2>'.


OpC30-0613 Unknown monitor '< x1>'. Ignoring received value.

The monitor agent received a monitor value for the currently notconfigured object. The value will be discarded. Solution: Check whetherthe configured monitor scripts deliver correct object names. Verifywhether other processes sending monitor values are active.

OpC30-0615 Can't get name of temporary directory. Using "."instead.


OpC30-0616 Can't open temporary file to save error messages ofmonitor '< x1>'.

The ITO monitoring agent is unable to open a temporary file to store theoutput of the monitoring script/program configured for the object<mon_name>. This error message is qualified by a system error text(errno).

OpC30-0617 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 stderroutput generated by the script/program configured for the object<mon_name>. The script/program exited with a non-zero exit code. Thiserror message is qualified by a system error text (errno).

OpC30-0618 Script for monitor '< x1>' failed.Error message: '< x2>'.Suppressing further error messages.

98 Chapter 2


The executed script for the object exits with a non-zero exit code. Themonitor agent assumes that the script failed. <msg> contains the stderroutput of the script. Solution: Verify whether the script works correctly.A monitor script should contain an exit 0 statement.

OpC30-0621 Can't open monitor value queue file; no monitoring viascripts possible.

The ITO monitoring agent is unable to open the queue file used forreading the actual values from the opcmon(1|3) interface. This errormessage is qualified by another message giving more information.

OpC30-0622 Can't close monitor value queue file.

The ITO monitoring agent is unable to close the queue file used forreading the actual values from the opcmon(1|3) interface. This errormessage is qualified by another message giving more information.

OpC30-0625 Can't send a 'threshold exceeded' message for monitor'< x1>'.

The ITO monitor agent could not send an ITO message but the thresholdfor the object is exceeded. This error message is qualified by anothermessage giving more information.

OpC30-0627 Monitor agent exits due to exception.

The ITO monitoring agent exits, due to a received signal. This errormessage is qualified by another message giving more information.

OpC30-0628 Monitored SNMP variable of object '< x1>' is not ofnumeric 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) orthe variable is unknown. Solution: Check whether the SNMP object ID ofthe variable is correct.

OpC30-0629 Monitor queue is empty.


OpC30-0630 Monitor value belongs to other object.


Chapter 2 99


OpC30-0631 Reading monitor queue failed.


OpC30-0632 Can't get name of monitoring queue.


OpC30-0633 Can't update configuration. Continuing with old one.

The ITO monitoring agent is unable to install a newly distributedconfiguration. The process continues using the previously installedconfiguration. This can happen you you assigned a monitor and ascheduled action with the same name to a agent. Please use uniquenames for monitors and a scheduled actions.

OpC30-0634 Can't get monitoring script directory to append to path.


OpC30-0635 Can't get path environment variable.

The ITO monitoring agent is unable to retrieve the execution path fromthe environment. This error message is qualified by a system error text(errno).

OpC30-0636 Can't update path environment variable.

The ITO monitoring agent is unable to add ITO related directories to theexecution path in the environment.

OpC30-0637 Appending default path for monitoring scripts failed.Using current path.

The ITO monitoring agent is unable to set the execution path in theenvironment. This error message is qualified by a system error text(errno).

OpC30-0638 Can't get interval for checking external monitoring.


OpC30-0639 Invalid value for external monitoring interval. Usingdefault (< x1>s).


100 Chapter 2


OpC30-0640 Invalid monitoring interval for object '< x1>' specified.Using default (< x2>s).

The ITO monitoring agent encountered a monitoring interval out of thevalid range configured for the object <mon_name>. The default value of<default> seconds will be used.

OpC30-0641 Can't get name of monitor pipe.


OpC30-0642 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).

OpC30-0643 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).

OpC30-0644 Number of valid monitored objects is zero.

The ITO monitoring agent's configuration contains no valid monitoredobject, or all the configured objects cannot be monitored due to othererrors. The monitoring agent will exit.

OpC30-0645 Can't execute monitor script for object '< x1>'. Systemcall exec(2) failed.

The ITO monitoring agent is unable to execute the script/programconfigured for object <mon_name>. This might happen if thescript/program is not present at all or the required permissions aremissing. This error message is qualified by a system error text (errno).

OpC30-0646 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 subsequentexecution 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 Can't find required perfmon object for the monitorscript '< x1>'

The agent was unable to find the object specified in a threshold monitortemplate. Please check to make sure that the software that produces theobject is installed on the system and that the name of the object isexactly the same as the name specified in the corresponding thresholdmonitor template.

OpC30-0648 Can't find required perfmon counter for the monitorscript '< x1>'

The agent was unable to find the counter specified in a threshold monitortemplate. Please check to make sure that the name of the object isexactly the same as the name specified in the corresponding thresholdmonitor template.

OpC30-0649 Can't find index/counter for the monitor script '< x1>'.This could occur if the system software has beendeinstalled or changed on the system.Performance data cannot be monitored, check the localsystem to make sure that the system software iscorrectly installed.

Please ensure that this is not a problem with the intallation of SystemSoftware on the Managed Node. Please also ensure that the name of theobject to be monitored is correct. If this problem is then still a concern foryou, please report this to your HP Response Center.

OpC30-0650 Can't find required perfmon instance for the monitorscript '< x1>'

Please verify that the name of the instance and of the parent instancematch the names in the corresponding threshold monitor template.

OpC30-0680 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 anyabbreviation 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 oneparameter. Quote if necessary.

OpC30-0681 Invalid monitor value in '< x1>'.

102 Chapter 2


The value passed to the opcmon(1) command is not in a numeric format.Valid is any floating point representation recognized by scanf(3C).

OpC30-0682 Extra characters in monitor value '< x1>'.

Trailing non-numeric characters in the passed value are encountered bythe opcmon(1) command. Valid is any floating point representationrecognized by scanf(3C).

OpC30-0683 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 themonitored object and <value> the current value. Note that this pair mustbe passed as one parameter. Quote if necessary.

OpC30-0684 Can't forward monitor value to ITO monitor agent.

The opcmon(1) command is unable to forward a passed value to the ITOmonitoring agent. This error message is qualified by another messagegiving more information.

OpC30-0685 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 anyabbreviation 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 oneparameter.

OpC30-0686 The ITO monitor agent is not running. Can't forwardvalue.

The opcmon(1) command is unable to forward a passed value to themonitoring agent, because this process is currently not running. Checkwhether monitoring is configured at all, and if so, whether the ITOmonitoring agent is running, by using opcagt/opcragt(1).

OpC30-0800 Communication failure between Distribution Agent andDistribution Manager.

Chapter 2 103


Communication problem between distribution agent and distributionmanager; the network might be down or too much network traffic hascaused timeouts. Solution: Make sure that the network is performingappropriately. Afterwards, re-start the ITO agents on that managednode.

OpC30-0801 Distribution Manager too busy (after several retries).Distribution Agent will stop requesting now.

Distribution agent will stop requesting now. The distribution manageron the management server system has to handle more requests inparallel than possible (max. 5 requests), so the distribution request ofthis distribution agent has not been accepted, however new data fortransmission is available for that managed node. Solution: Re-start theITO agents on that managed node after you are sure that thedistribution manager is accepting requests again.

OpC30-0802 Cannot get ITO version info from local opcinfo file.

Internal Error. The opcinfo file does not exist or does not contain theOPC_INSTALLED_VERSION entry. The opcinfo file must have at leastthe following entries: OPC_INSTALLED_VERSION: <ITO_version>OPC_MGMT_SERVER: <mgmt_server_hostname>

OpC30-0803 Distribution Agent has been stopped during accessof new configuration or binary data; you have tore-enforce the distribution for consistent andcomplete data.

The distribution agent got an interrupt (for example, due to 'Stop Agents'call) and not all data available on the management server has beentransmitted yet. Solution: Re-distribute the data once more, after theITO agents on the managed node are running.

OpC30-0804 Cannot set signal mask.

Internal error. Please report this to your HP Response Center. Re-startthe management server processes and then re-distribute the selectedcomponents to that managed node. (This may not always work.)

OpC30-0805 Cannot install signal handler.


104 Chapter 2


OpC30-0806 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: OnUN*X systems: uname -a On MPE/iX systems: showme Compare theresult with the list of supported platforms and OS versions.

OpC30-0807 Got unexpected return value when calling DistributionManager.


OpC30-0808 Invalid transmission mode specified: '< x1>'. Using TCPsocket as default.

The ITO distribution agent encountered an invalid data transmissionmode configured in the local nodeinfo/opcinfo file. Valid is DIST_RPC orDIST_TCPSOCK. Using TCP socket mode.

OpC30-0809 Can't convert IP address of management server from NCShandle.

Internal NCS error. This error message is qualified by a message fromthe NCS subsystem giving more information.

OpC30-0810 Can't connect Distribution TCP socket server on system'< x1>'.

The ITO distribution agent is unable to connect the TCP socket serverprocess on the management server system <server>. This process will bestarted dynamically by the ITO distribution manager on demand. Checkthe opcerror logfile on the management server for a corresponding errormessage.

OpC30-0811 Receiving package from Distribution TCP socket serverfailed.

The ITO distribution agent is unable to receive expected distributiondata from the TCP socket server running on the management server.This error message is qualified by another message giving moreinformation. Check the opcerror logfile on the management server for acorresponding error message.

Chapter 2 105


OpC30-0812 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 therequested value of <size> bytes. The process continues with a defaultvalue.

OpC30-0813 Invalid number of busy-tries specified: '< x1>'. Valuemust be greater than zero. Trying infinitely.

The ITO distribution agent needed an invalid number of tries to getrequired data from the ITO distribution manager. This situation occurswhen the number of parallel requesting distribution agents exceeds theconfigured limit. The number of tries can be specified in thenodeinfo/opcinfo file and must be greater than zero. The distributionagent will try until success or an error.

OpC30-0814 The following configuration information was successfullydistributed:<x1> < x2> < x3> < x4> < x5>

The ITO distribution agent on this managed node received the specifiedconfiguration information from the distribution manager.

OpC30-0815 Invalid maximum number of distribution files per packagespecified: '< x1>'. Valid is < x2> - < x3>. Using '< x4>' asdefault.

The ITO distribution manager encountered an invalid maximum numberof files allowed per distribution package. This value may be in thespecified range only.

OpC30-0816 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 theformat V.##.##.

OpC30-0817 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.

OpC30-0818 Invalid line in distribution info file '< x1>': '< x2>';

106 Chapter 2


The distribution date file <distfile> contains an entry in an incorrectformat: <line>. Solution: Remove the file. It will be generated whendistributing next time.

OpC30-0819 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.

OpC30-0820 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 whendistributing next time.

OpC30-0821 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 givingmore information.

OpC30-0822 Can't read config directory '< x1>' to merge newdistributed elements.

OBSOLETE.

OpC30-0823 Can't read template file '< x1>'.

The ITO distribution agent could not read the template file <file> tomerge the newly distributed configuration with the already available.This error message is qualified by another message giving moreinformation.

OpC30-0824 Merge of new distributed and already present templatesfailed.

The ITO distribution agent could not merge the newly distributedconfiguration with the already available. This error message is qualifiedby another message giving more information.

OpC30-0825 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 moreinformation.

Chapter 2 107


OpC30-0826 Internal error: Unknown template type '< x1>'.


OpC30-0827 Can't get status of filesystem '< x1>'.

The ITO distribution agent could not get the status of the file system thepath <path> belongs to. This error message is qualified by anothermessage giving more information.

OpC30-0828 Cluster server '< x3>'(< x4>) reported by node '< x1>'(< x2>)unknown.

The ITO distribution manager received a distribution request from acluster client <client> but the corresponding cluster server <server> isnot configured as ITO managed node. The distribution request cannot bemapped to the cluster server. Solution: Configure the cluster server as anITO managed node.

OpC30-0829 Hostname to IP resolution for '< x1>' (mode='< x2>',preferred='< x3>') failed.

OBSOLETE.

OpC30-0830 Can't connect to distribution manager on '< x1>'.

The ITO distribution agent could not connect to the distributionmanager on the management server system <node>. This error messageis qualified by another message giving more information.

OpC30-0831 Can't resolve hostname '< x1>' (gethostbyname(3N)failed).

The ITO distribution agent could not resolve the name of themanagement server <node> using the gethostbyname(3N) call. Eitherthe name is wrong or not configured or maybe the name service is notaccessible. This message is qualified by a system error message (errno)giving more information.

OpC30-0832 Can't copy file '< x1> to '< x2>'.

The ITO distribution agent couldn't copy or link aaction/command/monitor script which is expected to be present on themanaged node. This might be caused by either a manual removal of thesource file on the managed node or by a modification of the correspondingfile on the management server in a way that the time of last modification

108 Chapter 2


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 errormessage exists; if not re-distribute with the 'Force update' option.Otherwise check the last modification time using ls -l on themanagement server and update the current time using the commandtouch(1).

OpC30-0835 Detected invalid template(s). Please re-distributeonly the templates once again with force-update(if not just happened).

This message is sent, since the current template files on a managed nodeare 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.

OpC30-0836 Can't get own identity from login context.

The ITO distribution agent failed to retrieve it's own identity from theinherited DCE login context. This login context is supposed to beestablished by the ITO Control agent. Check the ITO error logfile forerror messages from the Control agent. This error message is qualifiedby another message giving more information.

OpC30-0837 Can't authenticate with DCE security service. Managementserver: '< x1>'.Manager name: '< x2>'; own name: '< x3>'.

The ITO distribution agent failed to initialize an authenticated RPCconnection to the management server <mgmt sv>. This error message isqualified by another message giving more information. The Messageagent will send further data unauthenticated.

OpC30-0862 Access to the MPE console messages was disabled byan other program. The ITO console interceptor will exitnow.

The ITO console interceptor for MPE terminated, because it could notread further messages from the kernel data segment in which consolemessages are stored. There can be only one reader on that data segment.

Chapter 2 109


If another application (e.g. SYSMAN or EASYTIME) captured themessage queue, there is no chance to obtain further data for the consoleinterceptor.

OpC30-0913 The ITO Message Command is not configured on thissystem.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 tothe node was interrupted or failed or has been delayed for some otherreason. To solve this problem the administrator must check to see thatan opcmsg template is assigned to the node (directly or as a template in agroup) and then distribute templates to the node, using force update ifnecessary. If it is still not possible to distribute the templates it may helpto stop and restart the management server processes and then distributeagain.

OpC30-0955 Empty ITO Message Interceptor configuration.

The ITO message interceptor found that it's configuration file does notcontain any active logfiles. It will keep on running but won't process anymessages.

OpC30-1001 Can't initiate ITO configuration distribution

Could not start sub-process to control the distribution agent. No newtemplates, scripts or programs were distributed. The problem may becaused due to missing system resources (memory or process table). Try todistribute configuration data once again.

OpC30-1002 Can't open pipe to distribution agent

Can't open communication pipe between control agent and distributionagent. This may e.g. happen, if system resources (file descriptors) areexhausted. Distribution of new templates, scripts and programs failed.Try to distribute the data once again.

OpC30-1003 Can't delete file < x1>

Internal error. Please contact your HP Response Center.

OpC30-1004 Can't fork process

110 Chapter 2


No further process can be initiated, because system resources (processtable or memory) are exhausted. Check, how much processes run on theappropriate node; maybe some of them are obsolete.

OpC30-1005 Can't lock file < x1>


OpC30-1006 Can't create directory < x1>

Internal error. Please contact your HP Response Center. Maybe theappropriate file system is full.

OpC30-1007 Can't move < x1> to < x2>


OpC30-1008 Can't move < x1> to < x2>


OpC30-1009 Can't open directory < x1>

Internal error. Please contact your HP Response Center. There isprobably a resource problem (no further file descriptors available).

OpC30-1010 Can't open file < x1>

Internal error. Please contact your HP Response Center. There isprobably a resource problem (no further file descriptors available).

OpC30-1011 Can't read file < x1>


OpC30-1012 Can't initiate reconnect of ITO Message Agent to the ITOMessage Receiver

The control agent cannot contact its message agent via RPC-call.Therefore the message agent won't be informed, that it should forwardbuffered messages to the management station. Check, if the messageagent or local location broker aborted on the managed node. Maybe ithelps to restart the agent processes.

OpC30-1013 Can't set sid


Chapter 2 111


OpC30-1014 Can't start ITO Control Agent

The control agent cannot fork itself, because system resources (memoryor process table) are probably exhausted. Please check, if there areprocesses on the node, which are obsolete and could be killed.

OpC30-1015 Can't stat file < x1>


OpC30-1016 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 onceagain or do it manually.

OpC30-1017 Can't unlock ITO distribution lock file.


OpC30-1018 Can't write file < x1>


OpC30-1019 Errors occurred during the add of new configurationfiles for ITO.Solve the problems and distribute the configurationagain.

It was probably impossible, to move away current configuration data tobackup location, because some files there, which are still accessed(textfile busy), could not be overwritten. Refer to the trouble shootingsection in the administrator's guide.

OpC30-1020 Can't add the new configuration for ITO.


OpC30-1021 Errors occurred during the replace of configurationfiles for ITO.Solve the problems and distribute the configurationagain.

112 Chapter 2



OpC30-1022 Can't replace the configuration for ITO.


OpC30-1023 Can't connect to the ITO Message Agent

After starting the message agent, the control agent checks, if it came upsuccessfully. Check, if the local location broker is running. Maybe ithelps, to restart the agents.

OpC30-1025 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 onceagain or do it manually.

OpC30-1026 The ITO Distribution Agent reported an unexpected error.

The distribution agent aborted with an error. Check the error logfile formessages produced by the distribution agent. Try to distribute onceagain. Possibly the distribution agent couldn't be executed at all - checklocation and permissions.

OpC30-1027 The ITO Distribution Agent aborted.

The distribution agent aborted with an error. Check the error logfile formessages produced by the distribution agent. Try to distribute onceagain.

OpC30-1028 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 backuplocation, because some files there, which are still accessed (textfile busy),could not be overwritten. Refer to the trouble shooting section in theadministrator's guide.

Chapter 2 113


OpC30-1029 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 backuplocation, because some files there, which are still accessed (textfile busy),could not be overwritten. Refer to the trouble shooting section in theadministrator's guide.

OpC30-1030 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 backuplocation, because some files there, which are still accessed (textfile busy),could not be overwritten. Refer to the trouble shooting section in theadministrator's guide.

OpC30-1031 Could not start ITO Distribution Agent

Could not start ITO distribution agent, because there are probably toolittle system resources (memory or process table).

OpC30-1032 Invalid directory name < x1> for delete directory.


OpC30-1033 Can't copy ITO nodeinfo file


OpC30-1034 Can't distribute the nodeinfo file for ITO.


OpC30-1035 Can't read pipe

Internal error. Please contact your HP Response Center. Distribute theconfiguration data once again.

OpC30-1036 Initialize of the ITO Control Agent failed.


OpC30-1037 Can't start ITO Agents

114 Chapter 2


There are probably too little system resources (memory or process table),to start the ITO agents. Please check, how many processes are runningon the appropriate node. Maybe some are obsolete and can be killed. Tryto restart the ITO agents once again.

OpC30-1038 Unexpected data received from the ITO Distribution Agent

Internal error. Please contact your HP Response Center. Please checkappropriate logfiles for errors produced by distribution agent andmanager.

OpC30-1039 Can't inform the ITO Agents about the new configuration.

Internal error. Please contact your HP Response Center. A sub-process ofthe control agent could not get the process ids of the ITO agents. Theagents could not be informed, that new configuration is available.

OpC30-1040 <x1> of subagent < x2> aborted; process did an exit < x3>

The process monitoring of the control agent found an agent processwhich has aborted due to an exit(2) call.

OpC30-1041 <x1> of subagent < x2> aborted; process got signal < x3>

The process monitoring of the control agent found an agent processwhich has aborted due to a kill(2) call.

OpC30-1042 <x1> (< x2>) aborted on MPE-node

Internal error. Please contact your HP Response Center. The processmonitoring of the control agent found an agent process on MPE whichhas aborted. Please check the error logfile for messages produced by theaborted agent. Please check the output spool file of the ITO agents' jobfor program stack dumps.

OpC30-1043 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 missingsystem resources. Please, try to start the agents once again.

OpC30-1044 Can't connect to the ITO control agent. Checkwhether the local location broker runs on the node.

Chapter 2 115


Can't connect to the ITO control agent. Check whether the local locationbroker is running on the node. Without the llbd/rpcd, the ITO-agentscannot work correctly.

OpC30-1045 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 toconnect to the control agent once again if you think that it is supposed torun. Especially on MPE-nodes, the init-phase can last some seconds.

OpC30-1046 Can't readlink file < x1>.

Problem since following a symbolic link. Please, check the concerning fileand directories.

OpC30-1047 There are to many symbolic links in the link chain offile < x1>.

There are to many symbolic links in the link chain of the concerning file.

OpC30-1048 Cannot start ITO agent.No Local Location Broker or DCE RPC Daemon is running onthe system.

Cannot start ITO control agent. No Local Location Broker or DCE RPCDaemon is running on the system. Please start the appropriate service.Otherwise, the ITO-agents cannot work correctly.

OpC30-1049 Cannot start ITO agent.Network communication problems occurred.

Cannot start ITO agent. Network communication problems occurred.Please contact your system administrator. Maybe, the loopback interfaceof the concerning system is not running properly.

OpC30-1050 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 notconfigured as an ITO managed node.

OpC30-1055 The ITO control agent is currently not available but theagent job OPCAGTJ is running. Please try again later.

116 Chapter 2


The ITO control agent is currently not available but the agent jobOPCAGTJ is running. Please try to connect once again later.

OpC30-1056 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 notgenerate temporary job-file from original file opcagtj.bin.ovopc Trying touse the original jobfile to start the ITO-agents.

OpC30-1057 Job-stream of < x1> failed (used < x2> as job-streamfacility).<x3>

It failed to stream the ITO agents job with the customer definedjob-stream facility. Tried to use the default facility instead.

OpC30-1058 Job-stream of < x1> probably failed (used < x2> asjob-stream facility) (CI-warning < x3> < x4>).run opcagt -status to check, whether the agents werestarted.

It probably failed to stream the ITO agents job with the customer definedjob-stream facility. Run opcagt -status to check, whether the agents werestarted.

OpC30-1059 Directory < x1> could not be removed. Is it in use at themoment?

Please check to make sure that this directory is not being accessed fromany shell or file manager and that no programs are running from thisdirectory.

OpC30-1060 Directory < x1> could not be renamed to < x2>. Are they inuse at the moment?

Please check to make sure that this directory is not being accessed fromany shell or file manager and that no programs are running from thisdirectory.

OpC30-1071 Can't initialize DCE security as '< x1>'. Security level:'< x2>'.

Chapter 2 117


The ITO control agent failed to initialize the DCE security relatedcomponents. This includes a process login and RPC server initialization.This error message is qualified by another message giving moreinformation. Use the opc_sec_verify.sh utility on the managed node toverify a proper DCE configuration.

OpC30-1072 Can't login as agent administrator principal '< x1>'.

The ITO control agent could not log into DCE with it's primary identityand tried to use the administrative principal to recover the primaryaccount. This login operation failed, too. If the account 'opc-agt'adm' isdisabled, automatic password generation for the primary account cannotbe performed. This error message is qualified by another message givingmore information. Use the opc_sec_verify.sh utility on the managed nodeto verify a proper DCE configuration.

OpC30-1073 Can't recover primary account '< x1>'. Passwordgeneration failed.

The ITO control agent could not log into DCE with it's primary identityand tried to use the administrative principal to recover the primaryaccount. This operation failed even if the login as 'opc-agt-adm'succeeded. This error message is qualified by another message givingmore information. Use the opc_sec_verify.sh utility on the managed nodeto verify a proper DCE configuration.

OpC30-1074 Can't resolve local hostname '< x1>' with name service.Using hostname for authentification.

The primary identity of an ITO agent within DCE contains the fullyqualified hostname of the managed node. The ITO control agent failed toresolve the local hostname with the name service and will use the simplehostname. Possibly the login operation itself will fail. Always make surethat the local hostname can be resolved with the name service n any ITOnode.

OpC30-1075 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 securityattributes and refused the request. This can happen if the knownsecurity level on the managed node doesn't match the one configured on

118 Chapter 2


the management server - possibly due to a distribution failure. Alsomake sure that the calling management server is configured correctly inthe opcinfo resp. mgrinfo file.

OpC30-1094 output of kill -0 differs from internal pids-table forindex < x1>

Internal error. Please contact your HP Response Center. The buffercontaining agents' process ids does not correspond to actual status. Thementioned index has following meaning: if it contains a 1, storedmessage agent pid doesn't correspond to reality, if it contains a 2, storedaction agent pid doesn't correspond to reality, if it contains a 3, storedmonitor agent pid doesn't correspond to reality, if it contains a 4, logfileencapsulator pid doesn't correspond to reality, if it contains a 5, storedSNMP agent pid doesn't correspond to reality, if it contains a 6, storedmsg interceptor pid doesn't correspond to reality.

OpC30-1095 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.

OpC30-1096 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 stillaccessed. It remains as it is.

OpC30-1097 The following files could not be replaced duringITO distribution because they were accessed(textfile busy). The old files will be usedfurthermore

List of files couldn't be replaced during configuration distribution. Thefiles were still in access and therefor they were write-protected. Thesefiles remain unchanged. If it is really necessary to replace them, stop theagents and than do the distribution once again. This should help in mostcases.

OpC30-1100 Can't execute action on node < x1>. The ITO managementserversending the action request is not an authorizedITO management server for the managed node.

Chapter 2 119


The ITO control agent received an action request from an ITOmanagement server not configured as 'action allowed' ITO manager.Because only 'action allowed' ITO managers can execute actions on anITO agent the action request is ignored. Solution: Check the configured'action allowed' ITO managers. This can be done by checking the mgrconfand opcinfo file of the ITO agent.

OpC30-1110 Can't copy ITO responsible manager configuration file.

An error occurred during the copy of the ITO responsible managersconfiguration file. This error message is qualified by another messagegiving more information.

OpC30-1111 Can't get name of ITO responsible manager configurationfile.


OpC30-1193 Couldn't reconfigure subagent with ID < x1>.

The ITO Control agent failed to reinitialize the subagent <subagt>. Thiserror message is qualified by another message giving more information.

OpC30-1200 Errors occurred during the read of theITO responsible manager configuration.

During the read of the ITO responsible manager configuration file someerrors occurred. This error message is qualified by another messagegiving more information.

OpC30-1201 The ITO responsible manager configuration file < x1>containsmore than one configuration. The configuration file isignored.

The ITO responsible manager configuration file contains more than oneconfiguration. Solution: Check the configuration file in the respmgrsdirectory on the ITO management system and correct the configuration.

OpC30-1202 Errors occurred during the convertion of the ITOresponsible managerconfiguration file < x1>. The configuration file isignored.


120 Chapter 2


OpC30-1203 Warnings occurred during the read of theITO responsible manager configuration.

During the read of the ITO responsible manager configuration file somewarnings occurred. This error message is qualified by another messagegiving more information.

OpC30-1300 Pipe control failed, error < x1>.

The fcntl(2) call to control the ECS agent pipe failed. This message isqualified by a system error message (errno) containing the cause of theerror.

OpC30-1301 Pipe read failed, error < x1>.

The read(2) call to read the ECS agent pipe failed. This message isqualified by a system error message (errno) containing the cause of theerror.

OpC30-1302 Select MSI queue file failed, error < x1>.

The select(2) system call for the ECS MSI queue file failed. This messageis qualified by a system error message (errno) containing the cause of theerror.

OpC30-1303 Cannot load data store < x1>.

The ECS data store file could not be loaded. Probably the fopen(3) call toopen the data store file failed. This message is qualified by a systemerror message (errno) containing the cause of the error. Otherwise it isan HP internal ECS library error, in this case please contact your HPResponse Center.

OpC30-1304 Cannot load fact store < x1>.

The ECS fact store file could not be loaded. Probably the fopen(3) call toopen the fact store file failed. This message is qualified by a system errormessage (errno) containing the cause of the error. Otherwise it is an HPinternal ECS library error, in this case please contact your HP ResponseCenter.

OpC30-1305 Cannot open ECS engine log file < x1>.

The ECS engine log file could not be opened. This error message isqualified by another message providing more information.

Chapter 2 121


OpC30-1306 Cannot open ECS engine trace file < x1>.

The ECS engine trace file could not be opened. This error message isqualified by another message providing more information.

OpC30-1307 Cannot open ECS engine event input log file < x1>.

The ECS engine event input log file could not be opened. This errormessage is qualified by another message providing more information.

OpC30-1308 Cannot open ECS engine event output log file < x1>.

The ECS engine event output logfile could not be opened. This errormessage is qualified by another message providing more information.

OpC30-1309 Cannot put message into EC event log file < x1>.

Put an ITO message into an ECS event logfile failed. This error messageis qualified by another message providing more information.

OpC30-1310 No event types found to register.

The retrieved input event type value contains no event types for register.Check the used circuit.

OpC30-1311 Non string type event found for register.

Non-string type events could not register, because ITO messages arestrings. If it is not a string, it will be ignored.

OpC30-1350 MSI output is not enabled.No event correlation can be done.

The MSI output is not enabled. This means that the opcecm/opcecacannot receive from the Message Stream Interface. Check that theServer/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.

OpC30-1351 Cannot open MSI. Return error code < x1>.

The opcif_open(3) call to open ECS MSI instance failed. Check that theevent correlation MSI files in the OV temporary ITO directory do notexist; 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 Cannot close MSI. Return error code < x1>.

The opcif_close(3) call to close the MSI instance failed.

OpC30-1353 Cannot get MSI pipe file descriptor. Return error code<x1>.

The opcif_get_pipe(3) call to get the MSI pipe file descriptor failed.

OpC30-1354 Cannot register for ITO messages from the MSI.

The opcif_register(3) call to register for ITO messages from the MSIfailed.

OpC30-1355 Cannot unregister for ITO messages from the MSI.

The opcif_unregister(3) call to unregister for ITO messages from the MSIfailed.

OpC30-1356 Cannot create a registration condition.

The opcreg_create(3) call to initialize a registration condition failed.

OpC30-1357 Cannot set message type of registration condition.

The opcreg_set_str(3) call to set the message type field of a registrationcondition failed.

OpC30-1358 Cannot create empty ITO data type structure.

The opcdata_create(3) call to initialize an empty ITO data type structurefailed.

OpC30-1359 Cannot read a message from the MSI. Return error code<x1>.

The opcif_read(3) call to read a message from the MSI failed.

OpC30-1360 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.

OpC30-1400 Cannot initialize the EC engine.

Chapter 2 123


Internal ECS library error. If this occurs after a distribution, try torestart the ITO agent or distribute again. Otherwise please contact yourHP Response Center.

OpC30-1401 Cannot unload the EC engine.

Internal ECS library error. Please contact your HP Response Center.

OpC30-1402 Cannot create a new circuit from file < x1>.

Internal ECS library error. Probably a incorrect circuit was used. Thiscan be checked by using the EventFlow Circuit Simulator. If no error isfound, please contact your HP Response Center.

OpC30-1403 Cannot create event.


OpC30-1410 Cannot retrieve circuit variable "< x1>".


OpC30-1420 Wrong engine value type code. Type code: < x1>.


OpC30-1421 Cannot create engine value object of type < x1>.


OpC30-1422 Cannot copy engine value object.


OpC30-1430 Cannot input event to ECS circuit (ECS err code < x1>).


OpC30-1431 Event was rejected by the ECS circuit. It's probablyolder thanspecified in the circuit's maximum transit delay.

The message was rejected by the ECS engine because no circuit wasinterested in it. By the time the message was delivered to the engine, themessage was probably older than specified in the circuit's maximumtransit delay (an indicator for this is the difference between themessages creation time and its receive time).

124 Chapter 2


OpC30-1440 Cannot create and initialize a new log message buffer.


OpC30-1441 Cannot create and initialize a new trace message buffer.


OpC30-1442 Cannot register an EC engine logging message buffer.


OpC30-1443 Cannot register an EC engine trace buffer.


OpC30-1444 Cannot set the EC engine log mask.


OpC30-1445 Cannot set the EC engine global trace mask.


OpC30-1446 Cannot set the EC engine global component mask.


OpC30-1450 Cannot initialize the encode/decode libraries internaldata structures.


OpC30-1451 Encode/decode library has not been initialized.


OpC30-1452 Cannot register a "< x1>" event encoding and decodingmodule.


OpC30-1453 Encode/decode library has not been initialized or themodule type "< x1>" was not known.


Chapter 2 125


OpC30-1454 Module type "< x1>" already known by the encode/decodelibrary.


OpC30-1455 Cannot initialize an encode/decode library eventworkspace.


OpC30-1456 Cannot set the default workspace pointer.


OpC30-1457 Cannot get event structure from the internal eventsmemory pool.


OpC30-1458 Cannot extract a raw event from an encode/decode eventobject.


OpC30-1459 Cannot delete all allocated events.


OpC30-1460 Cannot add a type entry to the encode/decode type table.


OpC30-1462 Annotate request ("< x1>") timed out.

The ECS annotate node executed a command but it was not possible topass back the results to the circuit due to a timeout. You can modify thetimeout by changing the time-limit value for annotate-node definitions inthe ECS designer.

OpC30-2000 NT API < x1>: WIN32API_ERROR; Thread ID < x2>.

Internal NT API error. Please contact your HP Response Center. Reportthe API function name and Thread ID.

OpC30-2050 Could not open the NT window sockets.

Internal NT API error. Please contact your HP Response Center.

126 Chapter 2


OpC30-2100 NT API < x1>: Could not get a valid handle.

Internal NT API error. Please contact your HP Response Center. Reportthe API function name.

OpC30-2101 NT API < x1>: The handle for < x2> could not be closed.

Internal NT API error. Please contact your HP Response Center. Reportthe API function name and the resource.

OpC30-2120 NT API < x1>: Thread with Id < x2> failed to suspend.


OpC30-2121 NT API < x1>: Thread with Id < x2> failed to terminate.


OpC30-2122 NT API < x1>: Thread could not be created.

The system might have been overloaded when the API tried to create thethread. If this error reoccurs, Please contact your HP Response Center.Report the API function name.

OpC30-2123 NT API < x1>: Thread with Id < x2> failed to resume.


OpC30-2130 NT API < x1>: Failed to get Mutex for < x2>.


OpC30-2131 NT API < x1>: Failed to release Mutex for < x2>.


OpC30-2140 NT API < x1>: Event < x2> could not be created.

Internal NT API error. Please contact your HP Response Center. Reportthe API function name and event name.

OpC30-2141 NT API < x1>: Event < x2> failed to be set.

Chapter 2 127



OpC30-2142 NT API < x1>: Event < x2> failed to be reset.


OpC30-2143 NT API < x1>: Event < x2> does not exist.


OpC30-2150 NT API < x1>: Can't create security descriptor.


OpC30-2151 NT API < x1>: Can't init security descriptor.


OpC30-2152 NT API < x1>: Can't set security descriptor.


OpC30-2160 NT API < x1>: Process could not be created.


OpC30-2161 NT API < x1>: Process with Id < x2> failed to terminate.

Internal NT API error. Please contact your HP Response Center. Reportthe API function name and process ID.

OpC30-2170 NT API < x1>: Can't open NT Registry Key < x2>.

Internal NT API error. Please contact your HP Response Center. Reportthe API function name and NT Registry Key name.

OpC30-2171 NT API < x1>: Can't query NT Registry Key < x2>.

Internal NT API error. Please contact your HP Response Center. Reportthe API function name and NT Registry Key name.

128 Chapter 2

ITO Error MessagesError messages of manager processes

Error messages of manager processes

OpC40-0001 Can't open pipe < x1>.

Either the action manager pipe or the message manager pipe could notbe opened. This message is qualified by a system error message (errno)giving more information.

OpC40-0002 Can't create pipe < x1>.

Either the action manager pipe or the message manager pipe could notbe created. This message is qualified by a system error message (errno)giving more information.

OpC40-0003 Retrieving names of queues/pipes failed.


OpC40-0004 Opening of queues/pipes failed.

The ITO message receiver could not open a queue or pipe to the actionmanager or message manager. More information is contained in anotherpart of the error message.

OpC40-0005 Can't close message queue.

The ITO message receiver is unable to close the message queue file usedto pass messages to the ITO message manager. This error message isqualified by another message giving more information.

OpC40-0006 Can't write message queue.

The ITO message receiver is unable to pass a message through themessage queue file to the ITO message manager. This error message isqualified by another message giving more information.

OpC40-0007 Internal error: Invalid request to assemble.


OpC40-0008 Initializing server failed.

Chapter 2 129


The ITO message receiver encountered a problem during initialization asRPC server. This error message is qualified by another message givingmore information.

OpC40-0009 Server main loop terminated. Exiting.

The ITO message receiver's RPC main loop terminated abnormally. Thiserror message is qualified by another message giving more information.

OpC40-0011 Assembly of fragmented request failed.


OpC40-0012 Can't close action request queue.


OpC40-0013 Can't put action request into queue.

The ITO message receiver is unable to pass a action response throughthe message queue file to the ITO action manager. This error message isqualified by another message giving more information.

OpC40-0014 Can't unregister message receiver.

The ITO message receiver couldn't unregister during shutdown. Thiserror message is qualified by another message giving more information.

OpC40-0015 Can't create server thread.

The ITO message receiver couldn't start a thread executing the Sun RPCserver loop. This error message is qualified by another message givingmore information.

OpC40-0016 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 moreinformation.

OpC40-0017 Initializing Sun RPC server failed.

The ITO message receiver encountered a problem during initialization asSun RPC server. This error message is qualified by another messagegiving more information.

130 Chapter 2


OpC40-0018 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 moreinformation.

OpC40-0019 Can't read server registration file.

The ITO message receiver couldn't read the Common Agent serverregistration file. Check existence and permissions of this file. This errormessage is qualified by another message giving more information.

OpC40-0101 Inconsistent distribution package data.

Internal error. Please report this to your HP Response Center.Re-distribution of the selected components may help.

OpC40-0102 Invalid distribution type < x1> got from DistributionAgent.


OpC40-0103 No more free entries of package table.

More than five distribution agents are trying to access the newconfiguration simultaneously. The distribution agents will retry severaltimes; if they fail, a corresponding message will also be sent. In the lattercase, you have to re-start the agents on that managed node (re-startingtriggers the distribution agent, too).

OpC40-0104 Distribution package for system < x1> cleaned,because no new data request of the DistributionAgent for more than 10 minutes.

The distribution agent on managed node did not retrieve all provideddistribution packages. It might have terminated due to unexpectedinterrupt or the network connection has been broken. Solution: Verifythe network connection is okay; then re-distribute the entireconfiguration (and monitor/actions/commands binaries) to the managednode.

OpC40-0105 No ITO version found in file < x1> supportingOS version < x2> of Managed Node < x3>.

Chapter 2 131


The managed node has an ITO version installed which is no longeravailable on the Management server. An appropriate ITO version cannotbe found which supports the OS version of the Managed node. Solutions:

a. Re-install the appropriate ITO version on the management serverusing ovinstall(1).

b. Update/downgrade the OS of the managed node to an OS versioncurrently supported by ITO.

OpC40-0106 ITO version related directory < x1> not found,even if it is mentioned in correspondingrequirements file.

Internal error. Please report this to your HP Response Center. Therequirements file contains information that is not installed on themanagement server. Remove the corresponding entry from therequirements file/usr/OV/databases/OpC/mgd_node/vendor/<arch>/require.dat.

OpC40-0107 Invalid link-ID < x1> got from Distribution Agent;Note, link-ID range 0 - < x2>.


OpC40-0108 Installed ITO version < x1> on Managed Node<x3> (architecture < x4>) adapted to < x2> to getvendor's actions/cmds/monitor data.

The ITO version installed on the managed node is no longer available onthe management server, but another ITO version also supports the OSversion of the managed node. Therefore the related ITO information willbe used instead. Solution: Update the installed ITO version on thatmanaged node to avoid this warning.

OpC40-0109 Managed Node < x1> (architecture < x2>) stops currentdistribution requestdue to interrupt; therefore packages will be cleaned up.

The distribution agent got an interrupt in the middle of the distributionsequence and exited appropriately (for example, 'Stop ITO Agents'issued). The remaining data will be distributed when re-starting the ITOagents.

132 Chapter 2


OpC40-0110 Too few table entries are available to save data forManaged Node < x1>;new entries have been made in the meantime in theaction/cmd/monitordirectories which have not been counted during thedistribution 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 componentsonce more.

OpC40-0111 Terminated due to signal. Possibly some data has notbeen transmitted to requesting nodes.

The distribution managers stopped due to a receipt signal. If thedistribution manager was currently submitting data to the distributionagents, a corrupted version will be left on the managed nodes. Thedistribution agents will also generate an error message that thedistribution manager has been gone. Solution: After restarting the ITOmanagers, re-distribute the selected components to those managed nodeswhich issued the warning about the distribution agent.

OpC40-0112 Maybe ITO fileset no longer installed on the ManagementServer supporting the architecture of Managed Node < x1>.

The ITO distribution manager is unable to determine the systemrequirements for a managed node. The requirement specification file wasnot found. Check whether the corresponding fileset is still installed.

OpC40-0113 Can't update node status after distribution.

The ITO distribution manager is unable to update the status of themanaged node in the database after a successful distribution. This errormessage is qualified by another message giving more information.

OpC40-0114 Can't add node to IP address mapping table.

The ITO distribution manager is unable to add a newly configuredmanaged node to the IP address mapping table. This error message isqualified by another message giving more information.

OpC40-0115 Invalid limit for parallel distribution requestsspecified: '< x1>'. Valid id < x2> - < x3>. Using < x4> aslimit.

Chapter 2 133



OpC40-0116 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 serverprocess to serve a requesting distribution agent. Check whether theprogram opctss exists in the ITO management server binary, andwhether the program is executable.

OpC40-0117 ITO distribution TCP socket server failed with exit code'< x1>'.

The TCP socket server subprocess made an unexpected exit. Check theopcerror logfile for an corresponding entry reported by the opctssprogram.

OpC40-0118 Can't kill ITO distribution TCP socket server.

The ITO distribution manager is unable to terminate the TCP socketserver after successful configuration distribution to a managed node.This error message is qualified by a system error text (errno). InternalError. Please report this to your HP Response Center.

OpC40-0119 Can't create pipe.

The ITO distribution manager is unable to create a pipe to communicatewith the TCP socket server subprocess. The pipe(2) system call failed.This error message is qualified by a system error text (errno).

OpC40-0120 Waiting for port number to be returned by ITOdistribution TCP socket server timed out.

The ITO distribution manager receives no response from the startedTCP 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 acorresponding entry reported by the opctss program. Please report this toyour HP Response Center.

OpC40-0121 ITO distribution TCP socket server didn't return portnumber.


134 Chapter 2


OpC40-0122 ITO distribution TCP socket server didn't return a validport number: '< x1>'.


OpC40-0123 Internal error: Reading TSS pipe returns 0.


OpC40-0124 Can't write distribution file name to ITO distributionTCP socket server.

The ITO distribution manager is unable to pass data to the TCP socketserver subprocess through a pipe. Probably the TCP socket serveraborted. Check the opcerror logfile for a corresponding entry reported bythe opctss program.

OpC40-0125 Can't terminate ITO distribution TCP socket server.

The ITO distribution manager is unable to terminate the TCP socketserver subprocess. This error message is qualified by another messagegiving more information.

OpC40-0126 Can't start ITO distribution TCP socket server.

The ITO distribution manager is unable to start the TCP socket serversubprocess. This error message is qualified by another message givingmore information.

OpC40-0127 Can't inform ITO distribution TCP socket server aboutnext package.

The ITO distribution manager is unable to pass controlling data to theTCP socket server subprocess. This error message is qualified by anothermessage giving more information.

OpC40-0128 Managed Node < x1> (architecture < x2>) aborts currentdistribution request. Distribution agent could notconnect to ITO distribution TCP socket server.

The ITO distribution agent running on the managed node <mgd_node>aborts a requested configuration distribution. The distribution agentcould not connect the TCP socket server running on the managementserver. Check the opcerror logfile for an corresponding entry reported bythe opctss program. Check the opcerror logfile on the managed node for acorresponding entry reported by the distribution agent.

Chapter 2 135


OpC40-0129 Managed Node < x1> (architecture < x2>) aborts currentdistribution 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 thedistribution manager failed for unknown reason. Check the opcerrorlogfile for a corresponding entry reported by the distribution manager.

OpC40-0130 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 errormessage is qualified by another message giving more information.

OpC40-0131 Rejecting distribution request from an ITO 1.* agent'< x1>'.

The ITO distribution manager received a distribution request from amanaged node running an older ITO version. Due to configuration filesyntax enhancements the old agents will not be able to process the newconfiguration data, But they will continue to work with the oldconfiguration. To distribute new configuration you have to upgrade themanaged node to the latest version using the ITO admin GUI.

OpC40-0132 Can't pass distribution request to ovoareqsdr - notrunning.

The ITO distribution manager could not redirect a distribution request amanaged node running on a cluster client to the cluster server because itcould not send a distribution request to the control manager. Check thelocal error logfile for a reason why the control manager is down andrestart the ITO server processes.

OpC40-0133 Can't pass distribution request to ovoareqsdr - can'twrite queue.

The ITO distribution manager could not redirect a distribution request amanaged node running on a cluster client to the cluster server because itcould not send a distribution request to the control manager. This errormessage is qualified by another message giving more information.

OpC40-0134 Can't open ovoareqsdr queue.

136 Chapter 2


The ITO distribution manager could not connect to the control managerat start-up. Check the local error logfile for a reason why the controlmanager is down and restart the ITO server processes.

OpC40-0135 Can't pass request to ITO communication manager.

The ITO distribution manager could not forward a command to thecommunication manager. This error message is qualified by anothermessage giving more information.

OpC40-0136 Can't execute ITO communication manager '< x1>'. Theexec(2) system call failed.

The ITO distribution manager could not start the communicationmanager. This error message is qualified by another message givingmore information.

OpC40-0137 ITO communication manager failed with exit code '< x1>'.

The ITO communication manager terminated abnormally with the exitcode <ecode>. Check the local error logfile for a reason why thecommunication manager aborted. It will be restarted on demand later.

OpC40-0138 Can't start ITO communication manager.

The ITO distribution manager could not start the communicationmanager. This error message is qualified by another message givingmore information.

OpC40-0139 Can't set heartbeat polling status of managed node'< x1>'.

The reporting process could not modify the heartbeat polling behavior forthe managed node <node>. This error message is qualified by anothermessage giving more information.

OpC40-0140 Invalid agent status command arrived for node '< x1>':<x2>.


OpC40-0141 Agent status command arrived for unknown node'< x1>'(< x2>).

Chapter 2 137


The distribution manager received a request to update the ITO agentstatus 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 thenode is already contained in the node bank the manager processes werenot informed automatically. In this case restart the ITO managerprocesses.

OpC40-0142 Agent '< x1>' requested configuration but authenticationchecks failed. Distributing only node configuration fileif available.

The distribution manager received a distribution request from amanaged node with insufficient security attributes. If available only themanaged node's internal configuration has been distributed to allow theagent to reconfigure and try again. This can happen if this was the firstdistribution request after increasing the node's security level.

OpC40-0201 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 connectthe ITO display manager. Check whether the processes are running, thellbd or rpcd is running and there are no network problems. Restart theITO managers if necessary.

OpC40-0202 Connection to the ITO Management Server lost.Check whether the processes are running.

Check whether the processes are running. A process lost the connectionthe ITO display manager. Check whether the processes are running, thellbd or rpcd is running and there are no network problems. Restart theITO managers if necessary.

OpC40-0203 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.

OpC40-0204 The ITO Action Manager is not running.

The ITO action manager is currently not running but it should. Checkthe error log file to get more information and restart the ITO managerprocesses.

138 Chapter 2


OpC40-0205 The ITO Control Manager is not running.

The ITO control manager is currently not running but it should. Checkthe error log file to get more information and restart the ITO managerprocesses.

OpC40-0206 Get operator information from database failed.

An error occurred during the database access to get information aboutITO operators. More information is contained in another part of the errormessage.

OpC40-0207 Get ITO node configuration from database failed.

An error occurred during the database access to get information aboutthe ITO node configuration. More information is contained in anotherpart of the error message.

OpC40-0208 Get message information from database failed.

An error occurred during the database access to get information about anITO message. More information is contained in another part of the errormessage.

OpC40-0209 Get operator configuration from database failed.

An error occurred during the database access to get information aboutthe ITO operator configuration. More information is contained in anotherpart of the error message.

OpC40-0210 Check operator change flag in database failed.

An error occurred during the database access to check the change flag ofan ITO operator. More information is contained in another part of theerror message.

OpC40-0211 Check realm change flag in nodebank failed.

An error occurred during the database access to check the realm changeflag of an ITO operator. More information is contained in another part ofthe error message.

OpC40-0212 Check desktop change flag in nodebank failed.

Chapter 2 139


An error occurred during the database access to check the desktopchange flag of an ITO operator. More information is contained in anotherpart of the error message.

OpC40-0213 Cannot open queue < x1>.

Can not open an ITO display manager queue. More information iscontained in another part of the error message.

OpC40-0214 Cannot create pipe < x1>. mkfifo(2) failed.

Can not create an ITO display manager pipe. This message is qualifiedby a system error message (errno) giving more information.

OpC40-0215 Cannot open pipe < x1>. open(2) failed.

Can not open an ITO display manager pipe. This message is qualified bya system error message (errno) giving more information.

OpC40-0216 Cannot write to queue < x1>.

Can not write to ITO display manager queue. More information iscontained in another part of the error message.

OpC40-0217 Can't connect to the ITO Management Server processeson node < x1>. Check whether the processes are running.

The reporting process failed to connect to the ITO management serverprocesses. Verify that all processes are running using the opcsv(1m)command. If necessary re-start the server processes by opcsv -start.

OpC40-0218 Display receiver of user < x1> is not reachableand will be logged off.

The display manager has lost the connection to the operator userinterface. The reason was probably an abnormal abort of the UI.

OpC40-0219 License check for node < x1> failed.

The ITO management server processes couldn't satisfy a managed nodelicense request for node <node> due to database problems. This errormessage is qualified by another message giving more information.

OpC40-0220 Number of entries in MCE queue exceeds max_entries;disconnecting < x1>.

140 Chapter 2


A connected ITO message stream interface client associated with theinterface <if> is registered to receive ITO message change events but theaction response queue contains the maximum number of entries. Makesure the application works properly and restart it.

OpC40-0221 MSI client exited without disconnect from interface<x1>.

A connected ITO message stream interface client associated with theinterface <if> terminated without disconnecting properly. Possibly theapplication crashed.

OpC40-0222 Cannot read user domain of registered user condition foruser < x1> of MSI instance < x2>.

A connected ITO message stream interface client associated with theinterface <if> is registered as user <user>. The corresponding conditionscould not be loaded from the database.

OpC40-0223 Number of entries in Application Response queue exceedsmax_entries; disconnecting < x1>.

A connected ITO message stream interface client associated with theinterface <if> is registered to receive ITO action responses but the actionresponse queue contains the maximum number of entries. Make sure theapplication works properly and restart it.

OpC40-0256 <x1> aborted; process did an exit < x2>.

The ITO self monitoring detected that an ITO manager process did anunexpected abort. Check the errorlog file to get more error informationand restart the ITO manager processes.

OpC40-0257 <x1> aborted; process got signal < x2>.

The ITO self monitoring detected that an ITO manager process did anunexpected abort because it got a signal. Check the errorlog file to getmore error information and restart the ITO manager processes.

OpC40-0258 Connect to database failed.

An ITO process is not able to connect to the database. Check whether thedatabase is running. If you have set database environment variables(Oracle: ORACLE_HOME, ORACLE_SID, NLS_LANG), check if they

Chapter 2 141


are correct. If the environment variables are not set, the values in theOpenView database configuration file /etc/opt/OV/share/conf/ovdbconfare used. Check, if they are correct.

OpC40-0259 The database server is probably down; cannot connect;

An ITO process is not able to connect to the database. Check whether thedatabase is running. If you have set database environment variables(Oracle: ORACLE_HOME, ORACLE_SID, NLS_LANG), check if theyare correct. If the environment variables are not set, the values in theOpenView database configuration file /etc/opt/OV/share/conf/ovdbconfare used. Check, if they are correct.

OpC40-0260 Main controlling loop aborted.

The ITO control manager's main loop terminated unexpectedly. Thiserror message is qualified by another message giving more information.

OpC40-0261 Contents of control manager queue is corrupt.

The ITO control manager queue contains corrupt data information. Stopthe ITO manager processes on the management server, delete the controlmanager queue ( /usr/OV/tmp/OpC/mgmt_sv/ctrlq ) and restart the ITOmanager processes.

OpC40-0263 Can't load nodebank.

An error occurred during the access to the database to get informationabout the configured ITO nodes. More information is contained inanother part of the error message.

OpC40-0264 Can't update internal object table.

An error occurred during the update of the heart beat pollingconfiguration. More information is contained in another part of the errormessage.

OpC40-0265 Get database maintenance information failed.

An error occurred during the access to the database to get informationabout the configured ITO database maintenance. More information iscontained in another part of the error message.

OpC40-0266 Download history messages failed.

142 Chapter 2


An error occurred during the download of the history messages. Moreinformation is contained in another part of the error message.

OpC40-0267 Download audit messages failed.

An error occurred during the download of the audit log. Moreinformation is contained in another part of the error message.

OpC40-0268 Check number of messages in the database failed.

An error occurred during the access to the database to check the numberof entries in the message and audit log tables. More information iscontained in another part of the error message.

OpC40-0269 Download of history messages started.

The ITO administrator can schedule the download of history messages toflat files. Every day at the specified time the history messages will bedownloaded.

OpC40-0270 Download of audit messages started.

The ITO administrator can schedule the download of audit entries to flatfiles. Every day at the specified time the audit entries will bedownloaded.

OpC40-0271 Invalid time specified to download history messages;download history messages will not be done.

The database contains an invalid time for download history messages ofthe ITO database maintenance. Check the time on the window in theITO admin GUI and set it to a correct value.

OpC40-0272 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 ITOdatabase maintenance. Check the time on the window in the ITO adminGUI and set it to a correct value.

OpC40-0273 Invalid interval specified to check number of messagesin the database.

The database contains an invalid interval. Check the interval for thenode in the ITO admin GUI and set it to a correct value.

Chapter 2 143


OpC40-0274 History messages downloaded.

The history messages were successfully downloaded to flat files and cannow be archived.

OpC40-0275 Audit messages downloaded.

The audit entries were successfully downloaded to flat files and can nowbe archived.

OpC40-0280 Number of < x1> messages in active-message-table is nearto limit < x2>.

A lot of messages in the active messages table leads to a badperformance. You should acknowledge some no longer needed messages.This error is generated when the number of messages reaches 95% of themaximum value that is set in Actions->Utilities->DatabaseMaintenance.

OpC40-0281 Number of < x1> messages in active-message-table reachedlimit < x2>.

A lot of messages in the active messages table leads to a badperformance. You should acknowledge some no longer needed messages.This error is generated when the number of messages reaches themaximum value that is set in Actions->Utilities->DatabaseMaintenance.

OpC40-0282 Number of < x1> messages in history-message-table is nearto limit < x2>.

A lot of messages in the history messages table consumes a lot of diskspace and leads to a long time when loading the history messagesbrowser. You should download the history messages on a regular basis.The download of history messages can be scheduled in the administratoruser interface from the Actions->Utilities->Database Maintenance...menu.

OpC40-0283 Number of < x1> messages in history-message-table reachedlimit < x2>.

A lot of messages in the history messages table consumes a lot of diskspace and leads to a long time when loading the history messagesbrowser. You should download the history messages on a regular basis.

144 Chapter 2


The download of history messages can be scheduled in the administratoruser interface from the Actions->Utilities->Database Maintenance...menu.

OpC40-0284 Number of < x1> messages in audit-message-table is near tolimit < x2>.

A lot of entries in the audit table consumes a lot of disk space and leadsto a long time when generating an audit report. You should download theaudit entries on a regular basis. The download of audit entries can bescheduled in the administrator user interface from theActions->Utilities->Database Maintenance... menu.

OpC40-0285 Number of < x1> messages in audit-message-table reachedlimit < x2>.

A lot of entries in the audit table consumes a lot of disk space and leadsto a long time when generating an audit report. You should download theaudit entries on a regular basis. The download of audit entries can bescheduled in the administrator user interface from theActions->Utilities->Database Maintenance... menu.

OpC40-0290 Reading name for < x1> from configuration failed.



Can not open the ITO control manager queue. More information iscontained in another part of the error message.

OpC40-0292 Cannot read from control manager queue.

Can not read from the ITO control manager queue. More information iscontained in another part of the error message.


Can not create the ITO control manager pipe. This message is qualifiedby a system error message (errno) giving more information.


Can not open the ITO control manager pipe. This message is qualified bya system error message (errno) giving more information.

Chapter 2 145


OpC40-0307 Can't connect to the DCE rpcd/dced. The daemon doesn'tseem to run.

Cannot start the ITO manager processes on the management server. Nollbd or rpcd is running. Start one of the daemons.

OpC40-0308 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 iscontained in another part of the error message.

OpC40-0331 Can't connect to OpenView daemons. Starting upstandalone.

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. Thecontrolling OV commands like ovstop(1m) and ovstatus(1m) won't workthen. Before re-starting the ITO server processes using these commandsor opcsv(1m) first shut down the running processes using opcctlm -stop.

OpC40-0362 Cannot become primary manager. Please check mgrconf ofthe node.

The ITO control agent received a request to change the primary ITOmanager from an ITO management server not configured as secondaryITO manager. Because only secondary ITO managers are allowed tobecome the primary ITO manager for an ITO agent the request isignored. Solution: Check the configured secondary ITO managers. Thiscan be done by checking the mgrconf and opcinfo file of the ITO agent.

OpC40-0363 ITO Server Initialization Complete. All processesstarted.

This message is written to the logfile, when the control manager hassuccessfully passed all steps to initialize the ITO server processes. Themessage can be used as time-stamp for an ITO server start-up.

OpC40-0364 ITO servers terminated.

This message is written to the logfile, since the control manager finishesan ITO session on the management server. The message can be used astime-stamp for an ITO server shutdown.

146 Chapter 2


OpC40-0369 Internal error: Can't read job from queue. Status: < x1>.


OpC40-0370 Internal error: Can't write job into queue. Status: < x1>.


OpC40-0371 Execution of job failed.

Processing of an internal DB maintenance request (history or auditdownload) or process handling request (like server start and stop) orconfig change request (like informing the managers about changing oradding a node, setting up a notification service etc.) failed. In case of anDB maintenance request, check, if the opchistdwn or opcauddwnprograms exist and have right permissions. In the other cases, restartingthe management server processes manually may help. This errormessage is qualified by another message giving more information.

OpC40-0372 Can't connect to OpenView process manager daemon.

The ITO control manager could not connect to the OpenView processmanager daemon and will start up independently. This will preventcommands like ovstop and ovstatus from operating on ITO processescorrectly.

OpC40-0373 Can't resolve local hostname '< x1>' with name service.Using hostname for authentification.

The primary identity of an ITO management server within DCE containsthe fully qualified hostname of the managed node. The ITO controlmanager failed to resolve the local hostname with the name service andwill use the simple hostname. Possibly the login operation itself will fail.Always make sure that the local hostname can be resolved with thename service on any ITO node.

OpC40-0374 There are < x1> nodes configured with a security levelhigher than < x2>.This requires the control manager to run inauthenticated mode but it is not logged into DCE.

The ITO control manager detected that the current nodebank containssome managed nodes configured for authenticated RPC. The controlmanager failed to determine whether it's own principal is configured atall which indicates whether any DCE security is desired. If

Chapter 2 147


authenticated RPC is desired certain ITO configuration within the DCEsecurity service is required. Use the opc_sec_register.sh utility toconfigure the ITO management server.

OpC40-0404 Message agent on node < x1> is not running.

The self-monitoring detected that the ITO message agent on themanaged node <node> terminated unexpectedly. Check the ITO errorlogfile on that node and re-start the agents using the GUI oropcragt(1m).

OpC40-0405 Control agent on node < x1> isn't running.

The self-monitoring detected that the ITO control agent on the managednode <node> does not run. This can happen if the managed node hasbeen added to the ITO node bank without installing the agent software.Otherwise check the ITO error logfile on that node and re-start theagents using opcagt -start. You cannot access the ITO agent remotely ifthe Control agent is down.

OpC40-0416 Update configuration for monitor loop failed.


OpC40-0424 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. Theagent will download this configuration data after the installation duringthe startup.

OpC40-0433 The llbd/rpcdaemon on node < x1> is down.

The request sender detected that the llbd/rpcd on the target node isdown. Check the llbd/rpcd on the target node and restart it if necessary.

OpC40-0436 Node < x1> is probably down. Even to contact it withping-packages failed.

The request sender was unable to perform the heartbeat monitoring.Check for network problems between the Management Server and thetarget node. Additional causes may be a very short HBP interval, highwork load or a congested network.

148 Chapter 2


OpC40-0437 Heartbeat-monitoring for the following nodes could notbe done in time:<x1>

The request sender could not perform the required heartbeat monitoringas configured for the listed nodes. This can be caused by a very shortHBP interval and high work load causing the request sender to beunable to execute the HBP operation in the configured interval.Configure the HBP interval as small as necessary but as long as possiblefor performance improvement.

OpC40-0462 Control agent on node < x1> is now running.

The request sender detected that the ITO control agent on the targetnode is up again. You can acknowledge all messages reportingcommunication problems related to this node.

OpC40-0463 General Common Agent error. Check agent and serverlogfile for more info.

The ITO control agent returned an error condition when executing thisrequest. Check the Managed Node ITO error log file for related errormessages.

OpC40-0464 Agent authorization error. The ITO Control agent refusedthis request.

The ITO control agent rejected this request. Probably the localManagement server is not configured to be responsible. Verify the opcinfoand mgrconf file on the managed node.

OpC40-0465 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 bulktransfer. Most likely it is related to file access or socket transferproblems. Check the Managed Node as well as the Management ServerITO error log file for related error messages.

OpC40-0489 The request was cancelled before its execution.

A request was not sent to an ITO managed node but cancelled ontheserver instead. For example, this can happen, if the stop_actionbutton was pressed, and the request could be caught on the server.

Chapter 2 149


OpC40-0498 Could not send this request as the agent'< x1>' was not found in the ITO node bank or itdoes 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 canhappen if this node has been added using the GUI but no agent softwarehas been installed from this Management Server. If the managed nodehas agent software installed from another server you can mark this nodeas installed by executing opcsw -i <node>.

OpC40-0499 Could not send this request to node '< x1>' as operationtype is unsupported.


OpC40-0568 execution of notification service < x1> failed

The program or script that you configured for the trouble ticket ornotification service interface could not be started. Please check if the fileexists and has sufficient permissions (need execute permission at leastfor opc_op). If it is a shell-script, you may need to add a line at the topsuch as #!/usr/bin/sh to tell the shell which shell to run the script in.

OpC40-0570 notification service < x1> aborted; it did an exit < x2>

The notification service script has exited with an exit code greater than256. The exact exit code is shown in the error message.

OpC40-0600 Can't add ITO message to the database.

It is not possible to add an ITO message to the database. Moreinformation is contained in another part of the error message.

OpC40-0601 Can't get message groups from the database.

An error occurred during the database access to get information aboutthe configured ITO message groups. More information is contained inanother part of the error message.

OpC40-0602 Can't get regroup conditions from the database.

An error occurred during the database access to get information aboutthe configured ITO regroup conditions. More information is contained inanother part of the error message.

150 Chapter 2


OpC40-0603 Can't convert the regroup conditions into internal form.

An error occurred during the conversion of the regroup conditions fromthe database into an internal form. More information is contained inanother part of the error message.

OpC40-0604 Can't get nodebank configuration from the database.

An error occurred during the database access to get information aboutthe configured ITO nodes. More information is contained in another partof the error message.

OpC40-0605 Can't get trouble ticket configuration from thedatabase.

An error occurred during the database access to get information aboutthe configured ITO trouble ticket interface. More information iscontained in another part of the error message.

OpC40-0606 Can't get notification configuration from the database.

An error occurred during the database access to get information aboutthe ITO notification configuration. More information is contained inanother part of the error message.

OpC40-0607 Can't get node configuration from the database.

An error occurred during the database access to get information about anITO node. More information is contained in another part of the errormessage.

OpC40-0608 Can't add annotation for ITO message to the database.

An error occurred during the database access to add an annotation. Moreinformation is contained in another part of the error message.

OpC40-0609 Can't acknowledge ITO message in the database.

An error occurred during the database access to acknowledge an ITOmessage. More information is contained in another part of the errormessage.


Can not open an ITO message manager queue. More information iscontained in another part of the error message.

Chapter 2 151


OpC40-0614 Cannot read from queue < x1>.

Can not read from an ITO message manager queue. More information iscontained in another part of the error message.


Can not create an ITO message manager pipe. This message is qualifiedby a system error message (errno) giving more information.


Can not open an ITO message manager pipe. This message is qualifiedby a system error message (errno) giving more information.


Can not write to ITO message manager queue. More information iscontained in another part of the error message.

OpC40-0621 MSI client exited without disconnect from interface<x1>.

A client application accessing the MSI terminated without closing theinterface instance. ITO noticed this and has closed the instance.

OpC40-0622 Number of entries in MSI queue exceeds max_entries;disconnecting < x1>.

The maximum number of entries allowed for the MSI queue (specified inthe max_entries parameter in opcif_open()) was exceeded. Theapplication that is connected to the Message Stream Interface still canread messages until the queue is empty; it then needs to close (andmaybe reopen, if desired) the MSI.

OpC40-0630 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 notaccessible correctly. It will be continued, as if there is no template at all.Messages will not be forwarded.

OpC40-0631 Problems detected while reading the message forwardingtemplate.

152 Chapter 2


This error occurs, when the message forwarding template stored at/etc/opt/OV/share/conf/OpC/mgmt_sv/respmgrs/msgforw contains syntaxerrors. It will be continued, as if there is no template at all. Messageswill not be forwarded. You can use the check-tool opcmomchk to verifythe template in advance.

OpC40-0632 Could not convert data from the message forwardingtemplate (msgforw) into an internal format.

An internal error occurred, when converting the message forwardingdata.

OpC40-0633 The target manager < x1> for message forwardingis not in the nodebank. Trying to continue withdefault values for security- and communicationprotocols.

All ITO management servers, that get in contact with each other, shouldknow the opposite's security level and communication type. Otherwise,default values will be taken (security=off, comm.type=DCE), that maynot fit. Therefore you should add the target manager to the nodebank ofthe source manager, as well as the source manager to the targetmanager's nodebank, and setup the communication parameters.

OpC40-0634 Could not get needed message attributes from thedatabase.

Problem, when contacting the database. Concerned database-tables arethe active- or history_messages.

OpC40-0635 Could not set message attribute (< x1>) in the database.

Problem, when contacting the database. Concerned database-tables arethe active- or history_messages.

OpC40-0636 Could not convert distribution lists used for messageforwarding.

Internal error; either there is not enough memory or the distribution listwas damaged during transfer or processing.

OpC40-0637 Could not store distribution lists for messageforwarding in the database.

Chapter 2 153


Problem when contacting the database. Concerned database-tables arethe active- or history_messages and the forw_msg_table.

OpC40-0638 Could not read distribution list for message forwardingfrom the database.

Problem, when contacting the database. Concerned database-table is theforw_msg_table.

OpC40-0639 Line < x1> of msi conf file < x2> was skipped due to syntaxerrors or order number out of range.

Check the msi conf file for syntax errors or out-of-range order numbers.

OpC40-0651 Didn't start < x1> < x2>on node < x3>.The ITO management server processes have been restartedsince thisrequest was entered (For more information see onlinehelp, error 40-651).

An action request was not executed, cause the ITO server was restartedsince the request was entered. you can change this behaviour by addingthe line OPC_EXEC_ACTIONS_AT_STARTUP TRUE to the opcsvinfofile. For more granularity you can additionally add the lineOPC_MAX_AGE_OF_ACTIONS_AT_STARTUP <age_in_seconds> toopcsvinfo. The server processes must be restarted to activate thechanges.

OpC40-0670 Can't find MSI instance '< x1>'.

Reconnect to an MSI instance is not possible. The ITO server processeswere successfully started but the applications using the MSI mustreconnect to the server. ITO can reconnect to MSI instances when theinstance process was not stopped when the server processes werestopped. Was the MSI instance process also stopped the MSI instancewill be removed from the database.

OpC40-0671 Can't find MSI registration condition.

This error can be safely ignored. If it occurs frequently, report it to yourHP Response Center.

154 Chapter 2


OpC40-0674 A message arrived from node '< x1>'.The required security level is '< x2>' but the agent islogged on as '< x3>' and has set security level '< x4>'.No more authentication failures will be reported forthis node.

The ITO management server received the previous message from amanaged node with insufficient security attributes. This message will beprocessed normally but automatic and operator-initiated actions havebeen set to FAILED if configured. Check the managed node's error logfilefor additional information. Verify the DCE security related configurationon the management server and managed node using theopc_sec_verify.sh utility.

OpC40-0675 Can't start < x1> < x2> on node < x3>.The message failed authentication checks - this messagehas possibly been sent by an untrusted source.

The action bound to this message has been disabled because the messagefailed authentication checks. This message will be processed normallybut automatic and operator-initiated actions have been set to FAILED ifconfigured. Check the managed node's error logfile for additionalinformation. Verify the DCE security related configuration on themanagement server and managed node using the opc_sec_verify.shutility.

OpC40-0676 Discarded < x1> < x2> for node < x3>The message failed authentication checks - this messagehas possibly been sent by an untrusted source.Nevertheless it is possible to start thisoperator-initiated action.

The operator-initiated action bound to this message has been set toFAILED because the message failed authentication checks. If desired theaction can be started again - this annotation is intended to notify youabout possible security problems. Check the managed node's error logfilefor additional information. Verify the DCE security related configurationon the management server and managed node using theopc_sec_verify.sh utility.

OpC40-0700 Initializing configuration failed.


Chapter 2 155


OpC40-0701 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 withan incorrect parameter list. Correct is: opcragt -help or opcragt [ -start |-stop | -update ] [ -all | <nodelist> ] where the first alternative specifiesthe command to be executed remotely. No command option returns thestatus on the managed node. The second alternative is either a list ofmanaged nodes, or -all for all ITO configured nodes. For moreinformation, see the opcragt(1) man page.

OpC40-0702 Can't connect to ITO control agent.

The opcragt command is unable to connect the ITO control agentrunning on a managed node displayed previously. This error message isqualified by another message giving more information.

OpC40-0703 Can't start ITO services.

The opcragt command is unable to execute the 'start' option on themanaged node. This error message is qualified by another messagegiving more information.

OpC40-0704 Can't stop ITO services.

The opcragt command is unable to execute the 'stop' option on themanaged node. This error message is qualified by another messagegiving more information.

OpC40-0705 Can't reconfigure ITO services.

The opcragt command is unable to execute the 'update' option on themanaged node. This error message is qualified by another messagegiving more information.

OpC40-0706 Can't get local IP address.

156 Chapter 2


The opcragt command is unable to obtain the local IP address. This errormessage is qualified by another message giving more information.

OpC40-0707 Command failed.

The opcragt command is unable to execute the requested operation. Thiserror message is qualified by another message giving more information.

OpC40-0708 The gethostbyname(3N) call failed.

The opcragt command is unable to resolve a passed node name to an IPaddress. The node name is displayed previously. Check whether the nodename is correct.

OpC40-0709 This node is not accessible via IP network.

The opcragt command is unable to execute a requested operation on thespecified managed node because it is configured in ITO with anothernetwork type than IP. Check the configuration of that node in ITO usingthe administrator's GUI.

OpC40-0710 Retrieving list of configured nodes failed.

The opcragt command is unable to obtain the set of configured managednode from the database. This error message is qualified by anothermessage giving more information.

OpC40-0711 Command not allowed. Node is neither controlled normonitored.

The opcragt command is unable to execute a requested operation on thespecified managed node because it is not configured in ITO as 'controlled'or 'monitored'. Check the configuration of that node in ITO using theadministrator's GUI.

OpC40-0712 Node < x1>:This node is not contained in the domain.

The opcragt command is unable to execute a requested operation on thespecified managed node, because it is not configured in ITO at all. Checkthe managed node configuration in ITO using the administrator's GUI.

OpC40-0714 You must be root to use this command.

The opcragt command may be used by a user with the effective user id 0only.

Chapter 2 157


OpC40-0715 Invalid IP address specification: < x1>.

A managed node specification passed as IP address is invalid. Theaddress is displayed previously. Valid is an IP address in the format#n.n.n.n where n is a numeric value.

OpC40-0716 Can't display ITO status.

The opcragt command is unable to display current status of the managednode. This error message is qualified by another message giving moreinformation.

OpC40-0717 Can't get list of all configured ITO node groups from thedatabase.

It was not possible to get required ITO information from the database.This error message is qualified by another message giving moreinformation.

OpC40-0718 <x1> used as node group name with the option -nodegrpis not configured within ITO as ITO node group.

The used node group name is not configured in ITO. Solution: Checkwhether you used the correct name.

OpC40-0719 Can't get the ITO management server name from thedatabase.

It was not possible to get required ITO information from the database.This error message is qualified by another message giving moreinformation.

OpC40-0720 Can't get IP addresses for the ITO management server<x1>.

It was not possible to convert the name of the management server to anIP address. Solution: Check the name of the management server systemto be correct and verify whether this name can be resolved to an IPaddress on the managed node.

OpC40-0721 The managed node requires authenticated RPC but theopcragt command is not logged into DCE.

158 Chapter 2


If there was no previous error message about a failed login operationeither the DCE security service was unavailable or the DCE principalused by the management server is not configured at all. Refer to theinstallation manual for more information about required DCE setup.

OpC40-0722 No node left for processing.

The job could not be done for any node because the specified nodes ornode groups were invalid. The command exited with exit code 1. If not allspecified nodes or node groups are invalid, only a warning will be writtento stderr for each invalid node or node group but the program stillcontinues with the other nodes and exits with 0.

OpC40-0723 The command is not supported by the agent platform or theagent type of this node.

The opcragt command is unable to execute a requested operation on thespecified managed node because the requested operation is notsupported on this node platform.

OpC40-0780 New ITO manager configuration download todirectory < x1>.

A new ITO manager configuration was distributed to your ManagementServer. It resides normally in /usr/OV/tmp/OpC_appl/cfgdwn on HP-UX9.x nodes or in /var/opt/OV/share/tmp/OpC_appl/cfgdwn on HP-UX 10.xnodes. You should use 'opccfgupld' to upload the new configuration.

OpC40-0782 Target server node '< x1>' is not configured in thelocal ITO database. You must configure othermanagement servers as regular nodes in the ITO nodebank.

To distribute configuration to another Management Server you mustconfigure the target node as regular node in ITO. Use the 'Node Add'functionality of the Administrator's GUI to perform this task.

OpC40-0783 Cannot read target of symbolic link '< x1>'.

The command cannot get information of a symbolic link. Check, that thesymbolic link exists and that the directory of the symbolic link and theparent directories have sufficient permissions.

OpC40-0784 Cannot send symbolic link '< x1>' to target manager.

Chapter 2 159


An error occured, when sending a symbolic link to another manager.Check, if the communication was broken or if the opccmm process on thetarget node aborted. If the target manager cannot receive symbolic links,use the

• no_symlink option. If the communication was

broken, send the data again.

OpC40-0785 Received invalid data for creating a symbolic link:'< x1>'

A symbolic link was sent, but the received data is invalid. Check, if thecommunication was broken and send the data again.

OpC40-0786 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 checkfor operating system errors. Probably the permissions of one of theparent directories are insufficient.


Can not open the ITO display receiver. More information is contained inanother part of the error message.


Can not create the ITO display receiver pipe. This message is qualifiedby a system error message (errno) giving more information.


Can not open the ITO display receiver pipe. This message is qualified bya system error message (errno) giving more information.


Can not write to the ITO display receiver queue. More information iscontained in another part of the error message.

OpC40-0854 Cannot start ITO display receiver. fork(2) failed.

Start of the ITO display receiver failed. This message is qualified by asystem error message (errno) giving more information.

160 Chapter 2


OpC40-0855 Cannot start ITO display receiver. exec(2) failed.


OpC40-0856 Did not get necessary information from display receiver.


OpC40-0900 Cannot start the tss server.

The 'opctss' process is unable to create a server connection. This messageis qualified by a system error message (errno) containing the cause of theerror.

OpC40-0901 Error during transfer of package file < x1>.

An error during the data transfer to the managed node occurred. Thismessage is qualified by a system error message (errno) containing thecause of the error.

OpC40-0902 Cannot write to socket.

The 'opctss' process is unable to write to a socket. This message isqualified by a system error message (errno) containing the cause of theerror.

OpC40-0903 Cannot write socket number.

The 'opctss' process can not deliver its socket number to the distributionmanager. This message is qualified by a system error message (errno)containing the cause of the error.

OpC40-0904 Cannot get filename.

The 'opctss' process is unable to read a temporary filename from thedistribution manager. This message is qualified by a system errormessage (errno) containing the cause of the error. This error may becaused by the termination of the distribution manager during adistribution or if an abnormally terminated distribution left the currentinstance of the TSS process.

OpC40-0905 Init of config file failed.

Chapter 2 161


The 'opctss' process is unable to open the opcinfo file. This message isqualified by a system error message (errno) containing the cause of theerror.

OpC40-0906 Pipe to opcdistm is broken.

The pipe between the distribution manager and the 'opctss' process isbroken. This message is qualified by a system error message (errno)containing the cause of the error.

OpC40-0907 Cannot unlink file < x1>. Continuing with processing.

The 'opctss' process is unable to remove a temporary file This message isqualified by a system error message (errno) containing the cause of theerror.

OpC40-0950 Communication manager can't accept connection on TCPsocket.

The ITO communication manager could not start as TCP socket server.The accept(2) system call failed.

OpC40-0951 Communication manager can't open output file '< x1>'.

The ITO communication manager could not open the requested outputfile <file> to write data into. This message is qualified by a system errormessage (errno) containing the cause of the error.

OpC40-0952 Communication manager can't receive data on TCP socket.

The ITO communication manager failed to receive data from a remotemanagement server. This error message is qualified by another messagegiving more information.

OpC40-0953 Communication manager can't write output file '< x1>'.

The ITO communication manager could not write the requested outputfile <file> to write data into. This message is qualified by a system errormessage (errno) containing the cause of the error.

OpC40-0954 Internal error: Invalid command parameters.


OpC40-0955 Internal error: Invalid connection ID.

162 Chapter 2



OpC40-0956 Internal error: Invalid command.


OpC40-0957 Can't initialize as TCP server.

The ITO communication manager could not initialize as TCP socketserver. This error message is qualified by another message giving moreinformation.

OpC40-0958 Lost connection to ITO distribution manager.

The ITO communication manager lost the connection to the distributionmanager. Probably the distribution manager terminated. Check theerror log file to get more information and restart the ITO managerprocesses.

OpC40-0959 Communication manager can't send data via TCP socket.

OBSOLETE.

OpC40-1111 Cannot write NNM license file to save licenseinformation.The file '< x1>' is not writable.

The managed node to operate on is configured in ITO to use a highersecurity level than SEC_NONE. This requires the calling RPC client tobe logged into DCE. This login operation failed. This error message isqualified by another message giving more information.

OpC40-1200 No distribution manager registered on management servernode.

The ITO distribution manager is not registered on the local managementserver system. This will prevent the ITO DCE agent manager fromforwarding distribution requests. Check the error log file to get moreinformation and restart the ITO manager processes.

OpC40-1201 No distribution manager running on management servernode.

Chapter 2 163


The ITO distribution manager is registered on the local managementserver system but not responding. This will prevent the ITO DCE agentmanager from forwarding distribution requests. Check whether the ITOmanager processes are running. If not examine the error log file to getmore information and restart the ITO manager processes.

OpC40-1202 Can't connect to distribution manager - can't reachrpcd/llbd.

The ITO DCE agent manager could not connect the ITO distributionmanager on the local management server system because it could notreach the llbd/rpcd. This will prevent the ITO DCE agent manager fromforwarding distribution requests. Check whether the llbd/rpcd and theITO manager processes are running. If not restart the llbd/rpcd, examinethe error log file to get more information and restart the ITO managerprocesses.

OpC40-1203 Can't connect to distribution manager.

The ITO DCE agent manager could not connect the distributionmanager. This error message is qualified by another message givingmore information.

OpC40-1204 Can't forward RPC call.

The ITO DCE agent manager could not forward an RPC call to either theITO distribution manager on the local management server system or to acontrol agent on a managed node. This error message is qualified byanother message giving more information.

OpC40-1205 Unsupported RPC call.


OpC40-1206 Can't retrieve value from config subsystem for number ofserver threads.Using default value.


OpC40-1207 Invalid number of server threads specified: < x1>. Usingdefault value < x2>.

164 Chapter 2


The configured number <num> of RPC threads to be started by the ITODCE agent manager is out of range. Valid is 1 - <maxnum>. The processwill use <maxnum> as default. Fix this value in your opcinfo file.

OpC40-1252 Can't obtain name of current DCE user. You must be loggedinto DCE when running this command.

The installation of a password into the DCE registry requires a validlogin context as a privileged user. You need to log into DCE beforerunning the opcpwd command.

OpC40-1300 Could not read configuration data.

Internal error

OpC40-1301 Could not initialize internal data structures (< x1>).

Internal error or no more memory available.

OpC40-1302 Could not set registration condition to catchmessage-change events.

Internal error or no more memory available.

OpC40-1303 Could not open message-stream interface < x1>.

The ITO forward manager cannot open a link to the ITO displaymanager via message-stream interface to get message-change events.Error causes may be a failed file operation or insufficient memory.

OpC40-1304 The ITO message reciever on the target manager(< x1>) is registered at the location broker, butit's not reachable.

The ITO message receiver (opcmsgr) on the target manager is registeredin the location broker (rpcd/dced),of the target system but it's notrunning. This can happen, when the message receiver terminatedabnormally; it has no time to unregister itself. Cleanup the locationbroker with the control program rpccp or by restarting the ITO serviceson the target system.

OpC40-1305 The ITO message receiver on the target manager(< x1>) isn't running. Probably, ITO isn't up on thetarget system.

Chapter 2 165


The ITO message receiver on the target manager is not running.Probably, ITO does not run there.

OpC40-1306 Could not connect to target manager < x1>.

Could not connect to ITO target manager. Either the node is not runningor there are network problems or the location broker on the node is notrunning.

OpC40-1307 Could not forward data to ITO management server onsystem < x1>.

Summary-message; cannot forward any data to target manager.

OpC40-1308 Could not register to catch message change events.

It was not possible to forward an registration condition to the ITOdisplay manager; error causes may be a failed file operation orinsufficient memory.

OpC40-1309 Read invalid data from communication queue.

Read invalid data from communication queue. The data is not in theexpected format; maybe it was damaged during transport or processing.It's very likely an internal error.

OpC40-1310 Could not generate distribution list for messageforwarding.

Internal error or insufficient memory.

OpC40-1311 Could not read data from communication queue.

Could not read data from communication queue. Error causes are afailed file operation or insufficient memory.

OpC40-1313 Can't authenticate with DCE security service.Management server: '< x1>'.Manager name: '< x2>';own name: '< x3>'.Sending data unauthenticated.

166 Chapter 2


The ITO Forward Manager failed to initialize an authenticated RPCconnection to the Management Server <mgmt sv>. This error message isqualified by another message giving more information. The forwardmanager will send further data unauthenticated and try to recover anauthenticated connection later.

OpC40-1314 Authentication failure during RPC to message receiver on'< x1>': < x2>.Retrying unauthenticated ...

The ITO Forward Manager failed to send an ITO message viaauthenticated RPC. This can happen if the target ITO Message Receiverdoes not run authenticated but the sending Forward Manager does. TheForward Manager will send further data unauthenticated and try torecover an authenticated connection later. Possibly the ManagementServer failed to initialize properly or the Management Server has beenunconfigured in the DCE security service. Verify the ITO ManagementServer error logfile for security related error messages.

OpC40-1400 The Mid-Level-Manager is running on the node.

The RPC-server of the Mid-Level-Manager is running and is ready toreceive RPC-calls.

OpC40-1401 The Mid-Level-Manager isn't running.

The RPC-server of the Mid-Level-Manager is not running, or theRPC-connection is not possible because of an RPC-error.

OpC40-1402 The Mid-Level-Manager specified for this node could notbe found.

The node is configured to be managed via a Mid-Level-Manager, but theMid-Level-Manager specified for this node could not be found in the NodeBank. Agent type and Mid-Level-Manager can be specified in the[Actions:Node:Modify] window.

OpC40-1403 The request is not supported by the agent platform or theagent type of this node.

Some request are not supported on specific platforms or they are notsupported on a specific Agent Type. Agent type and Mid-Level-Managercan be specified in the [Actions:Node:Modify] window.

OpC40-1404 The Mid-Level-Manager isn't running on node < x1>.

Chapter 2 167


The RPC-server of the Mid-Level-Manager is not running, or theRPC-connection is not possible because of an RPC-error.

OpC40-1405 The Mid-Level-Manager on node < x1> is registered at thellbdor rpcdaemon but it is not running.

Restart the RPC-server of the Mid-Level-Manager.

OpC40-1406 The Message Forwarding component of theMid-Level-Manager on node < x1> is not running.

The Message Forwarding component of the Mid-Level-Manager is notrunning. You cannot receive any messages from the Mid-Level-Manageror any of its managed nodes while this component is not running.

OpC40-1407 The Mid-Level-Manager on node < x1> is now running.

The request sender detected that the Mid-Level-Manager on the targetnode is up again.

OpC40-1408 The Message Agent on node < x1> is now running.

The request sender detected that the Message Agent on the target nodeis up again.

OpC40-1409 The Message Forwarding component of theMid-Level-Manager on node < x1>is now running.

The request sender detected that the Message Forwarding component ofthe Mid-Level-Manager on the target node is up again.

OpC40-1500 opcwall failed. Cannot inform users.

The command opcwall failed. See previous errors for the reason.

OpC40-1502 Cannot connect to database.

The program could not connect to the database. See the server errorlogfile for more details.

OpC40-1503 Cannot connect to display manger.

168 Chapter 2


The program could not connect to the ITO display manager. Probably theITO server processes are not running and no users need to be informed.See the server error logfile for more details.

OpC40-1504 Cannot do an API connect. opc_connect() failed witherror < x1>.

The program could not connect to the ITO API. See the server errorlogfile for more details.

OpC40-1505 The API function < x1> failed with error < x2>.

The specified API function failed. See the server error logfile for moredetails.

OpC40-1551 Cannot assign hierarchy of user < x1> to user < x2>.

Hierarchy of the source user could not be assigned to the target user. Seeprevious error messages for the reason.

OpC40-1553 Could not read password.

The program could not read the password because getpass() failed.

Chapter 2 169

ITO Error MessagesError messages of DB access

Error messages of DB access

OpC50-0001 Database inconsistency detected (< x1>).The entries in the two tables belong together. Butactually there is only an entry in one table.

The corresponding information is placed in more than one databasetable. But there is only an entry in one table. This error can occur if theadministrator has changed an operator configuration but the operator isstill logged in, or if the database installation was not successful. Deletethe affected object or rerun the database initialization program, usingthe clear option (all data in the database will be deleted!).

OpC50-0002 Could not connect to database < x1>.Please look if the database processes are running.

The application cannot connect to the database. This may have severalreasons: 1. The database environment variables are not set correctly. Ifyou have set database environment variables (Oracle: ORACLE_HOME,ORACLE_SID, NLS_LANG), check if they are correct. If theenvironment variables are not set, the values in the OpenView databaseconfiguration file /etc/opt/OV/share/conf/ovdbconf are used. Check, if thevalues in this file are still correct. 2. The database is not running.Restart it as described in the Administrator's Reference Guide. 3. Youhave resource problems. Check, if the number of open files or theavailable swap space is near the maximum and reconfigure it if needed.

OpC50-0003 No according data found in the database.

There is no corresponding data available in the database. This may notbe an error. It may be you have not yet set up the object. Other reasonsfor this message may be: The administrator has deleted an object, but anoperator who has this object is still logged in. When the operator exitsand again logs in, the error no longer occurs, as the operator now has thenew configuration. Another possible reason, is that the databaseinstallation was not successful. Re-running the database initializationprogram with the clear option (does delete all data from the databasetables!) solves this problem.

OpC50-0004 Login failed.

170 Chapter 2


In order to logon to the ITO application, user name and password mustbe entered. The entered user name is not yet configured or the enteredpassword is incorrect. Your ITO administrator defines the user name,along with the password, to give you access to your capabilities withinITO.

OpC50-0006 Invalid browser identifier received.


OpC50-0007 Invalid annotation identifier received.


OpC50-0008 Invalid application identifier received.


OpC50-0009 Invalid instruction identifier received.

The instruction to a message is no longer available. This occurs if youdelete the message condition that matched the message.

OpC50-0010 Invalid message identifier < x1> received.This error occurs if a old message is not in the databaseor a new message is already in the database.

This may not be a error. The message can have two reasons. Either theresponse of an automatic action has arrived before the message itself, ora message is no longer in the active- or history-table, and is referenced.

OpC50-0011 Invalid node identifier < x1> received.

ITO identifies nodes internally by node IDs. There exists no entry for thisnode 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 theinstructions to the error 50-91 for more information.

OpC50-0012 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 stilllogged-in was removed by the administrator from the user bank.

OpC50-0013 Invalid session identifier received. A UI process mighthave died.

Chapter 2 171


Each operator has a session identifier for the current session. Thesession identifier is not (or no longer) valid. Probably an operator who isstill logged in was removed by the administrator from the user bank. Ifthis error message appears in the admin GUI, it is very likely that theadmin's user interface process has been terminated unexpectedly. Exitthe program via the OpenView Exit menu and restart ITO.

OpC50-0014 Invalid view filter received.

The filters for the view browser or the filters for the history browser arenot valid.

OpC50-0015 Database: < x1>

This message contains the message text which was returned by thedatabase system. The message following this message will tell if thismessage is an informative message or if a real problem occurred. Apossible database message is:

'Database: ORA-00054: resource busy and acquire with NOWAITspecified' for an Oracle RDBMS: Another process has taken a lock on adatabase table. As several users and processes work on the database atthe same time this may occur sometimes. ITO will try to repeat thetransaction several times. This is indicated by the ITO message 'Retry.'.In this case the timeout has no influence on the system. Only if severalretries were without success, the database transaction will be aborted. Inthis cases another error message will follow the generic databasemessage and will tell which transaction was not successful.

A possible reason for this problem is a user who accesses the ITO tableswith a interactive database query tool. This user should commit histransactions or exit the query tool. Repeating the action now will work.

For more details about the generic database messages, ask your databaseadministrator.

OpC50-0016 The user is already logging into the system.

Previously somebody logged in but did not complete the user interfacestartup. This error is only for information. The login process willcontinue.

OpC50-0017 The user is already logged on.

172 Chapter 2


This message is caused because someone is already logged on as thesame user. ITO allows only one logged user for a single user name. If thismessage appears but the login is still successful, you can ignore thiserror. This means that an user interface session was not properly endedbut ITO detected this and thus allowed the new login. If nobody is loggedin for the affected user name and you are not able to log in, pleasecontact your HP Response Center.

OpC50-0018 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 databasequery tool. This user should commit his transactions or exit the querytool. Repeating the action now will work.

OpC50-0019 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 databasequery tool. This user should commit his transactions or exit the querytool. Repeating the action now will work.

OpC50-0020 Error in access to file (< x1>).

Check that the file exists and that it has the right permissions. Theadministrator user interface generally runs as user root, the operatoruser interface runs as user opc_op.

OpC50-0021 Error during delete of file (< x1>).

Check that the file exists and that the directory where the file resideshas write permissions. The administrator user interface generally runsas user root, the operator user interface as user opc_op.

OpC50-0022 Invalid node name received (< x1>).

An external node was used for an operation where only normal nodes(real nodes) are allowed.

OpC50-0025 Duplicate object detected (< x1>).

There are two entries with the same Key in the database in the specifiedtable. This may occur if you run the database initialization program asecond time without the clear option. It may also occur after you issue acopydb without previously clearing the database tables. You should

Chapter 2 173


delete the non-unique object with an interactive database query tool orre-run the database initialization program with the clear option (all datain the database will be deleted!).

OpC50-0027 Node is not managed.

The node is not in the nodebank.

OpC50-0028 Invalid symbol type identifier received.


OpC50-0029 Invalid node name or IP address received.

A node with this IP address or hostname is not in the database. If thenode 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 nameservice. Hidden IP addresses may be added to the opc.hosts file.

OpC50-0030 Can't convert node name to IP address (< x1>).

The IP-Address of the node can not be determined. Check if the nameservice is running.

OpC50-0031 Duplicate node name detected (< x1>).

Two different nodes have the same node name. The message contains theaffected node IDs of the two nodes. opcdbidx(1m) can fix some of thisproblems. If opcdbidx fails to correct the problem, please report this toyour HP Response Center.

OpC50-0032 Invalid nodegroup identifier received.

The internal used nodegroup ID for the node group does not exist. If yourecently did an opccfgupld, restart the user interface and the ITO serverprocesses to re-read the configuration from the database. If the error stilloccurs, please report this to your HP Response Center.

OpC50-0033 Invalid password.The password may not contain control characters.

The specified password contains unallowed characters or the password istoo long. Unallowed characters are control characters and spacecharacters.

OpC50-0034 Invalid condition ID.

174 Chapter 2



OpC50-0035 Invalid application type.


OpC50-0036 Invalid application group id received.


OpC50-0037 Invalid distribution status received.


OpC50-0039 Invalid desktop type.


OpC50-0040 Node not processed (< x1>).

A node of a list of nodes can not be processed. The other nodes areprocessed normal. Check the previous error messages for the reason.

OpC50-0041 Invalid tree fork type (operator desktop) received.


OpC50-0042 Error in read-access to file (< x1>).

Check that the file exists, and that it has read permissions. Check alsothat the directory where the file resides has read permissions. Theadministrator user interface generally runs as user root, the operatoruser interface, as user opc_op.

OpC50-0043 Invalid crypted password received.

The password has errors in crypt. Please change the password for theaffected application or operator. If this does not work or theadministrator password is the problem password, please report this toyour HP Response Center.

OpC50-0045 Invalid password.

If this error occurs for the database connection, there is currently nopassword set or it is empty. You can set the database password withopcdbpwd. If this error occurs when changing the own password of anuser, the old password is not correct.

Chapter 2 175


OpC50-0046 Error while reading report file: < x1>.

Check that the file exists, and that it has read permissions. Check alsothat the directory where the file resides has read permissions. Theadministrator user interface generally runs as user root, the operatoruser interface as user opc_op.

OpC50-0047 Error while reading report file or file is empty.

Check that the file exists, and that it has read permissions. Check alsothat the directory where the file resides has read permissions. Theadministrator user interface generally runs as user root, the operatoruser interface as user opc_op.

OpC50-0048 Node name (< x1>) is not valid for IP address (< x2>).

The node can not be resolved correctly. Check that the name service isrunning.

OpC50-0049 Can not get correct node name (invalid: < x1>) for IPaddress (< x2>).Please check node (< x3>).

The node is already in the database but with different values and thecorrect values can not be resolved. Check that the name service isrunning correctly.

OpC50-0050 There are two identical nodes (< x1>, < x2>) for thesame IP address (< x3>) configured in the nodebank.Please remove one of the nodes.

The name service returns the same IP-Address for both nodes. ITOhowever requires that the IP-Address must be unique in the database.Check that the name service is running correctly, and try the actionagain. If this does not work, delete one of the two entries manually.

OpC50-0051 The node < x1> is member of the ITO Nodebank.

You tried to add a node to the nodebank that is already in the node bankor you wanted to modify the node address of a node to the values ofanother node that is already in the node bank. Check the valuesreturned by the name service and modify the existing node if necessary.

OpC50-0052 Can't convert IP address to node name (< x1>).

176 Chapter 2


The node name of the node can not be determined. Check that the nameservice is running.

OpC50-0053 A timeout occurred during database access.Please try again later.

Another process has taken a lock on a database table. Several attemptsto repeat this transaction were without success. The transaction can notbe made. A possible reason for this error is a user who accesses the ITOtables with an interactive database query tool. This user should commithis transactions or exit the query tool. Repeating the action now willwork.

OpC50-0054 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 anode can be kept. It may also be that the node is not set up correctly inthe name service. Check the node.

OpC50-0055 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 nodewhich itself has a wrong IP-Address and so on. This might end in a loopand can not be handled. Try to modify the nodes from the end of thischain.

OpC50-0056 Management server configuration is missing in database(table opc_mgmtsv_config).

Configuration data for the management server system is missing in thedatabase. Probably the database initialization did not work correctly.The reason for this could be that the node address of the managementserver system can not be resolved. Please check that the name service isrunning correctly and re-run the database initialization program withthe clear option (this will clear all your data in the database!) or re-runthe database upgrade program.

OpC50-0057 Can't get name of Management Server, please check with'hostname'.

Chapter 2 177


The system call, gethostname, which delivers the name of the actualsystem, failed. Check that the networking is set up correctly.

OpC50-0058 Can't get node entry of Management Server (< x1>), pleasecheck the node bank.

The node address of the management server system can not be resolvedcorrectly. Check that the name service is running correctly, and re-runthe database initialization program, using the clear option (this willdelete all your data in the database!) or re-run the database upgradeprogram.

OpC50-0059 Invalid node pattern type received.


OpC50-0060 Can not call the compress program for file < x1> becausenumber of processes reached system limit.

Please either stop some processes or increase the kernel parameter forthe maximum number of processes per user (maxuprc) and themaximum number of processes on the system (nproc). Refer to theprerequisites in the installation manual for appropriate values.

OpC50-0061 Can not call the compress program for file < x1> becausephysical or reserved swap memory reached system limit.

Please either stop some processes or increase the swap space on thesystem. Refer to the prerequisites in the installation manual forappropriate values.

OpC50-0062 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.

OpC50-0063 Error while calling or executing the compress programfor file < x1>.

During the distribution of templates, a file could not be compressedbecause the exec call to compress failed. Check, if the compress commandexists and has execute permissions.

178 Chapter 2


OpC50-0065 Connection to database server processes lost.Please restart the database server processes if they arenot running.

Please check if the database server processes are running correct. For anOracle 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 andora_s000_openview. If you use another ORACLE_SID, the processes willhave a different end. Restart the database server processes if theprocesses are not running correct. If you use SQL*Net, this error mightalso be caused by network problems. For SQL*Net, the tnslsnr processmust also run on the database server.

OpC50-0066 File error (< x1>): < x2>.

An error occurred when trying to create a file. The file name is inbrackets, the reason for the error is behind the colon. Check, if thedirectory exists and has right permissions.

OpC50-0068 Wrong parent ID for nodebank group < x1>.Please use modify nodebank group to assign anotherparent to the nodebank group.

The parent nodebank group of the nodebank group is invalid. Pleaseassign the nodebank group to another parent nodebank group.

OpC50-0069 Wrong parent ID for node < x1>. Please use modify node toassign anotherparent to the node.

The nodebank group of the node is invalid. Please assign the node toanother parent nodebank group.

OpC50-0070 Nonexisting MSI ID (< x1>) received.

A process which is registered at the message processing interface uses awrong ID. The IDs are registered when connecting to the MessageStream Interface.

OpC50-0071 Platform family < x1> already exists with differentvalues.

Chapter 2 179


The referenced platform family already exists with different values. Aplatform family is specified in the agent platform file. Edit the agentplatform file of the currently loaded platform to fit to the other platforms.

OpC50-0072 Platform family name may not be empty.

A platform family is specified in the agent platform file. The name of theplatform family may not be empty. Edit the agent platform file of thecurrently loaded platform to fit to the other platforms.

OpC50-0073 Cannot delete platform. Node for this platform stillexist.

A agent platform may not be deleted from the database as long as nodesof this platform are in the nodebank. Delete the affected nodes from thedatabase or set the platform of the nodes to the correct value beforeremoving the platform.

OpC50-0074 Platform family < x1> does not exist. Platformfamily must be added before platform of this platformfamily can be added.

The platform family does not exist. Platform family must be added beforea platform of this platform family can be added. Please first load anotherplatform of this platform family which contains a definition of theplatform family.

OpC50-0084 ORACLE_HOME parameter does not exist in configurationfile < x1>.

The ORACLE_HOME parameter is needed to connect to the database. Ifthis variable is not set in the environment, it is read from theconfiguration file /usr/OV/conf/ovdbora. This file is written after asuccessful database configuration. If the database configuration failed,you should again run opcdbsetup.

OpC50-0086 Cannot update node address in database.

The opcchgaddr(1m) program cannot change the node address of thespecified node. Check for previous errors to see the reason. If the changedaddress cannot be resolved by the name service, check if the specifiedvalues are correct and if the name service is up and running.

180 Chapter 2


OpC50-0087 Invalid network type (< x1>) specified.Valid types are: IP, SNA, DEC, NOVELL, OTHER andUNKNOWN.

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 alsothe opcchgaddr(1m) man page for more information on the allowed nodeaddress formats.

OpC50-0088 Node name may not be empty.

The Node name may not be empty. See the opcchgaddr(1m) man page forinformation on the node address format.

OpC50-0089 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.

OpC50-0090 New address is different than values from nameservice. Following values have been used:Network type < x1>, IP address < x2>, Node name '< x3>'.

When -force is not used, opcchgaddr(1m) always checks the specifiedvalues with the values from the name service. If the values from thename service differ, the values from the name service will be used. Forexample, opcchgaddr(1m) will always use the fully qualified hostname.The used values are displayed together with the error message. If youwant opcchgaddr(1m) to use the specified values, you have to use -force.

OpC50-0091 Node < x1> is not in the node bank.

Check if the affected node is in the node bank. This error can also occur ifthe affected managed node has (also) an IP address which is not knownon the management server. To solve the problem, update your nameservice to know all IP-Addresses of the affected managed node. Seechapter 9, 'Tuning, Troubleshooting, Security and Maintenance' of theAdministrator's Reference guide, subchapter 'ITO Installation Problemsof Multi-homed Hosts' for more information about troubleshooting nodeswith multiple IP-Addresses.

OpC50-0095 ECS template '< x1>' cannot be distributed as itis unverified. The template will be skipped.

Chapter 2 181


An unverified event correlation circuit is assigned to a node or to themanagement server to which configuration is distributed. Only verifiedevent correlation circuits can be distributed. Please verify the ECScircuit prior distributing it with the ECS designer or de-assign it fromthe node/management server.

OpC50-0096 Error while trying to distribute more than one circuitto a node.

More than one circuit is assigned to distribute. Please undo the surplusassignments.

OpC50-0098 Could not fix inconsistency in opc_nodes_in_group.

opcdbidx could not fix an inconsistency. A node group contains a nodethat is not in the node bank. See previous error messages to see thereason why this not worked. If SQL errors like a timeout were thereason, you can start opcdbidx again. If this still does not work, call yourHP Response Center.

OpC50-0107 Setting software and configuration distribution statusflags to modified.

This step allows to set the software and configuration distribution statusflags to modified. This means, that even though nothing was changed,everything is again distributed like if force update was pressed duringthe distribution.

OpC50-0108 Template '< x1>' is already locked by user '< x2>'.

The Template is already locked by another template administrator or bythe administrator (see error message for the user name). Please contactthe user to finish the work on this template. This will release the lock.

OpC50-0109 No such template.

You tried to lock/unlock a template which does not exist. Probably youruser interface is not in sync with the database and the template wasmeanwhile deleted by another user. To get the current state, exit andrestart the user interface. This will load the data again from thedatabase.

OpC50-0110 Could not remove duplicate entries in opc_node_names.

182 Chapter 2


See the previous errors to see the reason why opcdbidx(1m) could notremove the duplicate entries. If an SQL Error like timeout occured, youcan run opcdbidx again. If this still does not work, call your HP ResponseCenter.

OpC50-0112 Template '< x1>' exists already in the database.

The template could not be added to the database because the databasereturned an non unique object error. Either a template with this namealready exists (e.g. because another template administrator added it).Please use another name to avoid this error. The other reason is, that theused UUID is already in use. In this case, try it again and another UUIDwill be generated.

OpC50-0113 Template '< x1>' will be skipped.

The named template will be skipped from distribution because ofprevious errors. But the other templates will be distributed.

OpC50-0114 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 eventcorrelation templates are distributed to the management server, first theold ECS configuration file and the old ECS circuits are deleted. This filesreside in the directory <OV_CONF>/OpC/mgmt_sv/ec. Please check thatthe directory exists and has proper rights.

OpC50-0115 Cannot remove old ECS files.The stat(2) call failed for file '< x1>'.

Could not get status of an old event correlation file. When eventcorrelation templates are distributed to the management server, first theold ECS configuration file and the old ECS circuits are deleted. This filesreside in the directory <OV_CONF>/OpC/mgmt_sv/ec. Please check thatthe directory exists and has proper rights.

OpC50-0116 Cannot remove old ECS files.The remove(3) call failed for file '< x1>'.

Could not remove an old event correlation file. When event correlationtemplates are distributed to the management server, first the old ECSconfiguration file and the old ECS circuits are deleted. This files reside inthe directory <OV_CONF>/OpC/mgmt_sv/ec. Please check that thedirectory exists and has proper rights.

Chapter 2 183


OpC50-0117 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 eventcorrelation templates are distributed to the management server, first theold ECS configuration file and the old ECS circuits are deleted. This filesreside in the directory <OV_CONF>/OpC/mgmt_sv/ec. Please check thatthe directory exists and has proper rights.

OpC50-0118 Cycle detected while resolving template groupwith ID '< x1>'. This operation would result in acycle. It was aborted.

A database function encountered a loop when it tried to generate allresulting templates. This also includes templates contained insubsequent template groups of a template group. Probably a certaintemplate group contains itself or a subsequent template group containsthe template group. This creates a loop. Template groups may notcontain loops. For this reason, the operation was aborted.

OpC50-0119 Could not modify config status flag(No entry for node_id '< x1>').

The configuration distribution status update of the node with thespecified node_id failed. If the node_id consists of only zeros, the updatein the opc_mgmtsv_config table for the management server failed.Otherwise, no entry for this node_id was found in the opc_node_namestable.

OpC50-0120 Message with ID '< x1>' is already forwarded to manager'< x2>'.

The Message with the given ID was already forwarded to the specifiedtarget manager. Probably you have set up duplicate rules for messageforwarding.

OpC50-0121 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 allresulting templates. This also includes templates contained insubsequent template groups of a template group. Probably a certaintemplate group contains itself or a subsequent template group containsthe template group. This creates a loop. Template groups may notcontain loops. For this reason, the operation was aborted.

184 Chapter 2


OpC50-0123 Templates of type < x1> are not allowed for theagent platform of node < x2>.

Not all types of templates are allowed for all platforms. E.g. Consoletemplates are only allowed on MPE/iX. When distributing, the resultingtemplates for a node are calculated (including templates assigned totemplate groups and node groups). For each of this templates a check isdone, if the template can be assigned to this platform. If not, thetemplate is not distributed and this error message is written. Only thosetemplates for which such an error appeared are skipped. All othertemplates are distributed.

OpC50-0124 Templates of type < x1> are not allowed for the managementserver.

Not all types of templates are allowed for assignment to the managementserver (not the agent of the management server). With ITO 4.0 only ECStemplates can be assigned. The not allowed templates will be skipped.But if some valid templates were assigned, they will still be activated.

OpC50-0125 Monitor Condition '< x1>' already exists.The description of a monitor condition must be unique.

The description of a Monitor Condition already exists within the samemonitor template. The description of a monitor condition must be unique.Please change the description of the new condition.

OpC50-0126 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 forthe user. The first application returned will be used. To avoid problems,you should rename the duplicates.

OpC50-0127 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 adatabase inconsistency is the reason for the error. The other conditionsare not affected from this error if they have not an error, too.

OpC50-0128 Cannot determine database variable < x1>. It is not setand cannot be read from the ovdbconf file.

Chapter 2 185


The specified database environment variable cannot be determined. Thevariable is either read from the environment or from the OV databaseconfiguration file /etc/opt/OV/share/conf/ovdbconf. You can either set thevariable in the environment or you can add a line to the config file in theform '<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 youalready configured the database, you can re-run opcdbsetup and letopcdbsetup use the existing database. This will create the file and othermissing database objects. But it will probably abort later on becausedatabase tables or configuration information already exists.

OpC50-0129 Management area does not exist (ID: < x1>, name: < x2>).

The specified management area ID (for the specified management areaname) does not exist. Probably the UI is out of sync with the databaseand the management area was meanwhile deleted. Please unmark thismanagement area. If the management area name is "Parent", thedatabase is inconsistent. No management area with the managementarea ID of the parent_id DB field exists.

OpC50-0143 Checking for orphans (unused entries) in opc_node_names.

ITO stores all node names in the opc_node_names table. As differenttables refer to this table, entries are not automatically deleted when theyare no longer used. This may leed to a lot of unused entries in theopc_node_names table and thus to performance problems. opcdbidx-orphan removes such unused entries. This message tells, that this checkand removal is currently in progress.

OpC50-0144 Error occured when checking and removing orphans inopc_node_names.

The program could not fix all orphans in the opc_node_names table. Seethe previous errors for more details about the reason. opcdbidx can becalled again.

OpC50-0147 Could not create temporary table < x1>.

The temporary table could not be created. Check previous errormessages for the reason. Check, if there is enough space left on disk.

OpC50-0148 Removed < x1> unused entries from the opc_node_namestable.

186 Chapter 2


ITO stores all node names in the opc_node_names table. As differenttables refer to this table, entries are not automatically deleted when theyare no longer used. This may leed to a lot of unused entries in theopc_node_names table and thus to performance problems. opcdbidx-orphan removes such unused entries. This message tells, that suchentries were removed and the number of removed entries.

OpC50-0153 The audit level is already locked. Nothing changed.

The program opc_audit_secure can only be called once. If the audit levelhas been locked, you can no longer change the audit level and the auditand history download directory. To unlock, you have to re-initialize thedatabase (opcdbinit -c).

OpC50-0154 Cannot read database maintenance information fromdatabase.

See the previous errors for details why this error occurred.

OpC50-0155 Cannot update database maintenance information indatabase.


OpC50-0156 Cannot get the audit level from the database.


OpC50-0157 Cannot update the audit level in the database.


OpC50-0159 Path name is too long: '< x1>'.

The path name is longer than the maximum allowed length of theplatform. On UNIX this is PATH_MAX.

OpC50-0162 The subpath '< x1>' exists but is no directory.

A part of the complete path is not a directory (e.g. a normal file or aspecial file). This prevents, that a directory bellow this path can be used.Please choose a different path or remove the file.

OpC50-0163 The subpath '< x1>' exists but is owned by user '< x2>'instead of user root or < x3>.

Chapter 2 187


The program checks, that the specified directory and any parentdirectory is only writable by root (or bin). This prevents, that thedirectory can be moved and therefore the security can be bypassed.

OpC50-0164 The subpath '< x1>' exists but it has wrong (too open)permissions: < x2>.

The program checks, that the specified directory and any parentdirectory is only writable by root (or bin). This prevents, that thedirectory can be moved and therefore the security can be bypassed.

OpC50-0167 Aborting program due to error. The audit level was notchanged.

Errors occurred. Because of this errors, the program stops. The reasonsfor the abort are in previous errors. Please fix this problems and run theprogram again.

OpC50-0168 Option -file is not possible because audit level islocked.

The audit level has been locked using opc_audit_secure. This means,that the audit level and also the audit and history download directoriescannot be changed anymore for security reasons. For security reasons, inthis case the -file option of opcauddwn and opchistdwn is disabled.

OpC50-0169 The configured download path is no directory. Becausethe audit level is locked, the download path must be adirectory.

To avoid, that old download files are overwritten, the configureddownload path must be a directory if the audit level has been locked.

OpC50-0170 Cannot modify node label. But node address has beenchanged.

Probably the modified node is not contained in the node bank.

OpC50-0172 Node group < x1> does not exist.

The node group with the specified name does not exist. Check if the nameis written correct. If the administrator deleted the node group, restartthe process to get the current list of node groups.

188 Chapter 2


OpC50-0173 Error in time conversion. localtime_r(3C) for < x1>failed.

The conversion of the time in seconds since the epoch to the stringrepresentation in local time needed for the database failed. Please checkthe the environment variable setting (e.g. TZ and LANG).

OpC50-0174 Cannot add audit entry. < x1> tries to find uniqueaudit_nr failed.

The primary key of audit entries is audit_nr. Several tries failed to find aunique audit_nr. If a lot of concurrent processes work, another try maywork. Another reason could be, that the maximum number is reached. Inthis case, you can download all audit entries with opcauddwn(1M). Thisensures that the numbers will again start with 1.

OpC50-0175 Audit entry with number < x1> skipped because it alreadyexists.

An audit entry could not be uploaded from file because an audit entrywith this number already exists in the database. This probably occuredbecause the same file has already been uploaded once. The affected auditentry is skipped, but the audit upload will continue.

OpC50-0185 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 thedetailed reason.

OpC50-0200 Cannot delete message < x1> from < x2> table.

Check the previous errors for the reason, why the message could not bedeleted. If a timeout or deadlock occured, trying it again may work.

OpC50-0201 Cannot move message < x1> to opc_hist_messages.Message with the same ID exists already.

You can download the current history messages with opchistdwn -older0s. Then it should be possible to move the message to the historymessage table.

OpC50-0202 Message < x1> does not exist.

Chapter 2 189


The message can have several reasons. Either the response of anautomatic action has arrived before the message. Or a message isreferenced that is no longer in the active- or history-table because it wasfor example already downloaded. Or a wrong message number wasspecified to an API program.

OpC50-0203 A Message with ID < x1> is already in the history table.

The message could not be inserted into the history message tableopc_hist_messages because a message with this message numberalready exists. Probably history messages were uploaded a second time.

OpC50-0204 Cannot add annotation for message < x1>.

An annotation could not be added. Check previous errors to see thereason for this problem. The message for the annotation may not exist.

OpC50-0205 Message < x1> could not be added.

A message could not be added to the database. See the previous errorsfor the details why this message could not be added.

OpC50-0206 Could not move messages that are marked acknowledged tohistory tables.

To improve the acknowledgement of messages, ITO first marks amessage as acknowledged, but keeps it in the active message tables. Inregular intervalls, the program opcdbmsgmv moves all marked messagesto the history tables. This move of messages failed for some or allmessages. See previous error messages for the reason. If this failedbecause of a timeout, you can run opcdbmsgmv manually again or waituntil it is scheduled the next time. Except of a worse performance fornew messages, this problem has no impact on the work of ITO.

OpC50-0284 Could not add missing nodes to node hierarchies.

opcdbidx tries to fix inconsistencies between the node bank and the nodehierarchies. If a node is not in a hierarchy, it is added. The previousmessages give more information, why this could not be done. If a lot ofchanges have to be done, the Oracle rollback segment may run out ofspace. Run opcdbidx again when you fixed the problem.

OpC50-0287 Removing duplicate applications ...

190 Chapter 2


ITO offers different message load policies to reduce the time needed toload the messages from the database. This policy can be changed by thesystem administrator in the opcsvinfo file. It is not supported to useexternal nodes in the node filter when using the ALLMSGS orNO_EXT_NO_MISC policy.

Chapter 2 191

ITO Error MessagesInternal Database messages

Internal Database messages

OpC51-0022 Retry.

Another process has taken a lock on a database table. ITO tries severaltimes to perform the transaction. The retry itself is not an error, it simplyindicates that ITO has tried to repeat the transaction. If the retries arenot successful, the transaction can not be made. A possible reason forthis error is a user who accesses the ITO tables with an interactivedatabase query tool. This user should commit his transactions or exit thequery tool. Repeating the action now will work.

OpC51-0023 Invalid software status received for updating all nodes.


192 Chapter 2

ITO Error MessagesMessage set used by the application integration program

Message set used by the applicationintegration program

OpC53-0001 Usage: opcdbupload [ -h[elp] ] [ -v[verbose] ] [ -r[eplace] ] [ -a[pplications] ] [ -e[xecutables] ] [ -t[emplates] ] < application>

opcdbupload is a subprogram of the application integration programopcupload. For details, see the man page opcupload(1m) or theAdministrator's Reference Guide, Appendix C.

OpC53-0020 Cannot find the ITO administrator.Cannot add applications.

The database contains no administrator user. Uploaded applicationsbelong to the administrator user. Please ensure that an administratoruser exists. This problem may be caused because the databaseinitialization was not successful. To reinitialize the database runopcdbinit -c -v. Warning: this will delete the contents of all tables.

OpC53-0100 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 ASCIIfile. For details, see the manual page opcdownload(1m) or theAdministrator's Reference Guide, Appendix C.

OpC53-0150 Usage: opchistupl < filename>

Upload program for history messages. For details see the man pageopchistupl(1m) or the Administrator's Reference Guide, Appendix C.

OpC53-0200 Usage: opcaudupl < filename>

Upload program for audit information. For details see the man pageopcaudupl(1m) or the Administrator's Reference Guide, Appendix C.

Chapter 2 193


OpC53-0452 Cannot send message through message interceptor.Message: < x1>.

The Oracle tablespace monitor creates messages which are sent to theITO message interceptor. Please check, that a template for the messageinterceptor is assigned to that node and that the message interceptoragent (opcmsgi) is running on that node.

OpC53-0453 Tablespace < x1> does not exist. Please adapt thetablespace monitor template and redistribute it.

The tablespace which was specified in the Oracle tablespace monitortemplate does not exist. Please adapt the arguments of the tablespacemonitor executable in the tablespace monitor template.

OpC53-0461 Could not open configuration file < x1>.

The configuration file for the Oracle tablespace extension programopcaddbf is missing. It contains information about where the new file ofthe tablespace should be located and what size it should have. For eachtablespace the configuration file should contain lines of the followingformat: <tablespace name> SIZE <size of new file> <directory of new file>

OpC53-0462 Specification for tablespace < x1> not found in < x2>.

The Oracle tablespace extension program opcaddbf was called for atablespace which does not exist. For each tablespace the configurationfile should contain lines of the following format: <tablespace name> SIZE<size of new file> <directory of new file>

OpC53-0463 Size specification for tablespace < x1> not found in < x2>.

The size specification for the tablespace was not found in the tablespaceextension configuration file. For each tablespace the configuration fileshould contain lines of the following format: <tablespace name> SIZE<size of new file> <directory of new file>

OpC53-0464 Directory specification for tablespace < x1> not found in<x2>.

The directory specification for the tablespace was not found in thetablespace extension configuration file. For each tablespace theconfiguration file should contain lines of the following format:<tablespace name> SIZE <size of new file> <directory of new file>

194 Chapter 2


OpC53-0465 SQL command '< x1>' failed.

The printed SQL command of the Oracle tablespace extension programopcaddbf failed. The previous error messages give more informationabout the reason of the failure.

OpC53-0466 Datafile '< x1>' of size < x2>K added to tablespace < x3>.

A new datafile has been successfully added to an full tablespace from theprogram opcaddbf. The tablespace should now have enough space forfurther operations. If the tablespace is a roll back tablespace (RBS1) youmust create and activate new rollback segments. Contact your Oracledatabase administrator to do this.

OpC53-0467 Adding datafile to tablespace < x1> failed.

The Oracle tablespace extension program opcaddbf could not add adatafile to the tablespace. The previous error messages give moreinformation about the reason of the failure.

Chapter 2 195

ITO Error MessagesUpload/Download feature messages

Upload/Download feature messages

OpC54-0001 You must be user root to run this program.

This program must be called with the effective user id of 'root'.

OpC54-0002 Unknown option '< x1>'.

An illegal option for this program was specified.

OpC54-0003 Cannot create directory '< x1>'.

The program failed to create a filesystem directory. Use the system errormessage which is printed out as a hint.

OpC54-0004 Cannot determine working directory.

The current working directory could not be determined. Use the systemerror message which is printed out as a hint.

OpC54-0005 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.

OpC54-0006 Cannot stat entry '< x1>'.

The status of the specified file system object (file, directory, link) couldnot be determined. Use the system error message which is printed out asa hint.

OpC54-0007 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.

OpC54-0008 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.

OpC54-0009 Cannot remove file '< x1>'.

196 Chapter 2


The specified file could not be removed. Use the system error messagewhich is printed out as a hint.

OpC54-0010 Registration file '< x1>' not linked to directory '< x2>'.

The symbolic link for the specified application registration file does pointto an expected target directory. This happens only if the uploaded data ischanged while 'opccfgupld' is running or the registration files used byIT/O are changed while 'opccfgdwn' is in progress.

OpC54-0011 Cannot execute command '< x1>'.

No instruction

OpC54-0012 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.

OpC54-0013 Cannot read from file/command '< x1>'.

An error occurred while reading from the specified file. Use the systemerror message which is printed out as a hint.

OpC54-0014 Cannot determine destination of symbolic link '< x1>'(readlink).

The target location for the specified symbolic link could not bedetermined. Use the system error message which is printed out as a hint.

OpC54-0015 Cannot make symbolic link '< x1>' (symlink).

The specified symbolic link could not be created. Use the system errormessage which is printed out as a hint.

OpC54-0016 Unknown character set.

The internal character set is not supported by either 'opccfgupld' or'opccfgdwn'.

OpC54-0017 Cannot initialize configuration handling.

The configuration file handling of the reporting process could not beinitialized correctly.

OpC54-0018 Cannot find administrator.

Chapter 2 197


The configuration download 'opccfgdwn' could not find the administratorin the IT/O database. Verify if you are trying to download a not properlyinitialized configuration (administrator present). The configurationupload 'opccfgupld' tried to upload applications into the application bankbut could not find the administrator in the IT/O database. Verify if youare trying to upload applications to a properly initialized configuration(administrator present).

OpC54-0050 usage: opccfgdwn [-help] | [-silent] [-force] [-v< version number>] < specification file> < target directory>

There is an error in the calling sequence of 'opccfgdwn'.

OpC54-0051 Internal error [< x1>].

This is an internal error. Please report this message to your HPResponse Center.

OpC54-0052 Cannot access specification file '< x1>'.

The configuration download 'opccfgdwn' could not access the downloadspecification file. Use the system error message which is printed out as ahint.

OpC54-0053 Cannot open specification file '< x1>'.

The configuration download 'opccfgdwn' could not open the downloadspecification file. Use the system error message which is printed out as ahint.

OpC54-0054 Target filetree is not empty and option '-force' is notspecified.Remove the filetree manually and restart the download.(use command 'rm -r < x1>').

The directory tree which was specified for the configuration download isnot empty. Since the option '-force' was not specified, the existent files arenot modified. Use the option '-force' or remove the directory treemanually. You may use the command mentioned in the error message.

OpC54-0055 File '< x1>' removed from target filetree.

198 Chapter 2


This is an informational message indicating the removal of an existentfile from the download directory. Files are removed only if the option'-force' was specified for 'opccfgdwn'.

OpC54-0056 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.

OpC54-0057 Syntax error in specification file '< x1>'.

The download specification file had syntax errors. If this specification filewas created using the administrator GUI, please report this message toyour HP Response Center. If you created this file manually, check theaccording line and correct the error.

OpC54-0058 Cannot create data file '< x1>'.

The configuration download could not create the specified data file. Usethe system error message which is printed out as a hint.

OpC54-0059 Illegal user name pattern for registration filedestination (< x1>).

This is an internal error. Please report this to your HP Response Center.

OpC54-0060 Error writing to file '< x1>'.

An error occurred while the configuration download was writing to thespecified file. Use the system error message which is printed out as ahint.

OpC54-0061 Options for < x1>: -help : Displays this message. -silent : Perform silent download, report only warningsand errors. If not specified, verbose progress messages aregenerated.

This message gives a short description for the options of 'opccfgdwn'.

OpC54-0062 -force : Overwrite existing files. < specification file> : Name of file containing the download specification. If no path is specified, the

Chapter 2 199


file is searched for in a subdirectory < target dir> of the default application data directory.

No instruction

OpC54-0063 < target directory> : Name of the directory under which thefile tree of downloading data will start. If no path isspeci- fied, the directory is used/created in the directory < x1>.

No instruction

OpC54-0064 Warning: Since not 'All Configuration Data' was selected for thedownload, 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 wasdownloaded. Uploading partial configuration data may result in lostreferences (since the referenced data was not downloaded, too) or deleteddata (since before replacing the node bank, say, the node group bank isdeleted, too). See the manual page for 'opccfgupld' for more details(section RESTRICTIONS).

OpC54-0065 Logfile output has been stored in '< x1>'

The configuration upload writes a logfile which basename is reported inthis message. This file is stored in '/var/opt/OV/log/OpC/mgmt_sv'.

OpC54-0100 Internal error [< x1>].

This is an internal error. Please report this message to your HPResponse Center.

OpC54-0101 Cannot open index file '< x1>'.

The index file, which controls 'opccfgupld', could not be opened. Verifythat the index file is located in the language specific subdirectory of yourupload path, and that it has the same name as the last component of thespecified upload directory (truncated to eight characters) with extension'.idx'. The index file is written by 'opccfgdwn' while downloading.

200 Chapter 2


OpC54-0102 Syntax error(s) in index file '< x1>'.

The index file, which controls 'opccfgupld', contains syntax errors. If youused an index file created by 'opccfgdwn', please report this message toyour HP Response Center. If you created your own index file, use thespecific error messages which were printed before the current messageand correct the error.

OpC54-0103 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'.

OpC54-0104 Character set of download data not compatible withinstalled set.

The character set which was installed on the downloaded server is notcompatible with the character set installed on the current managementserver.

OpC54-0106 Synchronize mode requires download of all data.

The synchronize mode is allowed only if a download of all configurationdata is used for uploading.

OpC54-0107 Cannot open data file '< x1>'.

The specified data file could not be opened for reading. Use the systemerror message which is printed out as a hint.

OpC54-0108 Syntax error in data file '< x1>'

The specified data file contains a syntax error. If you are uploading aprevious download from 'opccfgdwn', please report this message to yourHP Response Center. If you used a manually created data file, locate theerror using the error messages which were printed before this messageand correct the error.

OpC54-0109 Database modifications are skipped from now on.

Chapter 2 201


After an error occurred during the upload process, all databasemodifications are skipped from now on. However, the remaining datafiles are parsed and errors are reported.

OpC54-0110 Options for < x1>: -help : Displays this message. -contents : Show entities which are available in thedata files. -check : Check the syntax of the data files. -silent : Perform silent upload, report only warningsand errors. If not specified, verbose progress messages aregenerated. -installed : Set software status flag of new nodes to'active'.

This message gives a short description for the options of 'opccfgupld'.

OpC54-0111 -configured: Do not set config change flag if templatesare changed or newly assigned to a managed node. -no_license: Do not set flag to indicate licensechecking for new nodes. This option may only be used for configuration of Backup Servers, otherwise it violates the license agreements.

No instruction

OpC54-0112 -subentity : Specifies the behaviour in add or replacemode. -trace : Add SQL-execution info to our logfile < x1>.log. -add : Insert data in addition to existingconfiguration. -replace : Insert data and replace existingconfiguration.

No instruction

OpC54-0113 -index : Read upload specification from this indexfile. -heartbeat : Set the Heartbeat flag for nodes to ON,OFF, KEEP the valueor take the value of the DATA files (default). -layout : Upload also the operator layouts when

202 Chapter 2


uploading ITO 4.xoperator data and convert them to node hierarchies. < upload directory> : Name of the directory under which thefile tree of the upload data is located. If no path is specified, the directory is searched for in the directory < x1>.

No instruction

OpC54-0150 line < x1> "< x2>": error in application login.

This is a specific error message concerning a syntax error in a data file.

OpC54-0151 line < x1> "< x2>": error in 'APPLICATION' entity.


OpC54-0152 line < x1> "< x2>": error in 'APPLICATION_GROUP' entity.


OpC54-0153 line < x1> "< x2>": node address or 'PATTERN_OTHER < string>'expected.


OpC54-0154 line < x1> "< x2>": condition node address or patternexpected.


OpC54-0155 line < x1> "< x2>": condition severity expected.


OpC54-0156 line < x1> "< x2>": error in 'CONSOLE_TEMPLATE' entity.


OpC54-0157 line < x1> "< x2>": error in 'INTERFACE_TEMPLATE' entity.


OpC54-0158 line < x1> "< x2>": 'DOWNLOAD_DATA < entity>' expected.


Chapter 2 203


OpC54-0159 line < x1> "< x2>": error in 'INSTRUCTION_INTERFACE'entity.


OpC54-0160 line < x1> "< x2>": error in 'LOGFILE_TEMPLATE' entity.


OpC54-0161 line < x1> "< x2>": error in 'MONITOR_TEMPLATE' entity.


OpC54-0162 line < x1> "< x2>": error in template message conditionentry.


OpC54-0163 line < x1> "< x2>": error in 'MESSAGE_GROUP' entity.


OpC54-0164 line < x1> "< x2>": error in 'NODE_GROUP' entity.


OpC54-0165 line < x1> "< x2>": error in 'NODE' entity.


OpC54-0166 line < x1> "< x2>": node address expected.


OpC54-0167 line < x1> "< x2>": error in 'NODE_DEFAULTS' entity.


OpC54-0168 line < x1> "< x2>": error in 'LAYOUT' entry of managednode.


OpC54-0169 line < x1> "< x2>": name of node template expected.


OpC54-0170 line < x1> "< x2>": error in 'NOTIFICATION_SERVICE' entity.

204 Chapter 2



OpC54-0171 line < x1> "< x2>": error in notification schedule entry.


OpC54-0172 line < x1> "< x2>": error in 'OPERATOR' entity.


OpC54-0173 line < x1> "< x2>": error in application group entity ofoperator desktop.


OpC54-0174 line < x1> "< x2>": error in operator geometry entry.


OpC54-0175 line < x1> "< x2>": error in operator node 'LAYOUT' entry.


OpC54-0176 line < x1> "< x2>": 'NODE < address>' expected for operatorlayout.


OpC54-0177 line < x1> "< x2>": error in operator responsibility entry'NODE_GROUP'


OpC54-0178 line < x1> "< x2>": error in 'REGROUP_CONDITIONS' entity.


OpC54-0179 line < x1> "< x2>": error in 'TRAP_TEMPLATE' entity.


OpC54-0180 line < x1> "< x2>": error in snmp variable entry.


OpC54-0181 line < x1> "< x2>": error in trap template messagecondition entry.

Chapter 2 205



OpC54-0182 line < x1> "< x2>": character set is not compatible withinstalled set.


OpC54-0183 line < x1> "< x2>": error in operator scope entry.


OpC54-0184 line < x1> "< x2>": error in management area entry.


OpC54-0250 line < x1> "< x2>": error in application specification.


OpC54-0251 line < x1> "< x2>": error in application groupspecification.


OpC54-0252 line < x1> "< x2>": error in condition specification.


OpC54-0253 line < x1> "< x2>": error in instruction interfacespecification.


OpC54-0254 line < x1> "< x2>": error in monitor template spec. (stringexpected).


OpC54-0255 line < x1> "< x2>": error in message group specification.


OpC54-0256 line < x1> "< x2>": error in network/machine typespecification.


206 Chapter 2


OpC54-0257 line < x1> "< x2>": error in node specification.


OpC54-0258 line < x1> "< x2>": error in node address specification.


OpC54-0259 line < x1> "< x2>": error in node group specification.


OpC54-0260 line < x1> "< x2>": error in notification servicespecification.


OpC54-0261 line < x1> "< x2>": error in operator specification.


OpC54-0262 line < x1> "< x2>": error in operator configurationspecification.


OpC54-0263 line < x1> "< x2>": error in operator responsibilityspecification.


OpC54-0264 line < x1> "< x2>": error in template specification.


OpC54-0265 line < x1> "< x2>": error in template specification (stringexpected).


OpC54-0266 line < x1> "< x2>": error in template conditionspecification.


OpC54-0267 line < x1> "< x2>": error in header section.


Chapter 2 207


OpC54-0268 line < x1> "< x2>": error in template group specification.


OpC54-0269 line < x1> "< x2>": error in operator scope specification.


OpC54-0270 line < x1> "< x2>": error in ec template specification.


OpC54-0271 line < x1> "< x2>": error in schedule templatespecification.


OpC54-0300 line < x1> "< x2>": error in entity specification.


OpC54-0301 line < x1> "< x2>": error in operator configurationspecification.


OpC54-0302 line < x1> "< x2>": error in operator desktopspecification.


OpC54-0500 No data specified for insertion (< x1>)

No depot node was specified in the node defaults section. This is awarning only, the remaining data is processed.

OpC54-0501 No required data specified for insertion (< x1>)


OpC54-0502 Illegal structure passed (< x1>)


OpC54-0503 Illegal parameter passed (< x1>)


208 Chapter 2


OpC54-0504 Warning during Add - Regroup Condition already exists(< x1>)

The specified regroup condition exists and replace mode was not selected.

OpC54-0505 Warning - Instruction Interface not found (< x1>)

The specified instruction interface was referenced but does not exist inthe database. This happens if a downloaded template used an instructioninterface but the interface was not selected for the download and is notavailable at upload time.

OpC54-0506 Warning - Message Group not found (< x1>)

The specified message group was referenced but does not exist in thedatabase. This happens if an operator was downloaded which isresponsible for that group but the group was not selected for thedownload and is not available at upload time.

OpC54-0507 Warning - Node Group not found (< x1>)

The specified node group was referenced but does not exist in thedatabase. This happens if an operator was downloaded which isresponsible for that group but the group was not selected for thedownload and is not available at upload time.

OpC54-0508 Warning - Platform missing for node defaults.Please check platforms on source system and reinstall ondestination 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 missingplatforms on the destination system.

OpC54-0509 Warning - Platform missing (net/machine=< x1>).

The platform for the specified network/machine type is missing. Checkthe platforms available on the source system and reinstall missingplatforms on the destination system.

OpC54-0510 Warning - Platform missing for node "< x1>".Please check platforms on source system and reinstall ondestination system.

Chapter 2 209


The platform for the specified node is missing. Check the platformsavailable on the source system and reinstall missing platforms on thedestination system.

OpC54-0511 Warning - trouble ticket already existing, not beingreplaced

The trouble ticket information already exists in the database and is notgoing to be replaced (add mode selected).

OpC54-0512 Warning - management server configuration alreadyexisting, not being replaced

The management server configuration already exists in the database andis not going to be replaced (add mode selected).

OpC54-0513 Warning - DB maintenance already existing, not beingreplaced

The database maintenance information already exists in the databaseand is not going to be replaced (add mode selected).

OpC54-0514 Please wait cleaning up unused references in table "< x1>"...

This is a progress message from 'opccfgupld' if the option '-cleanup' isused to remove orphan database objects introduced with versions beforeIT/O A.04.x. Because the cleanup may consume a rather large amount ofprocessing time, a message indicating the beginning of the process isprinted.

OpC54-0515 ** DONE ** processed < x1> entries

This is an information indicating the completed cleanup of one databasetable.

OpC54-0516 Node < x1> found in database with different IP address

The specified node already exists in the database but the IP address isdifferent. The reference to this node is skipped. A database entry for anode is not only made if a node is added to the node bank, but also if amessage is received for this node (whatever occurs first).

OpC54-0517 Management Area "< x1>" not found in database (path is"< x2>")

210 Chapter 2


The specified management area is referenced from within an operatorsscope, but the area does not exist in the database. This happens if anoperator was downloaded which is responsible for that area but themanagement areas were not selected for the download are not availableat upload time.

OpC54-0604 Assignment to template group '< x1>' will be skipped.

Cannot assign template (group) to template group because it is not orseveral times in the database. If the template (group) is not in thedatabase, then create or upload it, or remove the assignment from thetemplate group. If the template (group) is several times in the database,then delete or rename it, to have unique template (group) names. Thenyou can upload the assignment by uploading the template group withopccfgupld(1m).

OpC54-0605 Assignment to node '< x1>' will be skipped.

Cannot assign template (group) to node because it is not or several timesin the database. If the template (group) is not in the database, thencreate or upload it, or remove the assignment from the node. If thetemplate (group) is several times in the database, then delete or renameit, to have unique template (group) names. Then you can upload theassignment by uploading the node with opccfgupld(1m).

OpC54-0606 Assignment to node group '< x1>' will be skipped.

Cannot assign template (group) to node group because it is not or severaltimes in the database. If the template (group) is not in the database, thencreate or upload it, or remove the assignment from the node group. If thetemplate (group) is several times in the database, then delete or renameit, to have unique template (group) names. Then you can upload theassignment by uploading the node group with opccfgupld(1m).

OpC54-1001 + downloading nodegroup "< x1>"

This is a progress message of the configuration download.

OpC54-1002 + downloading managed node "< x1>"


OpC54-1003 + downloading node defaults for < x1>/< x2>


Chapter 2 211


OpC54-1004 + downloading message group "< x1>"


OpC54-1005 + downloading application group "< x1>"


OpC54-1006 + downloading operator data


OpC54-1007 + downloading operator responsibility


OpC54-1008 + downloading operator layout


OpC54-1009 + downloading layout "< x1>"


OpC54-1010 + downloading operator desktop


OpC54-1011 + downloading < x1> "< x2>"


OpC54-1012 + downloading template "< x1>"


OpC54-1013 + reading node groups from DB


OpC54-1014 + reading managed nodes from DB


OpC54-1015 + reading node defaults from DB


212 Chapter 2


OpC54-1016 + reading message groups from DB


OpC54-1017 + reading applications from DB


OpC54-1018 + reading operators from DB


OpC54-1019 + reading < x1> templates from DB


OpC54-1020 + reading notification services from DB


OpC54-1021 + downloading service "< x1>"


OpC54-1022 + reading regroup conditions from DB


OpC54-1023 + downloading regroup condition "< x1>"


OpC54-1024 + reading administrator configuration from DB


OpC54-1025 + reading database maintenance data from DB


OpC54-1026 + downloading database maintenance data


OpC54-1027 + reading management server configuration from DB


Chapter 2 213


OpC54-1028 + downloading management server configuration


OpC54-1029 + reading trouble ticket data from DB


OpC54-1030 + downloading trouble ticket data


OpC54-1031 + reading instruction text interfaces from DB


OpC54-1032 + downloading instruction text interface "< x1>"


OpC54-1033 + uploading node defaults

This is a progress message of the configuration upload.

OpC54-1034 + uploading message groups


OpC54-1035 + uploading managed nodes


OpC54-1036 + uploading management server configuration


OpC54-1037 + uploading node groups


OpC54-1038 + uploading < x1> templates


OpC54-1039 + uploading regroup conditions


214 Chapter 2


OpC54-1040 + uploading applications


OpC54-1041 + uploading operators


OpC54-1042 + uploading administrator configuration


OpC54-1043 + uploading management server configuration


OpC54-1044 + uploading trouble ticket information


OpC54-1045 + uploading notification services


OpC54-1046 + uploading instruction interface


OpC54-1047 + verifying target filetree


OpC54-1048 + parsing download specification file "< x1>"


OpC54-1049 + starting download


OpC54-1050 + of all configuration data


OpC54-1051 + of selected configuration data


Chapter 2 215


OpC54-1052 + parsing index file "< x1>"


OpC54-1053 + parsing data file "< x1>"


OpC54-1054 + starting upload


OpC54-1055 + skipping upload of node defaults


OpC54-1056 + skipping upload of message groups


OpC54-1057 + skipping upload of managed nodes


OpC54-1058 + skipping upload of management server configuration


OpC54-1059 + skipping upload of nodegroups


OpC54-1060 + skipping upload of < x1> templates


OpC54-1061 + skipping upload of regroup conditions


OpC54-1062 + skipping upload of applications


OpC54-1063 + skipping upload of operators


216 Chapter 2


OpC54-1064 + skipping upload of administrator configuration


OpC54-1065 + skipping upload of db maintenance


OpC54-1066 + skipping upload of trouble ticket information


OpC54-1067 + skipping upload of notification services


OpC54-1068 + skipping upload of instruction interface data


OpC54-1069 + copying "< x1>"


OpC54-1070 + downloading file "< x1>"


OpC54-1071 + uploading file "< x1>"


OpC54-1072 + < x1> terminated with < x2> warning(s)/error(s)

Configuration download terminated with warnings or errors.

OpC54-1073 + < x1> finished

Configuration download terminated without warnings and errors.

OpC54-1074 + < x1> terminated with < x2> warning(s)/error(s)

Configuration upload terminated with warnings or errors.

OpC54-1075 + < x1> finished

Configuration upload terminated without warnings and errors.

Chapter 2 217


OpC54-1076 + downloading executables


OpC54-1077 + uploading executables


OpC54-1078 + downloading escalation manager configuration


OpC54-1079 + uploading escalation manager configuration


OpC54-1080 + downloading responsible manager configuration


OpC54-1081 + uploading responsible manager configuration


OpC54-1082 + downloading node configuration


OpC54-1083 + uploading node configuration


OpC54-1084 + skipping upload of node configuration


OpC54-1090 + downloading ec circuit files for template "< x1>"


OpC54-1091 + uploading ec circuit files for template "< x1>"


OpC54-1092 + downloading ec libraries


218 Chapter 2


OpC54-1093 + uploading ec libraries


OpC54-1094 + downloading ec modules


OpC54-1095 + uploading ec modules


OpC54-1100 + downloading template group "< x1>"


OpC54-1101 + reading template groups from DB


OpC54-1102 + uploading template groups


OpC54-1103 + downloading operator scope


OpC54-1104 + reading management areas from DB


OpC54-1105 + downloading toplevel management area "< x1>"


OpC54-1106 + skipping upload of management area information


OpC54-1107 + uploading management areas


OpC54-1132 + skipping the adjustment of node hierarchies with thenode bank

Chapter 2 219


The alignment of the node hierarchies with the node bank has beenskipped because database actions are skipped. If there is the need toalign the node hierarchies with the node bank, you can call opcdbidx-hierarchy.

220 Chapter 2

ITO Error MessagesDatabase installation/upgrade messages

Database installation/upgrade messages

OpC55-0004 Could not initialize error handling.

This error is because the program has too little free memory or thegethostname(2) system call failed.

OpC55-0005 Not enough resources to continue installation.

The Operating System Resources required by the database system, suchas memory or temporary disk space, have been exceeded. The previouserror message contains the error message delivered by the databasesystem which may describe the error in more detail.

OpC55-0006 Error in communication with database.

Check that the database server processes are running. The previouserror message contains the error message delivered by the databasesystem, which may describe the error in more detail.

OpC55-0007 Severe error in database server.

A severe error occurred which has terminated the session. The previouserror message contains the error message delivered by the databasesystem which may describe the error in more detail.

OpC55-0008 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 notmean any error if the next error message is 'Retry.' as the transactionwill be repeated several times. If the retries still are not successful, thetransaction can not be made. A possible reason for this error is a userwho 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.

OpC55-0009 Trying to reconnect to database server...

Chapter 2 221


The connection to the database system has been lost. The application istrying to reconnect to database system. If this is successful theapplication can go on to work.

OpC55-0010 Reconnect to database server was successful.

The connection to the database system was lost, but the application hasreconnected to the database system successfully and is able to continue.

OpC55-0011 Reconnect to database server failed.

The connection to the database system has been lost. The applicationtried to reconnect to database system without success. The applicationcan not continue. Check that the database servers are running. If not,restart the database servers and run the application again.

OpC55-0020 All retries failed.

Another process has taken a lock on a database table. Repeating thetransaction was without success. The transaction can not be made. Apossible reason for this error is a user who accesses the ITO tables withan interactive database query tool. This user should commit histransactions or exit the query tool. Repeating the action now will work.

OpC55-0025 Could not get message from message catalog.

Check that the message catalog exists and has read permissions for allusers. The file is: '/opt/OV/lib/nls/<lang>/opcsv.cat where lang is your setlanguage (default: C). Check also that the directory where the messagecatalog resides is readable for all users.

OpC55-0026 Retry last action.....

Another process has taken a lock on a database table. ITO tries severaltimes to perform the transaction. The retry itself is not an error, it issimply an indication that ITO has tried to repeat the transaction. If theretries are not successful, the transaction can not be made. A possiblereason for this error is a user who accesses the ITO tables with aninteractive database query tool. This user should commit histransactions or exit the query tool. Repeating the action now will work.

OpC55-0027 Usage: opcdbinst [-v][-r|-c|-ac|-rc] -v : verbose -r : remove all ITO tables from database

222 Chapter 2


-c : clear tables -ac : add constraints (foreign keys) -rc : remove constraints (foreign keys)

ITO database installation program. This program creates the ITOdatabase scheme in the OpenView database. For more details, see themanual page opcdbinst(1m) or the Administrator's Reference Guide,Appendix C.

OpC55-0028 Error while creating table < x1>.

The database table <table> could not be created. The previous errormessages will describe the reason in more detail. Probably a lock is thereason.

OpC55-0029 Error while creating secondary index < x1>.

The secondary index <index> for a table could not be created. Theprevious error messages will describe the reason in more detail.

OpC55-0030 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.

OpC55-0031 Error while modifying storage structure of secondaryindex < x1>.

The storage structure of the secondary index <index> could not bechanged. The previous error messages describe the reason in more detail.

OpC55-0032 Error while writing startup data into table < x1>.

The database table <table> could not be filled with startup data. Theprevious error messages describe the reason in more detail. Probably alock is the reason.

OpC55-0036 Error while deleting table < x1>.

The database table <table> could not be deleted. The previous errormessages describe the reason in more detail. Probably a lock is thereason.

OpC55-0037 Error while deleting secondary index < x1>.

Chapter 2 223


The secondary index <index> for a database table could not be deleted.The previous error messages describe the reason in more detail.

OpC55-0040 Error while removing contents of table < x1>.

The database table <table> could not be cleared. The previous errormessages describe the reason in more detail. Probably a lock is thereason.

OpC55-0043 Error while removing table < x1>.

The database table <table> could not be deleted. The previous errormessages describe the reason in more detail. Probably a lock is thereason.

OpC55-0099 Error in access to directory (< x1>):<x2>

The directory <dir> could not be accessed or created. The error numberof the previous system call was <errno>. Check that the parent directoryof the directory exists.

OpC55-0100 Usage: opc_dbinit [-v] [-s] -v : verbose -s : use Shiftjis as managment server character set

ITO database initialization program. This program fills the ITOdatabase tables with the default configuration. For more details, see themanual page opcdbinit(1m) or the Administrator's Reference Guide,Appendix C.

OpC55-0103 <x1> contains a wrong key word.

The file <file> which contains the default configuration data, hasincorrect syntax. Please use the original defaults file or use the samesyntax used in the original defaults file.

OpC55-0104 <x1> contains a wrong value for < x2>.

The file <file> which contains the default configuration data, contains awrong value. Check the values or use the original defaults file.

OpC55-0105 <x1>: end of file reached before value of < x2>.

224 Chapter 2


The file <file> which contains the default configuration data, hasincorrect syntax. Use the original defaults file or use the same syntaxused in the original defaults file.

OpC55-0106 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 havecorrect permissions.

OpC55-0107 File < x1> contains invalid node < x2>.

The file <file> which contains the default configuration data, contains awrong value. Please check the values or use the original defaults file.

OpC55-0111 Node < x1> is not configured for ITO.

The node <node> does not have a configuration file. Create one, or deletethe node from the NODE_NAMES file.

OpC55-0125 Unknown template < x1> specified in node configurationfile < x2>.

The template <template> does not have a configuration file. Create one,or remove the template from the node configuration file <file>.

OpC55-0126 Error in template configuration file < x1>.

The file <file> which contains default configuration data, has incorrectsyntax. Use the original defaults file or use the same syntax used in theoriginal defaults file.

OpC55-0250 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 thedatabase fields from ITO version 1.0 to version 1.1. For details, see themanual page opcdbupgr(1m), or the Administrator's Reference Guide,Appendix C.

OpC55-0257 Can not create or modify object < x1>.

Chapter 2 225


The database object <object> for a table could not be created. Theprevious error messages describes the reason in more detail.

OpC55-0260 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.

OpC55-0261 Database successful upgraded.

The database upgrade from the previous version of ITO was successfullyfinished. The database tables are now in the new database layout.

OpC55-0269 Aborting upgrade of ITO tables.

The program has been terminated due to earlier errors. Earlier errormessages describe the reason in more detail.

OpC55-0309 You must be user root to run this program.

This program must be called as superuser root.

226 Chapter 2

ITO Error MessagesError messages of user interface

Error messages of user interface

OpC60-0005 User name must be entered.

In order to logon to ITO, the user name must be entered. Your ITOadministrator defines your user name, along with the password, to giveyou access to your capabilities within ITO.

OpC60-0006 Password must be entered.

In order to logon to ITO, the password of the user must be entered. YourITO administrator defines your user name, along with the password, togive you access to your capabilities within ITO.

OpC60-0007 Error during open of the dialogfile (< x1>).Program aborted.

The user interface specification file (file) was not found. Therefore, ITOcould not be started. Check that the given file is available and has readpermissions.

OpC60-0008 Could not set the environment (< x1>).

ITO has tried to set the environment variable specified. This problem canonly occur if internal table limitations apply. Try to set the environmentvariable before you start ITO.

OpC60-0009 Could not execute the program with 'execlp'.(path=< x1> pgm=< x2>).

System call inside ITO failed. Check UNIX error number for the functionin HP-UX manpages.

OpC60-0010 Could not get the environment (< x1>).

The environment variable specified is expected by ITO. Due to internaltable limitations, the variable was not available. Exit the program viathe OpenView Exit menu and restart ITO.

OpC60-0011 Reentered password does not match the new password.

Chapter 2 227


You entered a different new password. In order to prevent typingproblems, you have to reenter the new password again. Type in thecorrect new password again or cancel the action.

OpC60-0015 Error during login occurred.

The login procedure could not be completed. This may happen if some ofthe ITO server processes do not run properly, or the same user has loggedin at the same time from another display station. Exit the program viathe OpenView Exit menu, and try to login again.

OpC60-0030 First finish the already started editing task, beforenew annotationscan be loaded

You have already started an add or modify task for an annotation. Youmust finish or cancel this task before you are able to load annotations foranother message.

OpC60-0031 Only the creator of the annotation is allowed to performthis action.

You are not allowed to modify or delete annotations created by anotherauthor. These actions can only be performed by the creator of theannotation. However, you are allowed to add additional annotations tothe message.

OpC60-0032 Field may not be empty.

In order to complete the editing task, the field which has the input focusmay not be left empty.

OpC60-0033 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 linebelonging to the annotation in the listbox. You are then able to performthe required task.

OpC60-0042 Unable to link file < x1>.

ITO was not able to create the specified symbolic link (probably for anApplication Registration File). Either try to create the indicated symboliclink 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


write to the directory or a file with that name already exists, whichcannot be overwritten, or the file system is full, quota has been reached,etc.

OpC60-0090 Help cannot be provided.The selected object does belong to another application.

ITO provides context-sensitive help. This may be invoked on editablefields by the use of <F1>. If the context-sensitive help has been invokedfrom the Help menu, the question mark cursor may be clicked on anyobject. In this case, ITO is only able to provide help for fields whichbelong to ITO windows, and which are non-map windows.

OpC60-0096 No instruction available!

No instruction could be found. If you are able to reproduce this problemthen please report this to your HP Response Center.

OpC60-0113 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 ITOGUI is running, another user might have incorrectly called `ovw -map<user_name>') the OV map for an ITO user will not have writepermission; in this case the ITO user is not able to re-login into the ITOGUI any more. If you are sure, that no other user has that OV map inaccess apply the following solution. Solution: /usr/OV/bin/ovwchmod +w<user_name>

OpC60-0198

You have just made changes to a registered OpenView Application (e.g.added a new one). To be able to use this application as ITOAdministrator, OpenView Windows must be restarted. Since ITO isintegrated into OpenView Windows, you need to exit this ITO sessionand start a new one if you want to use the application (or menu items orwhatever) that you just changed or added.

OpC60-0200 Unable to load messages due to database problems.

When a new browser is opened, messages are transferred from thedatabase to the user interface. A message received from the userinterface that is obviously corrupt would create an inconsistent state.

Chapter 2 229


Therefore the browser will not appear on the screen. Solution: Try toopen the browser again, or if the main `Message Browser' does notappear, restart the user interface.

OpC60-0202 Could not load the saved browser geometry.

The browser's geometry of the last ITO session could not be queried fromthe database. The browser will be opened with default geometry.

OpC60-0203 Could not invoke display receiver.

The display receiver is a child process of the user interface. For somereason it could not be started. See the error messages following thismessage for a detailed description of the reasons of this fault ( maybemaximum number of processes exceeded). See Solution of the moredetailed error message and restart the user interface.

OpC60-0205 Attempt to read from display receiver failed.

ITO events (for example, a new message, successful end of action) arereceived from the display receiver and transmitted in a queue from thedisplay receiver to the user interface. The user interface was unable toread the next event from this queue. Restart the user interface.

OpC60-0208 Unable to append message to internal message list. Warning: this may cause inconsistencies during thissession.

A message could not be stored in the internal message lists of the userinterface. If this message appears when trying to open the `HistoryMessage Browser' close and reopen this browser again. Otherwise,restart the user interface.

OpC60-0211 Cannot retrieve operator initiated action from database.

Open `Message Details' for this message, to review the predefinedoperator-initiated action. Try to start this action manually. If `Details'could not be opened, restart the user interface.

OpC60-0212 Warning: at least one of the selected messagesdoes not contain the specified type of action.

The ITO operator pressed `Perform Action' for a message that has nopredefined operator-initiated action.

230 Chapter 2


OpC60-0213 Warning: the specified type of action is currentlyrunning 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 isindicated by the ̀ O'-flag in the message browser. This field must be ̀ S' forsuccessful or `F' for failed. Then the action can be performed again.

OpC60-0214 Perform action failed:Display Manager reports Error on action request.

Display Manager reports error on action request. Look for a moredetailed description following this error message. Verify that the ITOmanagement server processes are running. If not, restart the ITOmanagement server processes. Do this either from the administratoruser interface or execute the command: /usr/OV/bin/OpC/opcsv -start Ifthe action was invoked from the Message Details window, try to start itdirectly from the Message Browser.

OpC60-0219 Unable to perform actionsince management server is down

Restart the ITO management server processes. Do this either from theadministrator user interface, or execute the command:/usr/OV/bin/OpC/opcsv -start

OpC60-0220 Unable to (un)acknowledge message(s).

The database could not serve a request to (un)acknowledge the selectedmessage(s). If more than one message should be acknowledged, try toacknowledge them in smaller portions. If a single message cannot beacknowledged, restart the user interface.

OpC60-0221 Unable to unacknowledge message

The database could not serve a request to unacknowledge the selectedmessages. If more than one message should be acknowledged, try toacknowledge them in smaller portions. If a single message cannot beacknowledged restart the user interface.

OpC60-0229 Unable to inform Display Manager about acknowledgerequestDisplays of other users will not be updated

Chapter 2 231


Connection to display manager lost. The display manager is informedabout the acknowledge request in order to update the displays of otherITO operators. Verify that the ITO management server processes arerunning. If not, restart the ITO management server processes. Do thiseither from the administrator user interface, or execute the command:/usr/OV/bin/OpC/opcsv -start

OpC60-0230 Unable to inform Display Manager about action startDisplays of other users will not be updated

Connection to display manager lost. The display manager is informedabout the start of an action in order to update the displays of other ITOoperators. Verify that the ITO management server processes arerunning. If not, restart the ITO management server processes. Do thiseither from the administrator user interface, or execute the command:/usr/OV/bin/OpC/opcsv -start

OpC60-0231 Unable to inform Display Manager about unacknowledgerequestDisplays of other users will not be updated

Connection to display manager lost. The display manager is informedabout the unacknowledge request in order to update the displays of otherITO operators. Verify that the ITO management server processes arerunning. If not, restart the ITO management server processes. Do thiseither from the administrator user interface, or execute the command:/usr/OV/bin/OpC/opcsv -start

OpC60-0235 Error in message filter: filtering of message failed.

In most cases the specified message text pattern is syntacticallyincorrect. Look for a more detailed description following this errormessage. Simplify the message filter (for example, don't use or usesimple message patterns) in order to find the component that is causingthe troubles.

OpC60-0236 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 inthe configuration of your 'Managed Nodes'. A message contains a nodeattribute that does not correspond to any of the ITO operators' managed

232 Chapter 2


nodes. For this reason the color of a node on the OpenView submapscould not be set according to the severity of the message. This canhappen if the ITO administrator has changed your configuration duringthe current ITO operator session. To get the new configuration, exit ITOand log on again.

OpC60-0250 Can't get message for the browser from database.

A message that has been unacknowledged by another ITO operator cannot be written back into your main `Message Browser'. The attempt toretrieve it from the database failed. Another ITO operator shouldacknowledge the message and then unacknowledge it again. If the errorappears again, restart the user interface.

OpC60-0255 Your acknowledge request can not be served.Unable to compose an acknowledge list.

Try to perform the same acknowledge request again. If this does notwork, try to acknowledge the messages in smaller portions.

OpC60-0261 Warning: Cannot disconnect from database.This may cause troubles if ITO is not terminatedproperly (Display receiver process opcdispr hangs).

This may cause troubles if ITO is not terminated properly (displayreceiver process, opcdispr, hangs). To be sure that this does not lead toany further problems, exit ITO and log on again. If the ITO session cannot be terminated properly, look for any remaining display receiverprocesses. Use the command: `ps -ef | grep opcdispr' to review thedisplay receiver processes running. If a display receiver doesn't have anassociated ITO parent process (third column is `1' (one)) kill this displayreceiver process: kill <process-id> (<process-id> = second column in `ps'output).

OpC60-0292 Cannot read the contents of the current workingdirectory "< x1>". If you are using SQL*Net, thedatabase connect may fail.

Under normal circumstances, you should set and export environmentvariable $OPC_HOME to a directory that you can change to, read fromand write into. If you don't want to do that then ITO will try to changeinto $HOME. Failing that, ITO will change into /tmp. If you haveinsufficient permissions for even this directory you may well haveproblems when working with the GUI later on.

Chapter 2 233


OpC60-0293 Cannot write to the current working directory"< x1>". When saving files you will have to specifya different directory.

Under normal circumstances, you should set and export environmentvariable $OPC_HOME to a directory that you can change to, read fromand write into. If you don't want to do that then ITO will try to changeinto $HOME. Failing that, ITO will change into /tmp. If you haveinsufficient permissions for even this directory you may well haveproblems when working with the GUI later on.

OpC60-0300 First finish the editing task already startedbefore beginning a new task.

You have already opened a sub window for another task. The openedwindow might be iconized or hidden by another window. You must finishor cancel this task before you are able to continue.

OpC60-0301 The syntax for specification of the Message Type isinvalid.

A syntax error was detected in the message type pattern definition.Check the syntax of the pattern by invoking context-sensitive help forthe pattern field.

OpC60-0302 Invalid time format ( valid is "1h40m10s" ).

The specified time format is invalid. You may enter a number only, whichis interpreted as seconds, or you may use 'h' for hours, 'm' for minutesand 's' for seconds. For example: 12h45m11s

OpC60-0303 Invalid Interval specified. A specification less than<x1>s is not allowed.

The specified time interval is invalid or too short. There is a minimumvalue required. A value less then this minimum would make no sense,since the affected processes would probably encounter performanceproblems.

OpC60-0304 Too many separators defined. Not more than < x1> areallowed.

234 Chapter 2


You are not allowed to specify more than n separators. The defaultseparators are blank and the tab character (specified as \t) if you leavethe field empty. A valid specification would be '.\n \t' for the use of theseparators, '.', carriage return, blank and tab.

OpC60-0305 Invalid timespan specified. A specification less than<x1>s is not allowed.

The specified time interval is invalid, or too short. There is a minimumvalue required. A value less then this minimum would make no sense,since the value is used to detect duplicate messages. Use the option onlyfor messages which might appear in a specific time period again, as anduplicate.

OpC60-0306 The re-send time specification must be 0, or greaterthan the time span.

The specified time interval is invalid or too short. The value must begreater then the time span, because it determines the time after whichyou want to re-send suppressed duplicate messages.

OpC60-0307 The Node (< x1>) is not defined within ITO yet.

The specified node is not known within ITO. You may only use nodeswhich are already defined within ITO (Node Bank), because it is notpossible 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.

OpC60-0308 The syntax for specification of the text pattern isinvalid.

A syntax error was detected in the message text pattern definition.Check the syntax of the pattern by invoking context-sensitive help forthe pattern field.

OpC60-0309 The content of the field is invalid or contains areference to an unknown parameter.

You may only use reference parameters which are reserved words forITO, or user-defined parameters.

OpC60-0310 The syntax for the specification of the Enterprise isinvalid.

Chapter 2 235


The format of the specified enterprise is invalid. The enterprise has theformat of A.B.C.D..., where A, B, C, and D are subidentifiers in decimalnotation. For example, a valid enterprise is 1.3.6.1.4.1.11.2.3

OpC60-0311 The syntax for the list is invalid. Multiple values mustbeseparated with the use of the "|" character.

A list of elements can be only specified by the use of '|' (bar) as theseparator.

OpC60-0312 The syntax for the node list is invalid. Multiple nodesmust beseparated with the use of the "|" character.

A list of elements can be only specified by the use of '|' (bar) as theseparator.

OpC60-0313 The field contains an invalid node name or a reference toan unknownvariable.

The specified node is not known within ITO or you used an invalidreference parameter ( reserved word for ITO or user-defined parameter ).You may only use nodes which are already defined within ITO (NodeBank), because it is not possible to perform actions on nodes which arenot managed by ITO.

OpC60-0314 A template with the same name already exists. Use aunique name for the template.

There already exists a template with the same name. Make sure that thename is unique, because the name will be used later, to assign thetemplate to nodes.

OpC60-0315 Message Group "Misc" is a reserved group and may not beused.

The message group (Misc) has a special meaning, and may not be usedhere. It is used to hold all messages which are assigned to a messagegroup which is not yet defined within ITO.

OpC60-0321 An instruction interface with the same name alreadyexists. Use a unique name for the instruction interface.

236 Chapter 2


There already exists an instruction interface with the same name. Makesure that the name is unique, because the name will be used later, toassign the instruction interface to templates or conditions.

OpC60-0323 A condition with the same description already exists.Please use aunique description for the condition.

You are not allowed to use the same description text for two differentconditions. Please use a unique description.

OpC60-0326 Unable to delete download specification file < x1>.

ITO could not delete the old Download Specification File. You gave theOK to delete this file before writing a new one, but for some reason, ITOcould not delete it. Perhaps it is on a read-only file system.

OpC60-0327 Please specify a path for the download directory.

This is an information message. ITO successfully wrote the desiredDownload Specification File into the specified directory.

OpC60-0329 ITO Download Configuration

Watch this window for messages on the progress of the ConfigurationDownload that you just started.

OpC60-0330 A node must be selected for the requested report.

A report was requested for a specific node, but no node was previouslyselected. Select a single node on one of the HP OpenView map windows,and activate the report again.

OpC60-0331 A nodegroup must be selected for the requested report.

A report was requested for a specific nodegroup, but no nodegroup waspreviously selected. Select a nodegroup from the Node Group Bank mapand activate the report again.

OpC60-0332 A messagegroup must be selected for the requestedreport.

A report was requested for a specific message group, but no messagegroup was previously selected. Select a message group from the MessageGroup map, and activate the report again. The report can only beinvoked for a single message group at a time.

Chapter 2 237


OpC60-0333 An application must be selected for the requestedreport.

A report was requested for a specific application, but no application waspreviously selected. Open the Application Desktop window. Select asingle application, and activate the report again. The report can only beinvoked for one application at a time.

OpC60-0334 A user must be selected for the requested report.

A report was requested for a specific operator, but no operator waspreviously selected. Open the User Bank window first. Select oneoperator and activate the report again. The report can only be invokedfor a single operator at a time.

OpC60-0335 Please select one or more messagesin the corresponding browser before tryingto run this report.

A report was requested for a specific message in the Message Browser,but no message was previously selected. Open the Message Browserwindow first. Select one message and activate the report again. Thereport can only be invoked for a single message at a time.

OpC60-0336 An error occurred during generation of the report.

The specified report generation failed, due to an error with the databasereport writer. Check that the report specification file for the requestedreport is available and accessible for user root and opc_op. The reportspecification 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 alsobe 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 useropc_op: runrep20 userid=/@P:openviewmodule=/usr/OV/conf/OpC/mgmt_sv/reports/C/<filename>

OpC60-0337 Could not open runtime file (< x1>) with reportinformation.

The configuration file for the ITO reporting utility is not accessible.Check that the listed file for the report configuration is available and hasread permission for everyone. If the file is not available, create, at least,an empty file.

238 Chapter 2


OpC60-0338 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 isallowed to open the file listed. The ITO Administrator generally accessesfiles as the user root. ITO Operators create all files as user opc_op.

OpC60-0339 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 isallowed to create the listed file. The ITO Administrator generallyaccesses files as user root. ITO Operators create all files as user opc_op.

OpC60-0340 A template must be selected for the requested report.

A report was requested for a specific template, but no template waspreviously selected. Open the Message Source Templates window first.Select one template from the list, and activate the report again. Thereport can only be invoked for a single template at a time.

OpC60-0341 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 errorwith the configured report program. Check that the listed UNIX programfile is available and executable. The ITO Administrator generallyaccesses 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.

OpC60-0342 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 currentuser is allowed to read the file. The ITO administrator generally accessesfiles as user root. ITO Operators create all files as user opc_op.

OpC60-0343 Could not write output file.

The report output file could not be generated by the ITO reportingfacility. Check that the file permissions are set correctly, and that thecurrent user is allowed to write to the file. The ITO Administratorgenerally access files as user root. ITO Operators create all files as useropc_op.

Chapter 2 239


OpC60-0345 No report selected.

No report was selected in the report list. Select a report from the list, andactivate the report again.

OpC60-0348 The report writer call returned an error: < x1>

To produce an Oracle report writer report, ITO calls the Oracle reportwriter 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 useropc_op must be able to execute the report writer binary.

• Is the environment variable ORACLE_HOME set correct (seeinstallation guide).

OpC60-0350 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 validnumeric value again.

OpC60-0351 File (< x1>) could not be opened.

The reference testfile either does not exist, or is not readable by theUNIX user, root. Check that the file listed has the correspondingpermissions, and that user root is able the read it.

OpC60-0352 File (< x1>) was not found or is not an executable programor script.

The given file either does not exist, or is not executable by the UNIX userroot. Check that the file listed has the corresponding permissions, andthat the user root is able to execute it.

OpC60-0409 Unable to automatically determine the node typefor node < x1>.

The method to automatically determine the node type is SNMP GET. Inorder for SNMP GET to work, make sure that

• the snmp daemon is working on the affected node and

240 Chapter 2


• the following entry exists (for HP-UX) on the node in file/etc/snmpd.conf: 'get-community-name:' or 'get-community-name:public'.

OpC60-0410 Unable to automatically determine the node typefor node < x1>, since SNMP OPEN fails.

The method to automatically determine the node type is SNMP GET. Inorder 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'.

OpC60-0460 Invalid node specification found.

The value in the node field of the action specification is neither an ITOmanaged node nor a valid parameter. To get more information about thenode specification syntax, click on the node field and press <F1>.

OpC60-0520

ITO could not find an Application Registration File for the integratedOpenView Application that you have specified in your ITO configured OVApplication or Action. Without this Application Registration File, ITOwill not be able to start the Action or Application you have specified. Soyou must find out where the Application Registration File for your newOV Application/Action is and copy it to the given location. Also, you mustrename the copied file to the name given in the error message or elsechange the symbolic link (i.e. delete it and create a new one) that ITOcreated to point to the copied file.

OpC60-0521 Cannot open hpterm or run script/program(/usr/bin/X11/hpterm or thedesired shell script or program returned an error).

ITO could not start a terminal on your display. This would be hpterm foran HP system or xterm for another system. Perhaps you don't haveenough free memory or too many processes or open files. Possibly theterminal could be started but the program or script that was calledreturned an error-status.

Chapter 2 241


OpC60-0544 Could not find the application registration filefor the integrated application "< x1>" under thedirectory "< x2>".For ITO Motif GUI users to be able to use theapplication, the ITO Administrator must add asymbolic link to the correct application registrationfile. For example:# ln -s /opt/OV/NewApplication/registration/C/NewApplArf\/etc/opt/OV/share/conf/OpC/mgmt_sv/appl/registration/CAfter the symbolic link has been added you must restartyour GUI if you want to use this ovw-integratedapplication.

The ITO administrator must add a symbolic link to the correctapplication registration file that contains an 'Application: <applname>'line, under the/etc/opt/OV/share/conf/OpC/mgmt_sv/appl/registration/<lang> directory.

OpC60-0545

Ask the system administrator of the management server to check that avalid entry for 'opcgrp' exists in the system group file /etc/group or/etc/logingroup.

OpC60-0613 Unable to activate management server.

Connection to display manager lost. Verify that the ITO managementserver processes are running. If not, restart them. Do this either from theadministrator user interface, or execute the command:/usr/OV/bin/OpC/opcsv -start

OpC60-0614 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/timeand/or message attribute criteria.

242 Chapter 2

ITO Error MessagesNT installation messages

NT installation messages

OpC130-0001 E-> Error from < x1>.

An internal error has occurred. Report the function name and errornumber to your HP Response Center.

OpC130-0002 E-> Error from < x1> for < x2>.


OpC130-0003 U-> Unknown return value from < x1>. errno=< x2>.


OpC130-0004 E-> Unable to convert < x1>.


OpC130-0005 U-> Invalid parameter for < x1>. nr=< x2>.


OpC130-0006 T-> Tracing information: < x1> < x2> < x3>.

This is a tracing message from the NT setup program.

OpC130-0007 U-> Unknown return value from < x1> for < x3>. errno=< x2>.


OpC130-0008 usage: < x1> [-n|-u|-s||-h|[-p < drive>] [-f]] -n complete interactive Installation (initiated fromremote) -u uninstall complete installation -s setup the ITO Agents(User/Service/Path/Filepermissions)

Chapter 2 243


-p < drive> setup the ITO Agents(User/Service/Path/Filepermissions) in pre-installedmode 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 commandline.

OpC130-0010 I-> Setup program started (preinit).

Informational message that the setup on NT was started.

OpC130-0011 I-> Setup program started at < x1>. It may need some time.

Informational message that the setup on NT was started.

OpC130-0012 I-> Setup program successfully finished.

Informational message that the setup on NT has finished.

OpC130-0013 E-> Setup program aborted.

There was a problem during the installation. Look into the tracefile tofind out more about the problem.

OpC130-0020 I-> Installing HP ITO Agent on drive < x1>.

Informational message that the setup on NT is installing the agent onthe said drive.

OpC130-0021 I-> Starting to remove the HP ITO Agent from drive < x1>.

Informational message that the setup on NT is removing the agent fromthe said drive.

OpC130-0022 I-> Starting the reinstallation of the HP ITO Agent ondrive < x1>.

Informational message that the setup on NT is re-installing the agent onthe said drive.

OpC130-0023 I-> Configuration installed.

244 Chapter 2


Informational message that the setup has finished installing theconfigurational data.

OpC130-0024 I-> The opcinfo file was updated.

The opcinfo file was successfully updated by the NT installationprogram.

OpC130-0025 I-> From opcsetup.inf found destination drive < x1>.

Informational message that the setup found the given drive asinstallation drive in the opcsetup.inf file.

OpC130-0026 I-> Installed source for event log messages < x1>.

Informational message telling that the source for the NT installationmessage that are written into the NT eventlog are registered with theNT eventlog service.

OpC130-0028 I-> Writing this information into the opcinfo file.Management Server is < x1>. Installation Time is < x2>.

Informational message that tells which management server is writteninto the opcinfo file.

OpC130-0030 I-> Found backup domain controller < x1>.

This is just an informational message that lists the first found backupdomain controller in the domain the node is in.

OpC130-0031 I-> No backup controller in domain < x1>.

Informational message that there was no backup domain controllerfound in the domain the node is in.

OpC130-0032 I-> This system is standalone.

Informational message stating that the node is a standalone system.

OpC130-0033 I-> This system is a primary controller in domain < x1>.

Informational message stating that the node is a primary domaincontroller.

OpC130-0034 I-> This system is a backup controller in domain < x1>.

Chapter 2 245


Informational message stating that the node is a backup domaincontroller.

OpC130-0035 I-> This system is a workstation in domain < x1>.

Informational message stating that the node is a workstation in adomain.

OpC130-0040 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.

OpC130-0041 I-> An installed version of ITO was found on drive < x1>.

The setup program for NT found an agent already installed on thenamed drive.

OpC130-0042 I-> Will check all drives on system.

Informational message that all drives are searched.

OpC130-0043 I-> Checking Drive < x1>.

Status message of the setup program saying that the named drive ischecked.

OpC130-0045 I-> Filesystem on drive < x1> is not NTFS.

The checked filesystem is not an NTFS filesystem, but may be a FAT orHPFS filesystem.

OpC130-0046 I-> Not enough free space on drive < x1>.

The free space used to install the NT agent is not sufficient on the nameddrive.

OpC130-0047 I-> Destination for the setup is drive < x1>.

Informational message stating which drive is the target drive for theinstallation.

OpC130-0048 W-> The volume < x1> does not contain a recognized filesystem.

The checked filesystem is not an NTFS filesystem.

246 Chapter 2


OpC130-0050 I-> Copied file < x1>.

Status message of the setup program stating that the given file wassuccessfully copied.

OpC130-0051 I-> Set rights on < x1>.

Status message of the setup program stating that the file rights for thegiven file were successfully set.

OpC130-0052 I-> Finished transfering files.

Status message of the setup program stating that the transfer of the NTagent files has finished successfully.

OpC130-0053 I-> Finished deleting source files.

Status message of the setup program stating that the deletion of the NTagent files has finished successfully.

OpC130-0054 I-> Finished setting file rights

Status message of the setup program stating that the setting of the filerights has finished successfully.

OpC130-0055 I-> The file < x1> could not be copied to its target < x3>.Therefore it is copied to < x2> for the moment and will bemoved to the correct place after the next reboot when thetargetfile is not locked.

A file could not be copied at the moment. It is scheduled to be moved inplace after the next reboot.

OpC130-0056 E-> The architecture string < x1> is invalid.

The architecture string could not be used to access the software packageon the installation server.

OpC130-0060 I-> Created new user account < x1>.

A new user account was created on the NT node. This account is used forthe NT ITO agent.

OpC130-0061 I-> Added privileges for user account < x1>.

Privileges were added to the given user account.

Chapter 2 247


OpC130-0062 I-> Installed service < x1>.

The given service was registered with the NT service manager.

OpC130-0071 I-> Removed all privileges of < x1>.

All privileges for the given user were removed by the setup program.

OpC130-0072 I-> Removed the user account < x1>.

The user account was successfully removed.

OpC130-0073 I-> Account < x1> not removed because it may be needed onthe 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.

OpC130-0074 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.

OpC130-0075 I-> Service < x1> was deleted.

The service was deleted successfully.

OpC130-0076 W-> Unable to delete user profile for user < x1>.

The user profile for the given user cannot be deleted. If you encounterthis problem with Windows NT 4.0, please remove the profile manuallywith the Control Panel 'System'.

OpC130-0077 W-> Unable to delete user profile for user < x1> (SID<x2>).

The user profile for the given user cannot be deleted. If you encounterthis problem with Windows NT 4.0, please remove the profile manuallywith the Control Panel 'System'.

OpC130-0078 I-> Successfully deleted the user profile for user < x1>(SID < x2>).

Informational message that the user profile was successfully deleted.

OpC130-0080 E-> Trouble registering the event source < x1>.

248 Chapter 2


The installation program was not able to register the given event source.HP ITO Agent Messages sent to the Eventlogging mechanism will not beresolvable.

OpC130-0081 E-> Trouble accessing the system event log.

The System Event log could not be opened. Please check with the NTEventviewer for problems.

OpC130-0082 E-> System event log is full. Please clean up Systemevent log or change Event logfile size or wrapping mode.

The System Event log is full. Setup messages of the HP ITO Agent willnot be sent to the System Event log.

OpC130-0085 E-> The Schedule service is disabled. Please call thescript < x1> manually to remove the HP ITO agentcompletely.

The Scheduler is disabled. The remove script could not be runautomatically. Please run the given script manually in a CommandPrompt to remove the HP ITO Agent files.

OpC130-0090 I-> Backing up HP ITO agent file < x1> to < x2>.

This is just an informational message. The backup of the agent files isdone each time a new agent is installed. This backup will be used torestore the agent files in case the installation of the new files failed.

OpC130-0100 W-> Could not find opcsetup.inf file.

The installation program was unable to find the opcsetup.inf file thatcontains information about the installation parameters.

OpC130-0101 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 ITOagent. The ITO agent requires 10MB of free space on a local NTFSformatted disk.

OpC130-0102 I-> Didn't find an installed HP ITO Agent.

There was no ITO agent found.

OpC130-0103 W-> Don't know the version of the agents.

Chapter 2 249


There is an ITO agent installed, but the installation program is unable toretrieve the version of that.

OpC130-0104 I-> NOTE: ITO software, version < x1> installed on system<x2>, will be reinstalled.

There was already an agent installed, but it will be reinstalled.

OpC130-0150 W-> No password specified. Generating a random one.

This message is not an error, but is provided for your information.

OpC130-0151 W-> Generating a random password for the account on thisnode. Since this is a primary domain controller you willhave to change it to a known password when you want toinstall the agent to a Backup Domain Controller in thisdomain.


OpC130-0152


OpC130-0153 W-> The given password is too long. It will be cut afterthe first < x1> characters.


OpC130-0154 E-> Decrypting the password returns an error. Willgenerate a random password and continue.

There was an internal error in the password encryption/decryptionfunctionality.

OpC130-0156 E-> Encountered an unknown NT error code < x1> whilecalling NT API function '< x2>'.

A call to an NT API function failed with an error, but the error codecannot be resolved to an NT error message.

OpC130-0157 E-> The call to the NT API function '< x2>' failed withthe following system error: < x1>

A call to an NT API function failed with the given error.

250 Chapter 2


OpC130-0158 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.

OpC130-0200 E-> More than one primary domain controller in domain<x1>.

Make sure your domain is set up correctly.

OpC130-0210 E-> Timeout from startup < x1>.

The service could not be started. Check if the user for the service existsand if the password is correct. Check for additional tracing of the serviceprogram.

OpC130-0211 E-> The Control Agent didn't register at the RPC Serveror has already terminated!

There was an error starting up the control agent. Check for additionaltracing of the agent.

OpC130-0221 E-> File < x1> exists and can not be overwritten.

There was an error copying the file. Verify that the file exists, is notcurrently being used, and has the correct permissions.

OpC130-0222 E-> File < x1> can not be copied (File not found).


OpC130-0223 E-> File < x1> can not be copied (Access denied).


OpC130-0224 E-> File < x1> can not be copied because it is in use byanother process.


OpC130-0230 E-> Couldn't lookup account < x1>.

Check to make sure that the user account actually exists. Check forprevious error messages during the installation.

Chapter 2 251


OpC130-0231 E-> Group < x1> not found.

Check to make sure that the group actually exists. Check for previouserror messages during the installation.

OpC130-0232 E-> User < x1> does not exist.


OpC130-0233 E-> Invalid account type of user < x1>.


OpC130-0234 E-> Access denied while adding user < x1> to group < x2>.

Check to make sure that the installation program runs with theappropriate administrative rights.

OpC130-0235 E-> Access denied while installing the user < x1>.

Check to make sure that the installation program runs with theappropriate administrative rights.

OpC130-0240 E-> No Password for the new user. Can't install user<x1>.

Check for previous error messages.

OpC130-0241 E-> No Password for user < x1>. Can't install service<x2>.

Check for previous error messages.

OpC130-0242 E-> User < x1> exists though it could not be looked upbefore.

An internal error has occurred. Report to your HP Response Center.

OpC130-0243 E-> Password too short or too long.

This may be caused by special settings in your password policy. Use adifferent password.

OpC130-0244 E-> Password Check: User < x1> not found.

252 Chapter 2



OpC130-0252 E-> Failed to stop service < x1>.

There was an error stopping the service. Check for additional tracing ofthe agent.

OpC130-0254 E-> Invalid user account < x1>.

Check to make that the user account actually exists. Check for previouserror messages during the installation.

OpC130-0255 E-> The service < x1> has been marked for deletion.

The service seems to be still running. Shut it down manually and retry. Ifthis happens again report to your HP Response Center.

OpC130-0256 E-> Failed to install service < x1>.

The service was not successfully installed. Check for previous errormessages.

OpC130-0257 E-> The Schedule service is disabled on node < x1>.

The Schedule service may not be disabled because it is used to executeprograms on other nodes. Re-enable the Schedule service on the NT nodeand try again.

OpC130-0260 E-> This is a backup controller. The user < x1> does notexist in the domain < x2>. Please install the HP ITOAgents on the primary domain controller < x3> first.

Since a backup domain controller does not have local users it has to usethe domain HP ITO account with the password setting that was createdon the primary domain controller. This must be done before the backupdomain controller can be installed.

OpC130-0261 E-> This is a backup controller. The password given foruser < x1> is wrong. Please reinstall and give thepassword that is set on the primary domain controller<x2> for this user.

Chapter 2 253


Since a backup domain controller does not have local users it has to usethe domain HP ITO account with the password setting that was createdon the primary domain controller. This must be done before the backupdomain controller can be installed.

OpC130-0262 E-> This is a primary controller. The password given foruser < x1> is wrong. Please reinstall and give thepassword that is set for the agent on the backup domaincontroller < x2> for this user.

See message.

OpC130-0270 E-> Can't find out my managment server's name.

The installation program cannot report to the management server aboutthe installation. Check for previous error messages.

OpC130-0271 E-> Connection error to management server < x1>.

Make sure that all server processes are running on the managementserver.

OpC130-0272 E-> Agent status could not be reported to managementserver < x1>.

Make sure that all server processes are running on the managementserver.

OpC130-0275 E-> Don't know which version was installed before.

The installation process found an old ITO agent, but cannot resolve itsversion. Deinstall the old agent before installing the new one.

OpC130-0276 E-> Don't know the version of the new agents.

This is an internal error message. Please look for previous errors.

OpC130-0277 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 thenamed management server to reinstall the agent software.

OpC130-0278 I-> NOTE: ITO software, version < x1> installed on system<x2>, will be replaced by version < x3>.

254 Chapter 2


A previous version of the agents were already installed and will beoverwritten now.

OpC130-0280 E-> Unable to retrieve the domain controllers of thecurrent domain < x1>. Maybe the PDC is down orunreachable. Please check and try again.

The setup program was not able to retrieve the domain controllers forthe domain the node is in. Please check if the domain configuration iscorrect and if the computer browser service is working.

OpC130-0281 E-> The retrieval of the domain controllers was denied,because of insufficient access rights. Please check andtry again.


OpC130-0282 E-> The retrieval of the domain controllers failed,because the remote computer is not available. Pleasecheck and try again.


OpC130-0283 E-> The retrieval of the domain controllers failed,because the remote computer currently handles as muchrequests as the computer can accept. Please check andtry again.


OpC130-0284 E-> The retrieval of the domain controllers failed,because the needed service is not started. Please checkand retry.


Chapter 2 255


OpC130-0285 E-> The retrieval of the domain controllers failed,because the password is invalid. Please check and retry.


OpC130-0300 I-> Installation Server: Initiating the startup of thesetup program on node < x1> (NT name is < x2>).

The installation server will start the installation of the new node.

OpC130-0301 I-> Installation Server: Setup program is scheduled onnode < x1>.

The setup program will be started on the new node.

OpC130-0302 E-> Installation Server: Tracing of EventLog for node<x1> aborted.

There was an internal error during the tracing of the installation of thenew node. There won't be any more progress messages about theinstallation of that node.

OpC130-0303 E-> Installation Server: Timed out while waiting for theend of the installation program on node < x1>. Probablyaborted. Please look on the node directly.

It took too long to install the new node. The installation program hasprobably aborted without informing the installation server. Check in theinstallation tracefile on the new node for errors.

OpC130-0304 <x1>

This is a progress message of the installation.

OpC130-0305 I-> Installation Server: The local reinstallation of newITO Agent Software will be started. There won't be anyprogress messages during the installation because theold agents have to be shut down. One of the next messagesof the new node will be '...successfullydistributed...'. After that you can look into theinstallation log for the status of the setup.

See message text.

256 Chapter 2


OpC130-0306 E-> Installation Server: The local reinstallationfailed, because the installation program could not befound under < x1> or < x2>. Please shutdown the agent onyour managed node and call the installation programopc_inst.bat from your local FTP directory on yourmanaged node.

See message text.

OpC130-0310 E-> Installation Server: Access denied from node < x1>.Verify the trust relationship between both domains.

Verify the trust relationship between both domains.

OpC130-0311 E-> Installation Server: The Schedule service isdisabled and cannot be started on node < x1>.

The Schedule service may not be disabled because it is used to executeprograms on other nodes.

OpC130-0312 E-> Installation Server: Could not find out remote timeof node < x1>.

The management server could not get the remote time of the node. Checkto make sure that <node name> is really a Windows NT system.

OpC130-0313 E-> The Schedule service was not started correctly onnode < x1>.

The Schedule service must be running on the new node because it is usedto execute programs. Check locally on the node if there are problems.

OpC130-0314 W-> Installation Server: Increasing the delay counterfor node < x1>. It seems to be a slow connection. Notreally a problem.

The connection between the installation server and the new node isslower than expected. This is not an error, but a notification of aproblematic connection.

OpC130-0320 E-> Installation Server: The Installation Server serviceis not configured on this node. Therefore it cannotinitiate the installation to node < x1>.

This machine cannot be used as an installation server because it is not aprimary domain controller.

Chapter 2 257


OpC130-0321 E-> Installation Server: Startup of the InstallationServer service failed. Therefore it cannot initiate theinstallation to node < x1>.Is the password in the service startup screen the same asthe one given for the account?Make sure that in the User Properties neither the 'UserMust Change Password at Next Logon' nor the 'AccountDisabled' fields are marked.

Make sure that in the User Properties neither the 'User Must ChangePassword at Next Logon' nor the 'Account Disabled' fields are marked.

OpC130-0322 E-> Installation Server: The configuration files for theinstallation of node < x1> could not be created.

There was an internal error during the creation of the configuration filesof the new node. Check for additional tracing of the program.

OpC130-0323 E-> Installation Server: The agent package for theinstallation of node < x1> could not be copied to thisnode.

There was an internal error during the transfer of the software packageof the new node. Check for additional tracing of the program.

OpC130-0324 E-> Installation Server: Don't know the remote node < x1>.

The installation server does not know the new node. Verify that yourWindows NT environment is set up correctly.

OpC130-0325 E-> Installation Server: The administrative share < x1>does not exist on remote node < x2>.

The installation server uses the administrative share to access theremote disk. If this does not exist in your environment (in violation of theMicrosoft standard), report to the HP Response Center.

OpC130-0326 E-> Installation Server: Path < x1> does not exist onremote node < x2> on network name < x3>.

Check for the existence of the path on the new node. Create it manuallyif it does not exist.

OpC130-0327 W-> Installation Server: The configuration files for theinstallation of node < x1> could not be deleted.

258 Chapter 2


There was an internal error deleting the configuration files for the newnode. Check for additional tracing of the program.

OpC130-0328 E-> Installation Server: Cannot match the HostName < x1>to an NT name and therefore cannot access the remote NTnode.

The IP hostname and the NETBIOS name cannot be matched. Pleasecheck the network settings for this node.

OpC130-0329 E-> Installation Server: Local Path < x1> does not exist.

The given path could not be found.

OpC130-0330 E-> Installation Server: Unable to copy file to < x1> onremote node < x2> on network name < x3>: Unknown networkerror occurred.

The installation server was not able to copy the given file, because annetwork error occurred.

OpC130-0331 E-> Installation Server: Transfer of defaultconfiguration files to new node failed. See previouserror messages for details.

The transfer of the configuration files failed. Please see previous errormessage for details.

OpC130-0400 I-> Deinstall: Deinstalling node < x1>. In case of successthere won't be any more messages from this node.

This message is provided for your information, and does not denote anerror.

OpC130-0401 E-> Deinstall: The Schedule service is disabled andcannot be started on node < x1>.

The Schedule service may not be disabled because it is used to executeprograms on other nodes.

OpC130-0500 The Host Name that is configured in the TCP/IP Protocolsettings is < x1>. This name does not match the name < x2>returned from the DNS.

Chapter 2 259


For the moment we will try to continue with this settingbut you should make sure that this is correctlyconfigured.

For the moment we will try to continue with this setting but you shouldmake sure that this is correctly configured.

OpC130-0501 The Computer Name that is configured in the Networksettings is < x1>. This name does not match the name < x2>returned from the DNS.For the moment we will try to continue with this settingbut you should make sure that this is correctlyconfigured.

This error may occur if you have changed the name of a Windows NTsystem. If you have changed the name of the computer you must reinstallthe ITO agent.

OpC130-0502 The Host Name that was returned from the DNS during theinstallation 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 toreinstall the ITO agent.

This error may occur if you have changed the name of a Windows NTsystem. If you have changed the name of the computer you must reinstallthe ITO agent.

OpC130-0510 Not all agents terminated in time.

One or more of the agent processes didn't terminate. Kill them manuallyor reboot the system.

260 Chapter 2

ITO Error MessagesSecurity related messages (commands and modules)

Security related messages (commandsand modules)

OpC140-0100 Can't init Security API.

This error could indicate out of memory, a corrupted skey.sdb file or adatabase problem (check qualifying error message).

OpC140-0101 Can't get the security session.

This error could indicate out of memory, that a secret key was not foundalthough configured, or the public key session negotiation returned acommunication error.

OpC140-0102 Can't set the security session.

This error could indicate out of memory, that a secret key was not foundalthough configured, or the public key session negotiation returned acommunication error.

OpC140-0103 Error during message encryption/compression.

A message could not compressed and/or encrypted. This could indicateout of memory.

OpC140-0104 Error during message decryption/decompression.

A message could not decrypted and/or uncompressed. This could indicateout of memory, or data corruption (check more qualifying error message).

OpC140-0105 Error during action request encryption/compression.

An action request could not compressed and/or encrypted. This couldindicate out of memory.

OpC140-0106 Error during action request decryption/decompression.

An action request could not decrypted and/or uncompressed. This couldindicate out of memory, or data corruption (check more qualifying errormessage).

Chapter 2 261


OpC140-0107 Error during action response encryption/compression.

An action response could not compressed and/or encrypted. This couldindicate out of memory.

OpC140-0108 Error during action response decryption/decompression.

An action response could not decrypted and/or uncompressed. This couldindicate out of memory, or data corruption (check more qualifying errormessage).

OpC140-0109 Error during message operation encryption/compression.

A message operation could not compressed and/or encrypted. This couldindicate out of memory.

OpC140-0110 Error during message operation decryption/decompression.

A message operation could not decrypted and/or uncompressed. Thiscould indicate out of memory, or data corruption (check more qualifyingerror message).

OpC140-0111 Can't read nodeinfo parameters for security type andversion.

Error reading network security protocol parameter OPC_NSP_TYPEand OPC_NSP_VERSION from nodeinfo file.

OpC140-0113 The generation of the hash value failed.

Internal Error. A hash value could not generated.

OpC140-0114 Invalid cookie after uncompression of data!

The data could not successfully uncompressed. Data seems to becorrupted.

OpC140-0115 The received MAC differs from the calculated. Data wasmodified!

A generated hash value over the data differs from the received one. Thedata seems to be corrupted.

OpC140-0116 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 Can't connect to session process '< x1>'

Communications error occurred during public key session establishment.Check more qualifying error message.

OpC140-0118 Remote procedure call for setting a session failed!


OpC140-0119 Remote procedure call for getting a session failed!


OpC140-0120 Error during encryption of a data block.

Could indicate out of memory.

OpC140-0121 Error during decryption of a data block.

The received data block could not decrypted. This indicates out ofmemory, or corruption (check more qualifying error message).

OpC140-0131 Can't create the pre master secret

Internal error.

OpC140-0132 Can't load public keys for client and server fromcertificate store

Could indicate a corrupted certificate store (certs.sdb).

OpC140-0133 Can't create the Client Hello

Internal protocol error.

OpC140-0134 Can't create hash for Server Hello and ServerCertificate message


OpC140-0135 Can't create hash for Client Verify message


OpC140-0136 Can't create hash for Finished message

Chapter 2 263



OpC140-0137 Received an invalid server id in Server Hello(Got:'< x1>', Have:'< x2>')

Could indicate a corrupted reply packet of a Client Hello. The expectedvalue was not part of the received data.

OpC140-0138 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.

OpC140-0139 Certificate mismatch! The received certificate isdifferent 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.

OpC140-0140 Server Certificate hash mismtch! The received ServerCertificate hash differs from the locally generated one

Could indicate corrupted data. Re-start the agent.

OpC140-0141 Can't parse Server Hello and Server Certificate message


OpC140-0142 Can't create Client Key Exchange message


OpC140-0143 Can't create Client Verify message


OpC140-0144 Can't connect to session process '< x1>'


OpC140-0145 Remote procedure call for phase 1 failed!


OpC140-0146 Phase 1 of the session establishment failed!

264 Chapter 2



OpC140-0147 Can't read my private key!

Check public key store 'pkey.sdb' for corruption.

OpC140-0148 Can't create reply messsage of phase 1 to client


OpC140-0149 Invalid protocol received: < x1>


OpC140-0150 Can't parse Client Hello


OpC140-0151 Remote procedure call for phase 2 failed!


OpC140-0152 Client rejected! No handshake info found for '< x1>' inphase 2


OpC140-0153 Client Verify hash mismtch! The received Client Verifyhash differs from the locally generated one


OpC140-0154 Finished message mismatch! The received Finish messageis different from the locally generated


OpC140-0155 Can't parse Phase 2 from client


OpC140-0156 Can't create Finish message


Chapter 2 265


OpC140-0171 Error during phase 1 handshaking from '< x1>'


OpC140-0172 Error during phase 2 handshaking from '< x1>'


OpC140-0173 Can't set the session to '< x1>'


OpC140-0174 Can't get the session to '< x1>'


OpC140-0181 Can't create RSA signature

Internal error.

OpC140-0182 Signature verification failed

Internal error.

OpC140-0183 Can't create RSA public and private key

Internal error.

OpC140-0184 Public key encryption failed

Internal error.

OpC140-0185 Public key decryption failed

Internal error.

OpC140-0186 Private key encryption failed

Internal error.

OpC140-0187 Private key decryption failed

Internal error.

OpC140-0188 DES encryption failed

Internal error.

266 Chapter 2


OpC140-0189 DES decryption failed

Internal error.

OpC140-0201 Can't set the session context

Internal error.

OpC140-0202 Can't get the session context

Internal error.

Chapter 2 267

openview operations error messages

Documents