对解决方案加入进行故障排除Troubleshoot solution onboarding

当加入 Azure 自动化更新管理解决方案时,可能会收到错误消息。You might receive error messages when you onboard the Azure Automation Update Management solution solution. 本文描述可能会发生的各种错误及其解决方法。This article describes the various errors that might occur and how to resolve them.

已知问题Known issues

场景:重命名已注册的节点需要取消注册或重新注册Scenario: Renaming a registered node requires unregister or register again

问题Issue

将一个节点注册到 Azure 自动化,然后更改操作系统计算机名。A node is registered to Azure Automation, and then the operating system computer name is changed. 节点的报表继续以原始名称显示。Reports from the node continue to appear with the original name.

原因Cause

重命名已注册的节点不会更新 Azure 自动化中的节点名称。Renaming registered nodes doesn't update the node name in Azure Automation.

解决方法Resolution

从 Azure Automation State Configuration 中注销该节点,然后重新注册它。Unregister the node from Azure Automation State Configuration, and then register it again. 在此之前,发布到服务的报表将不再可用。Reports published to the service before that time will no longer be available.

场景:不支持通过 HTTPS 代理重新签名证书Scenario: Re-signing certificates via HTTPS proxy isn't supported

问题Issue

通过终止 HTTPS 流量的代理解决方案进行连接,然后使用新证书重新加密流量时,服务不允许该连接。When you connect through a proxy solution that terminates HTTPS traffic and then re-encrypts the traffic using a new certificate, the service doesn't allow the connection.

原因Cause

Azure 自动化不支持对用于加密流量的证书重新签名。Azure Automation doesn't support re-signing certificates used to encrypt traffic.

解决方法Resolution

目前没有针对此问题的解决方法。There's currently no workaround for this issue.

常规错误General errors

场景:加入失败并显示消息“无法启用解决方案”Scenario: Onboarding fails with the message "The solution cannot be enabled"

问题Issue

尝试将 VM 加入解决方案时,你会收到以下消息之一:You receive one of the following messages when you attempt to onboard a VM to a solution:

The solution cannot be enabled due to missing permissions for the virtual machine or deployments
The solution cannot be enabled on this VM because the permission to read the workspace is missing

原因Cause

此错误是由于 VM、工作区或用户的权限不正确或丢失造成的。This error is caused by incorrect or missing permissions on the VM or workspace, or for the user.

解决方法Resolution

请确保你拥有加入计算机所需的权限,然后尝试重新加入解决方案。Ensure that you have correct permissions needed to onboard machines, and then try to onboard the solution again. 如果收到错误消息 The solution cannot be enabled on this VM because the permission to read the workspace is missing,请确保你具有 Microsoft.OperationalInsights/workspaces/read 权限,能够获知 VM 是否已加入工作区。If you receive the error message The solution cannot be enabled on this VM because the permission to read the workspace is missing, ensure that you have the Microsoft.OperationalInsights/workspaces/read permission to be able to find if the VM is onboarded to a workspace.

场景:加入失败,并显示消息“未能为诊断日志记录配置自动化帐户”Scenario: Onboarding fails with the message "Failed to configure automation account for diagnostic logging"

问题Issue

此错误代码表示,用于定向解决方案的已保存搜索计算机组查询的格式不正确。This error code means that the saved search computer group query used to target the solution isn't formatted correctly.

原因Cause

你可能已经更改了查询,或者系统可能已经更改了查询。You might have altered the query, or the system might have altered it.

解决方法Resolution

可以删除对此解决方案的查询,然后再次加入解决方案,这会重新创建查询。You can delete the query for the solution and then onboard the solution again, which re-creates the query. 可以在你的工作区内找到此查询,它位于“保存的搜索”下。The query can be found in your workspace under Saved searches. 查询名称是“MicrosoftDefaultComputerGroup”,查询类别是关联解决方案的名称。The name of the query is MicrosoftDefaultComputerGroup, and the category of the query is the name of the associated solution. 如果启用了多个解决方案,则“MicrosoftDefaultComputerGroup”查询会在“保存的搜索”下显示多次 。If multiple solutions are enabled, the MicrosoftDefaultComputerGroup query shows multiple times under Saved searches.

