Symptoms
  • During the creation of an automated pool, the folder is created and the path exists in VMware vCenter Server, but you see this error is indicating that the path does not exist:

    Error during provisioning: Unable to find folder
     
  • The View Connection Server Log contains entries similar to:

    <YYYY-MM-DD> <time>,412 WARN <propagate-98630fe0-0bbc-4b41-9ae5-4447b4f14c71> [VirtualCenterDriver] Could not determine naming suffix for VMs in pool Pool-Name, reason: Unable to find folder /FOLDERNAME/vm/Discovered Virtual Machine/VM-NAME
    <YYYY-MM-DD> <time></time>,412 DEBUG <propagate-98630fe0-0bbc-4b41-9ae5-4447b4f14c71> [VirtualCenterDriver] com.vmware.vdi.vcsupport.VmException: Unable to find fol
    der /FOLDERNAME/vm/Discovered Virtual Machine/VM-NAME com.vmware.vdi.desktopcontroller.VirtualCenterDriver.b(SourceFile:1238)
    com.vmware.vdi.vcsupport.VmException: Unable to find folder /FOLDERNAME/vm/Discovered Virtual Machine/VM-NAME
    at com.vmware.vdi.desktopcontroller.VirtualCenterDriver.b(SourceFile:999)
    at com.vmware.vdi.desktopcontroller.VirtualCenterDriver.a(SourceFile:945)
    at com.vmware.vdi.desktopcontroller.VirtualCenterDriver.b(SourceFile:1223)
    at com.vmware.vdi.desktopcontroller.VirtualCenterDriver.l(SourceFile:1138)
    at com.vmware.vdi.desktopcontroller.a.run(SourceFile:636)
    <YYYY-MM-DD> <time></time>,412 DEBUG <propagate-98630fe0-0bbc-4b41-9ae5-4447b4f14c71> [EventLogger] Info_Event:[BROKER_PROVISIONING_ERROR_CONFIG_SET] "Provisioning
    error occurred on Pool POOL-NAME because of a configuration problem": Source=com.vmware.vdi.desktoptracker.PoolInformation, DesktopId=VM-NAME, Time
    =Wed Nov 24 12:58:21 EST 2010, Severity=ERROR, Node=ConnectionServer-NAME, Module=Broker, Acknowledged=true
    <YYYY-MM-DD> <time></time>,412 ERROR <propagate-98630fe0-0bbc-4b41-9ae5-4447b4f14c71> [PoolInformation] Pool control for desktop VM-NAME is disabling provisioning due to a clone error - Unable to find folder /FOLDERNAME/vm/Discovered Virtual Machine/VM-NAME
    <YYYY-MM-DD> <time></time>,412 DEBUG <propagate-98630fe0-0bbc-4b41-9ae5-4447b4f14c71> [PoolInformation] Exception for clone error: com.vmware.vdi.desktoptracker.Poo
    lInformation.onCloneError(SourceFile:1221)
    com.vmware.vdi.vcsupport.VmException: Unable to find folder /FOLDERNAME/vm/Discovered Virtual Machine/VM-NAME
    at com.vmware.vdi.desktopcontroller.VirtualCenterDriver.b(SourceFile:999)
    at com.vmware.vdi.desktopcontroller.VirtualCenterDriver.a(SourceFile:945)
    at com.vmware.vdi.desktopcontroller.VirtualCenterDriver.b(SourceFile:1223)
    at com.vmware.vdi.desktopcontroller.VirtualCenterDriver.l(SourceFile:1138)
    at com.vmware.vdi.desktopcontroller.a.run(SourceFile:636)</time>

    Note: For more information on the location of the View log files, see Location of VMware View log files (1027744).

  • On the Inventory tab of the View Administrator page, the Desktop's Status column shows a status of Unknown (missing), Connected (missing) or Provisioned (missing).


    Note: The preceding log excerpts are only examples. Date, time, and environmental variables may vary depending on your environment.




     
 Cause
The Connection Manager looks through cached folder to determine a new virtual machine's name. The updating thread of this cache might be fully or partially blocked in the old server session. The Horizon View server's vCenter Server cache thread is blocked and does not sync its cache with the View Connection Server. As a result, the View Connection Server is not able to see any new folders added to vCenter Server.
 Resolution
To work around this issue, reboot the vCenter Server and View Connection server. After a reboot, the original blocking condition is gone and the cache is updated to include the folder information.
 
Note: Make sure the path to the folder of the pool exists on the vCenter Server virtual machines and Templates view. If it does not, create it. If it exists somewhere else in the vCenter Server folder structure, drag the folder to the correct location as shown in the pool settings of the Horizon View admin page and restart the Horizon View connection broker service.