question

razzzz avatar image
0 Votes"
razzzz asked razzzz answered

Prblems with DC Replication

Hello,

Please guys if you have time and knowledge, since i can't figure it by myself.

I have a tree domain, with 3 pain DC's , 2 of them also have DNS roles.
Since a few weeks ago I lost the sync between them and my dcdiag is full of problems.
Since the forest is very big (over 100 domains) all this becomes a very big mess in witch I am lost.

So I have 1 and 5 as DNS and 4 as DC

10.242.0.1 - primary dns
10.242.0.5 - 2nd DNS

10.242.0.4 - DC

Following the DCDIAG from main DC

 Directory Server Diagnosis
    
 Performing initial setup:
    Trying to find home server...
    Home Server = s4
    * Identified AD Forest.
    Done gathering initial info.
    
 Doing initial required tests
    
    Testing server: ***\S4
       Starting test: Connectivity
          ......................... S4 passed test Connectivity
    
 Doing primary tests
    
    Testing server: ***\S4
       Starting test: Advertising
          Warning: S4 is not advertising as a time server.
          ......................... S4 failed test Advertising
       Starting test: FrsEvent
          There are warning or error events within the last 24 hours after the
          SYSVOL has been shared.  Failing SYSVOL replication problems may cause
          Group Policy problems.
          ......................... S4 passed test FrsEvent
       Starting test: DFSREvent
          ......................... S4 passed test DFSREvent
       Starting test: SysVolCheck
          ......................... S4 passed test SysVolCheck
       Starting test: KccEvent
          A warning event occurred.  EventID: 0x80000786
             Time Generated: 04/16/2021   23:04:27
             Event String:
             The attempt to establish a replication link to a read-only directory
  partition with the following parameters failed.
          A warning event occurred.  EventID: 0x80000786
             Time Generated: 04/16/2021   23:04:27
             Event String:
             The attempt to establish a replication link to a read-only directory
  partition with the following parameters failed.
          A warning event occurred.  EventID: 0x80000786
             Time Generated: 04/16/2021   23:04:27
             Event String:
             The attempt to establish a replication link to a read-only directory
  partition with the following parameters failed.
          A warning event occurred.  EventID: 0x80000786
             Time Generated: 04/16/2021   23:04:27
             Event String:
             The attempt to establish a replication link to a read-only directory
  partition with the following parameters failed.
          A warning event occurred.  EventID: 0x80000786
             Time Generated: 04/16/2021   23:04:27
             Event String:
             The attempt to establish a replication link to a read-only directory
  partition with the following parameters failed.
          A warning event occurred.  EventID: 0x80000786
             Time Generated: 04/16/2021   23:04:27
             Event String:
             The attempt to establish a replication link to a read-only directory
  partition with the following parameters failed.
          A warning event occurred.  EventID: 0x80000786
             Time Generated: 04/16/2021   23:04:27
             Event String:
             The attempt to establish a replication link to a read-only directory
  partition with the following parameters failed.
          A warning event occurred.  EventID: 0x80000786
             Time Generated: 04/16/2021   23:04:27
             Event String:
             The attempt to establish a replication link to a read-only directory
  partition with the following parameters failed.
          A warning event occurred.  EventID: 0x80000786
             Time Generated: 04/16/2021   23:04:27
             Event String:
             The attempt to establish a replication link to a read-only directory
  partition with the following parameters failed.
          A warning event occurred.  EventID: 0x80000786
             Time Generated: 04/16/2021   23:04:27
             Event String:
             The attempt to establish a replication link to a read-only directory
  partition with the following parameters failed.
          A warning event occurred.  EventID: 0x80000786
             Time Generated: 04/16/2021   23:04:27
             Event String:
             The attempt to establish a replication link to a read-only directory
  partition with the following parameters failed.
          A warning event occurred.  EventID: 0x80000786
             Time Generated: 04/16/2021   23:04:27
             Event String:
             The attempt to establish a replication link to a read-only directory
  partition with the following parameters failed.
          A warning event occurred.  EventID: 0x80000786
             Time Generated: 04/16/2021   23:04:27
             Event String:
             The attempt to establish a replication link to a read-only directory
  partition with the following parameters failed.
          A warning event occurred.  EventID: 0x80000786
             Time Generated: 04/16/2021   23:04:27
             Event String:
             The attempt to establish a replication link to a read-only directory
  partition with the following parameters failed.
          A warning event occurred.  EventID: 0x80000786
             Time Generated: 04/16/2021   23:04:27
             Event String:
             The attempt to establish a replication link to a read-only directory
  partition with the following parameters failed.
          A warning event occurred.  EventID: 0x80000786
             Time Generated: 04/16/2021   23:04:27
             Event String:
             The attempt to establish a replication link to a read-only directory
  partition with the following parameters failed.
          A warning event occurred.  EventID: 0x80000786
             Time Generated: 04/16/2021   23:04:27
             Event String:
             The attempt to establish a replication link to a read-only directory
  partition with the following parameters failed.
          A warning event occurred.  EventID: 0x80000786
             Time Generated: 04/16/2021   23:04:27
             Event String:
             The attempt to establish a replication link to a read-only directory
  partition with the following parameters failed.
          A warning event occurred.  EventID: 0x80000786
             Time Generated: 04/16/2021   23:04:27
             Event String:
             The attempt to establish a replication link to a read-only directory
  partition with the following parameters failed.
          A warning event occurred.  EventID: 0x80000786
             Time Generated: 04/16/2021   23:04:27
             Event String:
             The attempt to establish a replication link to a read-only directory
  partition with the following parameters failed.
          A warning event occurred.  EventID: 0x80000786
             Time Generated: 04/16/2021   23:04:27
             Event String:
             The attempt to establish a replication link to a read-only directory
  partition with the following parameters failed.
          A warning event occurred.  EventID: 0x80000786
             Time Generated: 04/16/2021   23:04:27
             Event String:
             The attempt to establish a replication link to a read-only directory
  partition with the following parameters failed.
          A warning event occurred.  EventID: 0x80000786
             Time Generated: 04/16/2021   23:04:27
             Event String:
             The attempt to establish a replication link to a read-only directory
  partition with the following parameters failed.
          A warning event occurred.  EventID: 0x80000786
             Time Generated: 04/16/2021   23:04:27
             Event String:
             The attempt to establish a replication link to a read-only directory
  partition with the following parameters failed.
          A warning event occurred.  EventID: 0x80000786
             Time Generated: 04/16/2021   23:04:27
             Event String:
             The attempt to establish a replication link to a read-only directory
  partition with the following parameters failed.
          A warning event occurred.  EventID: 0x80000786
             Time Generated: 04/16/2021   23:04:27
             Event String:
             The attempt to establish a replication link to a read-only directory
  partition with the following parameters failed.
          A warning event occurred.  EventID: 0x80000786
             Time Generated: 04/16/2021   23:04:27
             Event String:
             The attempt to establish a replication link to a read-only directory
  partition with the following parameters failed.
          A warning event occurred.  EventID: 0x80000786
             Time Generated: 04/16/2021   23:04:27
             Event String:
             The attempt to establish a replication link to a read-only directory
  partition with the following parameters failed.
          A warning event occurred.  EventID: 0x80000786
             Time Generated: 04/16/2021   23:04:27
             Event String:
             The attempt to establish a replication link to a read-only directory
  partition with the following parameters failed.
          A warning event occurred.  EventID: 0x80000786
             Time Generated: 04/16/2021   23:04:27
             Event String:
             The attempt to establish a replication link to a read-only directory
  partition with the following parameters failed.
          A warning event occurred.  EventID: 0x80000786
             Time Generated: 04/16/2021   23:04:27
             Event String:
             The attempt to establish a replication link to a read-only directory
  partition with the following parameters failed.
          An error event occurred.  EventID: 0xC000060E
             Time Generated: 04/16/2021   23:04:28
             Event String:
             The following site has no NTDS Site Settings child object.
          An error event occurred.  EventID: 0xC00007C4
             Time Generated: 04/16/2021   23:05:25
             Event String:
             Active Directory Domain Services Replication encountered the existen
 ce of objects in the following partition that have been deleted from the local d
 omain controllers (DCs) Active Directory Domain Services database.  Not all dire
 ct or transitive replication partners replicated in the deletion before the tomb
 stone lifetime number of days passed.  Objects that have been deleted and garbag
 e collected from an Active Directory Domain Services partition but still exist i
 n the writable partitions of other DCs in the same domain, or read-only partitio
 ns of global catalog servers in other domains in the forest are known as "linger
 ing objects".
          A warning event occurred.  EventID: 0x8000051C
             Time Generated: 04/16/2021   23:07:09
             Event String:
             The Knowledge Consistency Checker (KCC) has detected that successive
  attempts to replicate with the following directory service has consistently fai
 led.
          A warning event occurred.  EventID: 0x8000051C
             Time Generated: 04/16/2021   23:07:09
             Event String:
             The Knowledge Consistency Checker (KCC) has detected that successive
  attempts to replicate with the following directory service has consistently fai
 led.
          A warning event occurred.  EventID: 0x80000785
             Time Generated: 04/16/2021   23:07:09
             Event String:
             The attempt to establish a replication link for the following writab
 le directory partition failed.
          A warning event occurred.  EventID: 0x80000785
             Time Generated: 04/16/2021   23:07:09
             Event String:
             The attempt to establish a replication link for the following writab
 le directory partition failed.
          A warning event occurred.  EventID: 0x80000786
             Time Generated: 04/16/2021   23:07:09
             Event String:
             The attempt to establish a replication link to a read-only directory
  partition with the following parameters failed.
          A warning event occurred.  EventID: 0x80000785
             Time Generated: 04/16/2021   23:07:09
             Event String:
             The attempt to establish a replication link for the following writab
 le directory partition failed.
          A warning event occurred.  EventID: 0x80000786
             Time Generated: 04/16/2021   23:07:09
             Event String:
             The attempt to establish a replication link to a read-only directory
  partition with the following parameters failed.
          A warning event occurred.  EventID: 0x80000786
             Time Generated: 04/16/2021   23:07:09
    
    
    
             Event String:
             The attempt to establish a replication link to a read-only directory
  partition with the following parameters failed.
          ......................... S4 failed test KccEvent
       Starting test: KnowsOfRoleHolders
          ......................... S4 passed test KnowsOfRoleHolders
       Starting test: MachineAccount
          ......................... S4 passed test MachineAccount
       Starting test: NCSecDesc
          ......................... S4 passed test NCSecDesc
       Starting test: NetLogons
          [S4] User credentials does not have permission to perform this
          operation.
          The account used for this test must have network logon privileges
          for this machine's domain.
          ......................... S4 failed test NetLogons
       Starting test: ObjectsReplicated
          ......................... S4 passed test ObjectsReplicated
       Starting test: Replications
          [Replications Check,S4] A recent replication attempt failed:
             From S1 to S4
             Naming Context: DC=xxxxx,DC=ro
             The replication generated an error (8606):
             Insufficient attributes were given to create an object. This object
 may not exist because it may have been deleted and already garbage collected.
    
             The failure occurred at 2021-04-16 22:58:01.
             The last success occurred at 2020-12-28 16:59:32.
             28728 failures have occurred since the last success.
          [Replications Check,S4] A recent replication attempt failed:
             From S5 to S4
             Naming Context: DC=xxxxx,DC=ro
             The replication generated an error (8606):
             Insufficient attributes were given to create an object. This object
 may not exist because it may have been deleted and already garbage collected.
    
             The failure occurred at 2021-04-16 23:06:18.
             The last success occurred at 2020-12-28 17:00:05.
             116520 failures have occurred since the last success.
          ......................... S4 failed test Replications
       Starting test: RidManager
          ......................... S4 passed test RidManager
       Starting test: Services
             Could not open NTDS Service on S4, error 0x5 "Access is denied."
             w32time Service is stopped on [S4]
          ......................... S4 failed test Services
       Starting test: SystemLog
          ......................... S4 failed test SystemLog
       Starting test: VerifyReferences
          ......................... S4 passed test VerifyReferences
    
    
    Running partition tests on : DomainDnsZones
       Starting test: CheckSDRefDom
          ......................... DomainDnsZones passed test CheckSDRefDom
       Starting test: CrossRefValidation
          ......................... DomainDnsZones passed test
          CrossRefValidation
    
    Running partition tests on : ForestDnsZones
       Starting test: CheckSDRefDom
          ......................... ForestDnsZones passed test CheckSDRefDom
       Starting test: CrossRefValidation
          ......................... ForestDnsZones passed test
          CrossRefValidation
    
    Running partition tests on : Schema
       Starting test: CheckSDRefDom
          ......................... Schema passed test CheckSDRefDom
       Starting test: CrossRefValidation
          ......................... Schema passed test CrossRefValidation
    
    Running partition tests on : Configuration
       Starting test: CheckSDRefDom
          ......................... Configuration passed test CheckSDRefDom
       Starting test: CrossRefValidation
          ......................... Configuration passed test CrossRefValidation
    
    Running partition tests on : xxxxx
       Starting test: CheckSDRefDom
          ......................... xxxx passed test CheckSDRefDom
       Starting test: CrossRefValidation
          ......................... xxxxx passed test CrossRefValidation
    
    Running enterprise tests on : xxxxxxx
       Starting test: LocatorCheck
          ......................... xxxxxxx passed test LocatorCheck
       Starting test: Intersite
          ......................... xxxxx passed test Intersite

