Error messages

Error messages provide information about problems that occur while running the probe. You can use the information that they contain to resolve such problems.

The following table describes the error messages specific to this probe. For information about generic Netcool/OMNIbus error messages, see the IBM Tivoli Netcool/OMNIbus Probe and Gateway Guide.
Table 1. Error messages

Error Message

Description

Action

[Command Port] host Failed to get socket IO io

[Command Port] host Failed to read command exception

[Command Port] Error occurred exception

[Command Port] Failed to get property 'CommandPort'

[Command Port] host Failed to close command socket exception

There was a problem with the command port.

Check that you have specified the command port properties correctly. Check the connection between the probe and the command port.

[Command Port] Failed to get CommandPortLimit property - using 10

The probe could not retrieve the value of the CommandPortLimit property. The probe will use the default value of 10.

Check that you have specified the command port correctly. Check the connection between the probe and the command port.

[Command Port] Failed to open listening socket, shutting down Thread!

The probe could not open a listening socket on the command port.

Try using another port.

[Command Port] Thread shutting down due to error!

There was a problem with the command port.

Check that the command port has been specified correctly and that the nco_p_nonnative process is running.

Cannot initialize the Orb exception

A problem was encountered during initialization of the Object Request Broker (ORB).

Ensure the CLASSPATH environment variable contains the path to the ORB .jar files.

Cannot proceed. Shutting down!

There is a problem with your network or with the probe configuration.

Contact IBM Software Support.

Communication failure - lost connection to NoticiationIRP: exception

CORBA.TRANSIENT exception raised. NotificationIRP is down!

CORBA.OBJECT_NOT_EXIST exception raised. NotificationIRP is down!

BAD_PARAM Exception i.e one or more of the in/out parameter is null exception

CORBA Exception stack trace to stderr exception

NetcoolIRPManager: Stack Trace to stderr exception

Communication with the Notification IRP server has failed.

Check that the Notification IRP server is running.

Failed to Connect exception

The server is not running, the IOR is out of date, or the probe cannot reach the remote server.

Check that the relevant properties are set correctly and that the target host is working correctly.

Failed to connect to the Naming Context exception

The probe cannot connect to the Naming Context.

Check the values of the NamingServiceHost and NamingServicePort properties.

Failed to iterate through resynch alarms

A problem occurred while the probe was parsing the alarms retrieved during a resynchronization.

Check that the server is running correctly. Check that you have specified the resynchronization parameters correctly.

Failed to perform resynch

The probe failed to get the alarm list or failed to iterate through the resynchronization alarms.

Check the value specified for the Resynch property.

Failed to ping notification service

The probe encountered connection problems with the Notification IRP point.

Check the value specified for the Agentheartbeat property.

Failed to resolve the AlarmIRP object exception

The Alarm IRP object is not registered in the Naming Service with the Alarm IRP name provided in the properties file.

Check the value specified for the AlarmIrpName property.

Failed to resolve the NotificationIRP object exception

The Notification IRP object is not registered in the Naming Service with the Notification IRP Name provided in the properties file.

Check the value specified for the NotificationIrpName property.

login: Unknown exception occurred exception

Problems getting the IRP Object.

Check the values specified for the AlarmIrpName, NotificationIrpName, and EntryPointIrpFile properties.

NetcoolIRPManager: ERROR when parsing a notification event

The probe encountered corrupted data while parsing. The data is not in the expected format.

Check the settings in the notification and problem log files.

NetcoolIRPManager: Failed to acknowledge_alarms(): exception

The probe could not acknowledge the alarm.

Check that the alarm identifier provided to the CLI is correct.

NetcoolIRPManager: Failed to retrieve AlarmIRP object from security interface

Failed to get the Alarm IRP object.

Check the value specified for the AlarmIrpName property.

NetcoolIRPManager: Failed to retrieve NotificationIRP object from security interface

Failed to get the Notification IRP object.

Check the value specified for the NotificationIrpName property.

NetcoolIRPManager: Failed to send event exception

The probe could not forward the event to the ObjectServer.

Check that the ObjectServer is running.

NetcoolIRPManager: Failed to Unacknowledge_alarms(): exception

The probe could not unacknowledge the alarm.

Check the connection between the probe and the command port. Check that you have specified the command port correctly.

OperationNotSupported exception

InvalidParameter Exception: exception

The Nokia-Siemens EMS does not support the operation specified.

Check the value specified for the NotificationIrpName property.

Problem while trying to connect to the IRP points exception

A problem occurred while connecting to the Alarm IRP or the Notification IRP.

Check the values specified for theAlarmIrpName and NotificationIrpName properties.

Login: Failed to narrow Entry Point IRP interface: exception

The probe failed to narrow the object reference to the Entry Point IRP Agent object.

Check the value of the EntryPointIRPFile property in the properties file.

Failed to retrieve property AlarmIrpFile

Failed to retrieve property NotificationIrpFile

The probe could not find one or more properties required to connect to the server.

Check that the properties given in the message are present in the properties file and that they have the correct values.

Failed to find IOR file 'alarmirp_ior_file'

The probe has failed to find the IOR file.

Check that the AlarmIrpFile property is set correctly in the properties file.

Failed to find IOR file

Login: Failed to find IOR file 'ior_file'

The probe has failed to find the IOR file.

Check that the EntryPointIrpFile property is set correctly in the properties file.

Failed to get subscription status: exception

The probe cannot get the subscription status from the notification service.

Check that the server is running correctly. Check the connection to the server.

VIV:printStackTrace:

Failed to Connect to notification service: exception

The probe lost its connection to the server.

Check that the server is running correctly. Check the connection to the server.

Either, the server is not running, the IOR is out of date, or probe cannot reach remote Server!

There are no responses from the Notification IRP point.

Check that the server is running correctly. Check the connection to the server. Check that the IOR is not out of date. Check that the probe has the permissions required to log into the server.

NetcoolIRPManager: Failed to clear_alarms: exception

The probe has failed to clear the alarms.

Check that the NV_ALARM_ID specified in the CLI is correct. Check that the port number is correct. Check the connection to the server.

Error. Failed to parse event completely

Name is null, cannot create Element

The probe failed to parse the alarm.

Check that the alarm conforms to the StructuredEvent format. Check that the server is running correctly.

Will listen for commands on port number listening_port

An information message identifying the port that the probe will listen on for commands.

None.

Failed to listen for commands on port number listening_port: io

The probe was unable to listen for commands on the specified. port.

Check that the CommandPort property is set correctly in the properties file.