Windows error 8399 (ERROR_DS_ATT_SCHEMA_REQ

Status / error code:		Category:

Constant name:
Source:	Operating System:
Description: The class schema lacks a readable governing OID.

Previous	Next
ERROR_DS_CANT_DELETE	ERROR_DS_BAD_ATT_SCHEMA_SYNTAX

ERROR_DS_ATT_SCHEMA_REQ_ID

A class schema record is missing its governing identity

ERROR_DS_ATT_SCHEMA_REQ_ID occurs while Active Directory is processing schema information and cannot obtain the governing class identifier. In AD DS, a classSchema object uses governsID as the class OID; it must be unique in the schema and is part of the information used to identify the class definition.

This is not a normal object-attribute validation error. Treat it as a schema-record or schema-cache problem: an incomplete class definition, a bad import, a replication inconsistency around the schema naming context, or an unsupported attempt to manipulate a protected schema field can all be more relevant than the application object that exposed the error.

What to inspect

Read the affected classSchema object from the schema naming context and verify its governsID, lDAPDisplayName, subClassOf, and object-class category.
Check that the OID is unique and belongs to the organization or product that introduced the extension; reusing another class or attribute OID creates an invalid identity model.
Verify schema-master health and schema replication before attempting a new import or a repair.
Keep recovery changes controlled. Schema additions are forest-wide and cannot simply be deleted once committed.

Why it differs from an undefined class

ERROR_DS_OBJ_CLASS_NOT_DEFINED means a client named a class that the directory cannot resolve. This code instead indicates trouble reading the identifying data of a schema record that should describe a class.

References

Looking for a different code? Search another status or error code.