Error (20408)
VMM could not get the specified instance Microsoft:{7172d33e-7a0b-4b32-b93b-e958f5cf7356} of class http://schemas.microsoft.com/wbem/wsman/1/wmi/root/standardcimv2/MSFT_NetAdapterRssSettingData on the server xxx. The operation failed with error NO_PARAM
I have not found any solution to fix this error.
Any help would be really appreciated!
Thanks in advance
Our SCVMM 2016 setup is failing with the following error:
A Hardware Management error has occurred trying to contact server 'MAIN-VMM-2016.main.local' .
WinRM: URL: [http://main-vmm-2016.main.local:5985], Verb: [GET], Resource: [http://schemas.microsoft.com/wbem/wsman/1/wmi/root/scvmm/FileInformation?Filename=\\MAIN-VMM-2016.main.local\MSSCVMMLibrary\VHDs\Blank Disk - Small.vhd]
Check that WinRM is installed and running on server 'MAIN-VMM-2016.main.local'. For more information use the command "winrm helpmsg hresult" andhttp://support.microsoft.com/kb/2742275.
MAIN-VMM-2016.main.local is a guest Windows Server 2016 VM running on Hyper-V Server 2016. We have confirmed the WinRM service is running and have followed the suggestion the referenced KB and KB2742246. MAIN-VMM-2016.main.local can ping itself, other hosts in the domain can ping MAIN-VMM-2016.main.local and we have turned all the firewall profile states to off.
Any suggestions or directions would be greatly appreciated.
pcf
Hi,
I have deployed a SCVMM 2012 R2 , two Windows Server 2012 R2 with the Hyper-V hosts.
For my test , I connect all devices (including a storage array(with two controllers),and a SMI-S provider) to the same switch.
When I tried to create iSCSI session and Use advanced settings, The three drop down lists Target portal, Target name and Initiator IP are empty.
The followings are some settings I have done.
1.I have create two storage pools.
2.I have allocated storage pools to the host group.
3.I have set Microsoft iSCSI Initiator Service to start automatically and start it on both Hyper-V Hosts.
4.I have installed MPIO feature.
5.I have add the iSCSI portals and logged both iSCSI Initiators to both controllers on the array.
6.SCVMM hyper-v host properties can show iSCSI Arrays and indicate that two storage pools are managed.
I would like to ask
1.if I have missed any settings,
2. should SCVMM automatically scan the values of drop down lists(Target portal, Target name and Initiator IP) or SMI-S provider should send the values to SCVMM?
Thanks!
David
Completely bold out,please help,this is while adding host back to SCVMM 2k16:
An internal error has occurred trying to contact the '<g class="gr_ gr_57 gr-alert gr_spell gr_inline_cards gr_run_anim ContextualSpelling" data-gr-id="57" id="57">xxxxxxx</g>.Qa.2k16_2' server: : .
WinRM: URL: [https://xxxxxxx.qa.2k16_2:5986], Verb: [ENUMERATE], Resource: [http://schemas.microsoft.com/wbem/wsman/1/wmi/root/cimv2/Win32_OperatingSystem], Filter: []
Hi everyone.
somebody knows if scvmm 2019 license can be apply to scvmm2016?
Thks.
Hi all,
I have the following situation - a single box with SQL2012, SCOM 2012 SP1 and SCVMM2012 SP1 (connected). As I am upgrading to VMM 2012 R2, I had to uninstall the VMM 2012 SP1. The issue is that the SP1 setup fails with error 1603. Before uninstalling I removed the VMM rollup update (there was only one installed). Here is part of the vmmserver.log file I think is somewhat relevant:
MSI (s) (40:F4) [21:33:23:983]: Invoking remote custom action. DLL: C:\Windows\Installer\MSI12C7.tmp, Entrypoint: DisableWsmanCredSSP Action start 21:33:23: DisableWsmanCredSSP. CustomAction DisableWsmanCredSSP returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)
I tried the following cmdlet - disable-wsmancredssp -role server and disable-wsmancredssp -role client but setup still fails with the same error.
I hope someone can enlighten me regarding this as now I don't have any VMM working :D
Thanks in advance!
Ivailo Tzenkov
Hello.
I'm evaluating the use of SP1. So far so good, except for silently installing the console on out technicians computers. We managed to do so with the 2012 RTM version, but with the 2012 SP1 RTM version we are having some problems. We are using this command
"%~dp0setup.exe" /client /i /f "%~dp0amd64\Setup\VMClient.ini"
But the installation stops early, and the logs say:
vmstpstub entered
Run SetupVM.exe
start /wait SetupVM.exe /spawned /SetupLocation "E:\amd64\3082\LaunchScreen.DLL\..\..\\" /i /client
start /wait SetupVM.exe /spawned /SetupLocation "E:\amd64\3082\LaunchScreen.DLL\..\..\\" /i /client
Error : Setup failed, error 15
Delete "E:\amd64\3082\LaunchScreen.DLL\..\..\\"
I have tried using absolute paths, using a network share, a mounted iso, a local path. Also tried not specifying a ini file.
If we try to install it manually it works perfectly. We are deploying on Windows 7 SP1 x64 Enterprise machines.
Any help?
Where can I download virtual machine manager 1807 non-eval copy? I looked at my volume license service site and I cannot find it. I was told we have a license for it, I just cannot figure out where to download it?
can someone point me in the right direction?
also, is this the newest version?
thanks
Frank
Entered in name, org, key and went to the next screen.
Then checked the checkbox and the next button was activated
Clicked next, nothing happens, click next a few times, nothing happened. Waited a while, nothing happens. I then as the button is selected I hit Enter key and the screen disappears and nothing happens. Wait and still nothing.
What could be the problem?
Hey Guys,
I'm currently upgrading my SCVMM 2012R2 environment to a SCVMM 2016.
I've imported a SQL Dump on a new SQL Server with the same version (13.0.4001.0).
The SCVMM himself will be installed on a new Windows Server 2019
During the Installation of SCVMM 2016 the installation will abort with the following error Message:
Unable to connect to the VMM database because of a general database failure. Ensure that the SQL Server is running and configured correctly, then try the operation again.The interesting Part of the Logfiles are:
11:01:03:Doing Postinstall task for PangaeaServer 11:01:03:ProcessInstalls: Install Item VMM management server was successful. We will launch the post process delegate. 11:01:24:Windows feature RSAT-Clustering-PowerShell already enabled, skipping 11:01:26:Windows feature WindowsStorageManagementService already enabled, skipping 11:01:28:Windows feature UpdateServices-API already enabled, skipping 11:01:31:Windows feature FabricShieldedTools already enabled, skipping 11:01:33:Windows feature RSAT-Storage-Replica already enabled, skipping 11:01:33:Out of Impersonation 11:01:33:Out of Impersonation 11:01:33:VMMPostinstallProcessor threw an exception: Threw Exception.Type: Microsoft.VirtualManager.DB.CarmineSqlException, Exception.Message: Unable to connect to the VMM database because of a general database failure. Ensure that the SQL Server is running and configured correctly, then try the operation again. 11:01:33:StackTrace: at Microsoft.VirtualManager.DB.SqlRetryCommand.ExecuteNonQuery() at Microsoft.VirtualManager.Setup.SetupDatabaseHelper.AlterDB(String databaseName, String instanceName, String commandString) at Microsoft.VirtualManager.Setup.SetupDatabaseHelper.AlterDB(String databaseName, String instanceName) at Microsoft.VirtualManager.Setup.VirtualMachineManagerHelpers.CreateDB() at Microsoft.VirtualManager.Setup.InstallItemCustomDelegates.PangaeaServerPostinstallProcessor() 11:01:33:InnerException.Type: System.Data.SqlClient.SqlException, InnerException.Message: Subquery returned more than 1 value. This is not permitted when the subquery follows =, !=, <, <= , >, >= or when the subquery is used as an expression. The statement has been terminated. 11:01:33:InnerException.StackTrace: at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction) at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose) at System.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj, Boolean& dataReady) at System.Data.SqlClient.SqlCommand.RunExecuteNonQueryTds(String methodName, Boolean async, Int32 timeout, Boolean asyncWrite) at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(TaskCompletionSource`1 completion, String methodName, Boolean sendToPipe, Int32 timeout, Boolean& usedCache, Boolean asyncWrite, Boolean inRetry) at System.Data.SqlClient.SqlCommand.ExecuteNonQuery() at Microsoft.VirtualManager.DB.SqlRetryCommand.ExecuteNonQuery() 11:01:33:ProcessInstalls: Running the PostProcessDelegate returned false. 11:01:33:ProcessInstalls: Running the PostProcessDelegate for PangaeaServer failed.... This is a fatal item. Setting rollback. 11:01:33:SetProgressScreen: FinishMinorStep. 11:01:33:ProcessInstalls: Rollback is set and we are not doing an uninstall so we will stop processing installs 11:01:33:**************************************************************** 11:01:33:****Starting*RollBack******************************************* 11:01:33:****************************************************************
I'm confused and can't see the problem.
The User is sysadmin on the database instance.
I've already tried to execute the script from
support.microsoft.com/en-us/help/3132774/how-to-retain-the-database-when-you-reinstall-virtual-machine-manager
but it won't help.
Any good ideas?
Thanks in advance
Oni
Hello,
I am trying to add iSCSI array to my 2019 hosts with SCVMM 2019, I checked everything and looks ok but "Add iSCSI Array" option is grayed out.
Please help me if you know what the issue is.
Thanks
Error message: "Storage logical unit LUN01 has been allocated to host group All Hosts where none of the hosts in host group has access to storage array" (warning 26129)
I have VMM 2016 managing several VM hosts through different sites, about 45 of them. At the moment, my domain controllers are physical servers but I would like to virtualize them all and use Core at the same time. In order to do this, I would like to put the DCs on stand alone servers, that way the host is not depending on the DCs at all.
What I need to do is to install the VMM agent on stand alone servers. I have followed the instructions in this link, https://adinermie.com/how-to-add-hyper-v-hosts-in-a-perimeter-network-in-vmm-2012-r2/. The agent installed fine but I can't contact the host after the agent is installed. I can't do anything else on the server either.
Any ideas?
Thanks.
One of my customers is required to use Zerto in combination with SCVMM 2016.
They currently run the Semi-Annual-Channel (SAC) version which is not compatible with Zerto.
Therefore, we need to go back to the LTSC version.
What is the easiest way to accomplish this?
If uninstall is required, could we have a problem with the SQL database for SCVMM being at a higher level?
Owner of AzureCloudLabs, previously Failover Cluster MVP, Hyper-V MVP and Cloud and Datacenter MVP
Hello,
I was wondering if I can add a 2016 Domain controller to my Environment with 2008R2 Domain and Forest function level?
Thanks
I bet you think this post is about you. Don't you…don't you. ♪
Im not sure if i write in the right category but moderator from Microsoft Community told me to share my problem with you. My problem i cant enable Windows Subsystem for Linux.I tried to turn it on from PowerShell by typing a command then restart my PC but it says the update couldn apply. The Moderator replied with some Troubleshooting articles but they didnt helped me.
I can't get the VMM 2019 server to manage a Windows 2019 server with Hyper-V enabled that resides in an untrusted domain. It always errors out. I've reproduced the issue in a fresh lab to confirm my production environment and GPO's aren't causing any problems. Adding hosts in the same domain as VMM works fine as expected. But untrusted hosts being added always results in this error:
Error (2917)
Virtual Machine Manager cannot process the request because an error occurred while authenticating 'labz-hv01.labz.localdomain'. Possible causes are:
1) The specified user name or password are not valid.
2) The Service Principal Name (SPN) for the remote computer name and port does not exist.
3) The client and remote computers are in different domains and there is not a two-way full trust between the two domains.
The network path was not found (0x80070035)
VMM Server: VMM 2019 on Server 2019 Standard
- joined to: labx.localdomain
- fqdn: labx-vmm.labx.localdomain
Hyper-V Host: Hyper-v Role enabled on Server 2019 standard
- joined to: labz.localdomain
- fqdn: labz-hv01.labz.localdomain
Per the documentation, adding a host in a separate, untrusted domain, is fully supported and the steps are very simple:
https://docs.microsoft.com/en-us/system-center/vmm/hyper-v-existing?view=sc-vmm-2019
Untrusted domain: Enter the FQDN or IP address of the server or cluster that you want to add, and then click Add. For a cluster, you can enter an FQDN or IP address of the cluster or of one of the cluster nodes.
Whether DNS is used, local accounts vs domain accounts for the runas account, the steps in the documentation always results in the above Job error when trying adding the host.
What steps are required to successfully add an untrusted Hyper-V server to VMM?
So I've just rolled out VMM 2019 and added in our 2019 hypervisors and I'm seeing a couple quirks I wanted to get some general consensus around.
1) VLAN config at the logical switch seems to drop off and on from the hypervisors. It working yesterday, came in this morning and had to re-enable the checkboxes again under the Host Network config.
2) Can't migrate VMs anymore. It says the
"The virtual machine (XXXXXX) is not compatible with the virtualization host (YYYYYYYY). The virtual machine may not start or operate correctly on the host. This may be due to inconsistent processor compatibility information. Yet it is enabled for the VM"
However these settings are in place:
3) Migration settings seem to have changed to CredSSP overnight. Very odd.