
vxnyv (vxnyv) asked a question.
"Automatic profile push of user to app Active Directory failed: Error updating active_directory user: There is no such object on the server."
I have been getting this error on 5 users and no one else within the businesses. I am at a loss of how to fix this any information would be great.

I've not had this issue but perhaps you could look at the directory mapping and perform a "Preview" with the accounts causing you trouble and see if any sort of mapping error pops up. If no errors, I would look in AD logs for errors.
Hello,
Thank you for reaching Okta help center! This error can occur if the user has been deleted from AD or if there is a mismatch between the user's username or email address in Okta and AD. When Okta attempts to update the user's profile in AD, it sends the user's email address or username to AD to identify the user object.
To resolve this issue, you should first check whether the user object still exists in AD. If the user has been deleted from AD, you will need to create a new user object in AD and then update the user's profile in Okta with the correct username or email address to match the new user object.
If the user object still exists in AD, you should verify that the username or email address in Okta matches the corresponding attribute in AD. You can do this by checking the user's profile in Okta and comparing it with the user's profile in AD. If there is a mismatch, you should update the user's profile in Okta with the correct attribute value.
If there is no mismatch and you're still having the same issue, please open a support ticket with us.
https://support.okta.com/help/s/article/How-to-Create-a-Support-Case?language=en_US
Regards,
Razvan Baiasu
Technical Support Engineer
Okta Global Customer Care
The issue we found out was that the Manager of the person was deactivated in workday. When the manager was deactivated the employees were not moved to an active manager.
Yes, I found that when the user's workday manager is deactivated and these users were from from Full time employee to contractors (with no link with workday) may cause this issue.
Removing all the attributes of a manager from this newly converted contractor profile and saving it will alow to remove the error and sync up with AD.