连接代理给出HTTP错误12044L [英] Connecting agent gives HTTP error 12044L

问题描述

在某些机器上尝试设置代理失败.发生故障的计算机在VNET中的Azure中运行，并且已加入域.

Trying to setup the agent fails on some machines for me. The machines where it fails are running in Azure in a VNET and are domain joined.

事件日志中的错误:

HTTP operation failed with error "12044L" (12044L).  The query will be retried later.  URL for Operation: https://myworkspaceguid.oms.opinsights.azure.com/AgentService.svc/AgentTopologyRequest

已设置正确检查的正确工作空间ID和访问密钥.

Double checked correct workspace ID and access key are set.

它适用于同一VNET中的其他独立计算机以及相同的OpsInsight工作区.

It works well for other, standalone machines in the same VNET and for the same OpsInsight workspace.

我怀疑证书处理可能存在一些问题，因为该代理似乎将客户端证书用于对工作区的身份验证.可能缺少一些强制性的受信任的根证书，但无法验证，找不到足够的信息 有效.

I suspect it may be some issue with certificate handling, since the agent seems to use client-cert for auth towards the workspace. Possibly there is some mandatory trusted root certificate missing, but can't verify, don't find enough information how this works.

有任何提示吗?

推荐答案

perpetualKid，

Hi perpetualKid,

对于Azure虚拟机，您如何进行代理安装?

For the Azure virtual machines, how are you doing the agent install?

共有3个选项:

1. 下载MSI，运行设置并输入工作区ID和密钥
2. 使用Azure门户(在Azure门户中的操作洞察工作区的服务器"选项卡上选择启用op洞察)
3. 使用PowerShell安装扩展程序

对于Azure虚拟机，选项2和3是最简单的.

For Azure virtual machines, options 2 and 3 are the easiest.

在每种情况下，代理程序的设置流程都涉及使用工作区ID和密钥对服务进行初始身份验证.完成初始身份验证后，客户端和服务器将协商证书，并将该证书用于后续身份验证.

In each case, the setup flow for agents involves using the workspace id and key to do the initial authentication with the service. Once the initial auth is done the client and server negotiate a certificate and the certificate is used for subsequent authentication.

我还将与一些工程师联系，以确定12044L错误的可能原因.

I'll also follow up with some engineers on what the cause of the 12044L error could be.

致谢

Richard

这篇关于连接代理给出HTTP错误12044L的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！