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, (SC14-7530).

Table 1. Error messages
Error	Description	Action
`Failed to set Element $ElementName: reason` `Cannot create alive timeout` `Cannot create idle timeout` `Failed to setup signals` `Failed to initialize heartbeat` `Failed to initialize` `Failed to define argument: argument_name` `Failed to initialize arguments`	These are internal errors.	Refer to your support contract for information about contacting Technical Support.
`Failed to set FirstOccurrence: reason`	The probe is unable to set the first occurrence field.	Ensure that this field exists in the ObjectServer table.
`Failed to read message, incorrect header.`	The message header from the device does not match that specified in the properties.	Ensure that the `AlarmHeaders` and the `MessageTerminator` properties are set correctly.
`Failed to allocate time stamp string: string` `Failed to create logreq message` `Failed to create logrsp message` `Failed to send login request` `Cannot create g2 message structure`	The probe is unable to perform the specified operation because of memory problems.	Make more memory available.
`Could not login: reason` `Failed to initialize TIM connection`	The probe was unable to log in to the XMC interface. This message is generally preceded by more specific error messages.	Check any preceding messages. Also, check that the username and password refer to a valid user account.
`SetEventTimes() failed: reason`	The probe was unable to set the `FirstOccurrence` and `LastOccurrence` fields.	Check that the `FirstOccurrence` and `LastOccurrence` fields exist in the ObjectServer tables.
`Unexpected EOF. Connection lost.`	The connection to the remote system has been lost.	Check the network connection and the remote system.
`Cannot create retry timer. Continuing without retries.`	The probe is unable to create a retry timer. This message is generally preceded by more specific error messages.	Check any preceding messages.
`Failed to read property: propertyname`	The probe was unable to start because the property indicated contains an incorrect value.	Check that you have set the properties and command line options correctly.
`Failed to get correct login response` `Failed to read logrsp`	The server did not respond.	Check the network connection and the remote system.
`Failed to get correct login response` `Unknown logrsp`	The server did not respond as expected.	Check that the `AlarmHeaders` property is set correctly.