I installed VMM (Virtual Machine Manager) Version 1807 to manage my Windows Server 2019 Hyper-V Server. Everything went fine even it’s not officially supported yet. But then, when I tried to deploy a logical Switch to the host the job failed with the following error message:

Error (2912)
An internal error has occurred trying to contact the ‘hyperv’ server: NO_PARAM: NO_PARAM.

WinRM: URL: [http://hyperv:5985], Verb: [INVOKE], Method: [GetError], Resource: [http://schemas.microsoft.com/wbem/wsman/1/wmi/root/microsoft/bits/BitsClientJob?JobId={763E790C-7F6B-4C0F-8828-73BE01DE2079}]

Internal server error (500) (0x801901F4)

Recommended Action
Check that WS-Management service is installed and running on server ‘hyperv’. For more information use the command “winrm helpmsg hresult”. If ‘hyperv’ 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

Cause

While there are different possibilities for this issue, in my case I had installed Windows Admin Center on the same machine. The Admin Center was using Port 443. VMM is using BITS (Background Intelligent Transfer Service), which is configured to Port 443 by default.

Solution

Luckily, if Port 443 is already used by another application, you can modify BITS Port used by SCVMM with a simple change in the registry:

  1. Open regedit
  2. Navigate to Settings key
    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft System Center Virtual Machine Manager Server\Settings
  3. Change DWORD BITSTcpPort to an unused Port (in my case I used 4443)
    BITSTcpPort"=dword:4443
  4. Restart the SCVMM Services
  5. Redeploy the Logical Switch