none
Unable to connect to Log Analytics RRS feed

  • Question

  • We have a new installation of SCOM 2019 - currently monitoring over 500 agents and all is working as expected. We are trying to create a connection to our Log Analytics however we are having issues. 

    We already have a connection working from our old 2012 R2 environment and that is still sending logs.

    When setting up a new connection in the 2019 console we login with our azure account and it sees our workspace. We hit the Next, Next and Save button and then it fails with Error 4200. 

    When looking in Azure we can see that it has created the new workspace for our 2019 environment and it has created the certificate profile in our console. It also downloads the Advisor Secure Reference Override management pack and then it stops. Nothing else occurs. 

    We have followed the prerequisites from this link

    https://docs.microsoft.com/en-us/azure/azure-monitor/platform/om-agents

    The management servers can all access the internet with no issues and also has access to all the URLs listed in the prerequisites document. We have created a Microsoft call for this too so waiting to hear back with what they come back with. Has anyone seen this or had issues like this? Any ideas?

    Friday, July 26, 2019 2:35 PM

Answers

  • Good Morning all,

    just to confirm we have finally managed to fix this with the help of Microsoft. It looks like there is a bug in the Microsoft.SystemCenter.Advisor.mpb file which SCOM uses to connect to Log Analytics. We provided Microsoft this and an error came back saying that our WorkSpace name was invalid. After altering the management pack and sending it back to us we were able to connect without any issues. 

    I'm guessing this is going to be a bug for alot of organisations if they had a workspace name which was like ours (some strange GUID). I'm guessing this will be something that is fixed in the first update rollup.

    Also - it only took Microsoft 4 months to work this out :)
    Friday, October 11, 2019 10:55 AM

All replies

  • Hi,

    Please check if the following two dll files are present under the console folder.

    Microsoft.IdentityModel.Clients.ActiveDirectory.dll and Microsoft.IdentityModel.Clients.ActiveDirectory.WindowsForms.dll

    If present, please take a backup of both the dll files and remove them and then try.

    Regards,

    Sourav

    Monday, July 29, 2019 6:57 PM
  • Hi Just to confirm these two files don't exist under the console directory.
    Friday, August 16, 2019 11:41 AM
  • Hi Again,

    Incase anyone is experiencing this like ourselves (I've not come across any yet) but we have an open case with Microsoft (open for over a month now) and we still have now received an answer on how to fix it.

    Wednesday, September 18, 2019 1:15 PM
  • Good Morning all,

    just to confirm we have finally managed to fix this with the help of Microsoft. It looks like there is a bug in the Microsoft.SystemCenter.Advisor.mpb file which SCOM uses to connect to Log Analytics. We provided Microsoft this and an error came back saying that our WorkSpace name was invalid. After altering the management pack and sending it back to us we were able to connect without any issues. 

    I'm guessing this is going to be a bug for alot of organisations if they had a workspace name which was like ours (some strange GUID). I'm guessing this will be something that is fixed in the first update rollup.

    Also - it only took Microsoft 4 months to work this out :)
    Friday, October 11, 2019 10:55 AM