Horizon 7.3.2 Connection Servers not replicating. Last success @ 2018-11-02 10:29:14

[UCL]

Hello.

vdiconn01 refuses to replicate with vdiconn02.

On vdiconn01 I get:

"

C:\Windows\system32>repadmin.exe /replicate vdiconn01:389 vdiconn02.:389 dc=vdi,dc=vmware,dc=int

DsReplicaSync() failed with status 8456 (0x2108):

    The source server is currently rejecting replication requests.

"

and in the reverse direction I get the same. Also for vdiconn02 in both directions

I got this from a repadmin.exe /showrepl localhost:389 run on vdiconn01

"

Source: Default-First-Site-Name\VDICONN02$VMwareVDMDS

******* 6059 CONSECUTIVE FAILURES since 2018-11-02 10:41:31

Last error: 8451 (0x2103):

            The replication operation encountered a database error.

"

Also last backup on vdiconn02 is 2018-11-01 and vdiconn01 is 2018-11-21 as shown on the Connection Servers tab.

Looks to me like vdiconn02 is so far behind in replications that vdiconn01 refuses to communicate with vdiconn02.

Now what?

Follow this one: VMware Knowledge Base  (including this VMware Knowledge Base ) or what ?

Best Regards

Peter Rasch Lageri

Denmark

[HussamRabaya]

if i would face the same issue , i would go to implement new replica VM rather than troubleshooting it

[UCL]

Hello HussamRabaya.

I think this is a replication issue between two Connection Servers in Horizon View.

The question is whether I can uninstall/install on vdiconn02 as per VMware Knowledge Base  or if I have to do both Connection Servers.

I'm not sure how a replica VM fits into this or do you mean a new Connection Server like a vdiconn03 ?

/Peter

[BenFB]

First follow the steps in Restart order of the View environment to clear ADLDS (ADAM) synchronization in Horizon View (2068381... to see if that resolved the replication issue.

If not I would follow the resolution in Replicating VMware Horizon View Connection server fails with the error: Insufficient attributes were... on vdiconn02 to completely remove it. Then perform a fresh install of the same version of Horizon Connection Server on vdiconn02 and make it a replica of vdiconn01.

[UCL · Accepted solution]

We ended up following this one. It works again.

VMware Knowledge Base