I am attempting to aggregate data from the source: “Active Directory.” It fails and shows the user is in OU4306, but AD shows the user in 3700.
It appears that there are certain special characters within your DN that are contributing to this problem. Kindly review the DN to identify and rectify the issue.
The special characters signifies an equal sign. If that was the issue it would be creating errors for all users. Looks like it is carrying over old data after the account was removed and re-aggregated.
(Ref: Unicode Character ‘EQUALS SIGN’ (U+003D) (fileformat.info))
Alright, so did the process of reaggregation helped? If not, you may want to attempt an unoptimized aggregation.
We did attempt an unoptimized aggregation without success. We’ve also moved the object to a new OU, ran aggregation, and moved the object back to the correct OU.
Can you remove the account in the Accounts tab of the user’s identity, then try re-aggregating?
FYI We are seeing a similar issue where AD is trying to write to an OU that the user is not in. It seems to have started 10/3/23, I have opened a case for it and am awaiting feedback.
Kevin we resolved the issue by deleting the identity from the identity list, and re-aggregating AD and our ERP software. This has repaired the issue for two separate users so far.
This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.