Thanks again !

windows-active-directory
· 1
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

As this is question is related to an on-premises/local Active Directory and not Azure AD Service I modified the tag.


Kind regards
Andreas Baumgarten

0 Votes 0 ·
DaisyZhou-MSFT avatar image
0 Votes"
DaisyZhou-MSFT answered DaisyZhou-MSFT edited

Hello @razzzz,

Thank you for your update.

I am sorry for the late reply.

From the following error message, it seems there are lingering objects on S4 or S5.

DsReplicaSync() failed with status 8606 (0x219e):
Insufficient attributes were given to create an object. This object may not
exist because it may have been deleted and already garbage collected.

We can check whether it is such case.


Tip: After two DC replicates forcely, we can check on S4 or S5, if there is event ID 1988 on any DC, the DC with event ID 1988 is DC without lingering objects.


For example: if you can see event ID 1988 on S4, then S5 has lingering objects.
91588-lol3.png


Check if there is any lingering object via LOL tool


1.Download the tool on S4 or S5.

Lingering Object Liquidator (LoL)
https://www.microsoft.com/en-us/download/details.aspx?id=56051

2.Open the tool and select one partition and source DC (such as s4) and target DC (such as s5).
Detect AD topology
Select partition
Select source DC
Select target DC
Detect lingering objects

