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
`NetcoolIRPManager: Exception when retrieving Alarm IRP`	Exception caught when probe was retrieving Alarm IRP information.	Check that the AlarmIRPName property is correctly set in the properties file.
`NetcoolIRPManager: Failed to acknowledge_alarms`	The probe has failed to acknowledge the alarms.	Check that the NV_ALARM_ID specified by the CLI is correct.
`NetcoolIRPManager: Failed to unacknowledge_alarms`	The probe has failed to unacknowledge the alarms.	Check that the NV_ALARM_ID specified by the CLI is correct.
`NetcoolIRPManager: Failed to clear alarms`	The probe has failed to clear the alarms.	Check that the NV_ALARM_ID specified by the CLI is correct.
`NetcoolIRPManager: Failed to comment alarms`	The probe has failed to comment the alarms.	Check that the NV_ALARM_ID and comment text specified by the CLI is correct.
`Failed to retrieve probe specific properties`	The probe has failed to retrieve probe specific properties because of a service exception.	Service exception errors originate from the OIDK framework. Contact IBM support.
`Login: Failed to discover interface for`	Failed to discover IRP interface with specific IRP version when probe trying to login into EntryPoint IRP.	Check that EntryPointIORFile, AlarmIRPName, NotificationIRPName and IrpVersion properties are correctly set in the properties file.
`Failed to narrow Entry Point IRP interface`	Failed to narrow the object reference to the Entry Point IRP Agent object.	Check that the EntryPointIORFile, AlarmIRPName, and NotificationIRPName properties are correctly set in the properties file.
`Failed to retrieve EPIRP version`	Failed to narrow the object reference to the Entry Point IRP version.	Check that the EntryPointIORFile, AlarmIRPName, and NotificationIRPName properties are correctly set in the properties file.
`Name is null, cannot create element`	The probe was unable to parse the event because of its name; or an attribute name is not defined correctly in the IDL attribute name mapping.	Check if the IDL attribute name mapping is defined correctly with the IDL set used.
`Failed to parse element` `Bad operation exception during event parsing`	A problem occurred while parsing an element. The probe may not have parsed the event completely.	Error during parsing of the element in the probe. Contact IBM support.
`Failed to convert additional text using specified encoding standard`	The probe has failed to convert additional text using the specified encoding standard.	Check the EncodingStandard property is correctly set in the properties file. Ensure the incoming data (additional text) is in the supported encoding.
`Problem while setting the AdditionalText token`	The probe was unable to set the AdditionalText token.	Contact IBM support.
`Exception when retrieving Notification IRP`	The probe has encountered a problem when retrieving the Notification IRP version.	Check that the NotificationIRPName property is correctly set in the properties file. If using other connection options (for example, naming service), check the related properties.
`Notification subscribe: Error while trying to get subsription id and detach the notificationIRP`	The probe has failed to retrieve the subscription ID and detach the previous subscribed session.	Check if the session has been removed in EMS, or there is a connection issue to the EMS (ensure the EMS is active and running).
`Notification subscribe: Error while trying to attach the notificationIRP`	The probe was unable to attach or subscribe to the Notification IRP.	Check if the EMS is active and running.
`Detaching Subscription Error`	The probe was unable to detach subscription during unsubscribe.	Check if the session has been removed in EMS, or there is a connection issue to the EMS (ensure the EMS is active and running).