您现在访问的是微软AZURE全球版技术文档网站,若需要访问由世纪互联运营的MICROSOFT AZURE中国区技术文档网站,请访问 https://docs.azure.cn.

排查 Azure 数据工厂问题Troubleshoot Azure Data Factory

适用于: Azure 数据工厂 Azure Synapse Analytics

本文探讨 Azure 数据工厂中的外部控制活动的常用故障排除方法。This article explores common troubleshooting methods for external control activities in Azure Data Factory.

连接器和复制活动Connector and copy activity

如果遇到连接器问题(例如,使用复制活动时遇到错误),请参阅排查 Azure 数据工厂连接器问题For connector issues such as an encounter error using the copy activity, refer to Troubleshoot Azure Data Factory Connectors.

Azure DatabricksAzure Databricks

错误代码:3200Error code: 3200

  • 消息:错误 403。Message: Error 403.

  • 原因The Databricks access token has expired.Cause: The Databricks access token has expired.

  • 建议:默认情况下,Azure Databricks 访问令牌的有效期为 90 天。Recommendation: By default, the Azure Databricks access token is valid for 90 days. 请创建新令牌并更新链接服务。Create a new token and update the linked service.

错误代码:3201Error code: 3201

  • 消息Missing required field: settings.task.notebook_task.notebook_path.Message: Missing required field: settings.task.notebook_task.notebook_path.

  • 原因Bad authoring: Notebook path not specified correctly.Cause: Bad authoring: Notebook path not specified correctly.

  • 建议:在 Databricks 活动中指定笔记本路径。Recommendation: Specify the notebook path in the Databricks activity.


  • 消息Cluster... does not exist.Message: Cluster... does not exist.

  • 原因Authoring error: Databricks cluster does not exist or has been deleted.Cause: Authoring error: Databricks cluster does not exist or has been deleted.

  • 建议:验证 Databricks 群集是否存在。Recommendation: Verify that the Databricks cluster exists.


  • 消息Invalid Python file URI... Please visit Databricks user guide for supported URI schemes.Message: Invalid Python file URI... Please visit Databricks user guide for supported URI schemes.

  • 原因Bad authoring.Cause: Bad authoring.

  • 建议:为工作区寻址方案指定绝对路径,或者为 Databricks 文件系统 (DFS) 中存储的文件指定 dbfs:/folder/subfolder/foo.pyRecommendation: Specify either absolute paths for workspace-addressing schemes, or dbfs:/folder/subfolder/foo.py for files stored in the Databricks File System (DFS).


  • 消息{0} LinkedService should have domain and accessToken as required properties.Message: {0} LinkedService should have domain and accessToken as required properties.

  • 原因Bad authoring.Cause: Bad authoring.

  • 建议:验证 链接服务定义Recommendation: Verify the linked service definition.


  • 消息{0} LinkedService should specify either existing cluster ID or new cluster information for creation.Message: {0} LinkedService should specify either existing cluster ID or new cluster information for creation.

  • 原因Bad authoring.Cause: Bad authoring.

  • 建议:验证 链接服务定义Recommendation: Verify the linked service definition.


  • 消息Node type Standard_D16S_v3 is not supported. Supported node types: Standard_DS3_v2, Standard_DS4_v2, Standard_DS5_v2, Standard_D8s_v3, Standard_D16s_v3, Standard_D32s_v3, Standard_D64s_v3, Standard_D3_v2, Standard_D8_v3, Standard_D16_v3, Standard_D32_v3, Standard_D64_v3, Standard_D12_v2, Standard_D13_v2, Standard_D14_v2, Standard_D15_v2, Standard_DS12_v2, Standard_DS13_v2, Standard_DS14_v2, Standard_DS15_v2, Standard_E8s_v3, Standard_E16s_v3, Standard_E32s_v3, Standard_E64s_v3, Standard_L4s, Standard_L8s, Standard_L16s, Standard_L32s, Standard_F4s, Standard_F8s, Standard_F16s, Standard_H16, Standard_F4s_v2, Standard_F8s_v2, Standard_F16s_v2, Standard_F32s_v2, Standard_F64s_v2, Standard_F72s_v2, Standard_NC12, Standard_NC24, Standard_NC6s_v3, Standard_NC12s_v3, Standard_NC24s_v3, Standard_L8s_v2, Standard_L16s_v2, Standard_L32s_v2, Standard_L64s_v2, Standard_L80s_v2.Message: Node type Standard_D16S_v3 is not supported. Supported node types: Standard_DS3_v2, Standard_DS4_v2, Standard_DS5_v2, Standard_D8s_v3, Standard_D16s_v3, Standard_D32s_v3, Standard_D64s_v3, Standard_D3_v2, Standard_D8_v3, Standard_D16_v3, Standard_D32_v3, Standard_D64_v3, Standard_D12_v2, Standard_D13_v2, Standard_D14_v2, Standard_D15_v2, Standard_DS12_v2, Standard_DS13_v2, Standard_DS14_v2, Standard_DS15_v2, Standard_E8s_v3, Standard_E16s_v3, Standard_E32s_v3, Standard_E64s_v3, Standard_L4s, Standard_L8s, Standard_L16s, Standard_L32s, Standard_F4s, Standard_F8s, Standard_F16s, Standard_H16, Standard_F4s_v2, Standard_F8s_v2, Standard_F16s_v2, Standard_F32s_v2, Standard_F64s_v2, Standard_F72s_v2, Standard_NC12, Standard_NC24, Standard_NC6s_v3, Standard_NC12s_v3, Standard_NC24s_v3, Standard_L8s_v2, Standard_L16s_v2, Standard_L32s_v2, Standard_L64s_v2, Standard_L80s_v2.

  • 原因Bad authoring.Cause: Bad authoring.

  • 建议:参考错误消息。Recommendation: Refer to the error message.


错误代码:3202Error code: 3202

  • 消息There were already 1000 jobs created in past 3600 seconds, exceeding rate limit: 1000 job creations per 3600 seconds.Message: There were already 1000 jobs created in past 3600 seconds, exceeding rate limit: 1000 job creations per 3600 seconds.

  • 原因Too many Databricks runs in an hour.Cause: Too many Databricks runs in an hour.

  • 建议:检查将此 Databricks 工作区用于其作业创建速率的所有管道。Recommendation: Check all pipelines that use this Databricks workspace for their job creation rate. 如果管道总共启动的 Databricks 运行数过多,请将一些管道迁移到新工作区。If pipelines launched too many Databricks runs in aggregate, migrate some pipelines to a new workspace.


  • 消息Could not parse request object: Expected 'key' and 'value' to be set for JSON map field base_parameters, got 'key: "..."' instead.Message: Could not parse request object: Expected 'key' and 'value' to be set for JSON map field base_parameters, got 'key: "..."' instead.

  • 原因Authoring error: No value provided for the parameter.Cause: Authoring error: No value provided for the parameter.

  • 建议:检查管道 JSON,确保 baseParameters 笔记本中的所有参数指定非空值。Recommendation: Inspect the pipeline JSON and ensure all parameters in the baseParameters notebook specify a nonempty value.


  • 消息User: SimpleUserContext{userId=..., name=user@company.com, orgId=...} is not authorized to access cluster.Message: User: SimpleUserContext{userId=..., name=user@company.com, orgId=...} is not authorized to access cluster.

  • 原因:不允许已生成访问令牌的用户访问链接服务中指定的 Databricks 群集。Cause: The user who generated the access token isn't allowed to access the Databricks cluster specified in the linked service.

  • 建议:确保该用户在工作区中拥有所需的权限。Recommendation: Ensure the user has the required permissions in the workspace.

错误代码:3203Error code: 3203

  • 消息The cluster is in Terminated state, not available to receive jobs. Please fix the cluster or retry later.Message: The cluster is in Terminated state, not available to receive jobs. Please fix the cluster or retry later.

  • 原因:群集已终止。Cause: The cluster was terminated. 对于交互式群集,此问题可能是争用条件问题。For interactive clusters, this issue might be a race condition.

  • 建议:若要避免此错误,请使用作业群集。Recommendation: To avoid this error, use job clusters.

错误代码:3204Error code: 3204

  • 消息Job execution failed.Message: Job execution failed.

  • 原因:错误消息指出了各种问题,例如意外的群集状态或特定的活动。Cause: Error messages indicate various issues, such as an unexpected cluster state or a specific activity. 往往不会显示任何错误消息。Often, no error message appears.

  • 建议:空值Recommendation: N/A

错误代码:3208Error code: 3208

  • 消息An error occurred while sending the request.Message: An error occurred while sending the request.

  • 原因: 与 Databricks 服务的网络连接已中断。Cause: The network connection to the Databricks service was interrupted.

  • 建议:如果使用的是自承载集成运行时,请确保来自集成运行时节点的网络连接是可靠的。Recommendation: If you're using a self-hosted integration runtime, make sure that the network connection is reliable from the integration runtime nodes. 如果使用的是 Azure 集成运行时,则重试通常有效。If you're using Azure integration runtime, retry usually works.

Azure Data Lake AnalyticsAzure Data Lake Analytics

下表适用于 U-SQL。The following table applies to U-SQL.

错误代码:2709Error code: 2709

  • 消息The access token is from the wrong tenant.Message: The access token is from the wrong tenant.

  • 原因:Azure Active Directory (Azure AD) 租户不正确。Cause: Incorrect Azure Active Directory (Azure AD) tenant.

  • 建议:Azure Active Directory (Azure AD) 租户不正确。Recommendation: Incorrect Azure Active Directory (Azure AD) tenant.


  • 消息We cannot accept your job at this moment. The maximum number of queued jobs for your account is 200. Message: We cannot accept your job at this moment. The maximum number of queued jobs for your account is 200.

  • 原因:此错误的原因是 Data Lake Analytics 中发生了限制。Cause: This error is caused by throttling on Data Lake Analytics.

  • 建议:减少提交到 Data Lake Analytics 的作业数。Recommendation: Reduce the number of submitted jobs to Data Lake Analytics. 更改活动中的数据工厂触发器和并发设置,或提高针对 Data Lake Analytics 的限制。Either change Data Factory triggers and concurrency settings on activities, or increase the limits on Data Lake Analytics.


  • 消息This job was rejected because it requires 24 AUs. This account's administrator-defined policy prevents a job from using more than 5 AUs.Message: This job was rejected because it requires 24 AUs. This account's administrator-defined policy prevents a job from using more than 5 AUs.

  • 原因:此错误的原因是 Data Lake Analytics 中发生了限制。Cause: This error is caused by throttling on Data Lake Analytics.

  • 建议:减少提交到 Data Lake Analytics 的作业数。Recommendation: Reduce the number of submitted jobs to Data Lake Analytics. 更改活动中的数据工厂触发器和并发设置,或提高针对 Data Lake Analytics 的限制。Either change Data Factory triggers and concurrency settings on activities, or increase the limits on Data Lake Analytics.