91587-lol1.png


Then if there are indeed lingering objects, do you still want to keep these lingering objects?

If you still want the lingering objects and want to replicate to the other DC.

Action Plan:
1.Set the following two registry entries on DC without lingering objects.

Value Path: HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\NTDS\Parameters
Value Name: Allow Replication With Divergent and Corrupt Partner
Value Type: REG_DWORD
Value Data: 1
Allow Replication With Divergent and Corrupt Partner=1 means the allow the replication even though the replication interval has exceeded the tombstone lifetime.

Value Path: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NTDS\Parameters
Value Name: Strict Replication Consistency
Value Type: REG_DWORDA
Value Data: 0
Strict Replication Consistency=0 means that allow replication of outdated Active Directory objects.

2.Restart the DC without lingering objects.

3.For S4 and S5 replicates immediately to see if everything is OK.


If you do not want the lingering objects, you can delete them via tool button above.

91464-lol2.png

After that, check AD replication between S4 and S5 again.


Hope the information above is helpful.

Should you have any question or concern, please feel free to let us know.


Reference
Active Directory replication Event ID 1388 or 1988: A lingering object is detected
https://docs.microsoft.com/en-us/troubleshoot/windows-server/identity/active-directory-replication-event-id-1388-1988



Best Regards,
Daisy Zhou


