Launching soon: The world's first vendor agnostic bug scrubLearn more & join waitlist
OPERATIONAL DEFECT DATABASE
...
...
Important: We recommend you migrate from Horizon 7 to Horizon 8 as soon as possible. Horizon 8 offers numerous improvements in performance, scale, and experience for both Administrators and end users. Please see Ensuring a successful migration from Horizon 7 to Horizon 8 (89840) for additional advice. After upgrading VMware View: Recompose or refresh operation on pools created in the earlier version fails.You are able to perform a recompose or refresh operation on any new pools created.Recompose operations fail with one of these errors: VMware.Sim.Fault.InvalidOperationFault, NonCompatibleDeploymentGroupFailed to authenticate to VC
This issue may occur if there are multiple VC_CONFIG_ID values in the VMware View Composer database pointing to the same vSphere Server.
Editing the Deployment Group setting to use the correct VC_CONFIG_ID resolves this issue. The correct VC_CONFIG_ID is the one associated with the new pools created after the upgrade. To edit the Deployment Group setting:Note: Backup the VMware View Composer database and stop the View Composer service before making any changes. Open the VMware View Composer Database using Microsoft SQL Server Management Studio.Right-click dbo.SVI_VC_CONFIG_ENTRY and click Open Table.There should be multiple rows in this table. Make note of the ID and SERVICE_ENDPOINT entries.Determine which rows are used for the pre-upgrade pools and which are used by new pools. Right-click dbo.SVI_SIM_CLONE and click Open Table.From column VM_NAME determine the DEPLOYMENT_GROUP_IDfor the old and new pools. Note: Alternatively, you can run this script if you have a large number of VM_NAME entries: /* This SQL script will assist in searching for the DEPLOYMENT_GROUP_IDin a Composer Database */ /* Replace view_composer with the actual View Composer database name below */ USE view_composer SELECT * from dbo.SVI_SIM_CLONE WHERE VM_NAME = 'vm-name' Right-click dbo.SVI_DEPLOYMENT_GROUP and click Open Table.Locate the DEPLOYMENT_GROUP_ID for old pools from step 4 in the ID column of the dbo.SVI_DEPLOYMENT_GROUP table. Note: Alternatively, you can run this script if you have a large number of DEPLOYMENT_GROUP_IDentries: /* This SQL script will assist in searching the VC_CONFIG_ID used for the VM in the Composer Database */ /* Replace view_composer with the actual View Composer database name below */ USE view_composer /* Replace 'ffaa62618-8cff-b2f0-e965a2c34c29' with the actual DEPLOYMENT_GROUP_IDfrom Query in step 4 */ SELECT * from dbo.SVI_DEPLOYMENT_GROUP WHERE ID ='ffaa62618-8cff-b2f0-e965a2c34c29' For each row with a match, verify that the VC_CONFIG_ID is pointing to the old value of VC_CONFIG_ID.Change the value of the VC_CONFIG_ID from the pre-upgrade value to the correct VC_CONFIG_ID value. Note: Alternatively, to update VC_CONFIG_ID, run this SQL script: USE view_composer UPDATE dbo.SVI_DEPLOYMENT_GROUP SET VC_CONFIG_ID = 'correct_id' WHERE VC_CONFIG_ID = 'incorrect_id' Close Microsoft SQL Server Management Studio.Recompose pools. Note: In SQL 2008, there is no Open Table option. When using SQL 2008, use the Edit Top 200 Rows option. To view more than 200 entries, click Tools > Options > SQL Server Object Explorer and change the value for Edit Top <n> Rows command. Setting the value to 0 displays all rows.
If you have not composed any new pools after the upgrade, you can find the current VC_CONFIG_ID in the ADAM database. To locate the VC_CONFIG_ID: Perform steps 1-7 in Configuring the View Composer Domain fails with the error: The database has been reinitialized or is corrupt .Copy the value of pae-SVIVCId. This value corresponds to the VC_CONFIG_ID value in the Composer database. Configuring the View Composer Domain fails with the error: The database has been reinitialized or is corruptVMware View のアップグレード後、リンク クローン プールの再構成と更新に失敗する在升级 VMware View 后重组或刷新链接克隆池失败