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

Table 1. Error messages
Error	Description	Action
`A problem while connecting to AlarmIRP or NotificationIRPBAD_PARAM Exception i.e one or more of the in/out parameter is null: +e` `Cannot proceed. Shutting down!` `CORBA.OBJECT_NOT_ EXIST exception raised.` `NotificationIRP is down!` `InvalidParameter Exception` `NetcoolIRPManager: Exception occurred. Stack trace to stderr` `OperationNotSupported Exception` `Unexpected CORBA Exception`	The probe could not connect to `AlarmIRP` or `NotificationIRP` points due to a problem with the CORBA interface.	Check that the Nokia-Siemens NetAct server is running correctly. Refer to your CORBA documentation.
`Cannot initialize the Orb: " + e:`	The probe encountered a problem during initialization of the Object Request Broker (ORB).	Ensure that the $CLASSPATH environment variable contains the path to the IBM® ORB .jar files.
`Command_Port Error occurred` `Command_Port Failed to get CommandPortLimit property - using 10` `Command_Port Failed to get property CommandPort` `Command_Port Failed to send probewatch message!` `Command_Port host Failed to close command socket` `Command_Port host Failed to get socket IO` `Command_Port host Failed to read command` `Command_Port Thread shutting down due to error!` `NetcoolIRPManager: Failed to acknowledge_alarms()` `NetcoolIRPManager: Failed to Unacknowledge_ alarms()`	The probe encountered a problem with the command port CLI function.	Check that you have specified the command port correctly. Check the connection between the probe and the command port.
`Command_Port Thread shutting down due to error!`	The probe encountered a problem with the command port CLI function.	Check that the CommandPort property has the correct value. Check that the nco_p_nonnative process is running correctly.
`Command_Port Failed to open listening socket, shutting down Thread!`	The probe could not open a listening socket on the command port specified.	Specify a different port in the CommandPort property.
`COMMUNICATION FAILURE Exception i.e Server is dead` `GetSubscriptionStatus Exception`	The probe could not connect to the Nokia-Siemens NetAct server.	Check that the Nokia-Siemens NetAct server is running correctly.
`Error to parse event completely` `Failed to parse event completely` `Name is null, cannot create Element` `NetcoolIRPManager: Category Value NOT supported: Discarding Alarm` `NetcoolIRPManager: Error when parsing event`	The probe cannot parse the alarm. This is probably because the alarm is in a format that the probe cannot understand.	Check that the Nokia-Siemens NetAct server is running correctly.
`Failed to get timeout property value, defaulting to 0`	The probe could not get the timeout value, and is not going to time out.	Check the value of the Timeout property is correct. Change the value if necessary.
`Failed to connect to the Naming Context: " + e:`	The probe could not connect to the NamingContext.	Check that the NamingServiceHost and NamingServicePort properties have the correct values.
`Failed to resolve the NotificationIRP object: " + e:`	The probe could not resolve the `NotificationIRP` object as the object is not registered in the NamingService.	Check that the NotificationIrpName property has the correct value.
`Name is null, cannot create Element`	The probe could not create the matching element for an unknown field found in an alarm. Parsing of the remaining known fields continues.	Check whether the default fields of the ObjectServer are modified.
`NetcoolIRPManager: Failed to send event`	The probe could not send the parsed event to the ObjectServer.	Check whether the ObjectServer is running correctly.
`NetcoolIRPManager: Failed to retrieve AlarmIRP object from security interface` `NetcoolIRPManager: Failed to retrieve NotificationIRP object from security interface` `login: Failed to get IRP object: +ex` `login: Unknown exception occured +ex`	The probe could not get either the `AlarmIRP` or the `NotificationIRP` object. (`ex` in the error message specifies the related Java™ exception.)	Check that the AlarmIrpName and NotificationIrpName properties have the correct values.
`NetcoolIRPManager: Failed to find IOR file filename`	The probe could not locate the IRP Manager as the `filename` does not exist.	Check that the IRP Manager is set up correctly.
`NetcoolIRPManager: Failed to perform resynch` `Failed to perform resynch` `Failed to iterate through resynch alarms`	The probe could not resynchronize the alarms.	Check that Nokia-Siemens NetAct server is running correctly. Check that the Resynch property has the correct value.
`NetcoolIRPManager: Stack Trace to stderr:`	The probe could not connect to `AlarmIRP` or `NotificationIRP` points due to a problem with the CORBA interface.	Use this message from the Netcool® IRP Manager while debugging.
`NetcoolIRPManager: Notificationirp property needs to be set` `NetcoolIRPManager: Both NameServiceHost and NSPort property needs to be set` `NetcoolIRPManager: Alarmirp property needs to be set`	The probe could not find one or more properties required to connect to the Nokia-Siemens NetAct server.	Check that the properties given in the error message have the correct values.
`Failed to connect to the Naming Context : + e`	The probe cannot connect to the NamingContext.	Check that theNamingServiceHost and NamingServicePort properties have the correct values.
`Failed to resolve the AlarmIRP object : + e`	The `AlarmIRP` object is not registered in the Naming Service with the `AlarmIrpName` provided in the properties file.	Check that AlarmIrpName property has the correct value.
`Failed to resolve the NotificationIRP object : + e`	The `NotificationIRP` object is not registered in the Naming Service with the `NotificationIrpName` provided in the properties file.	Check that the NotificationIrpName property has the correct value.
`NetcoolIRPManager: Failed to retrieve AlarmIRP object from security interface` `NetcoolIRPManager: Failed to retrieve NotificationIRP object from security interface` `Failed to narrow Security IRP interface :" +ex'` `Problem while trying to connect to the IRP points : "+e` `login: Failed to get IRP object : " +ex` `login: Unknown exception occured " +ex`	Failed to get either the `AlarmIRP` or `NotificationIRP` object. There is a problem with the CORBA interface.	Refer to your CORBA documentation.
`NetcoolIRPManager: Failed to find IOR file '" +ior_file+ "'`	The probe could not locate the IRP Manager as the `filename` does not exist.	Check that the IRP Manager has been set up correctly.
`Failed to perform resynch` `Failed to ping notification service`	There is a problem with the resynchronization process.	Check that Nokia-Siemens NetAct server is running correctly. Check that you have specified the resynchronization parameters correctly.
`"Communication failure - lost connection to NoticiationIRP: " +e` `“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: " +e` `"CORBA Exception stack trace to stderr: " +e` `"Failed to Connect : " +e`" `Either, the server is not running, the IOR is out of date, or probe cannot reach remote Server!"` `"Failed to Connect : " +e`" `Cannot proceed. Shutting down!"`	The probe could not connect to the `NotificationIRP` point in the Nokia-Siemens NetAct system.	Check whether the Nokia-Siemens NetActserver is still running.
`Failed to iterate through resynch alarms`	The probe failed to get the alarm list or failed to perform resynchronization of alarms.	Check that the Nokia-Siemens NetAct server is running correctly. Check that the Resynch property is set correctly.
`NetcoolIRPManager: Failed to acknowledge_alarms() : +e` `NetcoolIRPManager: Failed to Unacknowledge_alarms() : +e`	The probe could not acknowledge the alarms.	Check that you have specified the command port correctly. Check the connection between the probe and the command port.
`NetcoolIRPManager: ERROR when parsing a notification event` `NetcoolIRPManager: Stack Trace to stderr: + e`	The probe has a problem during initialization of the ORB.	Ensure that the $CLASSPATH environment variable contains the path to the IBM ORB .jar files.
`NetcoolIRPManager: Failed to send event : +e`	The probe could not forward the event to the ObjectServer.	Check that the ObjectServer is still running.
`Name is null, cannot create Element`	The probe could not find one of the expected element for the event.	Check the log file that stores the alarms for the syntax error. If the probe is run in debug mode, the alarm is printed in the log file created by the probe. Also check that the alarm is in the correct format. Note: This inability of the probe to create element does not affect the parsing of the rest of the fields.
`[Command Port] Failed to get CommandPortLimit property - using 10`	The probe could not retrieve the value of the `CommandPortLimit` property.	Check that the CommandPortLimit property has the correct value. Note: As the default value is set to 10, this error does not affect the behavior of the probe.
`[Command Port] Failed to get property 'CommandPort` `[Command Port] Failed to open listening socket, shutting down Thread!` `[Command Port] Thread shutting down due to error!`	The probe has failed to unacknowledge the alarms.	Check that the NV_ALARM_ID specified by the CLI is correct.
`[Command Port] Error occured :+e`	A problem occurred while the user attempted to connect to the CommandPort, or while the user sent a command.	Check that the CommandPortLimit property has the correct value.
`[Command Port] host Failed to get socket IO : "+e`	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] host Failed to read command : "+e` `[Command Port] host Failed to close command socket : +e`	The probe found that there is 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.