OPERATIONAL DEFECT DATABASE
...
...
You cannot remove replica virtual machines associated with desktop pools in View ComposerRemoving source and replica virtual machines associated with desktop pools in View Composer failsYou have already used ViewDBChk Removing invalid linked clone entries automatically using the ViewDBChk tool (2118050) without success.
This article provides information on the unprotected entity operation in sviconfig, which allows you to unprotect replica virtual machines for deletion from VirtualCenter or vCenter Server.This is a legacy article for versions of Horizon prior to Horizon 8 Horizon 7.13.x has reached its End of General Support (Apr 30, 2023) and has entered into its Technical Guidance Support phase (ends Apr 30, 2025) Important: We recommend you migrate from Horizon 7 to Horizon 8 as soon as possible. Horizon 8 offers numerous improvements in performance, scale, and experience for both Administrators and end users. Please see Ensuring a successful migration from Horizon 7 to Horizon 8 (89840) for additional advice. Support level for deprecated features with Horizon 8.0(2006) (94831) has details in regards to Horizon 8.0 which allowed a transition period/
Note: If you are trying to find or remove an unused replica virtual machine, see Finding and removing unused replica virtual machines in VMware View (2009844). The View Connection Server creates, manages, and deletes linked clones during the View Composer operations. If the Connection Server functions are interrupted, the linked clones create orphaned folders, protected folders and virtual machine objects remaining in vCenter Server. To resolve this issue, run the unprotectentity command to remove the protection from linked clone objects. Run these commands from the command prompt on the View Composer Server:C:\Program Files (x86)\VMware\VMware View Composer Note: In Windows Server 2008 machines, the command prompt must be run as an Administrator or you will receive an error. To accomplish this, Click Start, and type cmd. Hold Ctrl + Shift, and press Enter. User Account Control then confirms the escalated permissions, and you will be running cmd.exe as an Administrator. Unprotecting a replica in the VMwareViewComposerReplicaFolder folder For View Composer 2.7 and earlier (View 5 and earlier), run this command: sviconfig -operation=UnprotectEntity -VcUrl=https://VirtualCenter_address/sdk -Username=VirtualCenter_account_name -Password=VirtualCenter_account_password -InventoryPath=/Datacenter_name/vm/VMwareViewComposerReplicaFolder/Replica_Name -Recursive=true For View Composer 3.0 (View 5.1and later), run this command: sviconfig -operation=UnprotectEntity -DsnName=name_of_DSN -DbUsername=Composer_DSN_User_Name -DbPassword=Composer_DSN_Password -VcUrl=https://vCenter_Server_address/sdk -VcUsername=Domain\User_of_vCenter_Server_account_name -VcPassword=vCenter_Server_account_password -InventoryPath=/Datacenter_name/vm/VMwareViewComposerReplicaFolder/Replica_Name -Recursive=true Notes: The sviconfig command parameters are case sensitive.Values in italics are variables and must be replaced with your environmental values.Values with spaces must be surrounded by double quotes. For example: -InventoryPath= "/View Repository/vm/VMwareViewComposerReplicaFolder" The VMwareViewComposerReplicaFolder is a special container. The replica virtual machines are not visibly part of this container and the path to the virtual machine for sviconfig will always be /Datacenter_Name/vm/VMwareViewComposerReplicaFolder/replica-xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx, regardless of which Resource Pools or Folders contain the virtual machine.If the Datacenter object is not the top-level object and is inside a folder, the path must reflect this. For example, /folderName/Datacenter_Name/vm/VMwareViewComposerReplicaFolder/replica-xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx.In some cases the sviconfig command to unprotect the replica may fail. If this occurs, unprotect the folder containing the replica using the procedure below to unprotecting the replica folder and its contents, and remove the replica. Afterwards use the protectEntity operation to re-protect the folder once you have deleted the orphaned object. Note: For more information on removing replica in View 5.2 and later, see Finding and removing unused replica virtual machines in the VMware Horizon View (2009844). Manually removing problem desktops and pools from Horizon (2015112) Unprotecting the replica folder, VMwareViewComposerReplicaFolder and all the linked clone related objects it contains For View Composer 3.0 (View 5.1 and later), run this command: sviconfig -operation=UnprotectEntity -DsnName=name_of_DSN -DbUsername=Composer_DSN_User_Name -DbPassword=Composer_DSN_Password -VcUrl=https://vCenter_Server_address/sdk -VcUsername=Domain\User_of_vCenter_Server_account_name -VcPassword=vCenter_Server_account_password -InventoryPath=/Datacenter_name/vm/VMwareViewComposerReplicaFolder -Recursive=true In View Composer 2.5 and later, you can re-protect the VMwareViewComposerReplicaFolder using -operation=ProtectEntity The SviConfig utility does not check if a replica is currently in use by other linked clones. If a replica is in use, the linked clones cannot be powered on, refreshed, or recomposed after the replica is unprotected or deleted. You have to manually delete these unusable linked clones. Provisioning new linked clones from the same desktop pool creates new provisioned linked clones for these clones. Determining which replica disk is used for a linked clone virtual machine (1031842) can assist in determining if a linked clone is utilizing a disk. Note: The inventory path is case-sensitive. If any part of the path entered in the command line differs from the inventory path, you can receive an Error 11. Possible error codes from the SviConfig utility This table lists possible error codes from the SviConfig utility: Code Description 0 successful execution 1 The supplied DSN name can not be found 2 The supplied credentials are invalid 3Unsupported driver for the provided database4Unexpected problem arisen9 An invalid VirtualCenter URL was provided 10 VirtualCenter was unavailable or could not be accessed 11 The specified entity was not found 12 Unknown entity type. Recognized entities are VM and Folder 13 Failed to unprotect replica 14Unsupported database schema version is found15Other application is using required resources. Stop it and retry the operation18Unable to connect to database server26There are some errors during the operation27The replica folder name cannot be found in VC inventory28Failed to create unused replica folder29Failed to move VM into a VC folder34invalid VC certificate Note: If you receive Error code 11 when you run the command and your replicas are in a folder and not directly under the Datacenter, the path should be manually substituted in place of VMwareViewComposerReplicaFolder.
For related information, see: Manually deleting linked clones or stale virtual desktop entries from VMware View Manager 4.5 and later (2015112)Finding and removing unused replica virtual machines in VMware View (2009844)Re-protecting a View replica virtual machine (2015006)
Click on a version to see all relevant bugs
VMware Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.
