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 error messages, see the IBM Tivoli Netcool/OMNIbus Probe and Gateway Guide (SC14-7608).
Error |
Description |
Action |
---|---|---|
[Command Port] Failed to get property CommandPort [Command Port] Error occurred [Command Port] <+host+> Failed to get socket IO [Command Port] <+host+> Failed to read command [Command Port] host Failed to close command socket |
There was a problem with command port functionality. |
Check that you have specified the command port 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 command port functionality. |
Check that the command port has been set, and that the nco_p_nonnative_base process is running. |
Cannot initialize the Orb |
Problem during initialization of the ORB. |
Ensure your CLASSPATH contains the path to the Visibroker jar files. |
Cannot proceed. Shutting down! |
There is a problem with your network, or the probe configuration. |
Contact IBM® Software Support. |
Communication failure - lost connection to NoticiationIRP: 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 CORBA Exception stack trace to stderr NetcoolIRPManager: Stack Trace to stderr |
There is a problem with the CORBA interface. |
Refer to your CORBA documentation. |
Failed to Connect |
Either the server is not running, the IOR is out of date, or the probe cannot reach the remote server. |
Check that the properties are set correctly and that the target host is working correctly. |
Failed to iterate through resynch alarms |
A problem occurred while the probe was parsing the alarms retrieved during the resynch. |
Check that the server is running correctly. Check that you have specified the resynchronization parameters correctly. |
Failed to narrow Security IRP interface |
The method to authenticate the caller has failed. |
Check the name of the security IRP object. |
Failed to perform resynch |
The probe failed to get the alarm list, or failed to iterate through resynchronization alarms. |
Check the value specified for the Resynch property. |
Failed to ping notification service |
The probe has connection problems with the notification IRP point. |
Check the value specified for the Agentheartbeat property. |
Failed to resolve the AlarmIRP object |
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 |
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: Failed to get IRP object login: Unknown exception occurred |
The probe could not get the IRP Object. |
Check the name and path of the Security IRP object. |
NetcoolIRPManager: ERROR when parsing a notification event |
The probe encountered corrupted data while parsing. The data is not in expected format. |
Check the settings in the notification and problem log files. |
NetcoolIRPManager: Failed to acknowledge_alarms() |
The probe could not acknowledge the alarm. |
Check that the alarm identifier provided to the CLI is correct. |
NetcoolIRPManager: Failed to find IOR file ior file |
The probe could not locate the IOR file. |
Check the value specified for the ALUSecurityIrpFile property. |
NetcoolIRPManager: Failed to retrieve AlarmIRP object from security interface |
The probe could not get the alarm IRP object. |
Check the value specified for the AlarmIrpName property. |
NetcoolIRPManager: Failed to retrieve NotificationIRP object from security interface |
The probe could not get the Notification IRP object. |
Check the value specified for the NotificationIrpName property. |
NetcoolIRPManager: Failed to send event |
The probe could not forward the event to the ObjectServer. |
Check that the ObjectServer is running. |
NetcoolIRPManager: Failed to Unacknowledge_alarms() |
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 |
The Nortel system does not support the operation specified. |
Check the value specified for the NotificationIrpName property. |
Problem while trying to connect to the IRP points |
A problem occurred while connecting to the alarm IRP or the notification IRP. |
Check the value specified for the AlarmIrpName and NotificationIrpName properties. |
Unexpected fatal error, failed to connect Unexpected fatal error when connecting to interfaceUnexpected fatal error while getting IRP Outline Unexpected fatal error when getting IRP reference from Entry Point IRP |
The probe has encountered a fatal error. |
Contact IBM Software Support. |