Merge pull request #205342 from Clare-Zheng82/0720-Add_dataflow_error_code

Add error codes to data flow error TSG doc

Author: ttorble

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

@@ -243,7 +243,7 @@ This article lists common error codes and messages reported by mapping data flow
 - **Cause**: An invalid staging configuration is provided in the Hive.
 - **Recommendation**: Please update the related ADLS Gen2 linked service that is used as staging. Currently, only the service principal key credential is supported.
 
-- **Message**: ADLS Gen2 storage staging properties should be specified. Either one of key or tenant/spnId/spnKey or miServiceUri/miServiceToken is required.
+- **Message**: ADLS Gen2 storage staging properties should be specified. Either one of key or tenant/spnId/spn Credential/spnCredentialType or miServiceUri/miServiceToken is required.
 - **Cause**: An invalid staging configuration is provided in the Hive.
 - **Recommendation**: Update the related ADLS Gen2 linked service with right credentials that are used as staging in the Hive.
 
@@ -636,6 +636,31 @@ This article lists common error codes and messages reported by mapping data flow
 - **Cause**: Transient error
 - **Recommendation**: Retry the request after a wait period.
 
+## Error code: DF-Executor-OutOfMemorySparkError
+
+- **Message**: The data may be too large to fit in the memory.
+- **Cause**: The size of the data far exceeds the limit of the node memory.
+- **Recommendation**: Increase the core count and switch to the memory optimized compute type.
+
+## Error code: DF-SQLDW-InternalErrorUsingMSI
+
+- **Message**: An internal error occurred while authenticating against Managed Service Identity in Azure Synapse Analytics instance. Please restart the Azure Synapse Analytics instance or contact Azure Synapse Analytics Dedicated SQL Pool support if this problem persists.
+- **Cause**: An internal error occurred in Azure Synapse Analytics.
+- **Recommendation**: Restart the Azure Synapse Analytics instance or contact Azure Synapse Analytics Dedicated SQL Pool support if this problem persists.
+
+## Error code: DF-Executor-IncorrectLinkedServiceConfiguration
+
+- **Message**: Possible causes are,
+    - 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. 
+    - 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.
+- **Cause**: Delete operation on the Azure Data Lake Storage Gen2 account failed since its linked service is incorrectly configured as Azure Blob Storage.
+- **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.
+
+## Error code: DF-Delta-InvalidProtocolVersion
+
+- **Message**: Unsupported Delta table protocol version, Refer https://docs.delta.io/latest/versioning.html#-table-version for versioning information.
+- **Cause**: Data flows don't support this version of the Delta table protocol.
+- **Recommendation**: Use a lower version of the Delta table protocol.
 
 ## Next steps