| Previous | Next |
| ERROR_DS_CONSTRUCTED_ATT_MOD | ERROR_DS_DRA_REPL_PENDING |
ERROR_DS_WRONG_OM_OBJ_CLASS
The three syntax fields form one Active Directory type declaration
ERROR_DS_WRONG_OM_OBJ_CLASS reports an inconsistent custom attribute syntax. Active Directory identifies an attribute type using attributeSyntax, oMSyntax, and, for specific object syntaxes, oMObjectClass. When oMSyntax is 127, the object-class byte sequence is required and must correspond to the selected syntax mapping.
Compare the complete triplet with a documented built-in attribute that uses the intended syntax; do not copy only the OID or only the integer syntax code. Preserve the exact binary representation of oMObjectClass in LDIF, including its encoding and length. A mismatch can make clients disagree about whether values are DNs, binary blobs, security descriptors, or other structured data. Correct the schema extension before any production import, because changing the syntax of an attribute after values exist is restricted and can make persisted values uninterpretable.
Syntax fields that must agree
- attributeSyntax OID.
- Numeric oMSyntax value.
- Binary oMObjectClass value when required.
- Reference built-in attribute using the same syntax.
References
- Microsoft: selecting attributeSyntax, oMSyntax, and oMObjectClass
- MS-ADTS: LDAP syntax mappings
- Microsoft: formal attributeSchema characteristics
Looking for a different code? Search another status or error code.