Morning,
We have a stuck VMware Pool in the deleting phase and it is generating a lot of errors in the event log. I have followed this KB article http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=100865... and the query is not showing any results related to that pool. We are running VMware View 5.0.0. There are no VMs related to this pool in vSphere, it's just being stubborn and won't delete.
Any ideas here?
I followed the KB linked above to connect to the ADAM DB and went to the server roles table and manually deleted my stuck pool. Worked!
The instructions you posted were for 4.x ... Have a look at these : http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=201511...
We ran into the same problem at Christmas time and I was able to delete things from running the AD queries specified and removing the link to the old pool / stale desktop from View 5.2
Good luck
thanks! I just ran the SviConfig syntax and it said my VM was not found in the database because there is no VM related to the pool, there is only the pool name in View Admin page. I entered the pool name like this:
SviConfig -operation=RemoveSviClone -VmName=W7TA -AdminUser=* -AdminPassword=* -ServerUrl=https://localhost:18443/SviService/v2_0
Obviously I put the username and password in there. Any ideas?
Hmm I wish I could offer more advice. My situation was slightly different in that I had a pool I wanted to kill off but I had a VM that was stuck in deleting even though it had been removed from vCenter. Once i got it out of the composer DB, I was able to remove the pool without incident. You may want to contact support. There may be a slightly different query you can run to identify the pool in question to remove from sviconfig. But don't quote me on that.
Good luck, i hope you're able to sort it out
EDIT: I found this :
A broken pool that does not contain any desktops can be removed from View Manager by removing the pool entry from both the Server Groups and Applications organizational units. However, removing one entry and not the other from the ADAM database results in the java.lang.nullpointerexception error when attempting to view the pools or desktops inventory in View Manager. - See more at: http://www.itninja.com/blog/view/how-to-delete-a-stuck-vdi-pool-vm#sthash.RLdrIgkF.dpuf
http://www.itninja.com/blog/view/how-to-delete-a-stuck-vdi-pool-vm
Thanks so much, I have sent them an email and will report back the results!
Also had this in my bookmarks, perhaps it can be of use to you
I followed the KB linked above to connect to the ADAM DB and went to the server roles table and manually deleted my stuck pool. Worked!
Awesome !! I'm glad you got it resolved. I know how much it drove us crazy here for a couple days
I realize this is an old post, but this helped me as well. Thanks!
Conect Server Horizon Control Manager
Run View PowerCli
Comman Get-Pool -pool_id XXXX
Comman remove-Pool -pool_id ID03 -DeleteFromDisk $true
Good