错误代码:2705Error code: 2705

  • 消息Forbidden. ACL verification failed. Either the resource does not exist or the user is not authorized to perform the requested operation.<br/> <br/> User is not able to access Data Lake Store. <br/> <br/> User is not authorized to use Data Lake Analytics.Message: Forbidden. ACL verification failed. Either the resource does not exist or the user is not authorized to perform the requested operation.<br/> <br/> User is not able to access Data Lake Store. <br/> <br/> User is not authorized to use Data Lake Analytics.

  • 原因:服务主体或证书无权访问存储中的文件。Cause: The service principal or certificate doesn't have access to the file in storage.

  • 建议:验证用户为 Data Lake Analytics 作业提供的服务主体或证书是否有权从根文件夹访问 Data Lake Analytics 帐户和默认的 Data Lake Storage 实例。Recommendation: Verify that the service principal or certificate that the user provides for Data Lake Analytics jobs has access to both the Data Lake Analytics account, and the default Data Lake Storage instance from the root folder.

错误代码:2711Error code: 2711

  • 消息Forbidden. ACL verification failed. Either the resource does not exist or the user is not authorized to perform the requested operation.<br/> <br/> User is not able to access Data Lake Store. <br/> <br/> User is not authorized to use Data Lake Analytics.Message: Forbidden. ACL verification failed. Either the resource does not exist or the user is not authorized to perform the requested operation.<br/> <br/> User is not able to access Data Lake Store. <br/> <br/> User is not authorized to use Data Lake Analytics.

  • 原因:服务主体或证书无权访问存储中的文件。Cause: The service principal or certificate doesn't have access to the file in storage.

  • 建议:验证用户为 Data Lake Analytics 作业提供的服务主体或证书是否有权从根文件夹访问 Data Lake Analytics 帐户和默认的 Data Lake Storage 实例。Recommendation: Verify that the service principal or certificate that the user provides for Data Lake Analytics jobs has access to both the Data Lake Analytics account, and the default Data Lake Storage instance from the root folder.


  • 消息Cannot find the 'Azure Data Lake Store' file or folder.Message: Cannot find the 'Azure Data Lake Store' file or folder.

  • 原因:U-SQL 文件的路径错误,或链接服务凭据没有访问权限。Cause: The path to the U-SQL file is wrong, or the linked service credentials don't have access.

  • 建议:验证该路径,以及链接服务中提供的凭据。Recommendation: Verify the path and credentials provided in the linked service.

错误代码:2704Error code: 2704

  • 消息Forbidden. ACL verification failed. Either the resource does not exist or the user is not authorized to perform the requested operation.<br/> <br/> User is not able to access Data Lake Store. <br/> <br/> User is not authorized to use Data Lake Analytics.Message: Forbidden. ACL verification failed. Either the resource does not exist or the user is not authorized to perform the requested operation.<br/> <br/> User is not able to access Data Lake Store. <br/> <br/> User is not authorized to use Data Lake Analytics.

  • 原因:服务主体或证书无权访问存储中的文件。Cause: The service principal or certificate doesn't have access to the file in storage.

  • 建议:验证用户为 Data Lake Analytics 作业提供的服务主体或证书是否有权从根文件夹访问 Data Lake Analytics 帐户和默认的 Data Lake Storage 实例。Recommendation: Verify that the service principal or certificate that the user provides for Data Lake Analytics jobs has access to both the Data Lake Analytics account, and the default Data Lake Storage instance from the root folder.

错误代码:2707Error code: 2707

  • 消息Cannot resolve the account of AzureDataLakeAnalytics. Please check 'AccountName' and 'DataLakeAnalyticsUri'.Message: Cannot resolve the account of AzureDataLakeAnalytics. Please check 'AccountName' and 'DataLakeAnalyticsUri'.

  • 原因:链接服务中的 Data Lake Analytics 帐户错误。Cause: The Data Lake Analytics account in the linked service is wrong.

  • 建议:验证是否提供了正确的帐户。Recommendation: Verify that the right account is provided.

