# AD Aggregation Failed **URL:** \ **Category:** IIQ Discussion and Questions\ **Tags:** aggregation, identityiq\ **Created:** [May 27, 2024, 8:16am UTC](https://developer.sailpoint.com/discuss/t/ad-aggregation-failed/58030 "2024-05-27T08:16:08Z")\ **Posts on this page:** 10\ **Page:** 1
**Author:** ![niket345](https://avatars.discourse-cdn.com/v4/letter/n/ba8739/32.png) [@niket345](https://developer.sailpoint.com/discuss/u/niket345)\ **Post date:** [May 27, 2024, 8:16am UTC](https://developer.sailpoint.com/discuss/t/ad-aggregation-failed/58030/1 "2024-05-27T08:16:08Z")
### Which IIQ version are you inquiring about? Version 8.4 ### Share all details related to your problem, including any error messages you may have received. Hello Experts, I have noticed that AD Aggregation is failed with multiple error. I have identified that without Create link options it is failing but with Create link option, it is working fine. Please suggest. Error 1 - Cannot insert duplicate key in object ‘identityiq.spt\_identity’. The duplicate key value is (CAQA\caderogb). 2024-05-24T11:23:34,596 ERROR Thread-5303 sailpoint.api.Aggregator:1916 - Exception during aggregation of xx\caderogb. Reason: org.hibernate.exception.ConstraintViolationException: could not execute statement Error 2 – Exception during aggregation of CN=Adiham, Alxxxxx,OU=CHQ-QA,OU=Users-QA,OU=xxxx-QA,DC=xxxx,DC=xxxx,DC=com. Reason: java.lang.NullPointerException: Cannot invoke "sailpoint.object.Identity.getName()" because "this.\_lastIdentity" is null. Thanks ---
**Author:** ![kjakubiak](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/kjakubiak/32/7052_2.png) [@kjakubiak](https://developer.sailpoint.com/discuss/u/kjakubiak)\ **Post date:** [May 27, 2024, 8:18am UTC](https://developer.sailpoint.com/discuss/t/ad-aggregation-failed/58030/2 "2024-05-27T08:18:39Z")
It looks like IIQ trying to create Identity for orphaned AD account but can’t because the name it tries to use is already in use. I would start checking from - - Correlation - to check why account is not getting correlated to the existing identity - IdentityCreationRule - to check why it tries to create non unique identity name as it might be issue in the future In worst case you can just write CustimizationRule to exclude this account from aggregation but it does not really solve your problem - just masks symptoms. ---
**Author:** ![niket345](https://avatars.discourse-cdn.com/v4/letter/n/ba8739/32.png) [@niket345](https://developer.sailpoint.com/discuss/u/niket345)\ **Post date:** [May 27, 2024, 12:41pm UTC](https://developer.sailpoint.com/discuss/t/ad-aggregation-failed/58030/3 "2024-05-27T12:41:36Z")
@kjakubiak Thanks for the explaining. I understand that error 1 is happened due to duplicate of users. Can you please help me for Error 2 how to to fix that. is this something happened due to missing EmployeeID or username. ---
**Author:** ![kjakubiak](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/kjakubiak/32/7052_2.png) [@kjakubiak](https://developer.sailpoint.com/discuss/u/kjakubiak)\ **Post date:** [May 27, 2024, 1:13pm UTC](https://developer.sailpoint.com/discuss/t/ad-aggregation-failed/58030/4 "2024-05-27T13:13:32Z")
I think it’s happening because of the same reason - as in previous step no identity was created - now it is null while IIQ expects to have Identity object in \_lastIdentity. ---
**Author:** ![niket345](https://avatars.discourse-cdn.com/v4/letter/n/ba8739/32.png) [@niket345](https://developer.sailpoint.com/discuss/u/niket345)\ **Post date:** [May 27, 2024, 1:28pm UTC](https://developer.sailpoint.com/discuss/t/ad-aggregation-failed/58030/6 "2024-05-27T13:28:45Z")
Yes. any idea how to fix this issue or is this something because of Data issue ---
**Author:** ![kjakubiak](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/kjakubiak/32/7052_2.png) [@kjakubiak](https://developer.sailpoint.com/discuss/u/kjakubiak)\ **Post date:** [May 27, 2024, 1:30pm UTC](https://developer.sailpoint.com/discuss/t/ad-aggregation-failed/58030/7 "2024-05-27T13:30:01Z")
do you have Aggregator logger set to something above Info? there is a bug in this logger and it can sometimes throw nullpointer in \_lastIdentity when it is set to Info log level or more. ---
**Author:** ![niket345](https://avatars.discourse-cdn.com/v4/letter/n/ba8739/32.png) [@niket345](https://developer.sailpoint.com/discuss/u/niket345)\ **Post date:** [May 27, 2024, 1:37pm UTC](https://developer.sailpoint.com/discuss/t/ad-aggregation-failed/58030/8 "2024-05-27T13:37:24Z")
Yes. I checked that its commented out in log4j2.properties file. #logger.aggregator.name=sailpoint.api.Aggregator #logger.aggregator.level=trace Hope i am referring correct logs ---
**Author:** ![kjakubiak](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/kjakubiak/32/7052_2.png) [@kjakubiak](https://developer.sailpoint.com/discuss/u/kjakubiak)\ **Post date:** [May 27, 2024, 1:56pm UTC](https://developer.sailpoint.com/discuss/t/ad-aggregation-failed/58030/9 "2024-05-27T13:56:03Z")
That’s correct one, would be good to paste here complete log4j.properties file as it might be also eg. Root logger set to info ---
**Author:** ![niket345](https://avatars.discourse-cdn.com/v4/letter/n/ba8739/32.png) [@niket345](https://developer.sailpoint.com/discuss/u/niket345)\ **Post date:** [May 28, 2024, 5:21am UTC](https://developer.sailpoint.com/discuss/t/ad-aggregation-failed/58030/10 "2024-05-28T05:21:20Z")
[log4j2.txt](https://developer.sailpoint.com/discuss/uploads/short-url/cEf9R9wNuhaUbEJrKvpLDLegoHJ.txt) (16.4 KB) @kjakubiak I have attached log4j2 properties file. Please check ---
**Author:** ![system](https://global.discourse-cdn.com/sailpoint/original/2X/f/f2136700ed5e3703e0b85e02f6be799dacca7735.png) [@system](https://developer.sailpoint.com/discuss/u/system)\ **Post date:** [July 27, 2024, 5:21am UTC](https://developer.sailpoint.com/discuss/t/ad-aggregation-failed/58030/11 "2024-07-27T05:21:24Z")
Closed on July 27, 2024, 5:21am UTC This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.