Load All – Error Reference Guide
When running a Load All for an extraction, various errors may occur depending on the source system, connection configuration, or data being processed. This guide explains the most common errors, their causes, and how to resolve them.
Error Sheet
Cause: DataSync could not authenticate or reach the source API.
Solution: Confirm connection settings and credentials (API key/token, user, permissions).
Cause: The source API was unable to process the request.
Solution: Check the source connection configuration and request parameters.
Cause: API performance is degraded or the request timed out during a large load.
Solution: Retry the load or reduce the load size using filters or smaller date ranges.
Cause: The service is temporarily unavailable.
Solution: Check the Status page and retry.
Cause: The SQL Server connection failed during the pre‑login handshake (TLS/certificate issue or outage).
Solution: Confirm SQL reachability and TLS/certificate settings. For Cloud deployments, check the Status page.
Cause: An internal processing error occurred in DataSync.
Solution: Contact Nectari Support.
Cause: A temporary SQL Server or network interruption occurred.
Solution: Verify SQL Server availability and connectivity. For Cloud deployments, check the Status page.
Cause: Duplicate key values were detected due to an index or unique key configuration issue.
Solution: Review the table’s index or unique key settings and ensure the key is unique.
Cause: A value exceeds the precision or scale of the destination numeric field.
Solution: Increase the numeric precision/scale or adjust the mapping.
Cause: The task was stopped before completion.
Solution: Review the logs and rerun the task.
Cause: Some partitions were not loaded before running the clean delete process.
Solution: Load the missing partitions, then rerun.
Cause: Processing deleted records failed for a specific partition.
Solution: Rerun the process for the failing partition.
Cause: The database is offline or cannot be reached.
Solution: Verify the database is online and the connection is valid. For Cloud deployments, check the Status page and contact Nectari Support.
Cause: A deadlock occurred due to competing processes, such as another extraction, OLAP cube activity, or table locks.
Solution: Rerun the operation once the blocking process has completed.
Cause: The post‑execution SQL script is invalid and cannot be validated, causing the job to fail at the end of execution.
Solution: Review and correct the SQL in the post‑execution script.
Cause: The filter value is not in the expected data type. For example, SXA may return values like '(data invalid) 0.0000,50.6400'.
Solution: Split the value so it can be interpreted as a valid decimal.
Cause: The required docparid value is missing from the connection configuration.
Solution: Ensure docparid is set in the connection. Follow the steps in Configure the Connections.
Cause: The data warehouse has reached its allocated size limit.
Solution: Contact your Nectari sales representative.
Cause: A cloud configuration issue is preventing the customer entry from being found.
Solution: Contact your administrator or Nectari Support.
Cause: A technical issue occurred during processing.
Solution: Contact Nectari Support.
Cause: SQL Server returned an error because the table name or schema is invalid or does not exist.
Solution: Verify that the table and schema names are correct in the source or query.
Cause: A partition encountered an error during the load by partition process.
Solution: Review the failing partition to identify and correct the underlying issue.
Cause: The login credentials for the data warehouse are invalid or the user lacks required permissions.
Solution: If the issue is permission‑related, contact Nectari Support.
Cause: The job was manually canceled before completion.
Solution: Rerun the job if cancellation was unintentional.
Cause: Too much data is being processed for the available memory.
Solution: For Cloud deployments, contact Nectari Support.
Cause: The value is too large for the destination column, or a binary value is being inserted into a string column.
Solution: Increase the size of the destination column or correct the source data type.
Cause: A unique index cannot be created due to duplicate values, indicating data integrity issues.
Solution: Contact Nectari Support.
Cause: The connection is not valid or cannot be verified.
Solution: Verify that all source connection settings (username, password, server name, URL, etc.) are correctly configured.
Cause: The executing operation was canceled before completion.
Solution: Rerun the operation once the cancellation cause is resolved.
Cause: The extraction period is invalid. This message is returned by Sage Intacct.
Solution: Review the period settings and ensure they match valid Sage Intacct periods.
Cause: The data warehouse is not available in Cloud environments.
Solution: Contact Nectari Support.
Cause: Sage Intacct services are unavailable or experiencing downtime.
Solution: Wait for Sage Intacct services to recover, then retry the operation.
Cause: Too many extractions are using the same connection, exhausting the connection pool.
Solution: Increase the Max Pool Size property in the connection settings.
Cause: Some APIs enforce strict timeouts when responses exceed expected processing time. For example, Sage Intacct’s Gateway times out after 15 minutes.
Solution: If the source API is experiencing performance degradation, submit a support ticket to Sage Intacct.
Cause: The SQL Server instance is unavailable or experiencing an outage.
Solution: Confirm that the SQL Server instance is online. For Cloud deployments, check the Status page.
Cause: The transaction was selected as a deadlock victim due to competing processes (e.g., another extraction, OLAP cube activity, or table locks).
Solution: Rerun the transaction.
Cause: The DataSync user in Sage Intacct lacks permission to read the specified object.
Solution: Update the user’s permissions in Sage Intacct.