错误代码:2703Error code: 2703

  • 消息Error Id: E_CQO_SYSTEM_INTERNAL_ERROR (or any error that starts with "Error Id:").Message: Error Id: E_CQO_SYSTEM_INTERNAL_ERROR (or any error that starts with "Error Id:").

  • 原因:错误来自 Data Lake Analytics。Cause: The error is from Data Lake Analytics.

  • 建议:作业已提交到 Data Lake Analytics 且脚本存在,但作业和脚本均发生故障。Recommendation: The job was submitted to Data Lake Analytics, and the script there, both failed. 请在 Data Lake Analytics 中进行调查。Investigate in Data Lake Analytics. 在门户中转到 Data Lake Analytics 帐户,使用数据工厂活动运行 ID(不要使用管道运行 ID)查找该作业。In the portal, go to the Data Lake Analytics account and look for the job by using the Data Factory activity run ID (don't use the pipeline run ID). 其中的作业将提供有关错误的详细信息,可帮助你进行故障排除。The job there provides more information about the error, and will help you troubleshoot.

    如果解决方法不明确,请联系 Data Lake Analytics 支持团队并提供作业统一资源定位符 (URL),包括你的帐户名和作业 ID。If the resolution isn't clear, contact the Data Lake Analytics support team and provide the job Universal Resource Locator (URL), which includes your account name and the job ID.

Azure 函数Azure functions

错误代码:3602Error code: 3602

  • 消息Invalid HttpMethod: '%method;'.Message: Invalid HttpMethod: '%method;'.

  • 原因: 活动有效负载中指定的 Httpmethod 不受 Azure 函数活动的支持。Cause: The Httpmethod specified in the activity payload isn't supported by Azure Function Activity.

  • 建议:支持的 Httpmethod 为:PUT、POST、GET、DELETE、OPTIONS、HEAD 和 TRACE。Recommendation: The supported Httpmethods are: PUT, POST, GET, DELETE, OPTIONS, HEAD, and TRACE.

错误代码:3603Error code: 3603

  • 消息Response Content is not a valid JObject.Message: Response Content is not a valid JObject.

  • 原因: 调用的 Azure 函数未在响应中返回 JSON 有效负载。Cause: The Azure function that was called didn't return a JSON Payload in the response. Azure 数据工厂 (ADF) Azure 函数活动仅支持 JSON 响应内容。Azure Data Factory (ADF) Azure function activity only supports JSON response content.

  • 建议:更新 Azure 函数以返回有效的 JSON 有效负载,例如,C# 函数可以返回 (ActionResult)new OkObjectResult("{\"Id\":\"123\"}");Recommendation: Update the Azure function to return a valid JSON Payload such as a C# function may return (ActionResult)new OkObjectResult("{\"Id\":\"123\"}");

错误代码:3606Error code: 3606

  • 消息:Azure 函数活动缺少函数密钥。Message: Azure function activity missing function key.

  • 原因: Azure 函数活动定义不完整。Cause: The Azure function activity definition isn't complete.

  • 建议:检查输入的 Azure 函数活动 JSON 定义是否包含名为 functionKey 的属性。Recommendation: Check that the input Azure function activity JSON definition has a property named functionKey.

错误代码:3607Error code: 3607

  • 消息Azure function activity missing function name.Message: Azure function activity missing function name.

  • 原因: Azure 函数活动定义不完整。Cause: The Azure function activity definition isn't complete.

  • 建议:检查输入的 Azure 函数活动 JSON 定义是否包含名为 functionName 的属性。Recommendation: Check that the input Azure function activity JSON definition has a property named functionName.

错误代码:3608Error code: 3608

  • 消息Call to provided Azure function '%FunctionName;' failed with status-'%statusCode;' and message - '%message;'.Message: Call to provided Azure function '%FunctionName;' failed with status-'%statusCode;' and message - '%message;'.

  • 原因: 活动定义中的 Azure 函数详细信息可能不正确。Cause: The Azure function details in the activity definition may be incorrect.

  • 建议:修复 Azure 函数详细信息,然后重试。Recommendation: Fix the Azure function details and try again.

错误代码:3609Error code: 3609

  • 消息Azure function activity missing functionAppUrl.Message: Azure function activity missing functionAppUrl.

  • 原因: Azure 函数活动定义不完整。Cause: The Azure function activity definition isn't complete.

  • 建议:检查输入的 Azure 函数活动 JSON 定义是否包含名为 functionAppUrl 的属性。Recommendation: Check that the input Azure Function activity JSON definition has a property named functionAppUrl.

错误代码:3610Error code: 3610

  • 消息There was an error while calling endpoint.Message: There was an error while calling endpoint.

  • 原因: 函数 URL 可能不正确。Cause: The function URL may be incorrect.

  • 建议:验证活动 JSON 中的 functionAppUrl 值是否正确,然后重试。Recommendation: Verify that the value for functionAppUrl in the activity JSON is correct and try again.

错误代码:3611Error code: 3611

  • 消息Azure function activity missing Method in JSON.Message: Azure function activity missing Method in JSON.

  • 原因: Azure 函数活动定义不完整。Cause: The Azure function activity definition isn't complete.

  • 建议:检查输入的 Azure 函数活动 JSON 定义是否包含名为 method 的属性。Recommendation: Check that the input Azure function activity JSON definition has a property named method.

错误代码:3612Error code: 3612

  • 消息Azure function activity missing LinkedService definition in JSON.Message: Azure function activity missing LinkedService definition in JSON.

  • 原因: Azure 函数活动定义不完整。Cause: The Azure function activity definition isn't complete.

  • 建议:检查输入的 Azure 函数活动 JSON 定义是否包含链接服务详细信息。Recommendation: Check that the input Azure function activity JSON definition has linked service details.

Azure 机器学习Azure Machine Learning

错误代码:4101Error code: 4101

  • 消息AzureMLExecutePipeline activity '%activityName;' has invalid value for property '%propertyName;'.Message: AzureMLExecutePipeline activity '%activityName;' has invalid value for property '%propertyName;'.

  • 原因:属性 %propertyName; 的定义格式错误或缺失。Cause: Bad format or missing definition of property %propertyName;.

  • 建议:检查是否使用正确的数据在活动 %activityName; 中定义了属性 %propertyName;Recommendation: Check if the activity %activityName; has the property %propertyName; defined with correct data.

错误代码:4110Error code: 4110

  • 消息AzureMLExecutePipeline activity missing LinkedService definition in JSON.Message: AzureMLExecutePipeline activity missing LinkedService definition in JSON.

  • 原因:AzureMLExecutePipeline 活动定义不完整。Cause: The AzureMLExecutePipeline activity definition isn't complete.

  • 建议:检查输入的 AzureMLExecutePipeline 活动 JSON 定义是否正确包含链接服务详细信息。Recommendation: Check that the input AzureMLExecutePipeline activity JSON definition has correctly linked service details.

错误代码:4111Error code: 4111

  • 消息AzureMLExecutePipeline activity has wrong LinkedService type in JSON. Expected LinkedService type: '%expectedLinkedServiceType;', current LinkedService type: Expected LinkedService type: '%currentLinkedServiceType;'.Message: AzureMLExecutePipeline activity has wrong LinkedService type in JSON. Expected LinkedService type: '%expectedLinkedServiceType;', current LinkedService type: Expected LinkedService type: '%currentLinkedServiceType;'.

  • 原因:活动定义不正确。Cause: Incorrect activity definition.

  • 建议:检查输入的 AzureMLExecutePipeline 活动 JSON 定义是否正确包含链接服务详细信息。Recommendation: Check that the input AzureMLExecutePipeline activity JSON definition has correctly linked service details.

错误代码:4112Error code: 4112

  • 消息AzureMLService linked service has invalid value for property '%propertyName;'.Message: AzureMLService linked service has invalid value for property '%propertyName;'.

  • 原因:属性“%propertyName;”的定义格式错误或缺失。Cause: Bad format or missing definition of property '%propertyName;'.

  • 建议:检查是否使用正确的数据在链接服务中定义了属性 %propertyName;Recommendation: Check if the linked service has the property %propertyName; defined with correct data.

错误代码:4121Error code: 4121

  • 消息Request sent to Azure Machine Learning for operation '%operation;' failed with http status code '%statusCode;'. Error message from Azure Machine Learning: '%externalMessage;'.Message: Request sent to Azure Machine Learning for operation '%operation;' failed with http status code '%statusCode;'. Error message from Azure Machine Learning: '%externalMessage;'.

  • 原因:用于访问 Azure 机器学习的凭据已过期。Cause: The Credential used to access Azure Machine Learning has expired.

  • 建议:验证凭据是否有效,然后重试。Recommendation: Verify that the credential is valid and retry.

错误代码:4122Error code: 4122

  • 消息Request sent to Azure Machine Learning for operation '%operation;' failed with http status code '%statusCode;'. Error message from Azure Machine Learning: '%externalMessage;'.Message: Request sent to Azure Machine Learning for operation '%operation;' failed with http status code '%statusCode;'. Error message from Azure Machine Learning: '%externalMessage;'.

  • 原因:Azure 机器学习链接服务中提供的凭据无效,或者没有操作权限。Cause: The credential provided in Azure Machine Learning Linked Service is invalid, or doesn't have permission for the operation.

  • 建议:验证链接服务中的凭据是否有效且有权访问 Azure 机器学习。Recommendation: Verify that the credential in Linked Service is valid, and has permission to access Azure Machine Learning.

错误代码:4123Error code: 4123

  • 消息Request sent to Azure Machine Learning for operation '%operation;' failed with http status code '%statusCode;'. Error message from Azure Machine Learning: '%externalMessage;'.Message: Request sent to Azure Machine Learning for operation '%operation;' failed with http status code '%statusCode;'. Error message from Azure Machine Learning: '%externalMessage;'.

  • 原因:活动的属性(例如 pipelineParameters)对于 Azure 机器学习 (ML) 管道无效。Cause: The properties of the activity such as pipelineParameters are invalid for the Azure Machine Learning (ML) pipeline.

  • 建议:检查活动属性的值是否与链接服务中指定的已发布 Azure ML 管道的预期有效负载相匹配。Recommendation: Check that the value of activity properties matches the expected payload of the published Azure ML pipeline specified in Linked Service.

错误代码:4124Error code: 4124

  • 消息Request sent to Azure Machine Learning for operation '%operation;' failed with http status code '%statusCode;'. Error message from Azure Machine Learning: '%externalMessage;'.Message: Request sent to Azure Machine Learning for operation '%operation;' failed with http status code '%statusCode;'. Error message from Azure Machine Learning: '%externalMessage;'.

  • 原因:已发布的 Azure ML 管道终结点不存在。Cause: The published Azure ML pipeline endpoint doesn't exist.

  • 建议:验证链接服务中指定的已发布 Azure 机器学习管道终结点是否在 Azure 机器学习中存在。Recommendation: Verify that the published Azure Machine Learning pipeline endpoint specified in Linked Service exists in Azure Machine Learning.

错误代码:4125Error code: 4125

  • 消息Request sent to Azure Machine Learning for operation '%operation;' failed with http status code '%statusCode;'. Error message from Azure Machine Learning: '%externalMessage;'.Message: Request sent to Azure Machine Learning for operation '%operation;' failed with http status code '%statusCode;'. Error message from Azure Machine Learning: '%externalMessage;'.

  • 原因:Azure 机器学习中出现服务器错误。Cause: There is a server error on Azure Machine Learning.

  • 建议:请稍后重试。Recommendation: Retry later. 如果问题持续出现,请联系 Azure 机器学习团队以获得帮助。Contact the Azure Machine Learning team for help if the issue continues.

错误代码:4126Error code: 4126

  • 消息Azure ML pipeline run failed with status: '%amlPipelineRunStatus;'. Azure ML pipeline run Id: '%amlPipelineRunId;'. Please check in Azure Machine Learning for more error logs.Message: Azure ML pipeline run failed with status: '%amlPipelineRunStatus;'. Azure ML pipeline run Id: '%amlPipelineRunId;'. Please check in Azure Machine Learning for more error logs.

  • 原因:Azure ML 管道运行失败。Cause: The Azure ML pipeline run failed.

  • 建议:检查 Azure 机器学习中的其他错误日志,然后修复 ML 管道。Recommendation: Check Azure Machine Learning for more error logs, then fix the ML pipeline.

通用Common

错误代码:2103Error code: 2103

  • 消息Please provide value for the required property '%propertyName;'.Message: Please provide value for the required property '%propertyName;'.

  • 原因: 尚未提供属性的必需值。Cause: The required value for the property has not been provided.

  • 建议:提供消息中的值,然后重试。Recommendation: Provide the value from the message and try again.

错误代码:2104Error code: 2104

  • 消息The type of the property '%propertyName;' is incorrect.Message: The type of the property '%propertyName;' is incorrect.

  • 原因: 提供的属性类型不正确。Cause: The provided property type isn't correct.

  • 建议:修复属性的类型,然后重试。Recommendation: Fix the type of the property and try again.

错误代码:2105Error code: 2105

  • 消息An invalid json is provided for property '%propertyName;'. Encountered an error while trying to parse: '%message;'.Message: An invalid json is provided for property '%propertyName;'. Encountered an error while trying to parse: '%message;'.

  • 原因: 属性的值无效,或未采用预期的格式。Cause: The value for the property is invalid or isn't in the expected format.

  • 建议:参阅属性的文档,并验证提供的值是否采用正确的格式和类型。Recommendation: Refer to the documentation for the property and verify that the value provided includes the correct format and type.

错误代码:2106Error code: 2106

  • 消息The storage connection string is invalid. %errorMessage;Message: The storage connection string is invalid. %errorMessage;

  • 原因: 存储的连接字符串无效或格式不正确。Cause: The connection string for the storage is invalid or has incorrect format.

  • 建议:转到 Azure 门户,找到你的存储,将连接字符串复制并粘贴到链接服务,然后重试。Recommendation: Go to the Azure portal and find your storage, then copy-and-paste the connection string into your linked service and try again.

错误代码:2108Error code: 2108

  • 消息Error calling the endpoint '%url;'. Response status code: '%code;'Message: Error calling the endpoint '%url;'. Response status code: '%code;'

  • 原因: 某个根本性问题(例如网络连接问题、DNS 失败、服务器证书验证问题或超时)导致请求失败。Cause: The request failed due to an underlying issue such as network connectivity, DNS failure, server certificate validation, or timeout.

  • 建议:使用 Fiddler/Postman 验证请求。Recommendation: Use Fiddler/Postman to validate the request.

错误代码:2110Error code: 2110

  • 消息The linked service type '%linkedServiceType;' is not supported for '%executorType;' activities.Message: The linked service type '%linkedServiceType;' is not supported for '%executorType;' activities.

  • 原因: 活动中指定了错误的链接服务。Cause: The linked service specified in the activity is incorrect.

  • 建议:验证链接服务类型是否为活动支持的类型之一。Recommendation: Verify that the linked service type is one of the supported types for the activity. 例如,对于 HDI 活动,链接服务类型可以是 HDInsight 或 HDInsightOnDemand。For example, the linked service type for HDI activities can be HDInsight or HDInsightOnDemand.

错误代码:2111Error code: 2111

  • 消息The type of the property '%propertyName;' is incorrect. The expected type is %expectedType;.Message: The type of the property '%propertyName;' is incorrect. The expected type is %expectedType;.

  • 原因: 提供的属性的类型不正确。Cause: The type of the provided property isn't correct.

  • 建议:修复属性类型,然后重试。Recommendation: Fix the property type and try again.

错误代码:2112Error code: 2112

  • 消息The cloud type is unsupported or could not be determined for storage from the EndpointSuffix '%endpointSuffix;'.Message: The cloud type is unsupported or could not be determined for storage from the EndpointSuffix '%endpointSuffix;'.

  • 原因: 云类型不受支持,或者对于 EndpointSuffix 中的存储来说无法确定。Cause: The cloud type is unsupported or couldn't be determined for storage from the EndpointSuffix.

  • 建议:使用另一个云中的存储,然后重试。Recommendation: Use storage in another cloud and try again.

错误代码:2128Error code: 2128

  • 消息No response from the endpoint. Possible causes: network connectivity, DNS failure, server certificate validation or timeout.Message: No response from the endpoint. Possible causes: network connectivity, DNS failure, server certificate validation or timeout.

  • 原因: 网络连接、DNS 失败、服务器证书验证或超时。Cause: Network connectivity, DNS failure, server certificate validation or timeout.

  • 建议:验证尝试访问的终结点是否响应请求。Recommendation: Validate that the endpoint you are trying to hit is responding to requests. 可以使用 Fiddler/Postman 等工具。You may use tools like Fiddler/Postman.

自定义Custom

下表适用于 Azure Batch。The following table applies to Azure Batch.

错误代码:2500Error code: 2500

  • 消息Hit unexpected exception and execution failed.Message: Hit unexpected exception and execution failed.

  • 原因Can't launch command, or the program returned an error code.Cause: Can't launch command, or the program returned an error code.

  • 建议:确保可执行文件存在。Recommendation: Ensure that the executable file exists. 如果程序已启动,请验证是否已将 stdout.txtstderr.txt 上传到存储帐户。If the program started, verify that stdout.txt and stderr.txt were uploaded to the storage account. 良好的做法是在代码中包含用于调试的日志。It's a good practice to include logs in your code for debugging.

错误代码:2501Error code: 2501

  • 消息Cannot access user batch account; please check batch account settings.Message: Cannot access user batch account; please check batch account settings.

  • 原因: Batch 访问密钥或池名称不正确。Cause: Incorrect Batch access key or pool name.

  • 建议:验证链接服务中的池名称和 Batch 访问密钥。Recommendation: Verify the pool name and the Batch access key in the linked service.

错误代码:2502Error code: 2502

  • 消息Cannot access user storage account; please check storage account settings.Message: Cannot access user storage account; please check storage account settings.

  • 原因: 存储帐户名称或访问密钥不正确。Cause: Incorrect storage account name or access key.

  • 建议:验证链接服务中的存储帐户名称和访问密钥。Recommendation: Verify the storage account name and the access key in the linked service.

错误代码:2504Error code: 2504

  • 消息Operation returned an invalid status code 'BadRequest'.Message: Operation returned an invalid status code 'BadRequest'.

  • 原因: 自定义活动的 folderPath 中的文件过多。Cause: Too many files in the folderPath of the custom activity. resourceFiles 的总大小不能超过 32,768 个字符。The total size of resourceFiles can't be more than 32,768 characters.

  • 建议:删除不必要的文件。或者压缩文件,并添加一个解压缩命令来解压缩文件。Recommendation: Remove unnecessary files, or Zip them and add an unzip command to extract them.

    例如,使用 powershell.exe -nologo -noprofile -command "& { Add-Type -A 'System.IO.Compression.FileSystem'; [IO.Compression.ZipFile]::ExtractToDirectory($zipFile, $folder); }" ; $folder\yourProgram.exeFor example, use powershell.exe -nologo -noprofile -command "& { Add-Type -A 'System.IO.Compression.FileSystem'; [IO.Compression.ZipFile]::ExtractToDirectory($zipFile, $folder); }" ; $folder\yourProgram.exe

错误代码:2505Error code: 2505

  • 消息Cannot create Shared Access Signature unless Account Key credentials are used.Message: Cannot create Shared Access Signature unless Account Key credentials are used.

  • 原因: 自定义活动仅支持使用访问密钥的存储帐户。Cause: Custom activities support only storage accounts that use an access key.

  • 建议:请参阅错误说明。Recommendation: Refer to the error description.

错误代码:2507Error code: 2507

  • 消息The folder path does not exist or is empty: ...Message: The folder path does not exist or is empty: ...

  • 原因: 存储帐户的指定路径下没有文件。Cause: No files are in the storage account at the specified path.

  • 建议:文件夹路径必须包含要运行的可执行文件。Recommendation: The folder path must contain the executable files you want to run.

错误代码:2508Error code: 2508

  • 消息There are duplicate files in the resource folder.Message: There are duplicate files in the resource folder.

  • 原因:具有相同名称的多个文件位于 folderPath 的不同子文件夹中。Cause: Multiple files of the same name are in different subfolders of folderPath.

  • 建议:自定义活动在 folderPath 下平展文件夹结构。Recommendation: Custom activities flatten folder structure under folderPath. 如果需要保留文件夹结构,请压缩文件,并使用一个解压缩命令将其解压缩到 Azure Batch 中。If you need to preserve the folder structure, zip the files and extract them in Azure Batch by using an unzip command.

    例如,使用 powershell.exe -nologo -noprofile -command "& { Add-Type -A 'System.IO.Compression.FileSystem'; [IO.Compression.ZipFile]::ExtractToDirectory($zipFile, $folder); }" ; $folder\yourProgram.exeFor example, use powershell.exe -nologo -noprofile -command "& { Add-Type -A 'System.IO.Compression.FileSystem'; [IO.Compression.ZipFile]::ExtractToDirectory($zipFile, $folder); }" ; $folder\yourProgram.exe

错误代码:2509Error code: 2509

  • 消息Batch url ... is invalid; it must be in Uri format.Message: Batch url ... is invalid; it must be in Uri format.

  • 原因: Batch URL 必须类似于 https://mybatchaccount.eastus.batch.azure.comCause: Batch URLs must be similar to https://mybatchaccount.eastus.batch.azure.com

  • 建议:请参阅错误说明。Recommendation: Refer to the error description.

错误代码:2510Error code: 2510

  • 消息An error occurred while sending the request.Message: An error occurred while sending the request.

  • 原因: Batch URL 无效。Cause: The batch URL is invalid.

  • 建议:验证 Batch URL。Recommendation: Verify the batch URL.

HDInsightHDInsight

错误代码:206Error code: 206

  • 消息The batch ID for Spark job is invalid. Please retry your job.Message: The batch ID for Spark job is invalid. Please retry your job.

  • 原因: 导致此错误的服务出现了内部问题。Cause: There was an internal problem with the service that caused this error.

  • 建议:此问题可能是暂时性的。Recommendation: This issue could be transient. 请在一段时间后重试作业。Retry your job after sometime.

错误代码:207Error code: 207

  • 消息Could not determine the region from the provided storage account. Please try using another primary storage account for the on demand HDI.Message: Could not determine the region from the provided storage account. Please try using another primary storage account for the on demand HDI.

  • 原因: 尝试从主存储帐户确定区域时出现内部错误。Cause: There was an internal error while trying to determine the region from the primary storage account.

  • 建议:尝试另一个存储。Recommendation: Try another storage.

错误代码:208Error code: 208

  • 消息Service Principal or the MSI authenticator are not instantiated. Please consider providing a Service Principal in the HDI on demand linked service which has permissions to create an HDInsight cluster in the provided subscription and try again.Message: Service Principal or the MSI authenticator are not instantiated. Please consider providing a Service Principal in the HDI on demand linked service which has permissions to create an HDInsight cluster in the provided subscription and try again.

  • 原因: 尝试读取服务主体或实例化 MSI 身份验证时出现内部错误。Cause: There was an internal error while trying to read the Service Principal or instantiating the MSI authentication.

  • 建议:请考虑提供一个有权在所提供订阅中创建 HDInsight 群集的服务主体,然后重试。Recommendation: Consider providing a service principal, which has permissions to create an HDInsight cluster in the provided subscription and try again. 验证是否正确设置了托管标识Verify that the Manage Identities are set up correctly.

错误代码:2300Error code: 2300

  • 消息Failed to submit the job '%jobId;' to the cluster '%cluster;'. Error: %errorMessage;.Message: Failed to submit the job '%jobId;' to the cluster '%cluster;'. Error: %errorMessage;.

  • 原因: 错误消息包含类似于 The remote name could not be resolved. 的消息。Cause: The error message contains a message similar to The remote name could not be resolved.. 提供的群集 URI 可能无效。The provided cluster URI might be invalid.

  • 建议:验证是否未删除该群集且提供的 URI 正确。Recommendation: Verify that the cluster hasn't been deleted, and that the provided URI is correct. 在浏览器中打开该 URI 时,应会看到 Ambari UI。When you open the URI in a browser, you should see the Ambari UI. 如果该群集位于虚拟网络中,则 URI 应是专用 URI。If the cluster is in a virtual network, the URI should be the private URI. 若要打开该 URI,请使用同一虚拟网络中的虚拟机 (VM)。To open it, use a Virtual Machine (VM) that is part of the same virtual network.

    有关详细信息,请参阅直接连接到 Apache Hadoop 服务For more information, see Directly connect to Apache Hadoop services.


  • 原因: 如果错误消息包含类似于 A task was canceled. 的消息,则意味着作业提交超时。Cause: If the error message contains a message similar to A task was canceled., the job submission timed out.

  • 建议:这可能是普通的 HDInsight 连接问题或网络连接问题。Recommendation: The problem could be either general HDInsight connectivity or network connectivity. 首先确认是否可以从任何浏览器打开 HDInsight Ambari UI。First confirm that the HDInsight Ambari UI is available from any browser. 然后检查凭据是否仍然有效。Then check that your credentials are still valid.

    如果使用自承载集成运行时 (IR),请从安装了自承载 IR 的 VM 或计算机执行此步骤。If you're using a self-hosted integrated runtime (IR), perform this step from the VM or machine where the self-hosted IR is installed. 然后再次尝试从数据工厂提交作业。Then try submitting the job from Data Factory again.

    有关详细信息,请阅读 Ambari Web UIFor more information, read Ambari Web UI.


  • 原因: 如果错误消息包含类似于“User admin is locked out in Ambari”或“Unauthorized: Ambari user name or password is incorrect”的消息,则意味着 HDInsight 的凭据不正确或已过期。Cause: When the error message contains a message similar to User admin is locked out in Ambari or Unauthorized: Ambari user name or password is incorrect, the credentials for HDInsight are incorrect or have expired.

  • 建议:更正凭据,然后重新部署链接服务。Recommendation: Correct the credentials and redeploy the linked service. 首先在任何浏览器中打开群集 URI 并尝试登录,以便验证凭据在 HDInsight 中是否有效。First verify that the credentials work on HDInsight by opening the cluster URI on any browser and trying to sign in. 如果凭据无效,可从 Azure 门户重置凭据。If the credentials don't work, you can reset them from the Azure portal.

    对于 ESP 群集,可通过自助式密码重置来重置密码。For ESP cluster, reset the password through self service password reset.


  • 原因: 如果错误消息包含类似于“502 - Web server received an invalid response while acting as a gateway or proxy server”的消息,则此错误是 HDInsight 服务返回的。Cause: When the error message contains a message similar to 502 - Web server received an invalid response while acting as a gateway or proxy server, this error is returned by HDInsight service.

  • 建议:当 Ambari 服务器进程已关闭时,往往会发生 502 错误。Recommendation: A 502 error often occurs when your Ambari Server process was shut down. 可以通过重启头节点来重启 Ambari 服务。You can restart the Ambari Services by rebooting the head node.

    1. 使用 SSH 连接到 HDInsight 上的节点之一。Connect to one of your nodes on HDInsight using SSH.

    2. 运行 ping headnodehost 以识别活动头节点主机。Identify your active head node host by running ping headnodehost.

    3. 当 Ambari 服务器位于活动头节点上时,使用 SSH 连接到活动头节点。Connect to your active head node as Ambari Server sits on the active head node using SSH.

    4. 重启活动头节点。Reboot the active head node.

      有关详细信息,请参阅 Azure HDInsight 故障排除文档。For more information, look through the Azure HDInsight troubleshooting documentation. 例如:For example:


  • 原因: 如果错误消息包含类似于“Unable to service the submit job request as templeton service is busy with too many submit job requests”或“Queue root.joblauncher already has 500 applications, cannot accept submission of application”的消息,则意味着同时提交到 HDInsight 的作业过多。Cause: When the error message contains a message similar to Unable to service the submit job request as templeton service is busy with too many submit job requests or Queue root.joblauncher already has 500 applications, cannot accept submission of application, too many jobs are being submitted to HDInsight at the same time.

  • 建议:限制提交到 HDInsight 的并发作业数。Recommendation: Limit the number of concurrent jobs submitted to HDInsight. 如果这些作业是同一活动提交的,请参阅“数据工厂活动并发性”。Refer to Data Factory activity concurrency if the jobs are being submitted by the same activity. 更改触发器,以将并发管道运行分散到不同的时间。Change the triggers so the concurrent pipeline runs are spread out over time.

    请参阅 HDInsight 文档,根据错误中的建议调整 templeton.parallellism.job.submitRefer to HDInsight documentation to adjust templeton.parallellism.job.submit as the error suggests.

错误代码:2301Error code: 2301

  • 消息Could not get the status of the application '%physicalJobId;' from the HDInsight service. Received the following error: %message;. Please refer to HDInsight troubleshooting documentation or contact their support for further assistance.Message: Could not get the status of the application '%physicalJobId;' from the HDInsight service. Received the following error: %message;. Please refer to HDInsight troubleshooting documentation or contact their support for further assistance.

  • 原因: HDInsight 群集或服务出现问题。Cause: HDInsight cluster or service has issues.

  • 建议:如果 ADF 尝试请求正在运行的作业的状态时未收到 HDInsight 群集的响应,则会发生此错误。Recommendation: This error occurs when ADF doesn't receive a response from HDInsight cluster when attempting to request the status of the running job. 此问题可能是群集本身造成的,也可能是 HDInsight 服务中断造成的。This issue might be on the cluster itself, or HDInsight service might have an outage.

    请参阅 https://docs.microsoft.com/azure/hdinsight/hdinsight-troubleshoot-guide 上的 HDInsight 故障排除文档,或联系支持人员以获得更多帮助。Refer to HDInsight troubleshooting documentation at https://docs.microsoft.com/azure/hdinsight/hdinsight-troubleshoot-guide, or contact their support for further assistance.

错误代码:2302Error code: 2302

  • 消息Hadoop job failed with exit code '%exitCode;'. See '%logPath;/stderr' for more details. Alternatively, open the Ambari UI on the HDI cluster and find the logs for the job '%jobId;'. Contact HDInsight team for further support.Message: Hadoop job failed with exit code '%exitCode;'. See '%logPath;/stderr' for more details. Alternatively, open the Ambari UI on the HDI cluster and find the logs for the job '%jobId;'. Contact HDInsight team for further support.

  • 原因: 作业已提交到 HDI 群集,但在群集上失败。Cause: The job was submitted to the HDI cluster and failed there.

  • 建议Recommendation:

  1. 检查 Ambari UI:Check Ambari UI:
    1. 确保所有服务仍在运行。Ensure that all services are still running.
    2. 在 Ambari UI 中,检查仪表板中的警报部分。From Ambari UI, check the alert section in your dashboard.
      1. 有关警报的详细信息以及警报解决方法,请参阅管理和监视群集For more information on alerts and resolutions to alerts, see Managing and Monitoring a Cluster.
    3. 检查 YARN 内存。Review your YARN memory. 如果 YARN 内存很高,作业处理可能会延迟。If your YARN memory is high, the processing of your jobs may be delayed. 如果没有足够的资源来适应 Spark 应用程序/作业,请纵向扩展群集,以确保群集具有足够的内存和核心。If you do not have enough resources to accommodate your Spark application/job, scale up the cluster to ensure the cluster has enough memory and cores.
  2. 运行示例测试作业。Run a Sample test job.
    1. 如果在 HDInsight 后端运行相同的作业,请检查该作业是否成功。If you run the same job on HDInsight backend, check that it succeeded. 有关示例运行的示例,请参阅运行 HDInsight 随附的 MapReduce 示例For examples of sample runs, see Run the MapReduce examples included in HDInsight
  3. 如果作业在 HDInsight 上仍然失败,请检查要提供给支持人员的应用程序日志和信息:If the job still failed on HDInsight, check the application logs and information, which to provide to Support:
    1. 检查作业是否已提交到 YARN。Check whether the job was submitted to YARN. 如果作业尚未提交到 YARN,请使用 --master yarnIf the job wasn't submitted to yarn, use --master yarn.
    2. 如果应用程序已执行完毕,请收集 YARN 应用程序的开始时间和结束时间。If the application finished execution, collect the start time and end time of the YARN Application. 如果应用程序尚未执行完毕,请收集开始时间/启动时间。If the application didn't complete the execution, collect Start time/Launch time.
    3. 使用 yarn logs -applicationId <Insert_Your_Application_ID> 检查并收集应用程序日志。Check and collect application log with yarn logs -applicationId <Insert_Your_Application_ID>.
    4. 检查并收集 /var/log/hadoop-yarn/yarn 目录下的 YARN 资源管理器日志。Check and collect the yarn Resource Manager logs under the /var/log/hadoop-yarn/yarn directory.
    5. 如果这些步骤不足以解决问题,请联系 Azure HDInsight 团队以获得支持,并提供上述日志和时间戳。If these steps are not enough to resolve the issue, contact Azure HDInsight team for support and provide the above logs and timestamps.

错误代码:2303Error code: 2303

  • 消息Hadoop job failed with transient exit code '%exitCode;'. See '%logPath;/stderr' for more details. Alternatively, open the Ambari UI on the HDI cluster and find the logs for the job '%jobId;'. Try again or contact HDInsight team for further support.Message: Hadoop job failed with transient exit code '%exitCode;'. See '%logPath;/stderr' for more details. Alternatively, open the Ambari UI on the HDI cluster and find the logs for the job '%jobId;'. Try again or contact HDInsight team for further support.

  • 原因: 作业已提交到 HDI 群集,但在群集上失败。Cause: The job was submitted to the HDI cluster and failed there.

  • 建议Recommendation:

  1. 检查 Ambari UI:Check Ambari UI:
    1. 确保所有服务仍在运行。Ensure that all services are still running.
    2. 在 Ambari UI 中,检查仪表板中的警报部分。From Ambari UI, check the alert section in your dashboard.
      1. 有关警报的详细信息以及警报解决方法,请参阅管理和监视群集For more information on alerts and resolutions to alerts, see Managing and Monitoring a Cluster.
    3. 检查 YARN 内存。Review your YARN memory. 如果 YARN 内存很高,作业处理可能会延迟。If your YARN memory is high, the processing of your jobs may be delayed. 如果没有足够的资源来适应 Spark 应用程序/作业,请纵向扩展群集,以确保群集具有足够的内存和核心。If you do not have enough resources to accommodate your Spark application/job, scale up the cluster to ensure the cluster has enough memory and cores.
  2. 运行示例测试作业。Run a Sample test job.
    1. 如果在 HDInsight 后端运行相同的作业,请检查该作业是否成功。If you run the same job on HDInsight backend, check that it succeeded. 有关示例运行的示例,请参阅运行 HDInsight 随附的 MapReduce 示例For examples of sample runs, see Run the MapReduce examples included in HDInsight
  3. 如果作业在 HDInsight 上仍然失败,请检查要提供给支持人员的应用程序日志和信息:If the job still failed on HDInsight, check the application logs and information, which to provide to Support:
    1. 检查作业是否已提交到 YARN。Check whether the job was submitted to YARN. 如果作业尚未提交到 YARN,请使用 --master yarnIf the job wasn't submitted to yarn, use --master yarn.
    2. 如果应用程序已执行完毕,请收集 YARN 应用程序的开始时间和结束时间。If the application finished execution, collect the start time and end time of the YARN Application. 如果应用程序尚未执行完毕,请收集开始时间/启动时间。If the application didn't complete the execution, collect Start time/Launch time.
    3. 使用 yarn logs -applicationId <Insert_Your_Application_ID> 检查并收集应用程序日志。Check and collect application log with yarn logs -applicationId <Insert_Your_Application_ID>.
    4. 检查并收集 /var/log/hadoop-yarn/yarn 目录下的 YARN 资源管理器日志。Check and collect the yarn Resource Manager logs under the /var/log/hadoop-yarn/yarn directory.
    5. 如果这些步骤不足以解决问题,请联系 Azure HDInsight 团队以获得支持,并提供上述日志和时间戳。If these steps are not enough to resolve the issue, contact Azure HDInsight team for support and provide the above logs and timestamps.

错误代码:2304Error code: 2304

  • 消息MSI authentication is not supported on storages for HDI activities.Message: MSI authentication is not supported on storages for HDI activities.

  • 原因: 为 HDInsight (HDI) 链接服务或 HDI 活动中使用的存储链接服务配置了不受支持的 MSI 身份验证。Cause: The storage linked services used in the HDInsight (HDI) linked service or HDI activity, are configured with an MSI authentication that isn't supported.

  • 建议:为 HDI 链接服务或 HDI 活动中使用的存储帐户提供完整的连接字符串。Recommendation: Provide full connection strings for storage accounts used in the HDI linked service or HDI activity.

错误代码:2305Error code: 2305

  • 消息Failed to initialize the HDInsight client for the cluster '%cluster;'. Error: '%message;'Message: Failed to initialize the HDInsight client for the cluster '%cluster;'. Error: '%message;'

  • 原因: HDI 群集的连接信息不正确、提供的用户无权执行所需的操作,或者 HDInsight 服务在响应来自 ADF 的请求时出现问题。Cause: The connection information for the HDI cluster is incorrect, the provided user doesn't have permissions to perform the required action, or the HDInsight service has issues responding to requests from ADF.

  • 建议:验证用户信息是否正确,并验证是否可以在安装 IR(如果使用自承载 IR)的 VM 上的浏览器中打开 HDI 群集的 Ambari UI,或者是否可以从任何计算机(如果使用 Azure IR)打开此 UI。Recommendation: Verify that the user information is correct, and that the Ambari UI for the HDI cluster can be opened in a browser from the VM where the IR is installed (for a self-hosted IR), or can be opened from any machine (for Azure IR).

错误代码:2306Error code: 2306

  • 消息An invalid json is provided for script action '%scriptActionName;'. Error: '%message;'Message: An invalid json is provided for script action '%scriptActionName;'. Error: '%message;'

  • 原因: 为脚本操作提供的 JSON 无效。Cause: The JSON provided for the script action is invalid.

  • 建议:错误消息应有助于识别问题。Recommendation: The error message should help to identify the issue. 请修复 JSON 配置,然后重试。Fix the json configuration and try again.

    有关详细信息,请查看 Azure HDInsight 按需链接服务Check Azure HDInsight on-demand linked service for more information.

错误代码:2310Error code: 2310

  • 消息Failed to submit Spark job. Error: '%message;'Message: Failed to submit Spark job. Error: '%message;'

  • 原因: ADF 已尝试使用 Livy API (livy/batch) 在 Spark 群集上创建批,但收到了错误。Cause: ADF tried to create a batch on a Spark cluster using Livy API (livy/batch), but received an error.

  • 建议:请按照错误消息解决问题。Recommendation: Follow the error message to fix the issue. 如果信息不足以解决问题,请联系 HDI 团队,并向他们提供可在 ADF“监视”页的活动运行输出中找到的批 ID 和作业 ID。If there isn't enough information to get it resolved, contact the HDI team and provide them the batch ID and job ID, which can be found in the activity run Output in ADF Monitoring page. 若要进一步进行故障排除,请收集批处理作业的完整日志。To troubleshoot further, collect the full log of the batch job.

    若要详细了解如何收集完整日志,请参阅获取批处理作业的完整日志For more information on how to collect the full log, see Get the full log of a batch job.

错误代码:2312Error code: 2312

  • 消息Spark job failed, batch id:%batchId;. Please follow the links in the activity run Output from ADF Monitoring page to troubleshoot the run on HDInsight Spark cluster. Please contact HDInsight support team for further assistance.Message: Spark job failed, batch id:%batchId;. Please follow the links in the activity run Output from ADF Monitoring page to troubleshoot the run on HDInsight Spark cluster. Please contact HDInsight support team for further assistance.

  • 原因: 作业在 HDInsight Spark 群集上失败。Cause: The job failed on the HDInsight Spark cluster.

  • 建议:点击 ADF“监视”页上的活动运行输出中的链接,排查 HDInsight Spark 群集上的运行问题。Recommendation: Follow the links in the activity run Output in ADF Monitoring page to troubleshoot the run on HDInsight Spark cluster. 联系 HDInsight 支持团队以获得更多帮助。Contact HDInsight support team for further assistance.

    若要详细了解如何收集完整日志,请参阅获取批处理作业的完整日志For more information on how to collect the full log, see Get the full log of a batch job.

错误代码:2313Error code: 2313

  • 消息The batch with ID '%batchId;' was not found on Spark cluster. Open the Spark History UI and try to find it there. Contact HDInsight support for further assistance.Message: The batch with ID '%batchId;' was not found on Spark cluster. Open the Spark History UI and try to find it there. Contact HDInsight support for further assistance.

  • 原因: 已在 HDInsight Spark 群集上删除该批。Cause: The batch was deleted on the HDInsight Spark cluster.

  • 建议:排查 HDInsight Spark 群集上的批问题。Recommendation: Troubleshoot batches on the HDInsight Spark cluster. 联系 HDInsight 支持人员以获得更多帮助。Contact HDInsight support for further assistance.

    若要详细了解如何收集完整日志,请参阅获取批处理作业的完整日志,并与 HDInsight 支持人员共享完整日志,以获得更多帮助。For more information on how to collect the full log, see Get the full log of a batch job, and share the full log with HDInsight support for further assistance.

错误代码:2328Error code: 2328

  • 消息Failed to create the on demand HDI cluster. Cluster or linked service name: '%clusterName;', error: '%message;'Message: Failed to create the on demand HDI cluster. Cluster or linked service name: '%clusterName;', error: '%message;'

  • 原因: 错误消息应会显示问题的详细信息。Cause: The error message should show the details of what went wrong.

  • 建议:错误消息应有助于排查问题。Recommendation: The error message should help to troubleshoot the issue.

错误代码:2329Error code: 2329

  • 消息Failed to delete the on demand HDI cluster. Cluster or linked service name: '%clusterName;', error: '%message;'Message: Failed to delete the on demand HDI cluster. Cluster or linked service name: '%clusterName;', error: '%message;'

  • 原因: 错误消息应会显示问题的详细信息。Cause: The error message should show the details of what went wrong.

  • 建议:错误消息应有助于排查问题。Recommendation: The error message should help to troubleshoot the issue.

错误代码:2331Error code: 2331

  • 消息The file path should not be null or empty.Message: The file path should not be null or empty.

  • 原因: 提供的文件路径为空。Cause: The provided file path is empty.

  • 建议:请提供存在的文件的路径。Recommendation: Provide a path for a file that exists.

错误代码:2340Error code: 2340

  • 消息HDInsightOnDemand linked service does not support execution via SelfHosted IR. Your IR name is '%IRName;'. Please select an Azure IR instead.Message: HDInsightOnDemand linked service does not support execution via SelfHosted IR. Your IR name is '%IRName;'. Please select an Azure IR instead.

  • 原因: HDInsightOnDemand 链接服务不支持通过 SelfHosted IR 执行。Cause: The HDInsightOnDemand linked service doesn't support execution via SelfHosted IR.

  • 建议:选择一个 Azure IR,然后重试。Recommendation: Select an Azure IR and try again.

错误代码:2341Error code: 2341

  • 消息HDInsight cluster URL '%clusterUrl;' is incorrect, it must be in URI format and the scheme must be 'https'.Message: HDInsight cluster URL '%clusterUrl;' is incorrect, it must be in URI format and the scheme must be 'https'.

  • 原因: 提供的 URL 未采用正确的格式。Cause: The provided URL isn't in correct format.

  • 建议:修复群集 URL,然后重试。Recommendation: Fix the cluster URL and try again.

错误代码:2342Error code: 2342

  • 消息Failed to connect to HDInsight cluster: '%errorMessage;'.Message: Failed to connect to HDInsight cluster: '%errorMessage;'.

  • 原因: 为群集提供了错误的凭据、存在网络配置或连接问题,或者 IR 在连接到群集时出现问题。Cause: Either the provided credentials are wrong for the cluster, or there was a network configuration or connection issue, or the IR is having problems connecting to the cluster.

  • 建议Recommendation:

    1. 通过在浏览器中打开 HDInsight 群集的 Ambari UI,验证凭据是否正确。Verify that the credentials are correct by opening the HDInsight cluster's Ambari UI in a browser.

    2. 如果群集位于虚拟网络 (VNet) 中,而使用的是自承载 IR,则 HDI URL 必须是该 VNet 中的专用 URL,且应在群集名称后面列出“-int”。If the cluster is in Virtual Network (VNet) and a self-hosted IR is being used, the HDI URL must be the private URL in VNets, and should have '-int' listed after the cluster name.

      例如,将 https://mycluster.azurehdinsight.net/ 更改为 https://mycluster-int.azurehdinsight.net/For example, change https://mycluster.azurehdinsight.net/ to https://mycluster-int.azurehdinsight.net/. 请注意,-int 位于 mycluster 的后面,.azurehdinsight.net 的前面Note the -int after mycluster, but before .azurehdinsight.net

    3. 如果群集位于 VNet 中,而使用的是自承载 IR,并且已使用专用 URL,但连接仍然失败,则表示安装 IR 的 VM 在连接到 HDI 时出现了问题。If the cluster is in VNet, the self-hosted IR is being used, and the private URL was used, and yet the connection still failed, then the VM where the IR is installed had problems connecting to the HDI.

      连接到安装了 IR 的 VM,并在浏览器中打开 Ambari UI。Connect to the VM where the IR is installed and open the Ambari UI in a browser. 对群集使用专用 URL。Use the private URL for the cluster. 应该能够在浏览器中建立此连接。This connection should work from the browser. 如果不能,请联系 HDInsight 支持团队以获得更多帮助。If it doesn't, contact HDInsight support team for further assistance.

    4. 如果未使用自承载 IR,则 HDI 群集应可公开访问。If self-hosted IR isn't being used, then the HDI cluster should be accessible publicly. 在浏览器中打开 Ambari UI,并检查它是否已打开。Open the Ambari UI in a browser and check that it opens up. 如果群集或其上的服务出现任何问题,请联系 HDInsight 支持团队以获得帮助。If there are any issues with the cluster or the services on it, contact HDInsight support team for assistance.

      ADF 链接服务中使用的 HDI 群集 URL 必须可供 ADF IR(自承载 IR 或 Azure IR)访问,这样才能通过连接测试,并使运行正常工作。The HDI cluster URL used in ADF linked service must be accessible for ADF IR (self-hosted or Azure) in order for the test connection to pass, and for runs to work. 可以通过在 VM 或任意公共计算机上的浏览器中打开该 URL,来验证此状态。This state can be verified by opening the URL from a browser either from VM, or from any public machine.

错误代码:2343Error code: 2343

  • 消息User name and password cannot be null or empty to connect to the HDInsight cluster.Message: User name and password cannot be null or empty to connect to the HDInsight cluster.

  • 原因: 用户名或密码为空。Cause: Either the user name or the password is empty.

  • 建议:提供连接到 HDI 所需的正确凭据,然后重试。Recommendation: Provide the correct credentials to connect to HDI and try again.

错误代码:2345Error code: 2345

  • 消息Failed to read the content of the hive script. Error: '%message;'Message: Failed to read the content of the hive script. Error: '%message;'

  • 原因: 脚本文件不存在,或 ADF 无法连接到脚本所在的位置。Cause: The script file doesn't exist or ADF couldn't connect to the location of the script.

  • 建议:验证脚本是否存在,以及关联的链接服务是否有适当的连接凭据。Recommendation: Verify that the script exists, and that the associated linked service has the proper credentials for a connection.

错误代码:2346Error code: 2346

  • 消息Failed to create ODBC connection to the HDI cluster with error message '%message;'.Message: Failed to create ODBC connection to the HDI cluster with error message '%message;'.

  • 原因: ADF 已尝试与 HDI 群集建立开放式数据库连接 (ODBC) 连接,但失败并出现错误。Cause: ADF tried to establish an Open Database Connectivity (ODBC) connection to the HDI cluster, and it failed with an error.

  • 建议Recommendation:

    1. 确认已正确设置 ODBC/Java Database Connectivity (JDBC) 连接。Confirm that you correctly set up your ODBC/Java Database Connectivity (JDBC) connection.
      1. 对于 JDBC,如果使用相同的虚拟网络,则可以从以下位置获取此连接:For JDBC, if you're using the same virtual network, you can get this connection from:
        Hive -> Summary -> HIVESERVER2 JDBC URL
      2. 若要确保正确设置 JDBC,请参阅在 HDInsight 中通过 JDBC 驱动程序查询 Apache HiveTo ensure that you have the correct JDBC set up, see Query Apache Hive through the JDBC driver in HDInsight.
      3. 对于开放式数据库 (ODB),请参阅教程:使用 ODBC 和 PowerShell 查询 Apache Hive 以确保设置正确。For Open Database (ODB), see Tutorial: Query Apache Hive with ODBC and PowerShell to ensure that you have the correct setup.
    2. 验证 Hiveserver2、Hive 元存储和 Hiveserver2 Interactive 是否处于活动运行状态。Verify that Hiveserver2, Hive Metastore, and Hiveserver2 Interactive are active and working.
    3. 检查 Ambari 用户界面 (UI):Check the Ambari user interface (UI):
      1. 确保所有服务仍在运行。Ensure that all services are still running.
      2. 在 Ambari UI 中,检查仪表板中的警报部分。From the Ambari UI, check the alert section in your dashboard.
        1. 有关警报的详细信息以及警报解决方法,请参阅管理和监视群集For more information on alerts and resolutions to alerts, see Managing and Monitoring a Cluster .
    4. 如果这些步骤不足以解决问题,请联系 Azure HDInsight 团队。If these steps are not enough to resolve the issue, contact the Azure HDInsight team.

错误代码:2347Error code: 2347

  • 消息Hive execution through ODBC failed with error message '%message;'.Message: Hive execution through ODBC failed with error message '%message;'.

  • 原因: ADF 已通过 ODBC 连接将要执行的 Hive 脚本提交到 HDI 群集,但脚本在 HDI 上失败。Cause: ADF submitted the hive script for execution to the HDI cluster via ODBC connection, and the script has failed on HDI.

  • 建议Recommendation:

    1. 确认已正确设置 ODBC/Java Database Connectivity (JDBC) 连接。Confirm that you correctly set up your ODBC/Java Database Connectivity (JDBC) connection.
      1. 对于 JDBC,如果使用相同的虚拟网络,则可以从以下位置获取此连接:For JDBC, if you're using the same virtual network, you can get this connection from:
        Hive -> Summary -> HIVESERVER2 JDBC URL
      2. 若要确保正确设置 JDBC,请参阅在 HDInsight 中通过 JDBC 驱动程序查询 Apache HiveTo ensure that you have the correct JDBC set up, see Query Apache Hive through the JDBC driver in HDInsight.
      3. 对于开放式数据库 (ODB),请参阅教程:使用 ODBC 和 PowerShell 查询 Apache Hive 以确保设置正确。For Open Database (ODB), see Tutorial: Query Apache Hive with ODBC and PowerShell to ensure that you have the correct setup.
    2. 验证 Hiveserver2、Hive 元存储和 Hiveserver2 Interactive 是否处于活动运行状态。Verify that Hiveserver2, Hive Metastore, and Hiveserver2 Interactive are active and working.
    3. 检查 Ambari 用户界面 (UI):Check the Ambari user interface (UI):
      1. 确保所有服务仍在运行。Ensure that all services are still running.
      2. 在 Ambari UI 中,检查仪表板中的警报部分。From the Ambari UI, check the alert section in your dashboard.
        1. 有关警报的详细信息以及警报解决方法,请参阅管理和监视群集For more information on alerts and resolutions to alerts, see Managing and Monitoring a Cluster .
    4. 如果这些步骤不足以解决问题,请联系 Azure HDInsight 团队。If these steps are not enough to resolve the issue, contact the Azure HDInsight team.

错误代码:2348Error code: 2348

  • 消息The main storage has not been initialized. Please check the properties of the storage linked service in the HDI linked service.Message: The main storage has not been initialized. Please check the properties of the storage linked service in the HDI linked service.

  • 原因: 未正确设置存储链接服务属性。Cause: The storage linked service properties are not set correctly.

  • 建议:HDI 活动的主存储链接服务中仅支持完整的连接字符串。Recommendation: Only full connection strings are supported in the main storage linked service for HDI activities. 验证你是否未使用 MSI 授权或应用程序。Verify that you are not using MSI authorizations or applications.

错误代码:2350Error code: 2350

  • 消息Failed to prepare the files for the run '%jobId;'. HDI cluster: '%cluster;', Error: '%errorMessage;'Message: Failed to prepare the files for the run '%jobId;'. HDI cluster: '%cluster;', Error: '%errorMessage;'

  • 原因: 提供的凭据(用于连接到文件所在的存储)不正确,或存储中不存在文件。Cause: The credentials provided to connect to the storage where the files should be located are incorrect, or the files do not exist there.

  • 建议:此错误是在 ADF 对 HDI 活动进行准备时发生的。ADF 在将作业提交到 HDI 之前,会尝试将文件复制到主存储。Recommendation: This error occurs when ADF prepares for HDI activities, and tries to copy files to the main storage before submitting the job to HDI. 请检查提供的位置是否存在文件以及存储连接是否正确。Check that files exist in the provided location, and that the storage connection is correct. ADF HDI 活动不支持与 HDI 活动相关的存储帐户中的 MSI 身份验证,因此请验证这些链接服务是否有完整的密钥或者是否使用 Azure Key Vault。As ADF HDI activities do not support MSI authentication on storage accounts related to HDI activities, verify that those linked services have full keys or are using Azure Key Vault.

错误代码:2351Error code: 2351

  • 消息Could not open the file '%filePath;' in container/fileSystem '%container;'.Message: Could not open the file '%filePath;' in container/fileSystem '%container;'.

  • 原因: 文件在指定的路径不存在。Cause: The file doesn't exist at specified path.

  • 建议:检查该文件是否确实存在,以及连接信息指向此文件的链接服务是否有正确的凭据。Recommendation: Check whether the file actually exists, and that the linked service with connection info pointing to this file has the correct credentials.

错误代码:2352Error code: 2352

  • 消息The file storage has not been initialized. Please check the properties of the file storage linked service in the HDI activity.Message: The file storage has not been initialized. Please check the properties of the file storage linked service in the HDI activity.

  • 原因: 未正确设置文件存储链接服务属性。Cause: The file storage linked service properties are not set correctly.

  • 建议:验证是否已正确配置文件存储链接服务的属性。Recommendation: Verify that the properties of the file storage linked service are properly configured.

错误代码:2353Error code: 2353

  • 消息The script storage has not been initialized. Please check the properties of the script storage linked service in the HDI activity.Message: The script storage has not been initialized. Please check the properties of the script storage linked service in the HDI activity.

  • 原因: 未正确设置脚本存储链接服务属性。Cause: The script storage linked service properties are not set correctly.

  • 建议:验证是否已正确配置脚本存储链接服务的属性。Recommendation: Verify that the properties of the script storage linked service are properly configured.

错误代码:2354Error code: 2354

  • 消息The storage linked service type '%linkedServiceType;' is not supported for '%executorType;' activities for property '%linkedServicePropertyName;'.Message: The storage linked service type '%linkedServiceType;' is not supported for '%executorType;' activities for property '%linkedServicePropertyName;'.

  • 原因: 活动不支持存储链接服务类型。Cause: The storage linked service type isn't supported by the activity.

  • 建议:验证所选的链接服务是否为活动支持的类型之一。Recommendation: Verify that the selected linked service has one of the supported types for the activity. HDI 活动支持 AzureBlobStorage 和 AzureBlobFSStorage 链接服务。HDI activities support AzureBlobStorage and AzureBlobFSStorage linked services.

    有关详细信息,请阅读可与 Azure HDInsight 群集配合使用的存储选项的比较For more information, read Compare storage options for use with Azure HDInsight clusters

错误代码:2355Error code: 2355

  • 消息The '%value' provided for commandEnvironment is incorrect. The expected value should be an array of strings where each string has the format CmdEnvVarName=CmdEnvVarValue.Message: The '%value' provided for commandEnvironment is incorrect. The expected value should be an array of strings where each string has the format CmdEnvVarName=CmdEnvVarValue.

  • 原因:commandEnvironment 提供的值不正确。Cause: The provided value for commandEnvironment is incorrect.

  • 建议:验证提供的值是否类似于:Recommendation: Verify that the provided value is similar to:

    \"variableName=variableValue\"
    ]
    

    另外,验证每个变量是否仅在列表中出现一次。Also verify that each variable appears in the list only once.

