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

Creating or recomposing a pool fails with error: Invalid value for parameter dgid passed to view composer function (1000541)

  • 15 Ratings


  • You are unable to create a new pool.
  • You are unable to add more desktops to an existing pool.
  • You are unable to recompose an existing pool.
  • Attempting to configure the pool fails with the error:

    invalid value for parameter dgid passed to view composer function

  • The connection server logs contain entries similar to:

    <YYYY-MM-DD> <TIME>,106 ERROR TP-Processor1 [SecuritySettingsBean] View Composer error: Invalid value for parameter dgId passed to View Composer function, Error type: com.vmware.SviService.InvalidParameterFault, Details: null


This issue occurs if the pool settings are not pointing to an existing snapshot of the parent machine, or if the value of Deployment_Group_ID in the SVI_SIM_CLONE table in the View Composer database differs from the value of pae-SVIVmDeploymentGroup in the View Connection Server ADAM database.


To resolve this issue, ensure that the pool settings in the View Admin page is pointing to an existing snapshot of the parent virtual machine and attempt to create/recompose the Pool/virtual machine.

If this fails again, verify that the ODBC connection for the vCenter Server is pointing to the correct database, and set the value of the two tables to the same number.

To verify the ODBC connection and set the table values:

  1. Log in to the vCenter Server where View Composer is installed.
  2. Click Start > Administrative Tools > Data Sources (ODBC).
  3. Click the System DSN tab.
  4. Verify the properties of the View Composer Database.
  5. Log in to the View Connection Server.
  6. Connect to the ADAM instance. For more information, see Connecting to the View ADAM Database (2012377).
  7. Navigate to the OU=Server Groups folder.
  8. Double-click the entry for the affected pool.
  9. Select the pae-SVIVmDeploymentGroup entry.
  10. Open the View Composer database.
  11. Open the SVI_SIM_CLONE table.
  12. Note the Deployment_Group_ID value for a View desktop in the affected pool.
  13. Verify that the Deployment Group ID found in the Deployment_Group_ID column corresponds to that in the ADAM database.
  14. If the ID is not the same, change it to the value in the Composer database.
  15. Click the entry pae-SVIVmDeploymentGroupsInUse and verify that it contains the Deployment Group ID entered in pae-SVIVmDeploymentGroup.

Note: This issue may also occur if the Composer database is corrupted or does not contain any data. To resolve this issue, restore the Composer database from a backup. For more information, see Performing an end-to-end backup and restore for View Manager (1008046).

Additional Information

Note: After changing the deploymentid value in ADAM database, you may see the parent vm not found error while accessing the pool. To resolve this issue, go to the pool settings and reassign the parent virtual machine and its associated snapshot to the pool.

See Also

Update History

10/21/2011 - Updated resolution steps. 03/01/2012 - Added note that this issue may also occur if the Composer database is empty 01/18/2013 - Added new information to Symptoms, Cause, and Resolution sections regarding parent snapshot in pool settings; added product versions 06/18/2103 - Added Note to the Additional Information section. 05/21/2014 - Added Horizon View 5.2 and 5.3 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.


  • 15 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.
  • 15 Ratings