Return codes for Publishing Server CLIs
When a Publishing Server CLI command exits with a return value other than 0 (success), additional textual information about the error cause is displayed to standard output and to the generated publishing CLI trace file installationDirectory\pw\server \tmp\pcli\pcli.trace. These exit codes, their meanings, and recommended remedial actions are described in the following table .
BMC Impact Publishing Server CLI error exit codes
Error exit code | Description | Recommended remedial action |
---|---|---|
1 | Indicates a syntax error on one or more command-line arguments or options | Verify the correct syntax for the command string. |
2 | Indicates an invalid number option | Verify the correct syntax for numerical options such as |
3 | Indicates that the home directory (installationDirectory/pw/server) of the application can not be found | Perform the following step:
|
10 | Indicates a generic (unspecified) error | (This is an internal error.) Do the following steps:
|
11 | Indicates that the CLI is unable to initialize its communication layer | Retry the command. If the error still occurs, do the following steps:
|
12 | Indicates a communication failure when the CLI sent data to its communication provider, for example, the jBoss server | Retry the command. If the error still occurs, do the following steps:
|
13 | Indicates that the CLI cannot decode an answer that it has received from its communication provider | (This is an internal error.) Do the following:
|
14 | Indicates that the CLI cannot find a file that it requires to run properly; for example, a FileNotFound exception | Verify that the file whose name appears as missing does exist. |
15 | Indicates that the CLI cannot resolve a host name | Repair the computer's network settings |
16 | Indicates the failure to authenticate with the BMC TrueSight Infrastructure Management Server | Perform the following steps:
|
17 | Indicates an Impact interface initialization failure; for example the I18N configuration might be wrong | Perform the following steps: |
18 | Indicates that the UTF-8 character set is not supported by the host | The host computer must support the UTF-8 character set. |
19 | Indicates that the CLI does not have a request identifier | Perform the following steps:
|
20 | Indicates an I/O error when the publishing log file is written | Verify that the write permission is set for the publishing request log file. You must specify the name of the RequestLogFile for a CLI command by using the |
Comments
Log in or register to comment.