错误代码:2356Error code: 2356

  • 消息The commandEnvironment already contains a variable named '%variableName;'.Message: The commandEnvironment already contains a variable named '%variableName;'.

  • 原因:commandEnvironment 提供的值不正确。Cause: The provided value for commandEnvironment is incorrect.

  • 建议:验证提供的值是否类似于:Recommendation: Verify that the provided value is similar to:

    \"variableName=variableValue\"
    ]
    

    另外,验证每个变量是否仅在列表中出现一次。Also verify that each variable appears in the list only once.

错误代码:2357Error code: 2357

  • 消息The certificate or password is wrong for ADLS Gen 1 storage.Message: The certificate or password is wrong for ADLS Gen 1 storage.

  • 原因:提供的凭据不正确。Cause: The provided credentials are incorrect.

  • 建议:验证链接到服务的 ADLS Gen 1 中的连接信息,并验证测试性连接是否成功。Recommendation: Verify that the connection information in ADLS Gen 1 linked to the service, and verify that the test connection succeeds.

错误代码:2358Error code: 2358

  • 消息The value '%value;' for the required property 'TimeToLive' in the on demand HDInsight linked service '%linkedServiceName;' has invalid format. It should be a timespan between '00:05:00' and '24:00:00'.Message: The value '%value;' for the required property 'TimeToLive' in the on demand HDInsight linked service '%linkedServiceName;' has invalid format. It should be a timespan between '00:05:00' and '24:00:00'.

  • 原因: 为必需属性 TimeToLive 提供的值的格式无效。Cause: The provided value for the required property TimeToLive has an invalid format.

  • 建议:更新该值,使其处于建议的范围内,然后重试。Recommendation: Update the value to the suggested range and try again.

