Error-level messages

Can't set generic property "property name" via command line

Property "property name" for option "option name" does not exist

An option in the probe is not mapped correctly to a property.

Check the properties file for the named property and see the probe publication for supported properties.

Could not send alert

The probe was unable to send an alert (usually an internal alert) to the ObjectServer.

Check that the ObjectServer is available.

Could not set "fieldname" field

The probe was unable to set a field value. This may be because the ObjectServer tables were modified so that default fields are no longer present.

Check whether the ObjectServer tables were modified.

CreateAndSet failed

CreateAndSet failed for attr: "element name"

The probe is unable to create an element.

See your support contract for information about contacting IBM Software Support.

Error Setting SIGINT Handler

Error Setting SIGQUIT Handler

Error Setting SIGTERM Handler

The probe was unable to set up a signal handler for either an INT, QUIT, or TERM.

See your support contract for information about contacting the IBM Software Support.

Failed to open file: "file name"

A file referred to in the rules file (for example, with the table function) does not exist.

There was a communication problem when a remote file was accessed via HTTP.

Check the rules file and ensure that the file is available.

Failed to open message log: "file name"

The probe is unable to open the specified log file.

Check the command line or properties file and correct the problem.

Failed to open Properties file: "properties file name"

The probe is unable to open the properties file.

Check the properties file or command line to ensure that the properties file is in the specified location.

Failed to open Rules file: "rules file name"

The rules file for the probe is not available or incorrectly specified.

The probe is unable to open the rules file.

Check the properties file or command line to ensure that the rules file is in the specified location.

No extraction data for "regexp" - missing ()'s?

Regexp doesn't match for "string"

A regular expression that is used in the extract function may be missing parentheses.

The string data that is used to extract may not match the regular expression.

The extract function is unable to extract data.

Check the rules file and correct the problem.

Option "option name" used without argument

The option that is used expects a value that was not supplied.

Check the probe publication and the contents of the command line.

OS Error: "error message"

Procedure "procedure name": "error message"

Server "server name": "error message"

There is an error in the Sybase connection. There should be a subsequent message from the probe that details the effect of this error.

See your support contract for information about contacting IBM Software Support.

Properties file: "error description" at line "line no"

There is an error in the format of the properties file.

Check the properties file at the specified line number and correct the problem.

PropGetValue failed

A required property was not set.

Check the properties file.

Regular Expression Error: "regexp"

A regular expression is incorrectly formed in the rules file.

Check the rules file for the regular expression and correct the problem.

Results processing failed

Unexpected return from results processing

Unexpected value during results processing

There is a problem with the ObjectServer.

See your support contract for information about contacting IBM Software Support.

Rules file: "error description" at line "line no"

There is an error in the rules file format or syntax.

Check the rules file at the specified line number and correct the problem.

SendAlert failed

The probe was unable to send an alert to the ObjectServer.

Check that the ObjectServer is available.

SessionProcess failed

The probe was unable to process the alert against the rules file.

See your support contract for information about contacting IBM Software Support.

Unknown message level "message level string" - using WARNING level

The properties file or command line specified a message level that is not supported.

Check the properties file or command line and use a supported message level (debug, info, warning, error, fatal).

Unknown option: "option name"

An option that is not supported by the probe was used on the command line to start the probe.

Check the probe documentation and the contents of the command line.

Unknown property "property name" - ignored

A property that is specified in the properties file does not exist in the probe.

Check the properties file for the named property and see the probe publication for supported properties.

HTTP request with URL: "Remote rules file URL" failed. Server responded with "Failure Number" "Failure Text"

The remote rules file specified was not correctly returned by the http server.

Check the response and correct the problem with the http server.

Failed to add client HTTP properties

Failed to add client HTTP arguments

Failed to add create client HTTP context

Failed to start client HTTP context

Failed to create client HTTP request structure

There is a problem configuring communication to remote http servers.

Check the HTTP properties in the properties file and the HTTP arguments. Ensure that the probe has enough memory.

Failed to send the HTTP request to the server.

There is a problem communicating with the remote rules file server.

Check that communication is configured with the remote rules file server.

Unknown remote file URL format

The remote URL is prefixed with a scheme that is currently not supported in this mode.

Prefix the URL with http://

Failed to create a temporary file to write data to "filename"

Failed to copy temporary file name "filename"

Failed to open temporary local http/https response file "filename"

Failed to stat file "filename"

There is a problem with the local temporary file used to receive data from a remote file.

Ensure that the temporary file location can be accessed and altered by the probe.