============================================
If the Answer is helpful, please click "Accept Answer" and upvote it.



lol3.png (16.8 KiB)
lol1.png (69.5 KiB)
lol2.png (10.2 KiB)
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

DSPatrick avatar image
0 Votes"
DSPatrick answered

The event logs should have more details but it looks like the "S4" server may have tombstoned. If that's the case the solution is to demote, reboot, promo it again.

--please don't forget to Accept as answer if the reply is helpful--





5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

razzzz avatar image
0 Votes"
razzzz answered

Thank you for your quick answer.
I did a snapshot (all 3 dc's are vms ...) and loggend on local adm account and proceed to demote the DC...
UnBIGfortunatelly I wasn't abe to demote it since I got an "unknown" error.
This case is so frustrating since I spend a lot of time searching and debugging error codes, this domain si old, very f# old. 15 years old.
I strongly think it's doomed and it can't be resuscitated no more.
A new one is kinda impossible to set up right now. So the whole damn situation is ....
Truth is I got tired ....

Made it here just to "check" every aspect of debugging and trying to fix this ...

5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

razzzz avatar image
0 Votes"
razzzz answered razzzz edited

Worth mentioning that after I did a Lingering Object deletion (deleted over 150 objects)
and stop Kerberos Key Distribution Center service I managed to manually sync from S1 to S5 and from S1 to S4 and back-ways....

But this is far from a solution

Thanks for all you reading and coming up with an idea or 2 :)

