question

JvdB-8931 avatar image
0 Votes"
JvdB-8931 asked ·

Jobs hang in SCVMM 2019 UR2

Since a few weeks we have this problem with VMM that certain jobs take way longer in VMM then they really do on the Hyper-V host. Jobs I'm talking about are for instance increasing disk sizes, increasing VM memory sizes and creating checkpoints. These jobs normally took between a few seconds and a few minutes, but now they all take between 20 and 50 minutes! The real task itself, if I check the Event Logs, finish within the normal time, it's just that VMM doesn't detect this and keeps the job running for way too long. This means, that for our customers, the job takes way too long and they are unable to do any other actions to the VM.
Does anyone have any clue on what can cause this problem?

windows-server-2019windows-server-hyper-vmsc-virtual-machine-manager-hyper-vmsc-virtual-machine-manager-general
· 1
10 |1000 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

@JvdB-8931, For our issue ,based on my research, I didn't find such known issue. Could you let us know that is there any change before we get this issue?

Meanwhile, could you let us know what is the OS version of SCVMM 2019 UR2? Was it Windows server 2019? If not we suggest to upgrade the OS to avoid some issue caused by component not updated. If yes, we suggest to install the latest windows update on the server. Meanwhile, please also try to install the latest windows update on Hyper-V server and VM to avoid any complexity issue.

If there's any update, feel free to let us know.

0 Votes 0 ·
JvdB-8931 avatar image
0 Votes"
JvdB-8931 answered ·

Thanks for your reply. The OS version of our VMM server as well all our Hyper-V hosts (except some stand-alone hosts) is Server 2019. The VMM server is fully updated, and we regularly update our Hyper-V hosts. We're already experiencing this issue on multiple update levels.
As far as I know there were no big changes before this started happening.

· 1 ·
10 |1000 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

@JvdB-8931, Thanks for the reply. From your description, I know all are update to the latest. And the event log shows normal behavior. To check such issue, more log analysis is needed. As Q&A has limitation for such case, we suggest to contact Microsoft support to troubleshoot it. Here is a link list the Phone number we can contact:
https://support.microsoft.com/en-us/topic/global-customer-service-phone-numbers-c0389ade-5640-e588-8b0e-28de8afeb3f2

Thanks for the understanding.

0 Votes 0 ·
JvdB-8931 avatar image
0 Votes"
JvdB-8931 answered ·

That's not entirely true. We discovered that on every Hyper-V host the vmmagent crashes every few minutes:
65352-image.png


This keeps happening, and we think this could have something to do with our issue.
Reinstalling doesn't fix the issue, because it happens at cluster we installed more then a year ago as well as on cluster we installed only a couple weeks ago.
I hope this sounds familiair to someone.


image.png (10.7 KiB)
· 9 ·
10 |1000 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

@JvdB-8931, Research and find WMI issue can cause the crash. we can check if there's any WMI error there. If yes, try to rebuild it to see if it is working.

0 Votes 0 ·

I haven't been able to find any WMI issues yet. If this isn't the issue, any more ideas on what can be causing this? The weird thing is that it happens on servers we provisioned 2 years ago and also a few weeks ago. Looks like some kind of bug in SCVMM 2019 or UR2 to me. But more people should be experiencing this issue then..

0 Votes 0 ·

@JvdB-8931, Research but didn't find such known issue published. But I find some issue mentioned that vmmagent version mismatch may cause the issue. If we didn't have this situation, we suggest to open case to troubleshoot the issue. Here is the contact list:
https://support.microsoft.com/en-us/topic/global-customer-service-phone-numbers-c0389ade-5640-e588-8b0e-28de8afeb3f2

Thanks for the understanding.

0 Votes 0 ·
Show more comments