Desktop Composer Error:VMware.Sim.Fault.AdAuthenticationFault

This particular error occurred when I was migrating my vCenter / vComposer server to new hardware.  There were 2 successive errors that would appear in View Manager that look something as follows:

  • Pool ::Unable to remove from inventory VM /DataCenter/vm/VDIFolderName/VMName - Failed to cleanup linked clone /DDTC/vm/VDIFolderName/
  • Desktop Composer Error:; Error Type:com.vmware.SviService.AdAuthenticationFault;Error FaultActor:null; Error code:{}Server.generalException; Error details:[Lorg.w3c.dom.Element;@1fc1ee1

Essentially the system was complaining that the vComposer account that is specified under Configuration -> Server -> vCenter Servers was not part of the local administrator group (Windows side, not vCenter) of the vCenter server.  This was one part of the issue, the other half were the QuickPrep accounts, the accounts specified need to have AD rights to create/modify/delete computer accounts.  If it is not able to, this error may occur as well.  In my case, the accounts were locked out.  I unlocked them, then re-entered the passwords for each quickprep account specified.

The Username specified here, must be part of the Windows local administrator group of the vCenter/vComposer server.

The Username(s) specified here, must have AD computer modify/delete/add rights.

VMWare View (Desktop Composer Fault: Virtual Machine with input specifications already exists)


This error is caused when View Composer has some kind of hiccup and ‘thinks’ it deployed a desktop and can’t get over the fact that it failed.  There are 3 event entries that will usually show up right next to each other:

  • Desktop Composer Error:VMware.Sim.Fault.InvalidParameterFaultParam: cSpec Detail: AlreadyExist; Error Type:com.vmware.SviService.InvalidParameterFau
  • Desktop Composer Fault: Virtual Machine with input specifications already exists
  • PendingOperation-Path/that/has/been/defined/VMName


  • View 4.0.1
  • SQL 2005


I found this SQL script on the vmware communities board after I went through the manual hell of finding each related key.  Essentially, you need to delete all related SQL entries so View Composer can move on to start deploying VM’s again.  This script makes this job a WHOLE lot easier.

   1: DECLARE @vmdelete varchar(20);
   2: set @vmdelete = 'FAILED_VM_NAME';
   3: delete from SVI_VM_NAME where NAME = @vmdelete
   4: delete from SVI_COMPUTER_NAME where NAME = @vmdelete
   5: delete from SVI_TASK_STATE where SIM_CLONE_ID = (SELECT ID FROM SVI_SIM_CLONE WHERE (VM_NAME = @vmdelete))
   7: delete from SVI_SC_PDISK_INFO where PARENT_ID = (SELECT ID FROM SVI_SIM_CLONE WHERE (VM_NAME = @vmdelete))
   8: delete FROM SVI_SIM_CLONE WHERE (VM_NAME = @vmdelete)