---
title: Unable to set password – The object does not exist (NO_OBJECT)
slug: unable-to-set-password-the-object-does-not-exist-noobject
docTags: 
createdAt: 2026-02-09T21:47:52.942Z
---

This article explains a scenario where a password set or reset fails even though the user exists in Active Directory.

## Symptoms

A password set or reset action fails with an error similar to:

:::BlockQuote
Unable to Set Password: \<domain>\\\<username>
The object does not exist.
0000208D: NameErr: DSID-0310028C, problem 2001 (NO\_OBJECT), data 0
best match of: 'DC=...'
:::

This can occur during:

- User creation workflows&#x20;
- Password reset requests&#x20;
- Privileged account password resets&#x20;

The user account exists in Active Directory at the time of the failure.

## Root cause

The issue is caused by password-related flags on the user object, most commonly:

- **User must change password at next logon** (pwdLastSet = 0)&#x20;

When this flag is set, Active Directory may reject LDAP password modify operations and return a misleading **NO\_OBJECT** error, even though the user object is valid and resolvable.

This is expected Active Directory behaviour and is not specific to Activate.

## Why the error is misleading

Active Directory successfully resolves the user’s distinguished name, which is reflected in the “best match of” value in the error.

The failure occurs during the extended password modify operation, not during object lookup. Active Directory surfaces this failure as problem 2001 (NO\_OBJECT), which incorrectly implies that the object does not exist.

## Common scenarios

This issue is most commonly seen when:

- A password is set immediately after user creation&#x20;
- A privileged account password is reset&#x20;
- A workflow sets **User must change password at next logon** and then attempts to set or reset the password in the same sequence&#x20;

## How to confirm

On the affected user account, check whether:

- **User must change password at next logon** is enabled&#x20;
- pwdLastSet is set to 0&#x20;

If either condition is true at the time of the password operation, this issue is expected.

## Resolution

Update the workflow sequencing so that one of the following approaches is used:

- Set the password **before** enabling **User must change password at next logon**&#x20;
- Temporarily clear the flag before resetting the password, then reapply it afterwards&#x20;

Once the flag is cleared, the password operation completes successfully.

If the workflow is orchestrated through Activate Orchestrator, ensure that password operations and password flag updates are handled as separate, correctly ordered steps.

## Not caused by

This issue is not caused by:

- An incorrect OU&#x20;
- The user not being created&#x20;
- Insufficient permissions&#x20;
- Password complexity requirements&#x20;
- Directory replication delays in typical environments&#x20;

## Summary

The user object exists and can be resolved by Active Directory. The failure is caused by the state of password-related flags at the time of the password operation. Although the error message is misleading, it is expected behaviour. Correct sequencing resolves the issue permanently.