Skip to content

Commit f5ab375

Browse files
committed
Update and add errors
1 parent a032ce2 commit f5ab375

File tree

1 file changed

+10
-2
lines changed

1 file changed

+10
-2
lines changed

articles/data-factory/data-flow-troubleshoot-errors.md

Lines changed: 10 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -650,9 +650,17 @@ This article lists common error codes and messages reported by mapping data flow
650650

651651
## Error code: DF-Executor-IncorrectLinkedServiceConfiguration
652652

653-
- **Message**: Possible causes are \n1. The linked service is incorrectly configured as type 'Azure Blob Storage' instead of 'Azure DataLake Storage Gen2' and it has 'Hierarchical namespace' enabled. Please create a new linked service of type 'Azure DataLake Storage Gen2' for the storage account in question. \n2. Certain scenarios with any combinations of 'Clear the folder', non-default 'File name option', 'Key' partitioning may fail with a Blob linked service on a 'Hierarchical namespace' enabled storage account. You can disable these dataflow settings (if enabled) and try again in case you do not want to create a new Gen2 linked service.
653+
- **Message**: Possible causes are,
654+
1. The linked service is incorrectly configured as type 'Azure Blob Storage' instead of 'Azure DataLake Storage Gen2' and it has 'Hierarchical namespace' enabled. Please create a new linked service of type 'Azure DataLake Storage Gen2' for the storage account in question.
655+
2. Certain scenarios with any combinations of 'Clear the folder', non-default 'File name option', 'Key' partitioning may fail with a Blob linked service on a 'Hierarchical namespace' enabled storage account. You can disable these dataflow settings (if enabled) and try again in case you do not want to create a new Gen2 linked service.
654656
- **Cause**: Delete operation on the Azure Data Lake Storage Gen2 account failed since its linked service is incorrectly configured as Azure Blob Storage.
655-
- **Recommendation**: Create a new Azure Data Lake Storage Gen2 linked service for the storage account in question. If that's not feasible, some known scenarios like **Clear the folder**, non-default **File name option**, **Key** partitioning in any combinations may fail with an Azure Blob Storage linked service on a hierarchical namespace enabled storage account. You can disable these data flow settings if you enabled them and try again.
657+
- **Recommendation**: Create a new Azure Data Lake Storage Gen2 linked service for the storage account. If that's not feasible, some known scenarios like **Clear the folder**, non-default **File name option**, **Key** partitioning in any combinations may fail with an Azure Blob Storage linked service on a hierarchical namespace enabled storage account. You can disable these data flow settings if you enabled them and try again.
658+
659+
## Error code: DF-Delta-InvalidProtocolVersion
660+
661+
- **Message**: Unsupported Delta table protocol version, Refer https://docs.delta.io/latest/versioning.html#-table-version for versioning information.
662+
- **Cause**: Data flow does not support this version of the Delta table protocol.
663+
- **Recommendation**: Use a lower version of the Delta table protocol.
656664

657665
## Next steps
658666

0 commit comments

Comments
 (0)