错误代码:2359Error code: 2359

  • 消息The value '%value;' for the property 'roles' is invalid. Expected types are 'zookeeper', 'headnode', and 'workernode'.Message: The value '%value;' for the property 'roles' is invalid. Expected types are 'zookeeper', 'headnode', and 'workernode'.

  • 原因: 为属性 roles 提供的值无效。Cause: The provided value for the property roles is invalid.

  • 建议:将该值更新为建议的值之一,然后重试。Recommendation: Update the value to be one of the suggestions and try again.

错误代码:2360Error code: 2360

  • 消息The connection string in HCatalogLinkedService is invalid. Encountered an error while trying to parse: '%message;'.Message: The connection string in HCatalogLinkedService is invalid. Encountered an error while trying to parse: '%message;'.

  • 原因:HCatalogLinkedService 提供的连接字符串无效。Cause: The provided connection string for the HCatalogLinkedService is invalid.

  • 建议:将该值更新为正确的 Azure SQL 连接字符串,然后重试。Recommendation: Update the value to a correct Azure SQL connection string and try again.

错误代码:2361Error code: 2361

  • 消息Failed to create on demand HDI cluster. Cluster name is '%clusterName;'.Message: Failed to create on demand HDI cluster. Cluster name is '%clusterName;'.

  • 原因: 群集创建失败,并且 ADF 未收到 HDInsight 服务返回的错误。Cause: The cluster creation failed, and ADF did not get an error back from HDInsight service.

  • 建议:打开 Azure 门户,尝试查找具有所提供名称的 HDI 资源,然后检查预配状态。Recommendation: Open the Azure portal and try to find the HDI resource with provided name, then check the provisioning status. 联系 HDInsight 支持团队以获得更多帮助。Contact HDInsight support team for further assistance.

