errorCode - Internal termination codes

Internal termination codes are set for different reasons.

In case of normal termination, the internal error code is set to one of the following reasons:

• 1 - Ok, but no content returned (DELETE, PUT, PATCH) ==> 200
• 2 - Instance(s) updated ==> 201
• 3 - Instance(s) created and/or updated ==> 201
• 4 - Instance(s) deleted ==> 201

Server start errors:

• -31 - Invalid authentication type (basic/none) ==> 401
• -32 - Invalid data source defined in server ini-file. No database available ==> 401

Request errors

• -10 - Syntax error in URL ==> 404
• -11 - Missing locator in URL (// not allowed)

• -20 - Invalid URL (property or method not found) ==> 404

• -21 - Invalid URL (could not locate instance) ==> 409

• -30 - Authentication error (invalid user name or password ==> 401
• -31 - Invalid data source defined in server ini-file. No database available ==> 404

• -32 - Request type not allowed (ALLOW option in server.ini) ==> 400

• -40 - Invalid parameter passed in URL ==> 400

• -41 - Too many parameter passed in URL ==> 400

• -100 - Syntax error in OSI REQUEST body ==> 400
• -101 - Error parsing request source in ... ==> 400
• -102 - Body for OSI POST request does not contain code ==> 400

• -110 - Invalid OSI REQUEST body (property or member not found) ==> 400

• -111 - Error executing OSI request (field source) ==> 409

• -112 - Error selecting data in OSI REQUEST body (field source) ==> 409

• -113 - Could not locate instance for URL or OSI field source ==> 409

• -114 - Could not assign data to complex data type property ==> 409

• -115 - URL must refer to collection property ==> 409

• -116 - Updating existing instance is not allowed (invalid request or missing parameter) ==> 409

• -117 - Cannot create new instance for LOID access ==> 409

• -118 - Creating new instance is not allowed (invalid request or missing parameter) ==> 409

• -119 - POST request must not refer to an instance (locator not allowed) ==> 409

• -120 - POST must refer to collection property (complex data type) ==> 409

• -121 - Data passed in body is not a valid JSON string ==> 409

• -122 - Property name or path not valid in current context ==> 409
• -123 - Missing data (body) for PUT, PATCH or POST request

• -900 - exception thrown ==> 500

In case of exceptions an error message is returned in response message text. Error codes are transformed later to HTTP error codes (e.g. ==> 200). In case of success error codes (HTTP return codes 2xx), an additional message are returned in response.