Troubleshoot the Salesforce Marketing Cloud connector
This feature is in Beta.
Learn how to troubleshoot common issues with the Salesforce Marketing Cloud connector.
For general troubleshooting guidance that applies to all managed ingestion pipelines, see Troubleshoot managed ingestion pipelines.
Invalid characters in column names
Error message:
Found invalid character(s) among ' ,;{}()\n\t=' in the column names of your schema.
Cause: The data extension at the source contains column names with invalid characters that are not supported by Delta.
Solution: Check the column name from the error trace and rename the column at the source so that it doesn't contain invalid characters. Then, rerun the pipeline.
Duplicate key violation
Error message:
DUPLICATE_KEY_VIOLATION
Cause: The entire row is duplicated at the source. The connector cannot currently support this scenario.
Solution: Either remove the duplicate row from the data extension, or set a primary key for the data extension in Salesforce Marketing Cloud. Then, run a full refresh of the pipeline.
Insufficient permissions
Error message:
SFMC_INSUFFICIENT_PERMISSIONS
Cause: The API Integration Package does not have the required scope to access the data.
Solution: Check the required scope from the error message, and ensure that you've added that scope in the API Integration package that you created in Salesforce Marketing Cloud. Then, rerun the pipeline.
Expired client secret
Cause: Salesforce Marketing Cloud client secrets for API integrations expire 180 days after they're generated. When the client secret stored in the connection expires, the connector can no longer authenticate to the source, and pipelines that use the connection fail. You can view expiration dates for all of your client secrets on the Installed Packages page in Salesforce Marketing Cloud Setup.
Solution: Rotate the client secret in Salesforce Marketing Cloud, then re-authenticate the Unity Catalog connection with the new secret:
- In Salesforce Marketing Cloud, generate and activate a new client secret for the API Integration Package. For the steps, see Rotate an OAuth 2.0 Secret in the Salesforce Marketing Cloud documentation.
- In the Databricks workspace, click
Catalog, find your Salesforce Marketing Cloud connection, and edit it to enter the new Client Secret. - Rerun the pipeline.