# Provisioning Error: "Failed to update attribute AC\_NewName Error - There is no such object on the server." **URL:** \ **Category:** SHF Discussion and Questions\ **Tags:** sailpoint-identity-security, provisioning\ **Created:** [May 30, 2025, 7:44pm UTC](https://developer.sailpoint.com/discuss/t/provisioning-error-failed-to-update-attribute-ac-newname-error-there-is-no-such-object-on-the-server/139863 "2025-05-30T19:44:59Z")\ **Posts on this page:** 15\ **Page:** 1
**Author:** ![ynara](https://avatars.discourse-cdn.com/v4/letter/y/35a633/32.png) [@ynara](https://developer.sailpoint.com/discuss/u/ynara)\ **Post date:** [May 30, 2025, 7:44pm UTC](https://developer.sailpoint.com/discuss/t/provisioning-error-failed-to-update-attribute-ac-newname-error-there-is-no-such-object-on-the-server/139863/1 "2025-05-30T19:44:59Z")
Hi Avid SailPoint Developers! We’ve written a Before Provisioning Rule in IDN/ISC to update/ placeholder the AC\_NewName attribute in Active Directory during a name change scenario. However, we’re seeing this error in UI and IQService Logs: ![Screenshot 2025-05-30 141038](https://global.discourse-cdn.com/sailpoint/original/3X/1/9/19048a8f0ca01c802d95167e249daa8edbddd8ec.png) ![Screenshot 2025-05-30 155006](https://global.discourse-cdn.com/sailpoint/original/3X/c/4/c4ff175ef0e4a5f8e853e7da77271d5e467c7358.png) [“Failed to update attribute AC\_NewName Error - There is no such object on the server.\n”. Has anyone experienced this with custom AD attributes? Could this be to a stale DN or timing issue in the provisioning plan? Any insights or recommendations are appreciated - especially if you’ve dealt with similar scenarios involving custom attributes or object not found errors. Thanks in advance ---
**Author:** ![ManvithaNalabolu06](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/manvithanalabolu06/32/26315_2.png) [@ManvithaNalabolu06](https://developer.sailpoint.com/discuss/u/ManvithaNalabolu06)\ **Post date:** [May 31, 2025, 5:58am UTC](https://developer.sailpoint.com/discuss/t/provisioning-error-failed-to-update-attribute-ac-newname-error-there-is-no-such-object-on-the-server/139863/3 "2025-05-31T05:58:54Z")
If you’re changing the user’s name (which might change the DN) and trying to update `AC_NewName` in the same provisioning plan, the order of operations might be wrong — AD may not find the object under the old DN after the rename.. Ensure `AC_NewName` is properly extended in your AD schema and reflected in the IQService configuration (custom schema and allowed attributes for update). first process the rename (changing DN), and only after that succeeds, send a second provisioning call to update `AC_NewName`.Add logging inside your rule to output the DN being used and whether the object exists before performing the update. Let me know if it works ---
**Author:** ![hkhandale](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/hkhandale/32/23833_2.png) [@hkhandale](https://developer.sailpoint.com/discuss/u/hkhandale)\ **Post date:** [May 31, 2025, 9:08am UTC](https://developer.sailpoint.com/discuss/t/provisioning-error-failed-to-update-attribute-ac-newname-error-there-is-no-such-object-on-the-server/139863/4 "2025-05-31T09:08:49Z")
You can refer to the following resources detailed guidance on handling AD account moves and renames in SailPoint IdentityNow: [Best Practices: Active Directory Account Moves](https://community.sailpoint.com/t5/Identity-Security-Cloud-Wiki/Best-Practices-Active-Directory-Account-Moves/ta-p/189661) ---
**Author:** ![ynara](https://avatars.discourse-cdn.com/v4/letter/y/35a633/32.png) [@ynara](https://developer.sailpoint.com/discuss/u/ynara)\ **Post date:** [June 2, 2025, 3:44pm UTC](https://developer.sailpoint.com/discuss/t/provisioning-error-failed-to-update-attribute-ac-newname-error-there-is-no-such-object-on-the-server/139863/5 "2025-06-02T15:44:06Z")
Thank you for the reply. I double checked our provisioning plan and the order of operations. The provisioning plan is set up exactly the same way as you described here, including logging the rename and DN update. ---
**Author:** ![ynara](https://avatars.discourse-cdn.com/v4/letter/y/35a633/32.png) [@ynara](https://developer.sailpoint.com/discuss/u/ynara)\ **Post date:** [June 2, 2025, 4:02pm UTC](https://developer.sailpoint.com/discuss/t/provisioning-error-failed-to-update-attribute-ac-newname-error-there-is-no-such-object-on-the-server/139863/6 "2025-06-02T16:02:57Z")
Thank you for sharing the guidance! Unfortunately it doesn’t offer comprehensive resolution on how to fix various errors. Our provisioning plan was working fine at the implementation stage and we started getting above mentioned error few months ago. ---
**Author:** ![j\_place](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/j_place/32/19181_2.png) [@j\_place](https://developer.sailpoint.com/discuss/u/j_place)\ **Post date:** [June 2, 2025, 4:41pm UTC](https://developer.sailpoint.com/discuss/t/provisioning-error-failed-to-update-attribute-ac-newname-error-there-is-no-such-object-on-the-server/139863/7 "2025-06-02T16:41:44Z")
Hi @ynara can you confirm the New Parent is getting correctly mapped with a full OU path and that it exists? ---
**Author:** ![RAKGDS](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/rakgds/32/2795_2.png) [@RAKGDS](https://developer.sailpoint.com/discuss/u/RAKGDS)\ **Post date:** [June 2, 2025, 4:45pm UTC](https://developer.sailpoint.com/discuss/t/provisioning-error-failed-to-update-attribute-ac-newname-error-there-is-no-such-object-on-the-server/139863/8 "2025-06-02T16:45:18Z")
Hi Nara, The AC\_NewParent will contain the OU for the user where he will be moved. **AC\_NewParent -** This is the new parent OU where the account will reside Did you check the complete OU path for the new user is present in the target and you can manually move the user over there ? Thanks Rakesh Bhati ---
**Author:** ![ynara](https://avatars.discourse-cdn.com/v4/letter/y/35a633/32.png) [@ynara](https://developer.sailpoint.com/discuss/u/ynara)\ **Post date:** [June 2, 2025, 8:30pm UTC](https://developer.sailpoint.com/discuss/t/provisioning-error-failed-to-update-attribute-ac-newname-error-there-is-no-such-object-on-the-server/139863/9 "2025-06-02T20:30:13Z")
I understand but the user is changing only last name not a department. The before provisioning rule we have states if users last name or first name is changed it will look for attribute AC\_NewName. If users department is changed it will look for AC\_NewParent. In our specific case we are having issue with last name changes. ---
**Author:** ![RAKGDS](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/rakgds/32/2795_2.png) [@RAKGDS](https://developer.sailpoint.com/discuss/u/RAKGDS)\ **Post date:** [June 3, 2025, 5:07am UTC](https://developer.sailpoint.com/discuss/t/provisioning-error-failed-to-update-attribute-ac-newname-error-there-is-no-such-object-on-the-server/139863/10 "2025-06-03T05:07:26Z")
Hi Nara, AC\_NewParent and AC\_NewName are internal to IdentityNow. These are special attributes which helps the connector identify if the OU or CN. If you want to changed only the AC\_NewName you will also need to add AC\_NewParent. Is your requirement to only change AC\_NewName. If so can you try to also add AC\_NewParent with the same value you currently have and see if the issue gets resolved ? ---
**Author:** ![ynara](https://avatars.discourse-cdn.com/v4/letter/y/35a633/32.png) [@ynara](https://developer.sailpoint.com/discuss/u/ynara)\ **Post date:** [June 3, 2025, 4:49pm UTC](https://developer.sailpoint.com/discuss/t/provisioning-error-failed-to-update-attribute-ac-newname-error-there-is-no-such-object-on-the-server/139863/11 "2025-06-03T16:49:35Z")
Hi Rakesh, Yes, I’m aware of the both attributes. I’m confused in the part where we need to add AC\_NewParent? AC\_NewParent attribute is part of our before Provisioning plan as well. Below attached are screenshots of our provisioning plan. ![Screenshot 2025-06-03 114352](https://global.discourse-cdn.com/sailpoint/original/3X/9/3/93c9b463e301c923674c2425aa99be8e85c82c5a.png) ![Screenshot 2025-06-03 113612](https://global.discourse-cdn.com/sailpoint/original/3X/a/2/a2c5cfc16b0cfed342ea0ea8078ce4687364b771.png) ---
**Author:** ![GOKUL\_ANANTH\_M](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/gokul_ananth_m/32/14416_2.png) [@GOKUL\_ANANTH\_M](https://developer.sailpoint.com/discuss/u/GOKUL_ANANTH_M)\ **Post date:** [June 3, 2025, 5:34pm UTC](https://developer.sailpoint.com/discuss/t/provisioning-error-failed-to-update-attribute-ac-newname-error-there-is-no-such-object-on-the-server/139863/12 "2025-06-03T17:34:19Z")
Hi @ynara , Make sure you add **`AC_NewName`** to the `accountRequest` first, and then add `AC_NewParent` **after that** , to avoid the issue. ### **Why `AC_NewName` should be set before `AC_NewParent?`** Setting `AC_NewName` before `AC_NewParent` ensures that the object is renamed (CN change) **before** it is moved to a new OU. This sequence is important because: - **`AC_NewName` (CN)** changes the **Distinguished Name (DN)**. - **`AC_NewParent` (OU)** changes the **parent container** , altering the path (DN) where the object resides. If we reverse the order and set `AC_NewParent` first: - The system will **move the object using its old name (CN)**. - When it then tries to rename it (`AC_NewName`), it may **fail to find the object** at its original location, because it has already been moved. - As a result: - The **OU change will succeed**. - The **rename may fail** , depending on how the provisioning engine tracks object state post-move. Therefore, we set `AC_NewName` first to ensure: 1. The object is renamed in place (same OU). 2. Then safely moved to the new OU using the updated name. Thanks! ---
**Author:** ![ynara](https://avatars.discourse-cdn.com/v4/letter/y/35a633/32.png) [@ynara](https://developer.sailpoint.com/discuss/u/ynara)\ **Post date:** [June 3, 2025, 7:49pm UTC](https://developer.sailpoint.com/discuss/t/provisioning-error-failed-to-update-attribute-ac-newname-error-there-is-no-such-object-on-the-server/139863/13 "2025-06-03T19:49:07Z")
Hi @GOKUL_ANANTH_M thank you for the suggestion. I checked and yes, AC\_NewName is added to the accountRequest, but the order of operations is not as described here. I read your post as well. You had similar error AC\_NewName error a year ago. Have you fixed the error by reversing order of operations: first setting AC\_NewName and then AC\_NewParent. ---
**Author:** ![GOKUL\_ANANTH\_M](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/gokul_ananth_m/32/14416_2.png) [@GOKUL\_ANANTH\_M](https://developer.sailpoint.com/discuss/u/GOKUL_ANANTH_M)\ **Post date:** [June 4, 2025, 5:58am UTC](https://developer.sailpoint.com/discuss/t/provisioning-error-failed-to-update-attribute-ac-newname-error-there-is-no-such-object-on-the-server/139863/14 "2025-06-04T05:58:29Z")
Hi @ynara , Its actually a different error, but still yes we have done the order change as well. ---
**Author:** ![ynara](https://avatars.discourse-cdn.com/v4/letter/y/35a633/32.png) [@ynara](https://developer.sailpoint.com/discuss/u/ynara)\ **Post date:** [June 4, 2025, 4:42pm UTC](https://developer.sailpoint.com/discuss/t/provisioning-error-failed-to-update-attribute-ac-newname-error-there-is-no-such-object-on-the-server/139863/15 "2025-06-04T16:42:05Z")
@GOKUL_ANANTH_M Got it. Thank you for the recommendation! We will test it and see if it works. ---
**Author:** ![system](https://global.discourse-cdn.com/sailpoint/original/2X/f/f2136700ed5e3703e0b85e02f6be799dacca7735.png) [@system](https://developer.sailpoint.com/discuss/u/system)\ **Post date:** [August 3, 2025, 4:42pm UTC](https://developer.sailpoint.com/discuss/t/provisioning-error-failed-to-update-attribute-ac-newname-error-there-is-no-such-object-on-the-server/139863/16 "2025-08-03T16:42:54Z")
Closed on August 3, 2025, 4:42pm UTC This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.