场景:PolicyViolationScenario: PolicyViolation

问题Issue

此错误代码表示部署由于违反一个或多个策略而失败。This error code indicates that the deployment failed due to violation of one or more policies.

原因Cause

策略正在阻止操作完成。A policy is blocking the operation from completing.

解决方法Resolution

若要成功部署解决方案,必须考虑更改指示的策略。To successfully deploy the solution, you must consider altering the indicated policy. 由于可以定义许多不同类型的策略,需要进行的更改取决于所违反的策略。Because there are many different types of policies that can be defined, the changes required depend on the policy that's violated. 例如,如果在资源组上定义了一个策略,该策略拒绝更改所包含资源的内容,则可以选择以下修复方法之一:For example, if a policy is defined on a resource group that denies permission to change the contents of some contained resources, you might choose one of these fixes:

  • 将该策略完全删除。Remove the policy altogether.
  • 尝试将解决方案加入不同的资源组。Try to onboard the solution to a different resource group.
  • 将策略重定向到特定资源,例如,自动化帐户。Retarget the policy to a specific resource, for example, an Automation account.
  • 修改该策略已配置为拒绝的资源集。Revise the set of resources that the policy is configured to deny.

检查 Azure 门户右上角的通知,或转到包含自动化帐户的资源组,然后选择“设置”下的“部署”以查看失败的部署 。Check the notifications in the upper-right corner of the Azure portal, or go to the resource group that contains your Automation account and select Deployments under Settings to view the failed deployment. 若要详细了解 Azure Policy,请参阅 Azure Policy 概述To learn more about Azure Policy, see Overview of Azure Policy.

问题Issue

尝试取消链接工作区时收到以下错误消息:You receive the following error message when you try to unlink a workspace:

The link cannot be updated or deleted because it is linked to Update Management Solutions.

原因Cause

当你的 Log Analytics 工作区中仍有活动的解决方案(取决于链接的自动化帐户和 Log Analytics 工作区)时,会发生此错误。This error occurs when you still have solutions active in your Log Analytics workspace that depend on your Automation account and Log Analytics workspace being linked.

解决方法Resolution

如果正在使用以下解决方案,请将其从工作区中删除:Remove the following solutions from your workspace if you're using them:

  • 更新管理Update Management

删除解决方案后,可以取消链接工作区。After you remove the solutions, you can unlink your workspace. 从工作区和自动化帐户中清理这些解决方案中的任何现有项目非常重要:It's important to clean up any existing artifacts from these solutions from your workspace and your Automation account:

  • 对于更新管理,请从自动化帐户中删除“更新部署(计划)”。For Update Management, remove Update Deployments (Schedules) from your Automation account.

Windows 扩展的 Log Analytics 故障Log Analytics for Windows extension failures

Note

从 Microsoft Operations Management Suite (OMS) 过渡到 Azure Monitor 期间,Windows 或 Linux 的 OMS 代理称为 Windows 或 Linux 的 Log Analytics 代理。As part of the ongoing transition from Microsoft Operations Management Suite (OMS) to Azure Monitor, the OMS Agent for Windows or Linux will be referred to as the Log Analytics agent for Windows and Log Analytics agent for Linux.

安装适用于 Windows 扩展的 Log Analytics 代理可能会因各种原因而失败。An installation of the Log Analytics agent for Windows extension can fail for a variety of reasons. 以下部分描述在部署 Windows 扩展的 Log Analytics 代理期间可能导致失败的加入问题。The following section describes onboarding issues that can cause failures during deployment of the Log Analytics agent for Windows extension.

Note

适用于 Windows 的 Log Analytics 代理是 Microsoft Monitoring Agent (MMA) 当前在 Azure 自动化中使用的名称。Log Analytics agent for Windows is the name used currently in Azure Automation for the Microsoft Monitoring Agent (MMA).

场景:在 WebClient 请求期间发生异常Scenario: An exception occurred during a WebClient request

VM 上适用于 Windows 扩展的 Log Analytics 无法与外部资源通信,并且部署失败。The Log Analytics for Windows extension on the VM is unable to communicate with external resources and the deployment fails.

