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.
`[Command Port] Failed to send probewatch message!`	The probe was unable to send a ProbeWatch message to the ObjectServer.	Check the connection to the ObjectServer.
`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` `NetcoolIRPManager : Exception raised from attaching to notification categories : exception` `Failed to retrieve subscr_id_filename_old file ='subscr_id_filename_old ' 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` `NetcoolIRPManager : Failed to attach to notification categories : exception`	The probe failed to get the alarm list or failed to iterate through the resynchronization alarms.	Check the value specified for the Resynch property. Check that the server is running correctly. Check that you have specified the resynchronization parameters correctly.
`Failed to ping notification service` `Failed to get subscription status: exception`	The probe encountered connection problems with the Notification IRP point.	Check the value specified for the Agentheartbeat property. Check that the CORBA interface is running correctly.
`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`	The Nokia-Siemens OMC-R GSR9 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 the AlarmIrpName and NotificationIrpName properties.
`Login: Failed to find IOR file 'ior_file'`	The probe failed to get the named IOR file.	Check the value specified for the EntryPointIrpFile property.
`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 specified for the EntryPointIrpFile property.
`Failed to retrieve property AlarmIrpFile`	The probe cannot retrieve the value specified by the AlarmIrpFile property.	Check the value specified for the AlarmIrpFile property.
`Failed to find IOR file 'alarmirp_ior_file'`	The probe cannot find the named Alarm IRP file.	Check the value specified for the AlarmIrpFile property.
`Failed to retrieve property NotificationIrpFile`	The probe cannot retrieve the value specified by the NotificationIrpFile property.	Check the value specified for the NotificationIrpFile property.
`Failed to find IOR file`	The probe failed to get the IOR file.	Check the value specified for the EntryPointIrpFile property.
`InvalidParameter Exception: exception`	There is a problem with the CORBA interface.	Refer to your CORBA documentation.
`Failed to Connect to notification service: exception`	The probe lost the connection to the CORBA server.	Check the connection to the CORBA server.
`Either, the server is not running, the IOR is out of date, or probe cannot reach remote Server!`	The probe lost the connection to the CORBA server.	Check the connection to the CORBA server.
`NetcoolIRPManager: Failed to clear_alarms: exception`	The probe failed to clear alarms.	Check that the alarm identifier (`NV_ALARM_ID`) specified by the CLI is correct.
`Error. Failed to parse event completely`	The probe encountered a problem while parsing an event.	Verify that the Probe for Motorola OMC-R GSR9 (CORBA) server is running correctly.
`Name is null, cannot create Element`	The probe failed to parse an alarm.	Verify that the alarm conforms to the `StructuredEvent` format.
`Failed to retrieve old probe-IOR: exception`	The probe failed to find the IOR file in the expected location at the first try.	The IOR file will not be available in the expected location the first time that you run the probe, so the probe throws the error. The next time that the probe is started, it will detect the IOR file in the expected location.