Cannot add Logical switch due to error 2915

Paul Boerefijn 1 Reputation point
2022-09-13T08:07:07.26+00:00

After a fresh installation of Windows Server 2022 Datacenter, applying the latest CU and connecting my brand new server to SCVM 2019 CU4, i like to create the Logical switch, which fails with error 2915. This issue is seen on 3 HyperV servers. Tried it several times, updated network drivers, performed reboots etc. Still getting error 2915.

While the job is run, a virtual switch is created. It looks like the Logical Switch is successfully created, but cleaned up after the failing GetFinalResult command.

Error (2915)
The Windows Remote Management (WS-Management) service cannot process the request. The object was not found on the server (hypervserver.local).

WinRM: URL: [http://hypervserver.local:5985], Verb: [INVOKE], Method: [GetFinalResult], Resource: [http://schemas.microsoft.com/wbem/wsman/1/wmi/root/scvmm/AsyncTask?ID=1003]

Unknown error (0x80078000)

Recommended Action
Ensure that the VMM agent is installed and running. If the error persists, restart the virtualization server (h004.ccs.nl) and then try the operation again.

This error can also happen due to an older version of the VMM agent on the virtualization server. Ensure that the VMM agent is upgraded to the latest version, and then try the operation again.

Used configuration

  • SCVMM Server Windows Server 2019 + SCVMM 2019 CU4
  • HyperV server Windows Server 2022 + VMM Agent 10.19.2648.0
  • DELL PowerEdge R650xs + Broadcom 57412 Dual Port 10GbE SFP+
Windows Server 2019
Windows Server 2019
A Microsoft server operating system that supports enterprise-level management updated to data storage.
3,472 questions
Hyper-V
Hyper-V
A Windows technology providing a hypervisor-based virtualization solution enabling customers to consolidate workloads onto a single server.
2,549 questions
Windows Server Management
Windows Server Management
Windows Server: A family of Microsoft server operating systems that support enterprise-level management, data storage, applications, and communications.Management: The act or process of organizing, handling, directing or controlling something.
421 questions

5 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Paul Boerefijn 1 Reputation point
    2022-09-14T15:04:46.507+00:00

    Still searching for a solution. A good idea was installing a SCVMM 2022 server to get on the same level as the Windows 2022 Server HyperV host. Unfortunately a different error while adding the Logical switch. No progress at all here. Downgrade to server 2019 helps me out.

    No logical switch, no VM connected. What else can i try to workaround this error? We're using LACP teams for connections. The LACP team (multiplexor) adapter can't be used in the HyperV manager.

    Error (2912)
    An internal error has occurred trying to contact the 'hyperv.local' server: : .

    WinRM: URL: [http://h002.ccs.nl:5985], Verb: [INVOKE], Method: [GetFinalResult], Resource: [http://schemas.microsoft.com/wbem/wsman/1/wmi/root/scvmm/AsyncTask?ID=1003]

    Unknown error (0x80078005)

    Recommended Action
    Check that WS-Management service is installed and running on server 'hyperv.local'. For more information use the command "winrm helpmsg hresult". If 'h002.ccs.nl' is a host/library/update server or a PXE server role then ensure that VMM agent is installed and running. Refer to http://support.microsoft.com/kb/2742275 for more details.

    0 comments
  2. Limitless Technology 43,956 Reputation points
    2022-09-19T07:47:59.427+00:00

    Hello there,

    Yes, you are right you need to upgrade VMM to 2022. This error can also happen due to an older version of the VMM agent on the virtualization server. Ensure that the VMM agent is upgraded to the latest version, and then try the operation again.

    Ensure that the VMM agent is installed and running. If the error persists, restart the virtualization server (win12-hv.jitpros.local) and then try the operation again.

    For Warning (2915) Check the health status of the host.

    To check the health status of a host, perform the following steps:

    Open the VMM console.
    Select the Fabric view, right-click the host that's experiencing issues and then choose Properties.
    Within the host properties, select Status.
    Select the category that has the red exclamation to view the error details.

    You can get the detailed steps from here https://learn.microsoft.com/en-us/troubleshoot/system-center/vmm/troubleshoot-host-status-errors

    ----------------------------------------------------------------------------------------------------------------------------

    --If the reply is helpful, please Upvote and Accept it as an answer–

  3. Paul Boerefijn 1 Reputation point
    2022-09-20T14:28:57.51+00:00

    While creating the Logical Switch we receive error 2912 with 0x80070005, which should be something like a communication issue or rights. However, creating a Logical Switch without teaming works fine. It has something to do with LACP teaming, which is deprecated in VMM2022! Creating a Logical Switch without teaming works fine. It's keeping me busy for three days now. Finally i have a good indication how to fix the Logical switch creation issue. RTFM about Switch Embedded Teaming.

    Error (2912)
    An internal error has occurred trying to contact the 'hyperv.local' server: : .

    WinRM: URL: [http://hyperv.ccs.nl:5985], Verb: [INVOKE], Method: [GetFinalResult], Resource: [http://schemas.microsoft.com/wbem/wsman/1/wmi/root/scvmm/AsyncTask?ID=1003]

    Unknown error (0x80078005)

    0 comments
  4. Paul Boerefijn 1 Reputation point
    2022-09-20T21:46:32.49+00:00

    And fixed. Error 2912 was received because of a misconfigured Port Profile. We configured only a LACP team Port Profile, just because we did this since Windows Supports LACP teams. In Windows Server 2022 and System Centre VM 2022 the LACP team is deprecated. Fine. But present me an error message that indicates that i have made configuration mistakes in the Logical Swich and his Port Profiles!

    0 comments
  5. Paul Boerefijn 1 Reputation point
    2022-09-20T21:46:32.927+00:00

    And fixed. Error 2912 was received because of a misconfigured Port Profile. We configured only a LACP team Port Profile, just because we did this since Windows Supports LACP teams. In Windows Server 2022 and System Centre VM 2022 the LACP team is deprecated. Fine. But present me an error message that indicates that i have made configuration mistakes in the Logical Swich and his Port Profiles!

    0 comments