skip to main content
Error messages : DataDirect Cloud Management API error messages : Management API Servlet error messages : DataSource API error messages
 

Try DataDirect Cloud Now
DataSource API error messages
The following section describes error messages you may receive back from the DataSource API. Each error message is followed by a possible cause and recommended actions, if applicable.
Table 68. Error messages for the DataSource API
Error code
Description
222207000
Problem updating your DataSource at this time. Please try again at another time.
222207001
Problem retrieving your DataSource at this time. Please try again at another time.
222207002
Invalid DataSource Option: {0}.
222207003
There is a problem connecting to the DataSource. {0}
222207004
There is no DataSource with that id: {0}.
222207005
Expected values for connect Type : 'Cloud' / 'On-Premise'. Your value was {0}. Please try again with proper value.
222207006
Problem deleting your DataSource at this time. Please try again at another time.
222207007
Invalid JSON Input: {0}
222207008
connectionType is not allowed to be changed . It must remain : {0}.
222207009
Expected values for map :'refresh'/'recreate'/'none'. Your value was{0}. Please try again with proper value.
222207010
Missing 'connectionType' in payload.
222207011
Invalid DataSource ID: {0}.
222207012
You are not authorized to create a DataSource with this DataStore id: {0}. Please contact Customer Support if you would like to upgrade your account.
222207013
Problem validating your DataSource at this time. Please try again at another time.
222207014
You already have a DataSource with the name {0}. Please choose another name.
222207015
Invalid DataStore ID: {0}.
222207016
Missing 'name' in payload.
222207017
Problem refreshing your DataSource at this time. Please try again at another time.
222207018
{0} is an unrecognized argument for /map. Expected 'map' and/or 'model' only.
222207019
Missing 'id' in payload.
222207020
Missing 'password' in payload.
222207021
DataStore is not allowed to be changed. It must remain: {0}.
222207022
There was a problem deleting the DataSource. Multiple rows were somehow deleted. {0}
222207023
Problem connecting to your DataSource at this time. Please try again at another time.
222207024
Problem retrieving your DataSources at this time. Please try again at another time.
222207025
Problem creating your DataSource at this time. Please try again at another time.
222207026
Missing 'dataStore' in payload.
222207027
There is a problem getting the DataStore(s) at this time. Please try again at another time.
222207028
Missing 'userId' in payload.
222207029
Expected values for model: 'refresh' / 'none'. Your value was {0}. Please try again with proper value.
222207030
Data Source 'id' in the JSON Request must match the resource. ie. /datasources/<id>. DataSource 'id' is an optional field.

HTTP response codes returned by the DataDirect Cloud Management DataSource API

DataDirect Cloud Management DataSource API returns standard HTTP response codes as described in the following table, under the conditions listed in the description.
Table 69. HTTP error messages for the DataSource API
Error code
Description
200
OK
The request was successfully completed. If this request created a new resource that is addressable with a URI, and a response body is returned containing a representation of the new resource, a 200 status will be returned with a location header containing the canonical URI for the newly created resource.
201
Created
A request that created a new resource was completed and no response body containing a representation of the new resource is being returned. A location header containing the canonical URI for the newly created resource will be returned.
400
Bad Request
The JSON request is invalid.
401
Not Authorized
The user is not authorized. An invalid Progress ID and/or password was used.
404
Not Found
The <DataSource> was not found, where <resource_type> is DataSource.
500
Internal Server Error
The server encountered an unexpected condition which prevented it from fulfilling the request.
501
Not Implemented
The server currently does not support the functionality required to fulfill the request.