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

Table 1. Error messages
Error	Description	Action
`Event queue full. Fail to add alarm into queue.`	The probe failed to add the new event into the event queue because it is full. This may occur when the probe was not able to catch up with the event rate received from the Kodiak EMS or there was an error removing events from the queue. This may cause a potential event loss.	Check the probe log to see whether an error occurred during event processing or while sending the alert to the ObjectServer. Check whether there was an event flood from the Kodiak EMS.
`Failed to add the ipAddress to the list`	The probe failed to add the IP address to the list of EMS systems to which it should connect.	Check that the IP address is specified correctly in the TargetEMSIPAddr property.
`No alarm manager interface`	The probe could not obtain the `AlarmManager` interface instance on the EMS card.	Check that the Kodiak EMS is running correctly.
`Malformed URL for target for IP address: ip_address`	The probe generated a malformed name server locator URL.	Check to see if the formats of the TargetEMSIPAddr and StandbyEMSIPAddr properties are correct.
`Input Output Exception for IP address: ip_address`	An error occurred when attempting to retrieve the naming service IOR.	Check that the ior.txt file is available on the target host. Check that the port number is specified correctly in the EMSPortNumber property.
`ParseAlarmInformation: Failed to send event : java_exception` `ParseAlarmInformation: Failed to send alarm operation update : java_exception`	Probe failed to parse the alarm received from the Kodiak EMS system. The data received may be corrupt.	Check that the Kodiak EMS is running correctly. Check that the alarm conforms to the `AlarmInformation` structure.
`CORBA.TRANSIENT exception raised. Lost connection to EMS!`	The probe has lost connection to the EMS system. The EMS is not live.	Check the EMS server availability. Check the connection between the probe and the EMS.
`Problem getting alarm during resynch.`	The probe failed to call the `getAlarms` function with the OSS ID specified.	Check that the EMS system received the `getAlarms` request during the probe resynchronization phase. Check the value set for the OSSId property.
`Could not obtain alarm interface`	The probe failed to narrow the object reference to the interface object.	This is a CORBA related error message. Check that the CORBA installation is correctly configured.
`Probe shutting down since it cannot connect to the EMS server.`	The probe failed to connect to the EMS server during startup.	Check the EMS server availability.