问题Issue

下面是返回的错误消息示例:The following are examples of error messages that are returned:

Please verify the VM has a running VM agent, and can establish outbound connections to Azure storage.
'Manifest download error from https://<endpoint>/<endpointId>/Microsoft.EnterpriseCloud.Monitoring_MicrosoftMonitoringAgent_australiaeast_manifest.xml. Error: UnknownError. An exception occurred during a WebClient request.

原因Cause

此错误的部分潜在原因包括:Some potential causes of this error are:

  • VM 中配置的代理只允许使用特定端口。A proxy configured in the VM only allows specific ports.
  • 某个防火墙设置已阻止访问所需的端口和地址。A firewall setting has blocked access to the required ports and addresses.

解决方法Resolution

确保已打开正确的端口和地址用于通信。Ensure that you have the proper ports and addresses open for communication. 有关端口和地址的列表,请参阅规划网络For a list of ports and addresses, see Planning your network.

场景:暂时性的环境问题导致安装失败Scenario: Install failed because of transient environment issues

在部署期间安装适用于 Windows 扩展的 Log Analytics 失败,因为另一项安装或操作阻止了此项安装。The installation of the Log Analytics for Windows extension failed during deployment because of another installation or action blocking the installation.

问题Issue

下面是可能返回的错误消息示例:The following are examples of error messages that might be returned:

The Microsoft Monitoring Agent failed to install on this machine. Please try to uninstall and reinstall the extension. If the issue persists, please contact support.
'Install failed for plugin (name: Microsoft.EnterpriseCloud.Monitoring.MicrosoftMonitoringAgent, version 1.0.11081.4) with exception Command C:\Packages\Plugins\Microsoft.EnterpriseCloud.Monitoring.MicrosoftMonitoringAgent\1.0.11081.4\MMAExtensionInstall.exe of Microsoft.EnterpriseCloud.Monitoring.MicrosoftMonitoringAgent has exited with Exit code: 1618'
'Install failed for plugin (name: Microsoft.EnterpriseCloud.Monitoring.MicrosoftMonitoringAgent, version 1.0.11081.2) with exception Command C:\Packages\Plugins\Microsoft.EnterpriseCloud.Monitoring.MicrosoftMonitoringAgent\1.0.11081.2\MMAExtensionInstall.exe of Microsoft.EnterpriseCloud.Monitoring.MicrosoftMonitoringAgent has exited with Exit code: 1601'

原因Cause

此错误的部分潜在原因包括:Some potential causes of this error are:

  • 另一项安装正在进行。Another installation is in progress.
  • 在部署模板期间,已触发系统重新启动。The system is triggered to reboot during template deployment.

解决方法Resolution

此错误本质上是暂时性的。This error is transient in nature. 请重试部署,以安装该扩展。Retry the deployment to install the extension.

场景:安装超时Scenario: Installation timeout

由于超时,适用于 Windows 扩展的 Log Analytics 安装未完成。The installation of the Log Analytics for Windows extension didn't complete because of a timeout.

问题Issue

下面是可能返回的错误消息示例:The following is an example of an error message that might be returned:

Install failed for plugin (name: Microsoft.EnterpriseCloud.Monitoring.MicrosoftMonitoringAgent, version 1.0.11081.4) with exception Command C:\Packages\Plugins\Microsoft.EnterpriseCloud.Monitoring.MicrosoftMonitoringAgent\1.0.11081.4\MMAExtensionInstall.exe of Microsoft.EnterpriseCloud.Monitoring.MicrosoftMonitoringAgent has exited with Exit code: 15614

原因Cause

发生这种类型的错误是因为在安装期间 VM 负载过重。This type of error occurs because the VM is under a heavy load during installation.

解决方法Resolution

在 VM 负载较低时,尝试安装安装适用于 Windows 扩展的 Log Analytics 代理。Try to install the Log Analytics agent for Windows extension when the VM is under a lower load.

后续步骤Next steps

如果你的问题未在本文中列出,或者无法解决问题,请尝试通过以下渠道之一获取更多支持:If you don't see your problem here or you can't resolve your issue, try one of the following channels for additional support: