Errors during aggregation: Error occurred while saving latest changenumber.Error:null

IdentityIQ (IIQ) IIQ Discussion and Questions
,
1

Which IIQ version are you inquiring about?

Version 8.4

Please share any other relevant files that may be required (for example, logs).

changenumber.txt (1.09 KB)

Share all details related to your problem, including any error messages you may have received.

Hi Community,

We have recently upgraded to 8.4, and are seeing the following error during the AD aggregations.

Error occurred while saving latest changenumber.Error:null. Stack trace attached.

All these applications have the entry.

Any pointers?

2

Did you also upgraded iqservice?

2 Likes
3

Yes, we have upgraded IQService.

4

Is this error consistent or intermittent, if this is consistent, can you please try to run AD On-Demand Aggregation of a particular user and provide more detailed logs.

Also is this error happening on both Full and Delta aggregations?

5

Hi and Hello,

The NullPointerException you’re encountering during AD aggregations in SailPoint 8.4 seems to be occurring as the system attempts to save the last change number in the ADLDAPConnector.

Null Value Handling: The method saveLastChangeNumber might be trying to handle or manipulate a null value, which is not anticipated in the code. Ensure that all expected values, particularly those related to change numbers and identity data, are being passed correctly and are not null.

Regards,
Adam

2 Likes
6

Hi Sanali,
It’s a bit strange error - it would be great if you could enable sailpoint.connector.ADLDAPConnector logger to DEBUG so we could see some more messages.

Generaly It looks like the problem is with Delta aggregation - does full aggregation work correctly?

2 Likes
7

Is that all, log available ? Generally, at bottom sailpoint conenctor do mention cause of null pointer excepetion.

8

This was resolved by removing the timestamps for these 2 entries in the app XML.

9

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.