| Previous | Next |
| ERROR_DS_INVALID_SEARCH_FLAG_SUBTREE | ERROR_DS_HIERARCHY_TABLE_TOO_DEEP |
ERROR_DS_INVALID_SEARCH_FLAG_TUPLE
Tuple indexing is limited to Unicode string attributes
Active Directory uses bits in searchFlags to request particular indexing behavior. MS-ADTS requires the tuple-index flag to be used only with attributes whose syntax is String(Unicode). A binary, numeric, DN, or otherwise incompatible syntax cannot use that index mode, so the attribute schema update is rejected.
Examine the actual Active Directory syntax tuple as well as the search flag. If substring-style search is needed, confirm that the application data is appropriately modeled as a Unicode string and that the chosen index behavior is justified. Changing a binary or structured identifier into text simply to enable tuple indexing can alter matching, storage, and client expectations.
What to inspect
- Decode
searchFlagsand identify the tuple-index bit. - Verify the attribute maps to Active Directory String(Unicode) syntax.
- Remove the unsupported index request or redesign the attribute with a data type appropriate to the application.
References
- Microsoft: searchFlags attribute
- MS-ADTS: schema consistency checks
- Microsoft: attributeSchema class
Looking for a different code? Search another status or error code.