Errors in the Integrator UI are specific and reflect which part of Jedox suite has problems. In addition to a short error description, a user-friendly message further explains the issues.
Common error messages
| Error message | Description |
|---|---|
| Bad request configuration | Code: ETL_S400 - Failed to execute load New Excel load: Configuration Error in load New Excel load: Only load mode CREATE supported for file location JedoxFiles. |
Server errors
These errors show up if the REST response from the server is returned with 4xx or 5xx code:
| Error message | Description |
|---|---|
| ETL_S400: 'Bad request configuration.' | Integrator Server returns this error if a request cannot be handled due to its content. For example, this error occurs when running a load or job that uses an invalid XML definition in the Integrator UI. |
| ETL_S401: 'Authentication credentials invalid.' | This error is returned if a user does not have appropriate rights to an operation. |
| ETL_S404: 'No such method.' | This error is returned if a non-existent REST method is called in the Integrator Server. For example, if incompatible versions of the Integrator UI and the Integrator Server are used, this error could occur. |
| ETL_S500: 'Internal Integrator server error. Please try again or restart Integrator server.' | This error occurs in case of an internal error in the Integrator Server. The log for Integrator Server may contain additional information in this case. |
| ETL_S503: 'Integrator server currently unavailable. Please try again later.' | This error is returned if the Integrator Server did not respond to the request, for example, if it is currently not running. |
RPC etl-mngr client errors
These errors show up in various scenarios when the server returns result, but either it is invalid or it could not be parsed.
| Error message | Description |
|---|---|
| ETL_C01: 'XPath exception error. Parsing XML configuration failed.' | This error occurs if XML is invalid or corrupted and parsing fails in the Integrator UI. |
| ETL_C02: 'XML configuration invalid.' | Generally should not be displayed - this happens if building XML configuration from the UI inputs fails. |
| ETL_C03: 'Operation unsuccessful.' | This is a generic error that could have multiple causes. It happens when a request is executed but "valid: false" returned, e.g., try to duplicate or rename component when a user with "R" rights on Integrator. |
| ETL_C04: 'JSON parsing error. Incorrect JSON format.' | This error covers the rare cases when the JSON parser fails. |
| ETL_C05: 'Input/Output error.' | This error shows up if files could not be accessed or an IOException happened. |
| ETL_C06: 'Invalid request output please check configuration or query.' | This error shows up if the result of /executions/metadata or /executions/output is invalid. This usually happens if the related SQL query is malformed. |
Updated April 9, 2025