| Previous | Next |
| ERROR_DS_CANT_FIND_DC_FOR_SRC_DOMAIN | ERROR_DS_SRC_SID_EXISTS_IN_FOREST |
ERROR_DS_SRC_OBJ_NOT_GROUP_OR_USER
SID-history migration supports only specific principal classes
The SID-history migration path expects a source user or group whose security identifier can be looked up, audited, and associated with a corresponding destination security principal. Directory containers, contacts, service configuration objects, and infrastructure classes do not satisfy that contract even if they have names resembling accounts.
Read the source object’s structural class and objectSid. Confirm that the migration tool resolved the intended object rather than a similarly named contact or container. Computer-account and specialized principal handling depends on the particular migration workflow; do not assume every object with an SID is accepted by the same API. Select a supported principal or use class-appropriate migration procedures.
What to inspect
- Inspect objectClass and objectSid on the source object.
- Resolve the source by GUID to avoid same-name ambiguity.
- Use the migration API only for its documented principal classes.
References
- Microsoft: supported DsAddSidHistory source principals
- MS-ADTS: user, group, and security-principal definitions
- Microsoft: Active Directory group objects
Looking for a different code? Search another status or error code.