错误代码:2362Error code: 2362

  • 消息Only Azure Blob storage accounts are supported as additional storages for HDInsight on demand linked service.Message: Only Azure Blob storage accounts are supported as additional storages for HDInsight on demand linked service.

  • 原因: 提供的附加存储不是 Azure Blob 存储。Cause: The provided additional storage was not Azure Blob storage.

  • 建议:提供 Azure Blob 存储帐户作为 HDInsight 按需链接服务的附加存储。Recommendation: Provide an Azure Blob storage account as an additional storage for HDInsight on-demand linked service.

使用 HDInsight ESP 群集的 ADF 链接服务时出现 SSL 错误SSL error when ADF linked service using HDInsight ESP cluster

  • 消息:Failed to connect to HDInsight cluster: 'ERROR [HY000] [Microsoft][DriverSupport] (1100) SSL certificate verification failed because the certificate is missing or incorrect.Message: Failed to connect to HDInsight cluster: 'ERROR [HY000] [Microsoft][DriverSupport] (1100) SSL certificate verification failed because the certificate is missing or incorrect.

  • 原因:问题最可能与系统信任存储区相关。Cause: The issue is most likely related with System Trust Store.

  • 解决方法:可以导航到 Microsoft Integration RUNTIME\4.0\SHARED\ODBC Drivers\Microsoft Hive ODBC Driver\lib 路径,并打开 DriverConfiguration64.exe 更改设置。Resolution: You can navigate to the path Microsoft Integration Runtime\4.0\Shared\ODBC Drivers\Microsoft Hive ODBC Driver\lib and open DriverConfiguration64.exe to change the setting.

    取消选中 "使用系统信任存储区"

