Skip to main content
What do ECLI error codes mean?

Troubleshooting failed ECLI validations

Philip Johnston avatar
Written by Philip Johnston
Updated over a week ago

Note: This Help Article applies to ECLI 2.3.0 and higher. In earlier versions, some error codes were duplicated. Now, they are all unique.

⛔️ ECLI Error Codes

Here is a list of all ECLI error codes that may appear in your logs.

  • You can also print this list from within ECLI with the --help parameter.

  • If the logs are hard to read, send them to us via the Enterprise Service Desk for troubleshooting help.

Group 1

  • CLI.1.1 [Error code: 255] General CLI exception

Group 2

  • CLI.2.2 [Error code: 234] Standard is unknown

  • CLI.2.3 [Error code: 233] Format type is unknown

  • CLI.2.4 [Error code: 232] Terminology value is invalid or not defined

  • CLI.2.5 [Error code: 231] Dictionary value is invalid or not defined

  • CLI.2.6 [Error code: 230] Enterprise data type is unknown

  • CLI.2.7 [Error code: 229] Release version is undefined

  • CLI.2.8 [Error code: 228] Parsing failed. Cannot read data source

  • CLI.2.9 [Error code: 227] Provided Value is unknown

  • CLI.2.10 [Error code: 210] Request type value is unknown

  • CLI.2.11 [Error code: 211] Invalid comment length

  • CLI.2.12 [Error code: 235] There is no define.xml in Define Designer associated with the provided data package

  • CLI.2.13 [Error code: 236] Required inputs are missing

  • CLI.2.14 [Error code: 237] The datapackage does not exist

  • CLI.2.15 [Error code: 238] There is no license configured for this dictionary

Group 3

  • CLI.3.1 [Error code: 225] Request type cannot be determined

  • CLI.3.2 [Error code: 224] Failed to copy data source

  • CLI.3.3 [Error code: 223] Define file does not exist

  • CLI.3.4 [Error code: 222] Failed to copy define.xml

  • CLI.3.5 [Error code: 221] Failed parsing input argument list

  • CLI.3.6 [Error code: 220] File or folder does not exist

  • CLI.3.7 [Error code: 219] Client call failed

  • CLI.3.8 [Error code: 218] Failed creating output directory

  • CLI.3.9 [Error code: 217] Controlled Terminology does not exist

  • CLI.3.10 [Error code: 202] Failed creating output file

  • CLI.3.11 [Error code: 201] Failed processing client task

  • CLI.3.12 [Error code: 200] Failed core process.

  • CLI.3.13 [Error code: 199] File is opened and cannot be written to. Please close the file and restart the process.

  • CLI.3.14 [Error code: 198] A required Aspera port is not accessible

  • CLI.3.15 [Error code: 197] Enterprise user group is not found

  • CLI.3.17 [Error code: 195] System installation qualification error

  • CLI.3.18 [Error code: 194] Failed json serialization

  • CLI.3.19 [Error code: 193] Permission denied

  • CLI.3.20 [Error code: 192] Download failed

  • CLI.3.21 [Error code: 191] The path does not exist or is invalid

Group 4

  • CLI.4.1 [Error code: 215] Data source is invalid

  • CLI.4.2 [Error code: 214] Argument parsing results must be provided

  • CLI.4.3 [Error code: 213] Standard type is required

  • CLI.4.4 [Error code: 212] Data source is required

  • CLI.4.5 [Error code: 211] Standard version is required

  • CLI.4.6 [Error code: 210] Report file is required

  • CLI.4.7 [Error code: 209] Config is required

  • CLI.4.8 [Error code: 208] Output is required

  • CLI.4.9 [Error code: 207] Output format type is required

  • CLI.4.10 [Error code: 154] Data source is missing

  • CLI.4.11 [Error code: 155] Command line option is invalid or unknown

  • CLI.4.12 [Error code: 156] Web host is required for Enterprise mode

  • CLI.4.15 [Error code: 159] Missing required input

  • CLI.4.16 [Error code: 160] Missing CDISC CT Version

  • CLI.4.17 [Error code: 161] Report file is invalid

  • CLI.4.18 [Error code: 162] Invalid engine version parameter

  • CLI.4.19 [Error code: 163] Invalid filter parameter

  • CLI.4.20 [Error code: 164] This request does not include an API key. Please provide an API key as an api.key argument or in a pinnacle21. conf file

  • CLI.4.21 [Error code: 165] Invalid ascp.path parameter

  • CLI.4.22 [Error code: 166] <variable> is not a valid variable for metadata creation

Most errors that we see are due to use of outdated ECLI versions. We recommend upgrading to the latest versions of both the ECLI and the main application platform as soon as they are released. 🛫

👣 What's Next?

Email questions or feedback to

Did this answer your question?