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.

Table 1. Error messages

Error

Description

Action

Alarm alarmID Error in acknowledge.

The probe could not acknowledge the alarm specified in the ackAlarm command to the HTTP/HTTPS command interface.

Check that the you have specified the parameters for the command correctly, in particular the alarm identifier.

Error in filtered resynchronization

An error occurred while processing the resyncFilter command to the HTTP/HTTPS command interface.

Check that you have specified the command correctly, in particular the attributes of the filter.

Error in resynchronization

An error occurred while processing the resync command to the HTTP/HTTPS command interface.

Check that you have specified the command correctly. Also check that the values of the ResyncProbableCause and ResynchSeverityFilter are correctly specified.

Failed to convert IOR to object

The probe failed to convert an IOR into an object reference.

Check that the value of the IORFile property is correct and up to date. Also, make sure that the target system is running correctly.

Failed to get active alarms

The probe received an exception while trying to retrieve active alarms from the EMS manager.

Check the properties related to resynchronization, in particular the filter properties. Check that the target system is running correctly and that there is not an IDL type mismatch.

Failed to get EMS Manager reference

The probe is unable to retrieve an EMS Manager reference from the target system.

Check that the target system is running and that there is not an IDL file mismatch.

Failed to get next iterated alarm batch

The probe is unable to retrieve the next batch of active alarms.

Check there is not an IDL file mismatch or contact IBM Support.

Failed to narrow manager reference

The probe is unable to narrow the EMS Manager reference from the target system.

Check that the target system is running correctly and that there is not an IDL file mismatch.

Failed to retrieve TMF814 Release

The probe was unable to retrieve the TMF814 release.

The probe could not retrieve the value of the TMF814 release. Check the value of the ReleaseTMF814 property and adjust as necessary. In addition, make sure that the properties file has not become corrupted.
Failed to start

The probe is unable to start due to an environment problem or an unsupported TMF814 release.

Check that all properties have the correct, and valid, values as defined in Properties and command line options.

Cannot parse attribute attribute-name with type [type]

The probe cannot parse the attribute named in the error message.

Check that the attribute is a supported type and is compliant with the TMF814 standard. Refer to the elements that the probe supports. You can also contact IBM Software Support for assistance.

Failed to close file ior_file

The probe failed to close the specified IOR file.

Check that the IOR file is in the correct place, defined by the NamingServiceIORFile property or the IORFile property. In addition, check that the directory that holds the file is not set to read only.

Loading TMF814 jar release: UNKNOWN from path file-path

The ReleaseTMF814 property has an incorrect, unrecognized value. This message may occur with Failed to start.

Ensure the property has one of the values defined in Properties and command line options.

Stream capture fails

The probe was not able to capture raw event data.

Check that the value of the StreamCaptureFilePath property is a valid file path and tat the path exists.

Unsupported TMF814 release

The ReleaseTMF814 property has an incorrect, unrecognized value.

Ensure the property has one of the values defined in Properties and command line options.

Unable to get EMS session

The probe is unable to connect to the target EMS session.

Check that the Username and Password properties contain the correct values for accessing the target system. In addition, check that the target system is running correctly.

Unable to ping the EMS session

The probe is unable to poll the target system during heartbeat checking.

Check that the target system is running correctly.