| Previous | Next |
| ERROR_DS_NAME_ERROR_NOT_UNIQUE | ERROR_DS_NAME_ERROR_DOMAIN_ONLY |
ERROR_DS_NAME_ERROR_NO_MAPPING
ERROR_DS_NAME_ERROR_NO_MAPPING is more specific than a failed lookup: the input name was resolved to an object, but Active Directory could not obtain the associated representation requested by the caller. The DS_NAME_ERROR contract notes that this can occur when the object lacks attributes required for the desired output format.
Read it as an output-contract failure
First establish which formatDesired was requested. A conversion to a UPN, service principal name, canonical form, or another directory representation is not just a formatting operation; it may depend on attributes or directory metadata that are absent, unsuitable, or not represented by one usable value.
Targeted diagnosis
- Keep the resolved object identity and inspect the attributes that support the requested name form rather than re-searching the original token.
- Verify that the selected output type is meaningful for this object class. A service-style representation is not automatically available for a user object, and a user-style representation is not automatically available for every service object.
- Check whether the application really needs the requested representation or only a stable identity such as the DN or GUID.
- Do not classify this as
NOT_FOUND: the object was found. The missing piece is the conversion target.
A change to the object should be made only when that attribute is part of the intended identity model. Adding a value merely to satisfy a name conversion can create duplicate or misleading identities elsewhere in the directory.
Microsoft: DS_NAME_ERROR, including NO_MAPPING
Microsoft: input and output name formats
RFC 4512: attribute types, values, and directory naming
Looking for a different code? Search another status or error code.