OVNM 5.3 - Operations Agent for NonStop Object Configuration Client Guide

Appendix F: OCC Errors 93
Appendix F: OCC Errors
Error
Description
Invalid Manager Name Configuration Invalid entry in the Manager Name field in the Threshold dialog box. This field is
not available for all the subsystems. For example, Manager name for BASE24
objects has to be the NCP process that owns the resource node and must have
been defined during the installation or using ALTROVNM before starting OCC.
Invalid Object Name Configuration
Invalid entry in the Objects field in the Threshold dialog box. This should contain
the object name for the selected subsystem. Wildcard characters are allowed for
most of the subsystems.
Invalid EMS Owner. Subsys
Configuration
Invalid entry in the Owner.Subsystem field in the Threshold dialog box. This field is
available for the EMS subsystem.
Examples of valid entries are: TANDEM.EMS, TANDEM.PATHWAY, and
MYORG.1.
For HP NonStop subsystems, the subsystem owner is “TANDEM”.
Command Failed. Error = -9999
Please List Again Working with thresholds or objects without updating the displayed information
with current data in the Threshold and Objects pane. Update the displayed
thresholds and objects with the current data in the Threshold and Objects pane
respectively by listing them again.
Multi-Node Key in use. Try again!
This error is generated on trying to create a copy of a multi-node configuration.
Check whether the configuration is multi-node in the Multi-node column of the
Threshold pane.
Lost connection with node
The connection with the NonStop node is lost.
Host version mismatch
There is a version mismatch between the OCC and the NonStop Server OVNM
component.
Insufficient Write privileges The user trying to perform a particular task does not have the required Write
privilege.
<value1> and <value2> should be >=0
The user trying to enter negative values in the Value1 and Value2 boxes. Enter
positive values in the boxes and create the threshold configuration again.
Threshold obsolete, use
PROCESS/LOOPING
Too many wildcards used, review config
Too many objects found for use. The system attempted to transfer too much data.
Use wildcard characters with care as this increases the search for objects to use for
the threshold configuration.
UPDATE OBJECTS/CONFIG
FAILED(201)
The current path to the device is down, an attempt was made to write to a non-
existent process, the message-system request was incorrectly formatted, or an error
was found in the message system interface.
Invalid Threshold in current OS Version
Support for the DIAGNOSING and SUSPENDED thresholds is not available on
Dxx machines. Selecting these thresholds will cause this error message to be
displayed and no configuration or object will be added to the database. For
example, Creating a threshold configuration of ATP6100 subsystem on Dxx
machines will give this error message as these machines do not support
DIAGNOSING and SUSPENDED thresholds.
Please List Objects before Add Object When multiple users are working with thresholds or objects without updating the
displayed information with current data in the Threshold and Objects pane. For
example, if one user has deleted a particular threshold and then the other user on
a separate workstation trying to Add object to the threshold will encounter this
error.
Update the displayed thresholds and objects with the current data in the Threshold
and Objects pane, respectively, by listing them again.