Details
When you initialize the Cloud Pod Architecture feature, View sets up the Global Data Layer on each View Connection Server instance in the pod federation. View Connection Server instances in a pod federation use the Global Data Layer to share key data. Each View Connection Server instance in a pod federation runs a second LDAP instance to store this shared data.
When you install View Connection Server, the installer checks for LDAP inconsistencies. The installer returns this error if the Cloud Pod Architecture feature is not enabled but the global LDAP instance exists, or if the Cloud Pod Architecture feature is enabled but the global LDAP instance does not exist:
Installation cannot continue. An instance of Directory Services for View Connection Server already exists on this system, and contains inconsistent data regarding the Multi-Datacenter View feature. Please refer to the View Installation Guide for details on how to proceed with installation.
Solution
Multiple View Connection Server Instances
If there are other View Connection Server instances in the same pod and they are functioning correctly, uninstall the local and global LDAP instances and install View Connection Server as a replica.This solution replicates the functioning local and global LDAP instances from the other View Connection Server instances and brings the new View Connection Server instance up-to-date.
Cloud Pod Architecture Recovery Options are outlined here :
Recovery scenarios for Horizon 7 environment (70906)
Single View Connection Server Instance
If the system on which you are installing View Connection Server is the only View Connection Server instance in the pod and you no longer need the Global Data Layer, perform these steps and then retry the View Connection Server installation:
Uninstall the global LDAP instance.If necessary, disable the Cloud Pod Architecture feature by modifying the pae-LinkedModeEnabled flags in the local LDAP instance. Note: For information about connecting to the View ADAM database, see Connecting to the View ADAM Database (2012377).
Use ADSI Edit to connect to localhost:389 with DN dc=vdi,dc=vmware,dc=int.Check the pae-LinkedModeEnabled attribute on these RDNs: cn=common,ou=global,ou=lmv,ou=properties cn=<each-connection-server>,ou=server,ou=lmv,ou=properties For each RDN, set the attribute value to 0.
If the pod is still part of a federation, eject the pod from the pod federation. For more information, see the Administering View Cloud Pod Architecture Guide.