none
Virtual VMM cannot connect to its own host

    質問

  • We have deployed virtual VMM 2016 rollup 4 on a Hyper-V 2012 R2 cluster and we noticed that VMM cannot connect to the host Hyper-V server where the VMM VM is hosted, if the VM migrated to another host the problem moves as well to the other host.

    Error: 

    VMM is unable to complete the request. The connection to the agent 'ServerName' was lost.

    WinRM: URL: [http://ServerName:5985], Verb: [ENUMERATE], Resource: [http://schemas.microsoft.com/wbem/wsman/1/wmi/root/standardcimv2/MSFT_NetAdapter], Filter: []

    Unknown error (0x80338126)

    Anyone knows any fix for this issue?

    2018年5月31日 8:56

すべての返信

  • Hi! What OS are you running your your SCVMM2016 on?

    In the support page it says the following about a virtual VMM server ”Don't install on a server running Hyper-V.”.

    Reference:
    https://docs.microsoft.com/en-us/system-center/vmm/system-requirements?view=sc-vmm-1801#server-operating-system

    Best regards,
    Leon

    • 編集済み Leon Laude 2018年5月31日 10:25 fixed text
    2018年5月31日 9:14
  • Hello A Seyam,

    Firstly, please make sure the the network connectivity is available between the VMM server and the Hyper-V host.

    You can verity that by ping the IP address of Hyper-V host in the CMD on the VMM server.

    Please also make sure that the FQDN name of the Hyper-V host is resolvable. 

    In addition, what's the type of the virtual switch, standard or logical switch? If you are using logical switch, please check out the settings for logical network, virtual network. Please make sure you configure them correctly.

    Best regards,

    Andy Liu


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    2018年6月1日 6:18
  • It seems no one understood the problem, if there was a problem with the OS or network connections the problem wouldn't disappear if the VMM VM migrated to another host and the problem started to appear on the other host!
    2018年6月3日 6:29
  • What you can try is remove the Hyper-V Cluster from VMM and add it back again. Occasionally this process solves strange errors in VMM. 

    Microsoft Certified Professional

    [If a post helps to resolve your issue, please click the "Mark as Answer" of that post or click Answered "Vote as helpful" button of that post. By marking a post as Answered or Helpful, you help others find the answer faster. ]

    2018年6月3日 7:28