Web 活动Web Activity

错误代码:2128Error code: 2128

  • 消息No response from the endpoint. Possible causes: network connectivity, DNS failure, server certificate validation or timeout.Message: No response from the endpoint. Possible causes: network connectivity, DNS failure, server certificate validation or timeout.

  • 原因: 此问题与网络连接、DNS 失败、服务器证书验证或超时相关。Cause: This issue is due to either Network connectivity, a DNS failure, a server certificate validation, or a timeout.

  • 建议:验证尝试访问的终结点是否响应请求。Recommendation: Validate that the endpoint you are trying to hit is responding to requests. 可以使用 Fiddler/Postman 等工具。You may use tools like Fiddler/Postman.

错误代码:2108Error code: 2108

  • 消息Error calling the endpoint '%url;'. Response status code: '%code;'Message: Error calling the endpoint '%url;'. Response status code: '%code;'

  • 原因: 某个根本性问题(例如网络连接问题、DNS 失败、服务器证书验证问题或超时)导致请求失败。Cause: The request failed due to an underlying issue such as network connectivity, a DNS failure, a server certificate validation, or a timeout.

  • 建议:使用 Fiddler/Postman 验证请求。Recommendation: Use Fiddler/Postman to validate the request.

更多详细信息More details

若要使用 Fiddler 创建受监视 Web 应用程序的 HTTP 会话,请执行以下步骤:To use Fiddler to create an HTTP session of the monitored web application:

  1. 下载、安装并打开 FiddlerDownload, install, and open Fiddler.

  2. 如果 Web 应用程序使用 HTTPS,请转到“工具” > “Fiddler 选项” > “HTTPS”。 If your web application uses HTTPS, go to Tools > Fiddler Options > HTTPS.

    1. 在“HTTPS”选项卡中,选择“捕获 HTTPS 连接”和“解密 HTTPS 流量”。 In the HTTPS tab, select both Capture HTTPS CONNECTs and Decrypt HTTPS traffic.

      Fiddler 选项

  3. 如果应用程序使用 TLS/SSL 证书,请将 Fiddler 证书添加到设备。If your application uses TLS/SSL certificates, add the Fiddler certificate to your device.

    请转到:“工具” > “Fiddler 选项” > “HTTPS” > “操作” > “将根证书导出到桌面”。 > Go to: Tools > Fiddler Options > HTTPS > Actions > Export Root Certificate to Desktop.

  4. 转到“文件” > “捕获流量”来关闭捕获。 Turn off capturing by going to File > Capture Traffic. 或者按 F12Or press F12.

  5. 清除浏览器缓存以删除所有已缓存的项;必须重新下载这些项。Clear your browser's cache so that all cached items are removed and must be downloaded again.

  6. 创建请求:Create a request:

  7. 选择“编辑器”选项卡。Select the Composer tab.

    1. 设置 HTTP 方法和 URL。Set the HTTP method and URL.

    2. 根据需要添加标头和请求正文。If needed, add headers and a request body.

    3. 选择“执行”。Select Execute.

  8. 再次打开流量捕获,并在页面上完成出问题的事务。Turn on traffic capturing again, and complete the problematic transaction on your page.

  9. 请转到:“文件” > “保存” > “所有会话”。 Go to: File > Save > All Sessions.

