Error 12711 The Cluster Group Could Not Be Found

(עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 (中文)台灣 (中文)日本 (日本語)  Home2012Previous VersionsLibraryForumsGallery Ask a question Quick access Forums home Browse forums users FAQ Search related threads Remove From My Forums Answered by: Error ID: 12711, Detailed Error: The cluster resource could not be found (0x138F) System the group or resource is not in the correct state to perform the requested operation (0x139f) Center - Virtual Machine Manager > Virtual Machine Manager – General Question 0

Scvmm 2012 R2 Error 12711

Sign in to vote I am trying to modify the properties of a Virtual Machine that is part of

Error 12711 Scvmm 2012 Sp1

a cluster via Powershell:Set-VM -startaction alwaysautoturnonVMOn some of the VMs in my cluster I get the following errors:Set-VM : VMM cannot complete the WMI operation on server Virtual11 because of error:[MSCluster_Resource.Name="fc75f97b-db7a-43c2-aaec-a154b1d07611"] The cluster

The Cluster Group Could Not Be Found (0x1395)

resource could not befound.(Error ID: 12711, Detailed Error: The cluster resource could not be found (0x138F)) Resolve the issue and then try the operation again. To restart the job, run the following command:PS> Restart-Job -Job (Get-VMMServer Virtual11 | Get-Job | where { $_.ID -eq "{b610c7cd-0969-41c7-9cf4-c8fc5bc5f118}"})At line:1 char:90+ Get-VM -VMMServer Virtual11 | Where {$_.StartAction -ne "AlwaysAutoTurnOnVM"} | set-vm <<<< -startaction alwaysautoturnonVM + CategoryInfo : ReadError: (:) [Set-VM], CarmineException + FullyQualifiedErrorId : 12711,Microsoft.SystemCenter.VirtualMachineManager.Cmdlets.SetVMCmdletI have tried uninstalling the VMM agent on all my cluster nodes, reinstalling, moving the VMs to another node, restarting the host server - none work.Let me also mention that:- After reinstalling the VM does show up on the right server as ok, with the refresh job successful- I already get a red X after trying to change the properties of the VM- After the first error the VM does not update in VMM if I move the VM to another cluster host, so that when I want to re-run the refresh job I get the following error:The WS-Management service cannot process the request. Object not found on the Virtual11 server. (Unknown error (0x80338000)) Then, if I try to put the host in Maintenance Mode, VMM gets stuck that the server is in MM, where even if I select "Stop Maintenance Mode" a couple of times, it is still stuck in that mode. After a minute or so if popsout of MM, but still, I see all my failed VMs there which are now running on a different host.Any ideas what the problem is?Thanks,Reuv Sunday, March 07

360 games PC games Windows games Windows phone games Entertainment All Entertainment Movies & TV Music Business & Education Business Students & educators Developers Sale Sale Find a store Gift cards Products Software & services Windows Office Free downloads & security Internet https://social.technet.microsoft.com/Forums/systemcenter/en-US/c597eec3-ddb6-4610-ae9e-4d15f8dbd4ac/error-id-12711-detailed-error-the-cluster-resource-could-not-be-found-0x138f?forum=virtualmachinemanager Explorer Microsoft Edge Skype OneNote OneDrive Microsoft Health MSN Bing Microsoft Groove Microsoft Movies & TV Devices & Xbox All Microsoft devices Microsoft Surface All Windows PCs & tablets PC accessories Xbox & games Microsoft Lumia All https://support.microsoft.com/en-us/kb/2417319 Windows phones Microsoft HoloLens For business Cloud Platform Microsoft Azure Microsoft Dynamics Windows for business Office for business Skype for business Surface for business Enterprise solutions Small business solutions Find a solutions provider Volume Licensing For developers & IT pros Develop Windows apps Microsoft Azure MSDN TechNet Visual Studio For students & educators Office for students OneNote in classroom Shop PCs & tablets perfect for students Microsoft in Education Support Sign in Cart Cart Javascript is disabled Please enable javascript and refresh the page Cookies are disabled Please enable cookies and refresh the page CV: {{ getCv() }} English (United States)‎ Terms of use Privacy & cookies Trademarks © 2016 Microsoft

Error (12711) VMM cannot complete the WMI operation on server because of error: [MSCluster_ResourceGroup.Name="a1e132f2-9f0d-41f3-8cdb-8a6562bf68c2″] The cluster group could not be found. (The cluster group could not be found (0x1395)) https://shcit.wordpress.com/2012/08/13/hyper-v-system-center-virtual-machine-manager-2008-r2-error-12711-the-cluster-group-could-not-be-found-0x1395/ Recommended Action Resolve the issue and then try the operation again. This problem comes up because of different VMResourceGroupID´s in the SCVMM Database and Hyper-V Host. The VM maybe was imported or exported without refreshing the Host in SCVMM or removed from the Cluster and added back again. If this happen you can do an export of the VM and import it back into the Hyper-V Cluster with SCVMM. error 12711 This means a downtime for your VM! If you need a non-downtime fix you have to change the information on the SQL Database of the SCVMM. First tpye the following text into powershell on the host running the VM # Add the SCVMM snapin to the powershell Add-PSSnapin microsoft.systemcenter.virtualmachinemanager # Connect to the Hyper-V-server Get-VMMServer –ComputerName Hyper-V-Server.fqdn.tld #write the not working VM into the variable $VM $vm = get-VM the cluster group -name „problematic-vm.fqdn.tld" #force a refresh of the vm refresh-vm -force $vm you will get the ID of the VM write this ID down we need it later again Now you have to change the wrong ID in the SVCMM Database with the right on from the Hyper-V Host First we have to find the true ID of the VM. Therefore open the registry-editor on the Hyper-V Host running the VM goto: - Now open the SQL Database using Mangement Studio Express - find the table “dbo.tbl_WLC_VMInstance” in the SCVMM Database. - find the VM by his name in the table - goto VMResourceGroupID column - check the ID in this cell wheter or not the ID in the cell is the same as found in the powershell - change the ID of the VM in the cell “VMResourceGroupID” to the ID of the registry - restart the SCVMM console (no server-reboot needed) - do a refresh of ALL hosts - try to move the VM again Attention this fix is not proofen by Microsoft. Use this at your own risk!!! thx to workinghardinit Gefällt mir:Gefällt mir Lade... Ähnlich This entry was posted on Montag, 13. August 2012 at 15:50 and is filed under Windows. You