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
`Failed to create new event :`	The ObjectServer was unable to create a new event.	Check that the ZTE server is running correctly.
`Failed to extract values from the remainder_of_body`	There was an error while extracting data from one of the fields of the CORBA event.	Check that there is not an IDL type mismatch.
`Failed to send event :`	The event manager could not send the event to the ObjectServer.	Check that the ObjectServer is running. Check that the network connection is working correctly.
`Name is null, cannot create element`	The name of the attribute being parsed is not recognized	Check that there is not an IDL type mismatch.
`Cannot parse type[`	The type of the attribute being parsed is not recognized	Check that there is not an IDL type mismatch.
`Failed to parse element :`	The element 'name' could not be parsed.	Check that there is not an IDL type mismatch.
`Failed to get object reference from IOR file :`	The probe failed to obtain a reference on the EmsSessionFactory object by reading its IOR file.	Check that the IOR file exists and it is up-to-date. Check that the network connection between the machine where the probe is running and the machine where the E300 is located is working correctly.
`Failed to connect to Naming Service :`	The probe could not connect to the Naming Service on the host and the port specified by the ORBInitialHost and ORBInitialPort properties.	Check that the Naming Service is running. Check that the network connection is working correctly.
`Failed to get object from IOR file :`	The probe failed to get a reference on the Naming Service by reading its IOR file specified in the NSIORFile property.	Check that the Naming Service is running. Check that the network connection is working correctly.
`Failed to resolve Naming Context`	The probe is connected to the Naming Service but could not obtain a reference to the object whose name is specified in the NamingContextPath property.	Check that the object name is correct and it's currently available.
`Failed to narrow object reference :`	The probe got a reference on a CORBA object but fails to narrow it into a EmsSessionFactory object reference.	Check the IOR files and check the NamingContextPath is correct and up-to-date.
`Failed to convert IOR to object :`	The probe failed to convert an object reference into an IOR	Check that the ZTE server is running correctly.
`Failed to find file, please check file exists!`	The probe is unable to locate a file.	Check that the file exists.
`The CORBA service is not running on the expected Host/Port/IOR :`	The Naming Service is not running on the expected Host/Port/IOR.	Check the Naming Service is running and then check that all the associated properties have been defined correctly.
`Exception raised when locating server : "Check Naming Service and CORBA interface is running!`	The object name specified by the NamingContextPath property cannot be found.	Check the object is available and the specified name is correct.
`Failed to generate and process Probewatch event for the event loss being cleared.`	The ProbeWatchManager failed to create a ProbeWatch message.	Check the ObjectServer is running.
`Failed generate and process Probewatch event for the event loss occurring.`	The ProbeWatchManager failed to create a ProbeWatch message.	Check the ObjectServer is running.
`ZTEE300Probe: error while checking subscription status :`	The probe received an exception while calling getSubscriptionStatus on the EMSSubscriptionManager.	Check that the ZTE server is running correctly.
`Failed to create CorbaUtil object :`	The probe could not create the internal object.	Ensure that the $CLASSPATH environment variable contains the path to the IBM® ORB .jar files.
`Failed to get object reference :`	The probe could not get a reference on the EmsSessionFactory object.	Check that the associated details are correct.
`Please check Username and Password""Unable to get EMS session :`	The probe received an authentication error while trying to retrieve an EmsSession object.	Check that the Username and Password properties have been specified correctly.
`Unable to get EMS session :`	The probe received an exception while trying to retrieve an EmsSession object.	Check that the ZTE server is running correctly.
`Failed to get EMS Manager reference :`	The probe received an exception while trying to retrieve the EMSManager reference from the EmsSession object.	Check that the ZTE server is running correctly.
`Failed to narrow manager reference :`	The object returned by the EmsSession is not an EMSManager.	Check that the ZTE server is running correctly.
`ZTEE300Probe: Failed to get object reference :`	The probe received an exception while trying to retrieve the EMSManager reference from the EmsSession object.	Check that the ZTE server is running correctly.
`ZTEE300Probe: problem while unsubscribing :`	The probe received an exception was while calling unsubscribe with the probe's subscriptionId.	Check that the ZTE server is running correctly.
`Failed to parse alarm :`	The probe received an exception while parsing an alarm.	Check that there is not an IDL type mismatch.
`Failed to get resynch alarm list :`	The probe received an exception while calling getAllActiveAlarms.	Check the ResyncProbableCauseFilter and ResyncBatchSize filters have the correct/supported values. Check that the ZTE server is running correctly.
`Failed to retrieve next batch of resync alarms :`	The probe failed to retrieve the next batch of alarms.	Check that the ZTE server is running correctly.
`Failed to perform resync :`	The probe received an exception during resynchronization.	Check that the ZTE server is running correctly.
`ZTEE300Probe: Failed to get 'Subscriber' interface reference :`	The probe failed to retrieve a reference on the subscriber manager.	Check that the ZTE server is running correctly.
`ZTEE300Probe: Failed to narrow manager reference :`	The probe retrieved an incorrect object type.	Check that the ZTE server is running correctly.
`ZTEE300Probe: failed to subscribe :`	The probe could not subscribe for real-time notifications.	Check that the ZTE server is running correctly.