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	Description	Action
`Cannot initialize the Orb`	The probe found a problem during initialization of the ORB.	Ensure that the $CLASSPATH environment variable contains the path to the IBM® ORB .jar files.
`Exception raised while creating ServiceMng object exception`	The probe cannot retrieve the `ServiceMng` object.	Verify that the Naming Service is running and that the `ServiceMng` object is registered with the Naming Service.
`Failed to get Comm Service exception`	The probe cannot call the Comm Service.	Verify that the Naming Service is running and that the `ServiceMng` object is registered with the Naming Service.
`Failed to retrieve NotificationIRP object`	The probe failed to get the `NotificationIRP` object specified by the NotificationObjectName property.	Verify that the value specified by the NotificationObjectName property is correct.
`Failed to retrieve AlarmMng object`	The probe failed to get the `AlarmMng` object specified by the AlarmObjectName property.	Verify that the value specified by the AlarmObjectName property is correct.
`Problem while trying to connect to the corba objects exception`	There was a problem connecting to the Alarm object or the Notification object.	Verify that the notification service is running.
`Failed to ping notification service`	The probe failed to ping the notification service or cannot get the Notification object.	Verify that the notification service is running.
`There was a Runtime exception while pinging NotificationIRP exception` `Communication failure - lost connection to NotificationIRP`	The probe encountered a runtime exception while pinging the notification service.	Verify that the notification service is running.
`Detach Error`	The probe failed to detach the subscription from the notification service.	You might need to restart the Naming Service.
`NetcoolIRPManager: Failed to parse remainder_of_body. Type Any cannot be extracted using PropertySeqHelper`	A problem occurred when the probe tried to parse an alarm.	Verify that the alarms are being generated in the correct alarm format.
`Failed to perform resynch` `Could not perform resynch`	The probe failed to get the alarm list or failed to iterate through resynch alarms.	Check that the connection to the host is still active.
`Error while trying to attach the NetcoolIRPManager`	The probe is not able to get a subscription to the notification service.	Verify that the ZTE N31 NMS server is running.
`NetcoolIRPManager: Failed to iterate through resynch alarms`	The probe encountered a problem while parsing the alarms retrieved during a resynchronization.	Verify that the ZTE N31 NMS server is running correctly. Verify that the Resynch property is set to true.
`Failed to acknowledge_alarms()` `Failed to Unacknowledge_alarms()` `Failed to clear_alarms` `Failed to comment_alarms`	The probe could not acknowledge, unacknowledge, clear, or add a comment to one or more alarms.	Verify that the correct alarm ID was used with the CLI command. Verify that the correct command port is specified by the CommandPort property. Check the connection between the probe and the command port.
`Failed to parse event completely`	The probe encountered a problem while parsing the event	Verify that the ZTE N31 NMS server is running correctly.
`Failed to send event`	The probe could not forward an event to the ObjectServer.	Verify that the ObjectServer is running.
`Name is null, cannot create Element`	The probe could not forward an event to the ObjectServer.	Verify that the ObjectServer is running.
`[Command Port] Failed to get CommandPortLimit property - using 10");` `[Command Port] Failed to get property 'CommandPort'"); [Command Port] Thread shutting down due to error!");` `[Command Port] Failed to open listening socket, shutting down Thread!");` `[Command Port] Error occurred : "+e);` `[Command Port] <"+host+"> Failed to get socket IO : "+io);` `[Command Port] <"+host+"> Failed to read command : "+e);` `[Command Port] <"+host+"> Failed to close command socket : "+se);`	The probe could not retrieve the value of the CommandPortLimit property.	Verify that the correct command port is specified by the CommandPort property. Check the connection between the probe and the command port.