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-7608).
Error |
Description |
Action |
|---|---|---|
| Connect Node not set up | The probe was unable to set up a connect mode. |
This is an internal error. Refer to your support contract for details about contacting IBM Software Support. |
| Connection in unknown state | The connection to the host is in a state that has not been defined in the configuration file. |
This is an internal error. Refer to your support contract for details about contacting IBM Software Support. |
| Date stamp not in recognized format | The date stamp is not in the correct format. |
Enter the date stamp in the correct format. |
| Error initializing list | The probe could not initialize. |
This is an internal error. Try running the probe again. If this error recurs, refer to your support contract for details about contacting IBM Software Support. |
| Expect timed out after number seconds | When the probe tried to log in or log out of the host, the expect part of the chat timed out. |
Check that the login name and password are valid for the target host. |
| Failed to create new command port connection | The probe could not set up a command port. |
Check that you have appropriate privileges to run the TL1 Probe. |
| Failed to initialize TSM | The probe failed to initialize. |
This is an internal error. Try running the probe again. If this error recurs, refer to your support contract for details about contacting the IBM Software Support. |
| Failed to set up command port port number | The probe could not start due to a problem setting up or creating the port specified. |
Check that the port number specified was positive, that you did not specify a reserved number, and that the port is not in use by another application. |
| Failed to retrieve value for property CommandPort port number | No command port number was specified in the properties file or on the command line. |
Specify a value for CommandPort property, either in the properties file or on the command line. |
| Failed to set up common TSM properties | The probe could not set up the properties specified in the properties file. |
Check that the properties file exists, that the permissions of the file and directory are set correctly, and the properties file is in the correct format. |
| Failed to start failover - aborting | The failover application failed to start. |
Check that both the master and slave are running and that the failover configurations are set correctly on both. |
| File entry line number: HeartbeatResponse not set! | The hosts file entry specified contains no value for the hr property. |
Specify a value for the heartbeat response for the hosts file entry specified. |
| NMutexLock failed | This is an internal error. |
Refer to your support contract for details about contacting IBM Software Support. |
| OplRegComp fail for Date | This is an internal error. |
Refer to your support contract for details about contacting IBM Software Support. |
| SID missing from header: string | The source identifier is missing from the message header. |
The file received from the host may have become corrupted. |
| Unknown expect connection error | An unknown error occurred while the probe was receiving the expect part of the chat. |
Refer to your support contract for details about contacting IBM Software Support. |
| Failed to parse auto id Failed to parse header Failed to parse response id Failed to parse text block Failed to parse message Failed to parse quoted line: string | The probe failed to parse the incoming data. The incoming data may be corrupt. |
Check that the device is running properly. |
| HeartbeatInterval property may not be negative (value) HeartbeatTimeout property may not be negative (value) ReconnectionInterval may not be negative - reverting to default ResynchInterval property may not be negative (value) WakeupAttempts property may not be negative (value) WakeupInterval property may not be negative (value) | The property specified has been set to a negative value. |
Change the property to a positive value. |
| ReconnectionInterval may not be negative - reverting to default | The property specified has been set to a negative value. |
The probe will use the default value for this property. |
| Unable to send HeartbeatString | The probe could not send a Heartbeat string to the device. |
Check that the connection to the host is still active. |
| Unable to send ResynchCommand | The probe could not send a Resynch command to the device. |
Check that the connection to the host is still active. |
| Unable to compile HeartbeatResponse regexp for: heartbeat response Unable to compile regexp for Heartbeat Response The following host file line did not match the expected format | The device was unable to compile the heartbeat response required by the probe. |
Check that the HeartbeatResponse property contains a valid regular expression. |
| REGEXP: sub number does not exist | A regular expression has not been specified. |
Check the rules file and correct the problem. |
| AddNewTextLineValue: Error allocating list space to node AllocateNewConnectNode: Error allocating new node AllocateNewConnectNode: Error allocating new node AllocateNewNode: Error allocating new node LogInOut: Error allocating memory for token SendCommand: Error allocating memory for command WakeUp: Error allocating memory for expect token WakeUp: Error allocating memory for send token | The probe failed to allocate internal storage. |
Make more memory available. |
| Error while logging out of host name port number Error while logging out of host name | The probe failed to log out of the specified device. |
Check the connection to the host. |
| Unexpected syntax for addne command: -host 'string' -cfg 'string' | Invalid syntax was provided with an addne command. |
Correct the syntax for the addne command. For details of the correct syntax see Issuing commands to the probe. |