I worked on this issue where the user was unable to perform a recompose task on a linked clone pool, that was part of the older version of View Manager. The View Manager had been recently upgraded to version 4.5
The error message included the following -
"VMware.Sim.Fault.InvalidOperationFault, NonCompatibleDeploymentGroup "
After some investigation, I found out that this issue was caused because the linked clone pool was still associated with the old VC_CONFIG_ID in the Composer database. The VC_CONFIG_ID is changed during the upgrade process.
Running the below command on the Composer database resolved the issue.
UPDATE dbo.SVI_DEPLOYMENT_GROUP
SET VC_CONFIG_ID = 'right_id'
WHERE VC_CONFIG_ID = 'wrong_id'
The right VC_CONFIG_ID can be identified from the table dbo.SVI_VC_CONFIG_ENTRY in the View Composer database. It would be the ID associated with any new pool created after the upgrade.
Another way would be to find the VC_CONFIG_ID from the ADAM database of the View Connection Server.
If this article is of some help, please leave a comment.
Thursday, April 14, 2011
Removing Stale/Orphaned VMs from View Manager
This other day, I got to work on a simple but interesting issue. This user had a power outage in his datacenter and all his servers went down. This caused various tasks initiated by the View Connection Server to fail which in turn led to orphaned VMs.
We tried removing the stale entries as per the below KB article, but we were still not able to create new VMs with the same name.
Manually deleting linked clones or stale virtual desktop entries from VMware View Manager
I was finally able to fix it, after I cleared the stale/orphaned VM entry from all the below locations.
1. View Connection Server Adam database - Refer above VMware kb
2. View Composer database - Refer above VMware kb
3. Virtual Center inventory - Manually delete the VM
4. Virtual Center Datastore - delete the VM folder
5. Active Directory
If this article is of some help, please leave a comment.
We tried removing the stale entries as per the below KB article, but we were still not able to create new VMs with the same name.
Manually deleting linked clones or stale virtual desktop entries from VMware View Manager
I was finally able to fix it, after I cleared the stale/orphaned VM entry from all the below locations.
1. View Connection Server Adam database - Refer above VMware kb
2. View Composer database - Refer above VMware kb
3. Virtual Center inventory - Manually delete the VM
4. Virtual Center Datastore - delete the VM folder
5. Active Directory
If this article is of some help, please leave a comment.
Subscribe to:
Posts (Atom)