| Previous | Next |
| ERROR_INVALID_ACCOUNT_NAME | ERROR_NO_SUCH_USER |
ERROR_USER_EXISTS
User creation collided with an existing account object
NetUserAdd and SAMR user-creation operations create a new user object in a selected security database. ERROR_USER_EXISTS means the create path reached an authority in which the requested user name is already occupied. It is not evidence that the existing account has the expected SID, profile, flags, or ownership for the application that attempted provisioning.
Before treating the operation as idempotent, query the existing user and compare stable identity and required attributes. Automation should not delete and recreate the account merely to clear a name collision: a recreated account receives a different security identifier and existing ACL entries can continue to reference the old SID. If the same logical user was expected, update the existing object through a set operation rather than repeating create.
What to inspect
- Query the existing user in the same server or domain that handled the create request.
- Compare SID/RID and account attributes with the provisioning record.
- Choose explicitly between adopt, update, rename, or fail; do not auto-delete the colliding user.
References
Looking for a different code? Search another status or error code.