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

Exception when attempting to run status monitor
Probe shutting down because CORBA Status monitor not polling successfully.

Exception thrown when attempting to start CORBA service
Probe shutting down as unable to access CORBA service, please ensure that server configuration is complete and try again
Probe shutting down because Probe unable to access CORBA service

Exception when attempting to establish a filter for alarms
Probe shutting down as unable to receive alarms,please ensure that the timestamp file pointed to does not contain corrupted data
Probe shutting down because unable to establish Alarm Watch filter

Exception when attempting to establish an Alarm Watch
Probe shutting down as unable to receive alarms,please ensure that server configuration is complete and try again
Probe shutting down because unable to establish Alarm Watch

The probe could not initialize the connection with the CORBA interface and is shutting down.

Check the SpectroSERVER configuration.

Verify that the values set for the Domain, Name, and IP attributes of the SpectroServer property are correct in the host configuration file.

Check the firewall settings in your environment.

Check that the appropriate additions were made to the SpectroSERVER server list.

Verify that a Spectrum User Model exists for the user ID that runs the probe.

Error occurred attempting to pass on details of cleared alarms to the Object Server.
Probe shutting down because Problem processing cleared alarms.

Error occurred attempting to pass updates to the Object Server
Probe shutting down because Problem processing updated alarms.

Error occurred attempting to pass details of new alarms to the Object Server
Probe shutting down because Problem processing new alarms

Error in connecting to CORBA interface
Error external to CORBA framework
Probe shutting down because External error in connection to CORBA interface

Exception thrown when querying whether we are accessing Primary SpectroSERVER
Probe shutting down because Problem querying SpectroSERVER.

Connection to CORBA interface has been lost.
Error internal to CORBA interface
Probe shutting down because Internal error in CORBA interface, connection lost

Error shutting down connection to CORBA interface

The probe connection with the CORBA interface has failed.

Restart the probe.

Check whether the SpectroSERVER configurations have changed.

Verify that the SpectroSERVER is running.

Failed to pick up probe property TimeStampFile
Not using timestamp file, proceeding to collect all active alarms.

Timestamp of alarms not stored for re-sync

Unable to create timestamp file

Unable to find time stamp file

Unable to write to timestamp file

Error closing timestamp file

Error opening timestamp file for reading





The probe failed to use the timestamp file. These errors are not fatal error messages.

Check the specific message and verify that the timestamp file is accessible.

Alarm + alarmID + Error clearing alarm
Error clearing alarm

Alarm + alarmID + Error in Event ID List update
Error updating the event ID List

Alarm + alarmID + Error in Trouble Shooter Model update
Error updating the trouble shooter model

Alarm + alarmID + Error in Trouble Ticket update
Error updating the trouble ticket

Alarm + alarmID + Error in Troubleshooter Name update
Error updating the trouble shooter name

Alarm + alarmID + Error in status update
Error updating the alarm status

Alarm + alarmID +Error in unacknowledge
Error un-acknowledging alarm

Alarm + alarmID + Error in acknowledge
Error acknowledging alarm

The probe failed to update an event.

Verify that the alarm you are trying to update exists in the SpectroSERVER.

Note: If the alarm is not found, the SpectroSERVER shows an error message.

Invalid spectrum alarm severity: MaxSpectrumSeverity is greater than 6. Valid spectrum alarm severity value is from 0 to 6.

The value set for the MaxSpectrumSeverity property is greater than the maximum valid value. The valid values for this property are between 0 to 6.

Set the MaxSpectrumSeverity property to a value between 0 to 6.

Invalid spectrum alarm severity: the values of MinSpectrumSeverity and MaxSpectrumSeverity are not in order. Valid spectrum alarm severity value is from 0 to 6.

The value set for the MinSpectrumSeverity property is greater than that set for the MaxSpectrumSeverity property.

Set the MinSpectrumSeverity property to a value between 0 to 6, and less than that set for the MaxSpectrumSeverity property.

Invalid spectrum alarm severity: MinSpectrumSeverity is less than 0. Valid spectrum alarm severity value is from 0 to 6.

The value set for the MinSpectrumSeverity property is less than 0, which is not valid.

Set the MinSpectrumSeverity property to a value between 0 to 6.

Host parser exception : file:///<host configuration file path> LineNumber=62 ColumnNumber=21 Msg=cvc-complex-type.2.4.b: The content of element 'ProbeHeadProperty' is not complete. One of '{SpectroServer}' is expected. Error in parsing host configuration file. Probe will shutdown

No SpectroServer is specified in host configuration file.

Specify at least one SpectroServer in the host configuration file.

Host parser exception : file:///<host configuration file path> LineNumber=51 ColumnNumber=37 Msg=cvc-complex-type.2.4.a: Invalid content was found starting with element '<property name in host config file>'. One of '{AlarmAttributes, TimeStampFile, FetchEventFormatFields, FetchEventString, EventFormatFile, ProbCauseLookupFile, ResyncInterval, ResyncSQLCmd}' is expected. Error in parsing host configuration file. Probe will shutdown

Duplicate entries were found in the host configuration file for at least one of the following properties: AlarmAttributes, TimeStampFile, FetchEventFormatFields, FetchEventString, EventFormatFile, ProbCauseLookupFile, ResyncInterval, ResyncSQLCmd.

Specify only one entry in the host configuration file for any of the properties listed.

[servername] failed to retrieve related events:

[servername] no events could be fetched successfully for this alarm

The Archive Manager service is down and the probe could not retrieve events for the alarm from the Archive Manager.

Restart the Archive Manager service.

Unknown host configuration file, <invalid host path>

Error in parsing host configuration file. Probe will shutdown

The probe could not detect the host configuration file because the path is invalid.

Set the a valid path to the host configuration file for the Host property.