About this article: This article is reviewed against the cited sources. This is source research, not lab validation. Check the stated versions and your own requirements before making changes.
Error 8453 (0x2105), "Replication access was denied", means the security context doing the replicating lacks a replication right. That context is either a domain controller (DC) running scheduled replication, or a person who started replication by hand with Replicate Now or repadmin.
The first job is to work out which of those it is, and on which directory partition. Microsoft lists several causes: a DC account with wrong flags, missing default or custom permissions on a partition, a person with no replication rights, a person whose group membership is stripped by User Account Control, a read-only DC (RODC) without the right group permission, and a missing object in a Lightweight Directory Services instance. Each has a different fix, and the fixes for error 5 do not apply.
What the error means
Microsoft's page says error 8453 "has multiple root causes", with two primary ones: "The destination domain controller doesn't have the required permissions to replicate the naming context/partition" and "The administrator who manually started replication doesn't have permissions to do so." For the second, the page adds: "This condition doesn't affect periodic or scheduled replication."
Permissions sit at the top of each directory partition (the naming context head) and are inherited down. DCs in a forest replicate using their own account's security context. A person who triggers replication uses their own, so a person without the right can fail while every DC is fine.
The page is for supported versions of Windows Server and was last dated 2026-02-12. It warns that "the steps for error 5 or error 8453 ... won't resolve replication failures on computers that are currently failing replication and generating the other error message." Error 5 ("Access is denied") has its own causes: time skew, UDP Kerberos fragmentation, missing "Access this computer from network" rights, broken secure channels, and a CrashOnAuditFail value of 2.
Likely causes
| Cause | What you see | How to confirm |
|---|---|---|
| RODC lacks permission on a partition | Scheduled replication to an RODC fails with 8453 for a partition it does not replicate | Enterprise Read-Only Domain Controllers has no Replicating Directory Changes on that partition's head; ADPREP /RODCPREP may not have been run |
| DC account flags wrong | dcdiag /test:MachineAccount fails |
userAccountControl lacks SERVER_TRUST_ACCOUNT or TRUSTED_FOR_DELEGATION |
| Default permissions missing on a partition | dcdiag /test:NCSecDesc lists missing rights for Enterprise Domain Controllers or Domain Controllers |
dsacls on the partition head |
| Person has no replication right | Only manual replication fails; scheduled replication works | The person is not in a group holding the right |
| UAC split token | Works from an elevated prompt, fails from a normal one | whoami /all differs between elevated and non-elevated |
| Missing NTDS Settings in an LDS instance | 8453 for a Lightweight Directory Services (LDS) instance | The NTDS Settings object is absent from the configuration container |
Prove the cause before changing anything
All of these read only. Run them on the destination DC that logs the error, then on the source DC.
repadmin /showrepl
repadmin /replsum
dcdiag /test:Replications
dcdiag /test:NCSecDesc
dcdiag /test:MachineAccount
dcdiag /test:CheckSecurityError
Microsoft's page lists REPADMIN /SHOWREPS, /SHOWREPL, /REPLSUM and /SYNCALL among the commands that report 8453. Find the line Last attempt @ <date> <time> failed, result 8453 (0x2105): Replication access was denied. and note the partition (for example DC=contoso,DC=com), the source DC and the consecutive failure count.
dcdiag /test:Replications prints "The replication generated an error (8453)". dcdiag /test:NCSecDesc prints lines such as "Error NT AUTHORITY\ENTERPRISE DOMAIN CONTROLLERS doesn't have Replicating Directory Changes" for each missing right. Microsoft notes this test "may report false positive errors" in environments that mix system versions, so treat it as a pointer, not a verdict. dcdiag /test:MachineAccount reports when userAccountControl is missing the DC flags.
Check the events in the directory service log. Microsoft lists 1699, 2896, 1655, 1265 (NTDS KCC) and 1925 as ones that carry the 8453 status. Event 2896 reads, "A client made a DirSync LDAP request for a directory partition. Access was denied due to the following error." and suggests the client "should be assigned the control access right 'Replicating Directory Changes' on the directory partition in question."
Next, read the account flags. In ADSI Edit, open the DC's computer account and read userAccountControl. Microsoft gives typical values: a writable DC is 532480 (hex 0x82000, which is SERVER_TRUST_ACCOUNT 8192 plus TRUSTED_FOR_DELEGATION 524288), and an RODC is 83890176 (0x5001000). Values can vary, but a writable DC must contain both flags.
Read the permissions on the failing partition head:
dsacls dc=contoso,dc=com
dsacls \\dc02\dc=contoso,dc=com
The second form targets a remote DC. Look for the five rights Microsoft lists as required: Manage Replication Topology, Replicating Directory Changes, Replication Synchronization, Replicating Directory Changes All, and Replicating Changes in Filter Set. Also look for Deny entries, which can remove a right from groups the account belongs to.
For a person whose manual replication fails, sign in as that person and run whoami /all. Then run it again from an elevated Command Prompt. If the group lists differ, Microsoft says the User Account Control split token is removing the membership.
Fix
RODC: group permission. Microsoft's "top solution" is to grant Replicating Directory Changes to the forest root domain's Enterprise Read-only Domain Controllers group on each partition the RODC does not replicate. In ADSI Edit on a DC, connect to the default naming context, open Properties of the partition head, select the Security tab, select Add, enter the group name, and Check Names. The page says the Allow boxes for Read, Read domain password & lockout policies and Read Other domain parameters are selected automatically and should be cleared, then you select Allow beside Replicating Directory Changes. Microsoft notes the group exists only in the forest-root domain.
Disruptive step: this edits the access control list on a directory partition head, and Microsoft notes such permissions "are inherited throughout the partition tree." To back out, remove the added entry in the same Security tab, and record the original list first with dsacls. Microsoft also says to verify that ADPREP /RODCPREP has been run in domains that host RODCs.
DC account flags. For a missing TRUSTED_FOR_DELEGATION flag, Microsoft's route is Active Directory Users and Computers: open the DC account, the Delegation tab, and select the option that trusts the computer for delegation to any service (Kerberos only), which the page prints as "Trusted this computer for delegation to any service (Kerberos only)".
Disruptive step: this sets a security-sensitive delegation right on a computer account. Impact: any service running as that DC account can then impersonate a client to other services. Back-out: clear the same option, and record the account's earlier setting first.
For a missing SERVER_TRUST_ACCOUNT, the page's ADSI Edit procedure reads the decimal value, converts it, adds a hex amount and writes it back. That procedure tells you to add 0x80000, but Microsoft's table on the same page lists 0x80000 as TRUSTED_FOR_DELEGATION and SERVER_TRUST_ACCOUNT as 0x2000 (8192). Microsoft's separate UserAccountControl flags page agrees: SERVER_TRUST_ACCOUNT is 0x2000 (8192), TRUSTED_FOR_DELEGATION is 0x80000 (524288), WORKSTATION_TRUST_ACCOUNT is 0x1000 (4096), and a domain controller's default is 0x82000 (532480). For a missing SERVER_TRUST_ACCOUNT the amount to add is therefore 0x2000 (8192), not 0x80000.
Risk: a wrong userAccountControl value changes what kind of account the DC has. Compare the whole value, not only the missing bit, against 532480 for a writable DC (83890176 for an RODC): if the account already carries a different account-type flag, such as WORKSTATION_TRUST_ACCOUNT (0x1000), adding a bit leaves two account-type bits and the value will not match. Stop if the result disagrees with 532480. There is no way back other than writing the old decimal value back, so record it first.
Default permissions missing. Add the missing entries from the five-right list in ADSI Edit's ACL editor, for the groups dcdiag and dsacls named.
Disruptive step: this edits the access control list on a directory partition head, and the entries are inherited through the partition tree. Impact: a wrong or over-broad entry changes who may replicate or read directory changes across the whole partition. Back-out: remove the added entry in the same Security tab, using the dsacls output you recorded first.
Person lacks the right. By default, members of Enterprise Administrators can start replication between any DCs in the forest, and members of the built-in Administrators group can do so within the same domain. Microsoft says to either add the person to a group that already has the right or create your own group, grant it the five rights across the forest, and add the person. The page refers to KB303972 for the second route.
Risk: granting replication rights widens who can pull directory changes. Prefer an existing group, and remove the grant when the task is done.
UAC split token. Run the replication command from an elevated Command Prompt.
LDS instance. If the NTDS Settings object is missing, Microsoft says to uninstall the LDS instance on the affected servers and rerun the ADAM configuration wizard.
Risk: an LDS uninstall removes the instance's service, so a certificate configured for LDAPS must be configured again. There is no undo.
Example (illustrative): dc02, an RODC in child.contoso.com, logs 8453 for DC=contoso,DC=com. In ADSI Edit its userAccountControl is 83890176. Microsoft's table builds the typical RODC value from three flags, 4096 plus 16777216 plus 67108864, which sum to 83890176, so the account flags match and are not the cause. dsacls dc=contoso,dc=com on dc01 shows no entry for CONTOSO\Enterprise Read-Only Domain Controllers. The administrator records the list, adds the group with only Replicating Directory Changes set, and repeats repadmin /showrepl on dc02.
Confirm the fix
On the destination DC, run repadmin /showrepl and repadmin /replsum. The failing partition should show a new last success time and a failure count that has stopped rising. Run dcdiag /test:Replications and dcdiag /test:NCSecDesc again. For a person-triggered failure, repeat the same command that failed, from an elevated prompt if the cause was the split token.
What to watch afterwards
- Events 1699, 2896, 1265 and 1925 in the directory service log on the destination DC.
- Changes to the ACL of partition heads. Record who may edit them and when.
- Removal of Domain Administrators or Enterprise Administrators from the built-in Administrators group. Microsoft says this has caused ad-hoc replication failures.
- Every new RODC: confirm the group permission before its first sync.
Read next
Related articles you may want next.
- TroubleshootingAD replication error 1722 "The RPC server is unavailable": find the layer that is really failingActive Directory replication fails with 1722 (0x6ba). Prove whether name resolution, a blocked port, signing or the network is at fault, fix that layer and confirm replication has caught up.Read article
- TroubleshootingReplication error -2146893022 "The target principal name is incorrect": DC password and name mismatchDomain controllers stop replicating with -2146893022 (0x80090322). Find out whether a stale machine password, a bad DNS or hosts entry or a duplicate SPN is the cause, and apply the matching fix.Read article
- TroubleshootingEvent 1311: the KCC cannot build a replication path between sitesNTDS KCC event 1311 says there is not enough connectivity to build a spanning tree between sites. Work out whether the site design or the infrastructure is at fault, prove it with repadmin, and fix it in the right order.Read article
Risks and limits
These commands have not been run or lab-tested. The 8453 page's step for a missing SERVER_TRUST_ACCOUNT flag does not match its own value table, as noted above, and its sample dcdiag output carries a 2010 timestamp. Output formats and ACL names can differ in your version of Windows Server. The page does not give a way to undo a changed userAccountControl value or ACL; keep a written copy of both before you edit. If the cause is not one of those on the page, error 5 may be the real fault and needs its own checks.
Sources
- Active Directory replication error 8453: Replication access was denied — Microsoft Learn, page dated 2026-02-12, accessed 18 November 2026
- UserAccountControl property flags — Microsoft Learn, page dated 2026-02-12, accessed 18 November 2026
This article was originally published on .