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

You must specify an alarm and/or a path file

The probe found that neither an alarm log file nor a path status log file have been specified.

Set either the AlarmLog or the PathLog property.

Failed to create File Name

The probe is unable to open the specified output file.

Check that the file exists and the file permissions are set correctly.

Could not process alert

The probe could not open the log file.

Check that the file exists and that the file permissions are set correctly.

Failed to set Element

The probe detected an unrecognized element.

Refer to your support contract for details about contacting the IBM Software Support.

Failed to start path status formatter

Failed to start alarm status formatter

The alarm received is in an unrecognizable format.

Refer to your support contract for details about contacting the Help Desk.

Failed to send alert

Probe failed to send an alert to the ObjectServer.

Check that the probe is still running. If it is not, restart the probe.

Unable to get events

The probe failed to get any events from the log file.

Check that the log file exists and the file permission is set to “read”.

Read error

The probe cannot read data from the log file.

Check that the log file exists and the file permission set to “read”.

Cannot process alert

The probe was either unable to set the first or last occurrence, or failed to process the rules file, or could not send the alert to the ObjectServer.

Make sure that the ObjectServer is alive and that there is a valid rules file.

Unrecognized line format

The probe found that an alarm line is not in a valid format.

Make sure the device is producing a valid alarm format.