5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

DSPatrick avatar image
0 Votes"
DSPatrick answered

wasn't abe to demote it since I got an "unknown" error

Then the simpler solution may be to remove it from network, perform clean up.
https://docs.microsoft.com/en-us/windows-server/identity/ad-ds/deploy/ad-ds-metadata-cleanup

Then rebuild it.

--please don't forget to Accept as answer if the reply is helpful--









5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

DaisyZhou-MSFT avatar image
0 Votes"
DaisyZhou-MSFT answered DaisyZhou-MSFT edited

Hello @razzzz,

Thank you for posting here.

Based on the description above, as I understand you want to try to fix the AD replication between the following three DCs in the tree domain.

10.242.0.1 - primary DNS
10.242.0.5 - 2nd DNS
10.242.0.4 - DC

1.Please check if netlogon folder and sysvol folder on the three DCs are shared.
Run net share on every DC to check.

2.Are the three DCs all writable DCs?

3.We can run command repadmin /showrepl * /csv >c:\repsum.csv on one DC to get the replication status and replication topology of the entire forest (it includes the three DCs in this tree domain).

4.You can check AD replication between two of the three DCs manually.

For example:

S1 and S4
S1 and S5
S4 and S5

Command to check AD replication between domain partition.
repadmin /replicate sourceDC targetDC "DC=domain,DC=com"
Or
repadmin /replicate targetDC sourceDC "DC=domain,DC=com"

Command to check AD replication between configuration partition.
repadmin /replicate sourceDC targetDC "CN=Configuration,DC=domain,DC=com"
Or
repadmin /replicate targetDC sourceDC "CN=Configuration,DC=domain,DC=com"


Command to check AD replication between schema partition.
repadmin /replicate sourceDC targetDC "CN=Schema,CN=Configuration,DC=domain,DC=com"
Or
repadmin /replicate targetDC sourceDC "CN=Schema,CN=Configuration,DC=domain,DC=com"


Command to check AD replication between application partition.
repadmin /replicate sourceDC targetDC "DC=DomainDnsZones,DC=domain,DC=com"
Or
repadmin /replicate targetDC sourceDC "DC=DomainDnsZones,DC=domain,DC=com"

repadmin /replicate sourceDC targetDC "DC=ForestDnsZones,DC=domain,DC=com"
Or
repadmin /replicate targetDC sourceDC "DC=ForestDnsZones,DC=domain,DC=com"


if any error occurs after any command, we can troubleshoot based on the error message or error code.

Also, check if there is any error in Directory Service log in Event Viewer\Applications and services Logs.
88899-ev.png


Should you have any question or concern, please feel free to let us know.



Best Regards,
Daisy Zhou





ev.png (14.0 KiB)
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

razzzz avatar image
0 Votes"
razzzz answered DaisyZhou-MSFT commented

1st thanks for this elaborate answer.

  1. yes netlogon and sysvol are shared - i can see my domain there

  2. there's a problem after running the cmd:


