| Previous | Next |
| ERROR_DS_OID_MAPPED_GROUP_CANT_HAVE_MEMBERS | ERROR_DS_DRA_RECYCLED_TARGET |
ERROR_DS_OID_NOT_FOUND
The dotted identifier must resolve in the directory context that uses it
ERROR_DS_OID_NOT_FOUND indicates that Active Directory could not find the requested object identifier. OIDs identify schema classes, attributes, syntaxes, matching rules, controls, and some directory mappings. A syntactically valid dotted string is not sufficient: the identifier must be allocated, unique, and present in the relevant schema or configuration object on the contacted domain controller.
Record which request field carried the OID, then search the schema naming context for matching attributeID and governsID values and inspect any feature-specific mapping objects. Verify schema replication before concluding that the definition is absent forest-wide. Do not replace an unknown OID with a similar Microsoft OID or invent a branch; obtain an identifier from an authority you control and deploy its definition consistently. For LDAP controls, also compare the OID with the server’s rootDSE supportedControl list.
OID resolution evidence
- Exact dotted OID and request field containing it.
- Schema or configuration partition searched.
- Definition visible on each relevant domain controller.
- Issuing authority and extension package that owns the OID.
References
- Microsoft: OIDs in Active Directory
- Microsoft: formal forest schema definitions
- IETF RFC 4512: OIDs in the LDAP schema model
Looking for a different code? Search another status or error code.