SCOM2016/VMM2016 integration error 11823

Tony Gedge 241 Reputation points
2020-08-31T08:28:11.153+00:00

My SCOM2016/VMM2016 integration is no longer working. The reported error is 11823:

VMM Management group object cannot be found.
One or more of the Virtual Machine Manager objects monitored by Operations Manager could not be discovered. This might be caused by a missing or outdated version of the System Center Virtual Machine Manager management pack in Operations Manager.

As far as I can tell I've got the correct MPs imported, port 5724 is open between the VMM and SCOM server and the domain account for the connection is a local admin on both the VMM and SCOM servers.

Where else can I look for more detail of why this isn't working?

Operations Manager
Operations Manager
A family of System Center products that provide infrastructure monitoring, help ensure the predictable performance and availability of vital applications, and offer comprehensive monitoring for datacenters and cloud, both private and public.
1,480 questions
System Center Virtual Machine Manager
0 comments

9 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Gautam R 1 Reputation point
    2020-09-05T18:59:08.867+00:00

    There are 2 things here:

    1. Either your objects in VMM are not added in SCOM. i.E SCOM Agent not added and not being managed on the Hyper-V hosts.
    2. Additionally from what i remember a BUG existed and was fixed in VMM 2016 UR8 & UR9 causing the Integration not to work as expected with a similar error what you are seeing.

    If the issue still exists after applying VMM 2016 UR9, You can raise a support case with Microsoft so they can provide you with a private fix.

    0 comments
  2. SChalakov 10,386 Reputation points MVP
    2020-09-07T07:26:27.93+00:00

    Hi @Tony Gedge ,
    were you able to fix this?
    We would definitely appreciate your feedback!
    Thanks and Regards,
    Stoyan

    0 comments
  3. Tony Gedge 241 Reputation points
    2020-09-14T00:39:39.833+00:00

    No, no fix so far. I'm basically stuck as to what to try next. As far as I can see SCOM Agents and UR versions are all correct, MP is updated and I've tried re-creating the SCOM<->VMM connection with and without PRO enabled, but no change.

    I've enabled the VMM debug log and VMM is definitely logging Microsoft.VirtualManager.EnterpriseManagement.Common.DiscoveryDataInvalidRelationshipSourceExceptionOM10 exceptions, but it doesn't give any information that I can determine about what object it is looking for (mind you the log is massive as this system isn't idle)

    My current speculation is that the hypervisor cluster itself is not being correctly discovered by SCOM, so when VMM goes to find the objects it's expecting to be there for that cluster, they're not present. Indications in favour of this are that one of our hypervisor clusters is shown as "not monitored" in SCOM. Unfortunately, I don't know how to debug that process to see why it's not working as expected.

  4. INDRA 1 Reputation point
    2020-10-23T20:41:35.527+00:00

    Hi Tony,
    Did you get any luck?? to fix this issue. I'm also facing the same error while integrating the SCVMM 2016 with SCOM 2016.
    Below is the same error I'm getting, even though I 've installed agents on all the Hyper-V hosts & SCVMM server.

    Warning (25940)
    One or more of Virtual Machine Manager objects could not be discovered. This might be caused by Operations Manager not monitoring one of the Hyper-V hosts or the Virtual Machine Manager Server. The detailed error is: "Exception of type 'Microsoft.VirtualManager.EnterpriseManagement.Common.DiscoveryDataInvalidRelationshipSourceExceptionOM10' was thrown."

    Recommended Action
    Check Operations Manager is monitoring all the Hyper-V hosts and the Virtual Machine Manager server.

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.