Name of desktop duplicated with composer

[MauroBonder]

Hi all,

I´ve a problem, when i try increase a number of maximum in my pool, when this pool start new provisioning i receive error because composer created a virtual machine with name duplicated.

Error "view composer fault: virtual machine with input specification already exist"

I´m using view 5.0.

Any tip ?

Thanks

[mittim12]

Check in Active Directory and see if there is already an entry for the machine it's attempting to create. 

[MauroBonder]

I check and after delete this duplicated VM, the composer recreate same virtual machine duplicated again, but now completed with success and put in AD normally, but removing old virtual machine that aldreay in vcenter previous of this recreate.

[MauroBonder]

Mittim,

I get some logs. and i found follow informations about one desktop that had problem to deploy.

15:28:07,476 INFO  <propagate-c8b02d6d-ae08-4471-ad50-8d3bb14b765e> [PendingOperation] Pool control for desktop desktopsibm is provisioning VM DesktopIBM11
15:28:15,092 ERROR <TP-Processor64> [SecuritySettingsBean] ADAM data error

15:28:16,000 INFO  <PendingOperation-/Cap/vm/Discovered virtual machine/DesktopsIBM/DesktopIBM11> [PendingOperation] Pool desktopsibm:: Datastore(s) selected for new clone:  /Cap/host/Desktops/CAP_VD_004 (system disks) and /Cap/host/Desktops/CAP_VD_004(user data disk)
15:28:20,183 ERROR <TP-Processor47> [SecuritySettingsBean] ADAM data erro

15:28:20,183 ERROR <TP-Processor47> [SecuritySettingsBean] ADAM data error
15:28:28,287 ERROR <TP-Processor26> [SecuritySettingsBean] ADAM data error
15:28:35,099 INFO  <PendingOperation-/Cap/vm/Discovered virtual machine/DesktopsIBM/DesktopIBM12> [PendingOperation] Created new Linked Clone VM /Cap/vm/Discovered virtual machine/DesktopsIBM/DesktopIBM12 (Clone Id: 048bfc87-570c-4bac-af01-16cf7a8a3a1d) successfully
15:28:50,144 INFO  <PendingOperation-/Cap/vm/Discovered virtual machine/DesktopsIBM/DesktopIBM11> [PendingOperation] Created new Linked Clone VM /Cap/vm/Discovered virtual machine/DesktopsIBM/DesktopIBM11 (Clone Id: e8fb0343-72e5-4796-bb66-ba5c67b8686d) successfully
15:28:50,471 INFO  <PendingOperation-/Cap/vm/Discovered virtual machine/DesktopsIBM/DesktopIBM12> [PendingOperation] Pool desktopsibm::Configured VM /Cap/vm/Discovered virtual machine/DesktopsIBM/DesktopIBM12 with extraConfig successfully

15:33:19,927 INFO  <propagate-c8b02d6d-ae08-4471-ad50-8d3bb14b765e> [PendingOperation] Pool control for desktop desktopsibm is refitting VM DesktopIBM11
15:33:26,876 ERROR <Outbound JMS Worker Thread> [j] Problem sending JMS message, message not sent: javax.jms.JMSException: com.swiftmq.swiftlet.queue.QueueHandlerClosedException: queue handler is closed! com.vmware.vdi.ice.server.j.run(SourceFile:114)
javax.jms.JMSException: com.swiftmq.swiftlet.queue.QueueHandlerClosedException: queue handler is closed!
    at com.swiftmq.jms.ExceptionConverter.convert(Unknown Source)
    at com.swiftmq.jms.v750.MessageProducerImpl.processSend(Unknown Source)
    at com.swiftmq.jms.v750.MessageProducerImpl.send(Unknown Source)
    at com.swiftmq.jms.v750.TopicPublisherImpl.publish(Unknown Source)
    at com.vmware.vdi.ice.server.au.a(SourceFile:253)
    at com.vmware.vdi.ice.server.au.b(SourceFile:277)
    at com.vmware.vdi.ice.server.j.run(SourceFile:99)
    at java.lang.Thread.run(Thread.java:619)
15:33:32,582 INFO  <DesktopControlJMS> [Audit] SHUTDOWN:Server:cn=70412b2a-34af-47a1-8113-5d730f1d5f7e,ou=servers,dc=vdi,dc=vmware,dc=int;Pool:cn=desktopsibm,ou=server groups,dc=vdi,dc=vmware,dc=int;DNS:DESKTOPIBM11.prod.cap;IP:172.20.4.118;
15:33:59,267 INFO  <PendingOperation-vm-2004> [VmInformation] Snapshot created for VM DesktopIBM11
15:34:09,240 INFO  <propagate-c8b02d6d-ae08-4471-ad50-8d3bb14b765e> [PendingOperation] Pool control for desktop desktopsibm is starting VM DesktopIBM11
15:34:42,350 INFO  <DesktopControlJMS> [Audit] DISCONNECTED:Server:cn=f0002d3b-578a-488d-98ec-4022678cf7db,ou=servers,dc=vdi,dc=vmware,dc=int;Pool:cn=tsibm01,ou=server

[MauroBonder]

I open a SR....

waiting response.....

thanks

[millski]

Look at KB Article: 1008658 on kb.vmware.com

In the past I have had to cleanup some desktops and used this kb successfully.  Looking at the logs, the error resides in the ADAM database, and needs to be cleaned up.