Update: Microsoft will be moving away from UserVoice sites on a product-by-product basis throughout the 2021 calendar year. We will leverage 1st party solutions for customer feedback. Learn more here.

Azure Monitor-Log Analytics

Welcome to the "Azure Log Analytics ":https://azure.microsoft.com/en-us/services/log-analytics/ Feedback page. We appreciate your feedback and look forward to hearing from you. Use this site for new ideas and bug reports or to request help.
NOTE – Log Analytics is now a part of Operations Management Suite. Learn more at http://microsoft.com/OMS

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. Event id 55041 advisior

    I am getting frequently this error on SCOM Management server and also few servers are not reporting to Azure via opsmgr

    Microsoft.SystemCenter.Advisor.Common.WebService.GatewayCommunicationException: Unable to communicate successfully with web service when performing Get Alert Update. ---> System.ServiceModel.EndpointNotFoundException: There was no endpoint listening at https://service.systemcenteradvisor.com/IdentityProvider/IdentityProviderService.svc that could accept the message. This is often caused by an incorrect address or SOAP action. See InnerException, if present, for more details. ---> System.Net.WebException: The remote server returned an error: (407) Proxy Authentication Required. at System.Net.HttpWebRequest.GetRequestStream(TransportContext& context) at System.Net.HttpWebRequest.GetRequestStream() at System.ServiceModel.Channels.HttpOutput.WebRequestHttpOutput.GetOutputStream() --- End of inner exception stack trace --- Server stack trace: at System.ServiceModel.Channels.HttpOutput.WebRequestHttpOutput.GetOutputStream() at System.ServiceModel.Channels.HttpOutput.Send(TimeSpan…

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)

    Your proxy is asking for Authentication.

    Please refer to the blog post here http://blogs.technet.com/b/momteam/archive/2014/05/29/advisor-error-3000-unable-to-register-to-the-advisor-service-amp-onboarding-troubleshooting-steps.aspx

    or the documentation on MSDN https://msdn.microsoft.com/en-us/library/azure/dn884643.aspx

    for how to configure a RunAs account to authenticate with the proxy, or what destinations to allow exceptions for.

    That one rule is only part of the old Advisor Configuration Alerts synchronization – a lot of people just seem to be turning off the flood and not syncing those ‘proactive’ alerts down to SCOM anyway – see more information on http://blogs.technet.com/b/momteam/archive/2014/07/24/how-to-stop-the-receiving-of-advisor-alerts-in-operations-manager.aspx and https://social.msdn.microsoft.com/Forums/azure/en-US/54de90e2-7efb-4274-943e-5904fb41ab1b/alerts-not-working-with-direct-agent?forum=opinsights

    If you need more help,
    Customers with Premier support can log support cases via Premier https://premier.microsoft.com/

    Customers with Azure support agreements can log support cases in the Azure portal https://manage.windowsazure.com/?getsupport=true

    For general discussion/question and answers (not ideas and bug reports) use the MSDN Forum

    Onboarding issues? Read this troubleshooting guide http://blogs.technet.com/b/momteam/archive/2014/05/29/advisor-error-3000-unable-to-register-to-the-advisor-service-amp-onboarding-troubleshooting-steps.aspx

    How do I do XYZ? Try our documentation http://azure.microsoft.com/en-us/documentation/articles/operational-insights-feature-guide/
2 Next →
  • Don't see your idea?

Feedback and Knowledge Base