Knowledge Base

The VMware Knowledge Base provides support solutions, error messages and troubleshooting guides
 
Search the VMware Knowledge Base (KB)   View by Article ID
 

Manually deleting linked clones or stale virtual desktop entries from VMware View Manager 3.x and 4.0.x (1008658)

Symptoms

  • You cannot provision a linked clone desktop pool.
  • You see the error:

    Desktop Composer Fault: 'Virtual Machine with Input Specification already exists'

  • Provisioning a linked clone desktop pool fails with the error:

    Virtual machine with Input Specification already exists

  • The Connection server shows that linked clone virtual machines are stuck in a deleting state.

Cause

This issue may occur when:
  • A table in the database contains incorrect data.
  • The virtual machine name has been manually changed in the vCenter Server after the pool has been created, which causes View Composer and vCenter Server to refer to the same virtual machine with different names.
  • There are inconsistencies in the Composer database. For example, if the database was restored to an out-of-date backup.

Resolution

This solution applies to VMware View 3.x and 4.0.x. For View 4.5 and later, see Manually deleting linked clones or stale virtual desktop entries from the View Composer database in VMware View Manager 4.5 and later (2015112).

Note: If you follow the steps in Manually deleting linked clones or stale virtual desktop entries from the View Composer database in VMware View Manager 4.5 and later (2015112) and it does not resolve the issue in View 4.5 and later, continue to perform the procedures in this article.

If the virtual machine was renamed through the vSphere Client after the pool was provisioned, you can resolve the issue by renaming the virtual machine to its original deployed name.

To resolve database inconsistency, you must delete the virtual machine references from the ADAM database and from the View Composer database so the tables regenerate properly. Then ensure that no pool desktop names are changed through vCenter Server after the pool is created.

Perform these steps in order. The sections are ordered in the most appropriate sequence to isolate the issue, identify the proper resolution, and minimize data loss. After each section, check to see if the issue is resolved. Work through each troubleshooting section in order, and do not skip a section.

Warning: Before you delete entries from either database, take a complete backup of the ADAM and Composer databases and disable provisioning for the pool in View Manager. For more information, see Performing an end-to-end backup and restore for VMware View Manager (1008046).

Removing the virtual machine from the ADAM database

Note: Before removing entries from the ADAM database, note the virtual machine name of the desktops that are being removed for reference when editing the Composer database.
  1. Connect to the View ADAM database. For more information on connecting to the ADAM database with ADSI Edit, see Connecting to the View ADAM Database (2012377).
  2. Locate the GUID of the virtual machine.

    To locate the GUID of the virtual machine:

    1. Right-click the Connection View ADAM Database [localhost:389], and click New > Query.
    2. Under Root of Search, click Browse and select the Servers organizational unit.
    3. Click OK.
    4. In the Query String, paste this search string:

      (&(objectClass=pae-VM)(pae-displayname=VirtualMachineName))

      Where VirtualMachineName is the name of the virtual machine for which you are trying to locate the GUID. You may use * or ? as wildcards to match multiple desktops.

    5. Click OK to create the query.
    6. Click the query in the left pane. The virtual machines that match the search are displayed in the right pane.

  3. Record the GUID in cn=<GUID>.
Delete the pae-VM object from the ADAM database:
  1. Locate the OU=SERVERS container.
  2. Locate the corresponding virtual machine's GUID (from above) in the list which can be sorted in ascending or descending order,
  3. Select Properties and check the pae-DisplayName attribute to verify the corresponding linked clone virtual machine object.
  4. Verify and delete the pae-VM object.
Notes:
  • Check if there are entries under OU=Server Groups and OU=Applications in the ADAM database.
  • 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.

Removing the linked clone references from the View Composer database

To remove the linked clone references from the View Composer database:
  1. Open SQL Manager > Databases > View Composer database > Tables.
  2. Open the dbo.SVI_VM_NAME table and delete the entire row where the virtual machine is referenced under the NAME column.
  3. Open the dbo.SVI_COMPUTER_NAME table and delete the entire row where the virtual machine is referenced under the NAME column.
  4. Open the dbo.SVI_SIM_CLONE table, find the virtual machine reference under column VM_NAME and note the ID. If you try to delete this row, it complains about other table dependencies.
  5. Open the dbo.SVI_SC_PDISK_INFO table and delete the entire row where dbo. SVI_SIM_CLONE ID is referenced under the PARENT_ID column.
  6. Open the dbo.SVI_SC_BASE_DISK_KEYS table and delete the entire row where dbo.SVI_SIM_CLONE ID is referenced under the PARENT_ID column.
  7. If the linked clone was in the process of being deployed when a problem occurred, there may be additional references to the clone left in the dbo.SVI_TASK_STATE and dbo.SVI_REQUEST tables:

    1. Open the dbo.SVI_TASK_STATE table and find the row where dbo.SVI_SIM_CLONE ID is referenced under the SIM_CLONE_ID column. Note the REQUEST_ID in that row.
    2. Open the dbo.SVI_REQUEST table and delete the entire row where dbo.SVI_TASK_STATE REQUEST_ID is referenced.
    3. Delete the entire row from the dbo.SVI_TASK_STATE table.

  8. In the dbo.SVI_SIM_CLONE table, delete the entire row where the virtual machine is referenced.

Removing the virtual machine from Active Directory

To remove the virtual machine from Active Directory:
  1. Log into the Domain Controller as Administrator.
  2. Navigate to Start > Administrative Tools > Active Directory Users and Computers.
  3. Remove the virtual machine from Computers.

    Note: The virtual machine may not be in the Computers OU (Organizational Unit). It may be in a different OU.

Deleting the virtual machine from vCenter Server

To delete the virtual machine from vCenter Server:
  1. Log into vCenter Server using the vSphere Client.
  2. Right-click the linked clone virtual machine and click Power > Power Off.
  3. Right-click the linked clone virtual machine and click Delete from Disk.

Additional Information

For more information about ADSI Edit, see the Microsoft TechNet ADSI Edit page.

Note: The preceding link was correct as of February 28, 2014. If you find the link is broken, provide feedback and a VMware employee will update the link.
 
Note: For help on removing physical machines from ADAM, see Removing stale physical machine entries from the ADAM database in View Manager (2036601).

Tags

view-composer view-pool-delete view-pool-delete-fails

See Also

This Article Replaces

1013635, 1019249, 1013395

Update History

11/02/2011 - Added substeps to locate the GUID of the virtual machine 03/07/2011 - Separated the process for View 3.x and 4.0.x from View 4.5 and later. 07/19/2012 - Added a note to say if KB 2015112 does not resolve the issue for View 4.5 and later, then follow this KB and also updated Product Versions 08/17/2012 - Added 5.0.x and 5.1.x to Product Versions 09/20/2012 - Created a section for removing VM from AD 10/04/2012 - Added link to 2036601 in Additional Information section 04/28/2013 - Added 5.2 to Product Versions

Request a Product Feature

To request a new product feature or to provide feedback on a VMware product, please visit the Request a Product Feature page.

Feedback

  • 130 Ratings

Did this article help you?
This article resolved my issue.
This article did not resolve my issue.
This article helped but additional information was required to resolve my issue.
What can we do to improve this information? (4000 or fewer characters)
  • 130 Ratings
Actions
KB: