VMMS.exe not listening on port 6600 after restarting server

Michael Gilmore 1 Reputation point
2021-03-22T14:33:37.3+00:00

After setting up Hyper-V for live migrations, the VMMS.exe is listening on port 6600 and works correctly. After restarting the server, the VMMS.exe service is up and running, however it is not listening on port 6600. But if I simply restart the VMMS.exe service, it then is now listening on 6600. I have also set the service to delayed start and that appears to work. However I have to wait until the service starts before I can manage any VM's that run on the local server. Delayed start seems like a Band-Aid fix. Is there any fix for this issue? Is something not in place or running so the VMMs.exe service can bind to port 6600? Firewall is all off while I troubleshoot this issue.

Michael

System Center Virtual Machine Manager
Hyper-V
Hyper-V
A Windows technology providing a hypervisor-based virtualization solution enabling customers to consolidate workloads onto a single server.
2,553 questions
0 comments

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Xiaowei He 9,871 Reputation points
    2021-03-23T02:21:28.233+00:00

    Hi,

    I meet this issue before, the workaround is like you said, to set the VMMS service to be delayed start.

    This issue may due to that, when the server restart, the VMMS service tries to register port 6600 on the Network card before the network card finished initialization.

    It seems there's no fix yet just a workaround.

    Thanks for your time!
    Best Regards,
    Anne

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

    If the Answer is helpful, please click "Accept Answer" and upvote it.
    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.