Resolving script errors

When you run Decision Server Insights scripts to manage solutions, set properties or initiate analytics jobs, you might encounter an error message if a script does not run successfully. To troubleshoot and resolve script errors, you must understand the script error codes.

Symptoms

All of the Decision Server Insights scripts produce error messages, including error codes, if a script command is unsuccessful.
The most common error codes are EX_USAGE and EX_SOFTWARE.
  • EX_USAGE: Indicates parameter errors
  • EX_SOFTWARE: Indicates other types of errors
The script returns a zero (0) when the command runs successfully.

Diagnosing the problem

The EX_USAGE error code indicates incorrect command syntax, for example, missing or incorrect parameters, an incorrect parameter flag, or a problem with the structure of the command.

If an error message includes the EX_SOFTWARE error code, then there is a problem with the script execution.

INFO/WARNING/SEVERE messages are also sent to help you diagnose a problem. The level for these messages is defined in the runtime/ia/etc/logging.properties file.

.level=INFO

handlers=java.util.logging.ConsoleHandler
java.util.logging.ConsoleHandler.level=INFO
java.util.logging.ConsoleHandler.formatter=java.util.logging.SimpleFormatter
java.util.logging.SimpleFormatter.format=%5$s%n

Resolving the problem

If the EX_USAGE code is returned when you run a script, check the syntax of the command and the parameters and rerun the script by using the correct syntax.

The EX_SOFTWARE error code means that the script did not run successfully, but this code does not correlate with a specific reason for the failure. Look for other system error messages that might be displayed at the same time as this error code and review the server log and trace messages.