locked
Operations Manager Log - Event ID 4502 RRS feed

  • Question

  • I'm trying to onboard my first set of machines into log analytics and azure monitor and all three machines (Domain Controllers) are throwing these errors in the 'Operations Manager' log. The message has a 169 ip address in there, but I'm not sure where that is coming from. I have .net FW 4.8 installed, and am not using sccm or scom to monitor these devices already.

    Event ID: 4502

    Source: HealthService

    A module of type "Microsoft.EnterpriseManagement.HealthService.HealthAssessmentData.HealthAssessmentDataSource" reported an exception System.Net.WebException: Unable to connect to the remote server ---> System.Net.Sockets.SocketException: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond 169.254.169.254:80
       at System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress)
       at System.Net.ServicePoint.ConnectSocketInternal(Boolean connectFailure, Socket s4, Socket s6, Socket& socket, IPAddress& address, ConnectSocketState state, IAsyncResult asyncResult, Exception& exception)
       --- End of inner exception stack trace ---

    Friday, November 22, 2019 5:02 PM

All replies

  • Thanks for reaching out!We recommend engaging our technical support team to investigate further.Please file a support case using these steps. If you do not have a support plan, send mail to AzCommunity@microsoft.com, include your subscription ID and a link to this MSDN thread (for context).
    Monday, November 25, 2019 10:39 AM
  • Did you have any luck with this issue as I have got the same problem
    Monday, December 2, 2019 7:15 PM
  • Try the suggestions from this page before raising case with MS :-

    https://support.microsoft.com/en-in/help/3126513/how-to-troubleshoot-operations-management-suite-onboarding-issues

    It could be firewall issue. Firewall may be blocking the communication. Make sure you have whitelisted the ports\urls that needed for machine to communicate with LA workspace. https://docs.microsoft.com/en-us/azure/azure-monitor/platform/log-analytics-agent

    • Proposed as answer by Keshav Jain Wednesday, December 4, 2019 9:19 AM
    Tuesday, December 3, 2019 6:50 AM
  • Seeing the same error.

    We use the LA Gateway, but seems that sometime it forgets the gateway / proxy information.

    OS: Win 2012 R2 - completely patched + required .net version.

    Have you figured out a solution?

    Monday, December 23, 2019 10:12 PM
  • I'm seeing this too, but I think it's a bug in the Microsoft Monitoring Agent, or the Management Pack, and is innocuous.

    169.254.169.254:80 is the IP address is the IP Address for the Azure Instance Metadata Service, and is not accessible outside of Azure (https://docs.microsoft.com/en-us/azure/virtual-machines/windows/instance-metadata-service).  It's used by software installed on a VM to gather the Azure data for the VM, like Resource ID, etc.)

    There are three reasons I can think of to generate the error:

    * The Microsoft Monitoring Agent is installed on a non-Azure Machine

    * Something is blocking access to that IP in Azure, like an Azure Network Security Group

    * The traffic to 169.254.169.254 is being piped somewhere outside first, like through a proxy server.

    I don't know if there's a good way to avoid that error, since that check is probably the best way for MMA to figure out whether it's an Azure machine or not.

    Wednesday, January 15, 2020 7:07 PM
  • Tim Mrazek If you have raised the support request , can you please share the solution so that it would beneficial to broader audience?
    Thursday, January 16, 2020 2:15 PM