Jaa

OMS Agent setup communication error ID 4004

  • Artikkeli

We have recently seen a customer attempt to add a server to an OMS Log Analytics workspace, but the attempt failed and produced the following error in the Operations Manager event log on that server.

Error in the Operations Manager event log

In the TracingGUIDSNative.log ETW log files, we saw these entries:

[ServiceConnector] [] [Information] :CBackgroundRequester::OnTimerCallback{backgroundrequester_cpp657}Beginning background request for URL "https:// a12b3c4d-5e6f-7a8b-9c0d-1e2f3a4b5c6d.oms.opinsights.azure.com/AgentService.svc/AgentTopologyRequest".

[HealthServiceCommon] [] [Verbose] :CHttpClientBase::CHttpRequest::SetProxy{httpclientbase_cpp1924}Using system default proxy for request to "https:// a12b3c4d-5e6f-7a8b-9c0d-1e2f3a4b5c6d.oms.opinsights.azure.com/AgentService.svc/AgentTopologyRequest".

[HealthServiceCommon] [] [Error] :CHttpClientBase::CHttpRequest::AddHeader{httpclientbase_cpp1452}WinHttpAddRequestHeaders(x-ms-OmsCloudId: ) for URL "https://a12b3c4d-5e6f-7a8b-9c0d-1e2f3a4b5c6d.oms.opinsights.azure.com/AgentService.svc/AgentTopologyRequest" failed with code WINERROR=    2F76

[HealthServiceCommon] [] [Error] :CHttpClientBase::CHttpRequest::AddCloudHeaders{httpclientbase_cpp1378}AddHeader name:(x-ms-OmsCloudId: ) value:(<NULL>) failed with code WINERROR=    2F76.

281 [10]11044.32756::01/17/2017-10:19:40.995 [HealthServiceCommon] [] [Error] :CHttpClientBase::CHttpRequest::BeginHttpRequest{httpclientbase_cpp883}AddCloudHeaders for URL "https://a12b3c4d-5e6f-7a8b-9c0d-1e2f3a4b5c6d.oms.opinsights.azure.com/AgentService.svc/AgentTopologyRequest" failed with code WINERROR=    2F76

[HealthServiceCommon] [] [Error] :CHttpClientBase::BeginHttpRequest{httpclientbase_cpp234}BeginHttpRequest for URL "https:// a12b3c4d-5e6f-7a8b-9c0d-1e2f3a4b5c6d.oms.opinsights.azure.com/AgentService.svc/AgentTopologyRequest" failed with code WINERROR=    2F76.

[HealthServiceCommon] [] [Error] :CHttpClientBase::BeginHttpRequest{httpclientbase_cpp378}BeginHttpRequest to URL "https://a12b3c4d-5e6f-7a8b-9c0d-1e2f3a4b5c6d.oms.opinsights.azure.com/AgentService.svc/AgentTopologyRequest" failed with code WINERROR=    2F76

[ServiceConnector] [] [Error] :CHttpClient::BeginRestHttpRequest{httpclient_cpp310}BeginHttpRequest to URL "https://a12b3c4d-5e6f-7a8b-9c0d-1e2f3a4b5c6d.oms.opinsights.azure.com/AgentService.svc/AgentTopologyRequest" failed with code WINERROR=    2F76

[ServiceConnector] [] [Error] :CBackgroundRestRequester::BeginRequest{backgroundrequester_cpp729}BeginRestHttpRequest for URL "https://a12b3c4d-5e6f-7a8b-9c0d-1e2f3a4b5c6d.oms.opinsights.azure.com/AgentService.svc/AgentTopologyRequest" failed with code WINERROR=    2F76.

[ServiceConnector] [] [Error] :CBackgroundRequester::OnTimerCallback{backgroundrequester_cpp673}Background request for URL "https://a12b3c4d-5e6f-7a8b-9c0d-1e2f3a4b5c6d.oms.opinsights.azure.com/AgentService.svc/AgentTopologyRequest" failed with code WINERROR=    2F76, will try again next interval.

Our investigation found that this could happen on systems that had an empty string for their SMBIOSAssetTag.

We are going to adapt our agent code to handle this situation, but in the meantime, to correct this issue, please install an earlier version of the agent from

…here for the 64-bit agent (https://go.microsoft.com/fwlink/?LinkID=517476)

...or here for the 32-bit agent (https://go.microsoft.com/fwlink/?LinkID=615592).

Brian McDermott
Senior Escalation Engineer
Microsoft