有关详细信息,请参阅 Fiddler 入门For more information, see Getting started with Fiddler.

常规General

活动停滞问题Activity stuck issue

如果观察到活动运行的时间比正常运行的时间长得多,并且几乎没有任何进展,则可能是停滞。When you observe that the activity is running much longer than your normal runs with barely no progress, it may happen to be stuck. 你可以尝试取消它,然后重试,看是否有帮助。You can try canceling it and retry to see if it helps. 如果是复制活动,您可以了解有关如何 排查复制活动性能问题的性能监视和故障排除问题;如果是数据流,请参阅 映射数据流性能 和优化指南。If it’s a copy activity, you can learn about the performance monitoring and troubleshooting from Troubleshoot copy activity performance; if it’s a data flow, learn from Mapping data flows performance and tuning guide.

有效负载太大Payload is too large

错误消息: The payload including configurations on activity/dataSet/linked service is too large. Please check if you have settings with very large value and try to reduce its size.Error message: The payload including configurations on activity/dataSet/linked service is too large. Please check if you have settings with very large value and try to reduce its size.

原因: 每个活动运行的有效负载包括活动配置、关联的数据集 (s) 以及链接服务 (s) 配置(如果有),以及根据活动类型生成的一小部分系统属性。Cause: The payload for each activity run includes the activity configuration, the associated dataset(s), and linked service(s) configurations if any, and a small portion of system properties generated per activity type. 此类负载大小的限制为 896 KB,如 " 数据工厂限制 " 部分中所述。The limit of such payload size is 896 KB as mentioned in Data Factory limits section.

建议: 达到此限制,很可能是因为从上游活动输出或外部传入了一个或多个大参数值,尤其是在控制流中跨活动传递实际数据时。Recommendation: You hit this limit likely because you pass in one or more large parameter values from either upstream activity output or external, especially if you pass actual data across activities in control flow. 检查是否可以减小大参数值的大小,或调整管道逻辑以避免跨活动传递此类值,而应在活动中处理此类值。Check if you can reduce the size of large parameter values, or tune your pipeline logic to avoid passing such values across activities and handle it inside the activity instead.

后续步骤Next steps

若要获取故障排除方面的更多帮助,请尝试参阅以下资源:For more troubleshooting help, try these resources: