skip to main content
Error messages : Data Store error messages : Oracle Eloqua error messages
 

Try DataDirect Cloud Now

Oracle Eloqua error messages

The following section describes error messages you may receive back from an Eloqua data store. Each error message is followed by a possible cause and recommended actions, if applicable.

Incorrect Connection Information.

*Error: Incorrect connection information. The specified value for FailOnIncompletedata is invalid. Valid value is '0' or '1'.[10300]
Cause: The value specified for the FailOnIncompletedata custom property is invalid.
Action: Make sure that the FailonIncompleteData custom property contains a valid value. Valid value is 0 or 1.
*Error: Incorrect connection information. KeywordConflictSuffix property should be a string of up to five characters.
Cause: The number of characters specified for the KeywordConflictSuffix custom property must be greater then five.
Action: Check the value of the KeywordConflictSuffix custom property. The value must be a string of up to five characters.

Login Failed

*Error: Login failed. Invalid Company, User name or Password.
Cause: Authentication has failed because either of the following is missing or the specified value is invalid:
*User Id.
*Password.
*Company.
Action: Make sure that the:
*Specified user ID and password are valid.
*Data source custom property contains the Company= custom property with a valid value.

Query Execution Failed

*Error: Query Execution Failed. Bulk is not available because the bulkversion= custom property was not specified. Query on "Account" table could not be resolved with available APIs because FailOnIncompleteData=1. Refer to Eloqua user documentation for alternate options.
Cause: The error is caused because all of the following conditions are true:
*The query contains the Account table.
*FailOnIncompleteData=1.
This query cannot be processed using the bulk interface as bulkversion is not specified or is invalid, and the standard interface returns incomplete data, which leads to an error.
Action: Make sure that you do either of the following:
*Update FailOnIncompleteData=0 (NULL is returned for columns that contain incomplete data).
*Error: Query Execution Failed. Bulk queries may not reference more than 100 columns. Query on "Account" table could not be resolved with available APIs because FailOnIncompleteData=1. Refer to user documentation for alternate options.
Cause: The error is caused because the query contains more than 100 columns with FailOnIncompleteData=1. This query cannot be processed using the bulk interface as the query contains more than 100 columns, whereas the standard interface returns incomplete data, which leads to an error.
Action: Make sure that you do either of the following:
*Reduce the number of columns being queried to less than 100.
*Update FailOnIncompleteData=0 (NULL is returned for columns that contain incomplete data).
*Error: Query Execution Failed. Bulk querying is not supported for the "CREATEDBY" column. Query on "Account" table could not be resolved with available APIs because FailOnIncompleteData=1. Refer to user documentation for alternate options.
Cause: The error is caused because all of the following conditions are true:
*The query contains the createdBy column of the Account table, which the bulk interface does not support.
*FailOnIncompleteData=1.
This query cannot be processed using the bulk interface as the query contains the createdBy column, and the standard interface returns incomplete data, which leads to an error.
Action: Make sure that you do either of the following:
*Remove the column(s) that the bulk interface does not support.
*Update FailOnIncompleteData=0 (NULL is returned for columns that contain incomplete data).
The records for the columns that are not supported by the bulk interface can be obtained using another query that uses the standard interface (Minimal Column Set/Partial Column Set).
*Error: Query Execution Failed. Bulk queries may not reference more than 100 columns. Query using "contact.accountId" column could not be resolved with available APIs because FailOnIncompleteData=1. Refer to user documentation for alternate options
Cause: The error is caused because all of the following conditions are true:
*The query contains more than 100 columns.
*The query contains the accountID column of the Contact table.
*FailOnIncompleteData=1.
This query cannot be processed using the bulk interface, and the standard interface does not return data for the accountID column, which leads to an error.
Action: Make sure that you do either of the following:
*Remove the accountID column from the query.
*Update FailOnIncompleteData=0 (NULL is returned for columns that contain incomplete data).
*Reduce the number of columns to less than 100.
*Error: Query Execution Failed. Bulk is not available because the bulkversion= custom property was not specified. Query using "contact.accountId" column could not be resolved with available APIs because FailOnIncompleteData=1. Refer to the user documentation for alternate options.
Cause: The error is caused because all of the following conditions are true:
*The query contains the accountID column of the Contact table.
*FailOnIncompleteData=1.
Action: Make sure that you do either of the following:
*Remove the accountID column from the query.
*Update FailOnIncompleteData=0 (NULL is returned for columns that contain incomplete data).
*Error: Query Execution Failed. Error invoking Service, Response Error Code: 404, NOT_FOUND.
Cause: The error is caused because it took more than bulktimeout, which is by default set to 18000 seconds (5 hours), for the query to execute and either of the following condition is true:
*The query is executed on Activity or CustomObject tables.
*A bulk query is executed on Account or Contact table.
Action: Set the bulktimeout custom property in the data source to a higher value and rerun the query.
Note: Other than these errors, you might encounter a few more exceptions that contain a prefix, such as "Query Execution failed" or "Query Execution failed: Internal error". These are Eloqua service errors or internal errors.