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
`ConvertEscapes: Error allocating memory for octal code` `ConvertEscapes: Error allocating memory for temp buffer` `Error allocating memory for line buffer` `Error allocating memory for single node` `Error allocating memory for socket list` `Expect: Error allocating memory for buffer` `Failed to allocate memory for property value: string` `ReadHostEntry: Error allocating memory for entry` `ReadHostEntry: Error allocating memory for line` `ReadHostFile: Error allocating memory for socket node` `ReadHostFile: Error allocating memory for token`	Unable to allocate memory for the buffer that contains the event being read. This caused the TSM to terminate.	Make more memory available.
`Could not open port, exiting`	There is a problem with the connection details that you specified or with the network connection itself.	Check that you can access the target port from the host running the probe. Check that you have specified the correct host and port.
`DMS User Alternative Password property not set, exiting` `DMS User Name property not set, exiting` `DMS User Password property not set, exiting`	One or more of the properties required for connecting to the DMS device are missing from the properties file.	Check that the properties file contains values for the AltPassword, Password, and UserName properties.
`Error converting ChatinString escapes` `Error converting ChatoutString escapes` `Error converting HeartbeatResponse escapesError converting HeartbeatString escapes`	There is an invalid escape code in the property specified.	Check the values specified for the ChatinString, ChatoutString, HeartbeatResponse, and HeartbeatString properties. For details of valid escape codes, see Escape Codes.
`Error reading host file filename`	The TSM could not open the hosts file for reading.	Check the permissions for the hosts file and directories, and amend if necessary.
`Failed to create new command port connection port` `Failed to set up command port port`	The TSM cannot start due to a problem setting up the port specified.	Check that the port number specified was positive, not a reserved number, and that it is not in use by another application.
`Failed to save PID to file`	The TSM could not save the process ID number to the file specified.	Check the permissions of the PID file and corresponding directories, and amend if necessary.
`HeartbeatInterval property may not be negative (value)` `HeartbeatTimeout property may not be negative (value)` `ReconnectionInterval may not be negative - reverting to default` `ResponseTimeout not positive, Exiting`	The property specified has been set to an invalid value.	Update the property in the properties file.
`HeartbeatInterval set but heartbeat properties not set, exiting`	The `HeartbeatInterval` property has been set, but the complementary heartbeat properties have been omitted.	Add values for the HeartbeatResponse, HeartbeatString, and HeartbeatTimeout properties in the properties file.
`Host property not set, exiting Port property not set, exiting`	Either the Host property or the Port property has been omitted, so the TSM cannot connect to the device.	Specify values for the Host and Port properties in the properties file.
`Hostfile entry line number: Chatin property set, but no chatout!` `Hostfile entry line number: Failed to retrieve host value` `Hostfile entry line number: Failed to retrieve port value` `Hostfile entry line number: Parse error ':' expected` `HostsFile entry line number: property not set!`	There is an error in the format of the hosts file at the line specified.	Correct the line specified. For details of the format of the hosts file, see Hosts File Format.
`SendAlert failed`	The TSM was unable to send an alert to the ObjectServer.	Check that the ObjectServer is available.
`This is not a valid DMS log report - discarding`	A report received from the DMS device is not in the correct format.	Check that the device is running correctly.
`Unable to compile HeartbeatResponse regexp for: heartbeat response` `Unable to compile regexp for heartbeat response`	The device was unable to compile the heartbeat response required by the TSM.	Check that the HeartbeatResponse property contains a valid regular expression.