Search the VMware Knowledge Base (KB)
View by Article ID

Unable to save pool settings or create new pools in VMware View (2082413)

  • 8 Ratings


  • You are unable to successfully apply pool settings.
  • Virtual machines may stall when deleting, provisioning, or customizing.
  • When creating a new pool, the folder is created in vCenter Server but no other tasks occur.
  • Connection server dashboards show different information on different connection servers.
  • The Connection server Administrator dashboard shows a red error status for vCenter Server and/or Composer certificates. When viewing the certificates, they cannot be accepted.


If you are experiencing this issue, perform these steps. Do not reboot your Connection Servers except when requested by VMware Technical Support representative, or in step 9 as required.
  1. Before proceeding with these steps, gather a log bundle from each Connection Server in your View environment. For more information on gathering Horizon View logs, see Collecting VMware Horizon View logs and diagnostic information (1017939).
  2. Verify that all Connection Servers are correctly configured with 10 GB RAM and 4 vCPU.

    For more information, see:

  3. Verify that all Connection Servers in the View Pod experiencing trouble are fully functional and replicating all information correctly.

    Go to the local web console of each Connection Server in the View Pod and verify that all displayed information is consistent across all of the Connection Servers.

    Note: There may be some small variations in the numbers shown for desktops in particular states as the monitoring intervals for the connection servers can be different. If any of the servers are in a red state or their local web consoles cannot be reached, see these articles:

  4. Verify that you do not have vCenter Operations Manager for Horizon View Broker Agent version 1.5 installed in your View environment. Note that only one instance of the V4V Broker Agent is installed on one Connection Server. This requires checking of all Connection Servers in the View Pod if you are not sure which Connection Server is running the V4V Broker Agent. This prevents View Administrator commands from running properly in vCenter Server.

    For more information, see View Administrator commands do not run in vCenter Server when the V4H Broker Agent is installed (2090736).

  5. Verify that the vCenter Server is working properly and communicating with View.

    For more information, see:

  6. Ensure that the vCenter Server and its sub-components (vSphere SSO, vSphere Web Client, etc.) meet the necessary hardware requirements for the environment.

    For more information, see Installing vCenter Server 5.5 best practices (2052334).

  7. If the issue is not resolved, file a support request with VMware Technical Support and note this Knowledge base article ID (2082413) in the problem description. For more information on filing a Support Request, see Filing a Support Request in My VMware (2006985). Ensure to provide the log bundles that you collected in step 1 with your request.
  8. After reviewing the impacts and risks listed, determine a time or maintenance windows where it is possible to stop Horizon View services.

    On each connection server stop the services providing the View brokering functionality by performing these steps:

    1. Under the Windows start menu, select Administrative Tools > Services. Locate the VMware Horizon View Connection Server service.
    2. Select Stop. You see that other Horizon View services stop on this server. Do no proceed until you see that the service stops.

      Repeat this for remaining brokers. Do not attempt to restart any service until all the Horizon View services have been stopped on all brokers.

    3. Return to the original broker, locate the VMware Horizon View Connection Server service and select Start.

      Repeat this for remaining brokers and wait for confirmation that the service has started.

    4. Monitor vCenter Server tasks to confirm that View tasks are processing normally. Note that this may take a few minutes after restarting the services. If process has resumed do not proceed to step 9.

  9. Perform this step only if, after completing Step 8, the processing did not resume as expected. If possible, do not reboot your environment until you contact VMware Technical Support to enable additional data collection, if required.

    VMware recommends to speak with technical support prior to rebooting your servers, however, if you choose to perform the reboot without talking to VMware Technical Support:

    1. Shut down all View Connection Servers at the same time.

      Note: The Connection Servers must be shut down, not restarted.

    2. After shutting down the Connection Servers, Power on all Connection Servers:

      • For View 5.2 and later, VMware recommends to do rolling restarts with intervals of no more than 30 to 60 seconds between servers. If the servers are not restarted at short intervals startup delays can occur on the Connection Servers.
      • For View 5.1.x and earlier, the Connection Servers can be restarted with larger intervals but this is not recommended.

    3. Monitor vCenter Server tasks to confirm that View tasks are processing normally.


Stopping the Horizon View Services or powering off all View Connection Servers may cause disconnected sessions, and no new users can connect until the services have been restored. You may arrange a maintenance window to complete this operation.


composer unknown internal pools

See Also

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.


  • 8 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)

Please enter the Captcha code before clicking Submit.
  • 8 Ratings