I am using SolidCP1.4.2 and Windows2019 Datacenter for creating VPS. General area is not working properly after I created Windows2016/2012R2 VPS. It means that I can not manage(Reboot/shutdown/reset) the VPS created in Windows2019DC. But Windows2019 VPS is OK. Please see the screenshot at http://prntscr.com/lqcc7b
But 3 of them are working well in Windows2016 Datacenter with SolidCP1.4.2.
Is there any good suggestion? Thank you in advance!
Please see logs below:
[12/3/2018 7:02:55 PM] ERROR: ‘Microsoft Hyper-V 2012 R2’ GetVirtualMachine
System.Management.Automation.GetValueInvocationException: Exception getting “PrimaryOperationalStatus”: “The object contained a value in property ‘OperationalStatus’ that is not valid.” —> Microsoft.Virtualization.Client.Management.InvalidWmiValueException: The object contained a value in property ‘OperationalStatus’ that is not valid.
at Microsoft.Virtualization.Client.Management.VMIntegrationComponentStatusUtilities.ConvertOperationalStatus(UInt16 operationalStatusValues)
— End of inner exception stack trace —
at System.Management.Automation.Adapter.BasePropertyGet(PSProperty property)
at SolidCP.Providers.Virtualization.VirtualMachineHelper.GetVMHeartBeatStatus(PowerShellManager powerShell, String name)
at SolidCP.Providers.Virtualization.HyperV2012R2.GetVirtualMachineInternal(String vmId, Boolean extendedInfo)
at SolidCP.Server.VirtualizationServer2012.GetVirtualMachine(String vmId)
Well, at this moment I don’t have test lab with the Windows Server 2019, so I can’t check this.
But it looks like in Windows Server 2019 Microsoft change something with returning value in the VMIntegrationService, so probably at this moment SolidCP doesn’t support HyperV2019.
Can you use this command on the server which have problem with SolidCP and show output?
Get-VMIntegrationService -VMName “name of server” -Name “HeartBeat” | Select *
replace “name of server” to your server with 2012R2, 2016 and 2019 OS
In Windows2016 Datacenter, we can get all status and description.
Please refer to https://prnt.sc/lrar04
Looks like the problem is from VM Integration Service in Windows2019 DC.
Well, It looks like another MS bug 🙁
I’ll think about the better solution, and try to push it in the next release version of SolidCP.
At this moment don’t use HyperV2019 with SolidCP 1.4.2
The solution is only one – don’t use HyperV2019 with SolidCP 1.4.2.
You also can try in HyperV Provider settings set the VMConfig to 5.0.
- Views1828 times
- Answers13 answers