Skip to content
Guide

Search the Guide

Enter a query to search the Guide.

Íslenska
Menu
On this page

Help

These are the statuses and warnings SQL Connector shows, with an explanation and what to do. Problems that come without a message are at the bottom. More detail about an error is in the Process Message, Response Status Code and Response Reason Phrase columns of the processing log.

Statuses and warnings

Message or statusExplanationWhat to do
The status Failed in the processing log or on the dashboardSending or executing the data package failed. The system retries up to Max Retry Attempts on the server setup.Read Process Message and Response Reason Phrase, fix the cause and choose Retry Package. See Processing Log and Deletion Log.
The status BlockedA previous entry for the same package failed and Stop Package on Error is enabled on the server setup, so later entries wait.Fix the first failed entry and choose Retry Package. Both failed and blocked entries then go back to pending.
Test Connection shows redThe server couldn't be reached through the Azure Function.Check Server, Database, the credentials or connection string, App Path and App Key. The key is in the Azure Portal under Function App → App Keys. See Server Setup.
A warning when you turn on Enable for a tableNo server setup is linked, no fields are set up, or the table structure hasn't been created. You can continue, but synchronization doesn't work until this is fixed.Fill in Server code, add fields and choose Create Table. See Table Setup.
A warning that a job queue for SQL Connector already existsShown in step 4 of the assisted setup.Use the existing job queue entry. See Automation.

Problems without a message

ProblemExplanationWhat to do
No data is sentA new job queue entry is created on hold and doesn't run until it is set to ready.Choose Set Ready on the Automation page. To send straight away, choose Process pending entries on the dashboard.
Entries stay PendingThe job queue entry contains PROCESSCHANGES but not SENDCOMMANDS, so packages are created but not sent.Add SENDCOMMANDS to Sync Type or create a separate job for sending. See Automation.
A new BC field doesn't reach the external tableThe field isn't in the field list, or the column doesn't exist in the external table.Add the field to the field list and choose Add Missing Columns on the table card. See Field Setup.
A field isn't shown in the field listBLOB, Media, MediaSet, FlowFields and FlowFilters are not supported and are not transferred.Nothing. These fields are not exported.
Sending large packages times outThe data package is too large for the Azure Function to respond within HTTP Timeout (ms).Choose Suggest Batch Size and lower Records per message, or raise HTTP Timeout (ms). See Table Setup.
The external table is out of sync with the BC tableData in the external table has drifted, for example after a manual change.Choose Force Full Re-sync. The next run clears the table and exports all data again.