C:\Windows\system32>repadmin /showrepl * /csv >c:\repsum.csv
LDAP error 49 (Invalid Credentials) Win32 Err 1326.
LDAP error 49 (Invalid Credentials) Win32 Err 1326.
LDAP error 49 (Invalid Credentials) Win32 Err 1326.
LDAP error 49 (Invalid Credentials) Win32 Err 1326.
LDAP error 49 (Invalid Credentials) Win32 Err 1326.
LDAP error 49 (Invalid Credentials) Win32 Err 1326.
LDAP error 49 (Invalid Credentials) Win32 Err 1326.
LDAP error 49 (Invalid Credentials) Win32 Err 1326.
LDAP error 49 (Invalid Credentials) Win32 Err 1326.
LDAP error 49 (Invalid Credentials) Win32 Err 1326.
LDAP error 49 (Invalid Credentials) Win32 Err 1326.
LDAP error 81 (Server Down) Win32 Err 58.
LDAP error 49 (Invalid Credentials) Win32 Err 1326.
LDAP error 49 (Invalid Credentials) Win32 Err 1326.
LDAP error 49 (Invalid Credentials) Win32 Err 1326.
LDAP error 49 (Invalid Credentials) Win32 Err 1326.
LDAP error 49 (Invalid Credentials) Win32 Err 1326.
LDAP error 49 (Invalid Credentials) Win32 Err 1326.
LDAP error 49 (Invalid Credentials) Win32 Err 1326.
LDAP error 49 (Invalid Credentials) Win32 Err 1326.
LDAP error 82 (Local Error) Win32 Err 8341.

and this goes on ...

What credentials is it referring to ?

I run the cmd from main DC S4.

Again thank you !


· 1
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Hello @razzzz,

Thank you for your update.

It seems you cannot check AD replication in the entire AD forest.

Then you can check DC replication in your tree domain (three DCs).


Check if DC replication between s1,s4 and s5 is OK?




Best Regards,
Daisy Zhou

0 Votes 0 ·
razzzz avatar image
0 Votes"
razzzz answered razzzz edited

Well it's odd...

Between S1 , S5 and S4 sync works ... sometimes

After I did this:

repadmin /options xxx +disable_outbound_repl
repadmin /options xxx -disable_outbound_repl

repadmin /options xxxx +disable_inbound_repl
repadmin /options xxxx -disable_inbound_repl

I see things synced

But now, if i check manually the replication I've got:

The target principal name is incorrect...

I can't stand anymore with all these DC's..

Thank you very much !


5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

DaisyZhou-MSFT avatar image
0 Votes"
DaisyZhou-MSFT answered

Hello @razzzz,

Thank you for your update.

I found I have the same error in my lab yesterday.

89779-tar1.png


From: vchzho720vm (PDC)
To: vchzho0280vm (BDC)

Then I run Netdom resetpwd /s:target_server /ud:mydomain\domain_admin /pd:* on PDC, after the command run successfully, I force vchzho720vm (PDC) and vchzho0280vm (BDC) to replicate, then the error message "The target principal name is incorrect" disappears.

For example:

89834-tar2.png


89893-tar4.png


You can try to reset DC machine password to see if it helps.


Best Regards,
Daisy Zhou





tar1.png (34.3 KiB)
tar2.png (4.8 KiB)
tar4.png (176.3 KiB)
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

razzzz avatar image
0 Votes"
razzzz answered DaisyZhou-MSFT commented

Hello @DaisyZhou-MSFT

Thank's a lot for your answer.
A new step was done.
It looks like after I've reset dc5 pass sync passed through.
S4 and S1 was ok so no need to reset.

But now, a "new" error emerged :)

SyncAll reported the following errors:
Error issuing replication: 8451 (0x2103):
The replication operation encountered a database error.

2 times same error after repadmin /syncall /AdeP

Thank you !

· 1
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Hello @razzzz,

Thank you for your update.

The following error message occurs between which two DCs?

SyncAll reported the following errors:
Error issuing replication: 8451 (0x2103):
The replication operation encountered a database error.

Best Regards,
Daisy Zhou

0 Votes 0 ·