| Previous | Next |
| ERROR_DS_NO_SERVER_OBJECT | ERROR_DS_NON_ASQ_SEARCH |
ERROR_DS_NO_NTDSA_OBJECT
Replication topology cannot identify the DC without its NTDS Settings object
In Active Directory, an nTDSDSA object in the configuration naming context represents a domain controller in the forest. The familiar “NTDS Settings” object under a server in Active Directory Sites and Services is therefore replication metadata, not a cosmetic console item. Replication topology and role-owner references use that DSA identity.
If the object is absent, the directory cannot treat the server as a normal replication participant. This can follow failed promotion, forced demotion, accidental metadata deletion, or inconsistent configuration-NC replication. Recreating a server object with the same display name is not equivalent to restoring the original DSA identity and GUID relationships.
What to inspect
- Check the DC’s server object and NTDS Settings object in Sites and Services from more than one healthy DC.
- Inspect configuration-NC replication and promotion/demotion events to determine whether the metadata should exist.
- For a permanently removed DC, complete metadata cleanup. For a live DC with broken promotion state, use supported AD DS recovery rather than hand-creating nTDSDSA objects.
References
- MS-ADTS nTDSDSA definition
- Microsoft DC metadata cleanup
- AD replication troubleshooting
- Samba AD DSA/partition model
Looking for a different code? Search another status or error code.