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
`ResynchInterval will not take -ve values`	A negative value was specified for the ResynchInterval property.	Make the value of the ResynchInterval property greater than or equal to 0.
`CorbaUtils: Cannot get object reference, IOR and NS values were empty`	The probe cannot get the required object references. No values have been specified for the IOR file or the Naming Service.	Depending on whether you are using an IOR file or a Naming Service to acquire event data, you must specify values for the required properties as described in Connecting to the CORBA interface.
`CorbaUtils: Failed to find file, please check file exists`	The probe could not find an IOR file.	Depending on whether you are using an IOR file or a Naming Service to acquire event data, you must specify values for the required properties as described in Connecting to the CORBA interface.
`CorbaUtils: CORBA.BAD_PARAM Exception. The IOR is not the expected Object. Please check IOR files are valid and up to date`	The IOR files are not pointing to the correct CORBA objects.	Verify that you have specified the correct values for the NetworkR1IOR and ObservableIOR properties, and that the IOR files are valid and up-to-date.
`CorbaUtils: CORBA.OBJECT_NOT_EXIST Exception. The CORBA service is not running on the expected Host/Port/IOR`	The CORBA service is not running on the expected host, port, or IOR.	Verify that you have specified the correct values for the NetworkR1NS, ObservableNS properties.
`CorbaUtils: Exception raised when locating server`	The probe cannot find a Naming Service object.	Verify that you have specified the correct values for the NetworkR1IOR and ObservableIOR properties, and that the IOR files are valid and up-to-date.
`CorbaUtils: Check Naming Service and CORBA interface is running`	There is a problem with the Naming Service or the CORBA interface.	Verify that the Naming Service and the CORBA interface are running.
`CorbaUtils: Unexpected Exception occurred`	An unexpected problem occurred with the CORBA interface.	Contact IBM Software Support.
`CorbaUtils: Failed to get the object reference`	The probe cannot get the required object references.	Depending on whether you are using an IOR file or a Naming Service to acquire event data, check the values that you specified for the required properties described in Connecting to the CORBA interface.
`Observer: Failed to get object reference for Observable object`	The probe cannot get the object reference for the `Observable` CORBA object.	Depending on whether you are using an IOR file or a Naming Service to acquire event data, check the values that you specified for the required properties described in Connecting to the CORBA interface.
`Observer: Failed to narrow Observable reference`	The `Observable` CORBA object could not be narrowed to the correct type.	Contact IBM Software Support.
`Observer: Check that IOR files are correct and up to date`	The IOR files are not pointing to the correct `Observable` CORBA object.	Verify that you have specified the correct value for the ObservableIOR property, and that the IOR file is valid and up-to-date.
`Servant appears to already be active when activating consumer`	A consumer object is already registered on the ORB.	Contact IBM Software Support.
`Observer: Failed to connect to the CORBA interface due to exception`	The gateway failed to connect to the CORBA interface due to an exception.	Check the probe message log file lucent_snms.log for more information. The log file is located in the following directory: $OMNIHOME/log If you cannot identify the problem, contact IBM Software Support.
`Observer: Please check that the interface is running and the probe is using up to date IOR files`	There is a problem with the CORBA interface or the IOR file for the `Observable` CORBA object.	Verify that the CORBA interface is running. Verify that you have specified the correct value for the ObservableIOR property, and that the IOR file is valid and up-to-date.
`Parser: Cannot parse type value_type: name`	The probe cannot parse the event value described in the error message.	Contact IBM Software Support.
`Parser: Error parsing name`	The probe cannot parse the event value described in the error message.	Contact IBM Software Support.
`Resynch: Failed to narrow networkR1 reference`	The `NetworkR1` CORBA object could not be narrowed to the correct type.	Contact IBM Software Support.
`Resynch: Failed to connect to the CORBA Interface due to exception`	Resynchronization failed due to a CORBA interface exception.	Verify that the CORBA interface is running correctly.
`Resynch: Please check that the interface is running and the probe is using up to date IOR files`	Resynchronization failed due to a problem with the CORBA interface or the IOR files.	Verify that the CORBA interface is running correctly. Depending on whether you are using an IOR file or a Naming Service to acquire event data, check the values that you specified for the required properties described in Connecting to the CORBA interface.
`Resynch: Failed to get interface version/name information`	Resynchronization failed because the probe could not get the required interface information.	Verify that the CORBA interface is running correctly.
`Resynch: Check that the CORBA service is running`	Resynchronization failed due to a problem with the CORBA interface.	Verify that the CORBA interface is running correctly.