Skip to content

Latest commit

 

History

History
51 lines (36 loc) · 3.13 KB

connector-troubleshoot-delimited-text.md

File metadata and controls

51 lines (36 loc) · 3.13 KB
Raw
title titleSuffix description author ms.service ms.subservice ms.topic ms.date ms.author ms.custom
Troubleshoot the delimited text format connector
Azure Data Factory & Azure Synapse
Learn how to troubleshoot issues with the delimited text format connector in Azure Data Factory and Azure Synapse Analytics.
jianleishen
data-factory
data-movement
troubleshooting
10/20/2023
jianleishen
has-adal-ref, synapse

Troubleshoot the delimited text format connector in Azure Data Factory and Azure Synapse

[!INCLUDEappliesto-adf-asa-md]

This article provides suggestions to troubleshoot common problems with the delimited text formatL connector in Azure Data Factory and Azure Synapse.

Error code: DelimitedTextColumnNameNotAllowNull

  • Message: The name of column index %index; is empty. Make sure column name is properly specified in the header row.

  • Cause: When 'firstRowAsHeader' is set in the activity, the first row is used as the column name. This error means that the first row contains an empty value (for example, 'ColumnA, ColumnB').

  • Recommendation: Check the first row, and fix the value if it is empty.

Error code: DelimitedTextMoreColumnsThanDefined

  • Message: Error found when processing '%function;' source '%name;' with row number %rowCount;: found more columns than expected column count: %expectedColumnCount;.

  • Causes and recommendations: Different causes may lead to this error. Check below list for possible cause analysis and related recommendation.

    Cause analysis Recommendation
    The problematic row's column count is larger than the first row's column count. It might be caused by a data issue or incorrect column delimiter or quote char settings. Get the row count from the error message, check the row's column, and fix the data.
    If the expected column count is "1" in an error message, you might have specified wrong compression or format settings, which caused the files to be parsed incorrectly. Check the format settings to make sure they match your source files.
    If your source is a folder, the files under the specified folder might have a different schema. Make sure that the files in the specified folder have an identical schema.

Related content

For more troubleshooting help, try these resources: