Failed to lazily initialize a collection of role: sailpoint.object.Rule.referencedRules, could not initialize proxy - no Session

IdentityIQ (IIQ) IIQ Discussion and Questions
, , , ,
1

SailPoint IIQ 8.4

failed to lazily initialize a collection of role: sailpoint.object.Rule.referencedRules, could not initialize proxy - no Session

Hi SailPoint Experts,

We are currently using SailPoint IIQ version 8.4.

Recently, without any changes being made to the production environment, several Account aggregation and refresh tasks have started failing unexpectedly.

The following tasks are failing:

  • Active Directory Aggregation

  • Azure AD Aggregation

  • Refresh Identity Cube – Lifecycle

  • Other Refresh tasks

Could you please advise where I should begin troubleshooting this issue?
Should I check the configuration, rules, or custom code within SailPoint IIQ?

If anyone has encountered a similar issue earlier, your guidance would be greatly appreciated.
Your prompt response will be highly appreciated.

Error Message:

failed to lazily initialize a collection of role: sailpoint.object.Rule.referencedRules, could not initialize proxy - no Session
failed to lazily initialize a collection of role: sailpoint.object.Rule.referencedRules, could not initialize proxy - no Session
failed to lazily initialize a collection of role: sailpoint.object.Rule.referencedRules, could not initialize proxy - no Session
failed to lazily initialize a collection of role: sailpoint.object.Rule.referencedRules, could not initialize proxy - no Session
failed to lazily initialize a collection of role: sailpoint.object.Rule.referencedRules, could not initialize proxy - no Session
failed to lazily initialize a collection of role: sailpoint.object.Rule.referencedRules, could not initialize proxy - no Session
2

@pmr542 We are discussing the same thing here: Full Identity Refresh Task Fails with Below Errors - #5 by neel193

Could you please also confirm below items:

  • If you are passing any identity and application object completely as arguments to any custom method. Modify it to pass the names and get the object from context inside the method.

  • If you are doing commitTransaction(), that may also invalidate some of the objects in reference.. For this you should create a sub context and then make the changes followed by commitTransaction().

  • If you are decache(), that also may cause the issue. Please change it to decache(object).

Please check your codebase for such cases and make the necessary adjustments.

Please also refer to the document: https://community.sailpoint.com/t5/IdentityIQ-Forum/Request-for-Official-Guidance-Use-of-commitTransaction-Inside/m-p/277486/highlight/true#M198717

Note: Found a fix?Help the community by marking the comment as solution. Feel free to react(:heart:,:+1:, etc.)with an emoji to show your appreciation or message me directly if your problem requires a deeper dive.