MicroStrategy ONE
Exit codes for Java syntax in procedures
When you execute a Command Manager command in a procedure using the execute statement, the statement returns a numeric exit code. If the statement has an error, this exit code can help you find the cause of the error. A more detailed explanation of what caused a specific exit code may be in the log file.
The exit codes are as follows:
|
Exit code |
Meaning |
|---|---|
|
0 |
No error. The command executed successfully. |
|
-1 |
A registry key or file required for Command Manager was not found. |
|
1 |
Command Manager was unable to load and prepare its operating environment. |
|
3 |
Your Command Manager license has expired. You can view license information in License Manager. |
|
4 |
Command Manager was unable to establish a connection to Intelligence Server. |
|
5 |
Command Manager was unable to establish a connection to Narrowcast Server. |
|
6 |
The statement contained a syntax error. |
|
8 |
Intelligence Server returned an error. |
|
9 |
Narrowcast Server returned an error. |
|
10 |
A file-related operation failed. For example, the script may have tried to write to a read-only file, or read from a file that does not exist. |
|
15 |
The execute statement does not contain a Command Manager statement to be executed. |
Related Topics
Using Java in Command Manager procedures