REST and JSON Palette Error Codes
This section describes the error messages that can be reported by the activities or entities associated with the ActiveMatrix BusinessWorks REST and JSON palette.
| Error Codes | Error Message | Error Resolution |
|---|---|---|
| TIBCO-BW-PALETTE-REST-100005 | An error occurred while parsing. | The resolution is not applicable. Contact TIBCO Support. |
| TIBCO-BW-PALETTE-REST-100006 | Error occurred during JSON transformation. | The resolution is not applicable. Contact TIBCO Support. |
| TIBCO-BW-PALETTE-REST-100008 | The selected encoding <<Encoding Name>> is not valid. | The resolution is not applicable. Contact TIBCO Support. |
| TIBCO-BW-PALETTE-REST-100009 | Encoding error occurred. | The resolution is not applicable. Contact TIBCO Support. |
| TIBCO-BW-PALETTE-REST-100010 | The encoded byte content is empty. | The resolution is not applicable. Contact TIBCO Support. |
| TIBCO-BW-PALETTE-REST-100012 | The input document's root element does not match the desired output's root element. | The resolution is not applicable. Contact TIBCO Support. |
| TIBCO-BW-PALETTE-REST-100013 | An error occurred while validating output. | The resolution is not applicable. Contact TIBCO Support. |
| TIBCO-BW-PALETTE-REST-100014 | An error occurred in render activity: Improper Invocation: Schema does not have a top-level array. | Check the RenderJSON activity configuration. |
| TIBCO-BW-PALETTE-REST-100016 | An error occurred while converting JSON to XML. | Check ParseJSON activity configuration. |
| TIBCO-BW-PALETTE-REST-100040 | No schema definition was found for the specified type | The resolution is not applicable. Contact TIBCO Support. |
| TIBCO-BW-PALETTE-REST-200029 | Elements with Anonymous types are not supported for XSD mode. Please select an Element with a named type. | The resolution is not applicable. Contact TIBCO Support. |
| TIBCO-BW-PALETTE-REST- 200030 | Missing value for the ACCEPT HTTP header. Since CUSTOM Response Type is selected in the configuration, a value MUST be provided for the ACCEPT HTTP header. | Provide a value for the ACCEPT HTTP header. |
| TIBCO-BW-PALETTE-REST- 200031 | Missing value for CONTENT-TYPE HTTP header. Since CUSTOM Request Type is selected in the configuration, a value MUST be provided for the CONTENT-TYPE HTTP header. | Provide a value for the CONTENT-TYPE HTTP header. |
| TIBCO-BW-PALETTE-REST- 200032 | Username or Password cannot be null when using Basic Authentication with the REST Invoke Activity. | Check the Identity Shared Resource configuration that is used by the HTTP Client Shared Resource to make sure the password or the username is not null. |
| TIBCO-BW-PALETTE-REST-200033 | An IOException was thrown while trying to execute the HTTP Method at the resource path. | Check client/server shared resources configuration. |
| TIBCO-BW-PALETTE-REST-400000 | Spec file is not found for JSON transformation. Provide the path to the file or a valid JSON transformation spec string. | Provide a valid JSON spec file for transformation. |
| TIBCO-BW-PALETTE-REST-400001 | Input JSON String not found. Provide a valid JSON string for transformation. | Provide a valid JSON string file for transformation. |
| TIBCO-BW-PALETTE-REST-400002 | Input spec file is not valid. Provide a valid spec file for JSON for transformation. | Provide a valid JSON spec file for transformation. |
| TIBCO-BW-PALETTE-REST-400003 | Input JSON is not valid. Provide a valid JSON string for transformation. | Provide a valid JSON string for transformation. |
| TIBCO-BW-PALETTE-REST-400004 | JSON Transformation could not be completed. | The resolution is not applicable. Contact TIBCO Support. |
| TIBCO-BW-PALETTE-REST-400005 | JSON Transformation returned null. Provide a valid Input JSON and Spec JSON Content. | Input file and spec file do not match. Provide valid input. |
| TIBCO-BW-PALETTE-REST-2000027 | Client received a 4xx response for invocation at the resource path. | Check the Invoke REST API activity configuration. |
| TIBCO-BW-PALETTE-REST-2000028 | Client received a 5xx response for invocation at the resource path. | Check service configuration. |