Please share any other relevant files that may be required (for example, logs).
2024-12-04T10:16:47,475 ERROR Thread-5017 services.standard.connector.LogiPlexConnector:872 - Error while reading back account: null
2024-12-04T10:16:47,837 WARN Thread-5017 engine.jdbc.spi.SqlExceptionHelper:137 - SQL Error: 515, SQLState: 23000
2024-12-04T10:16:47,837 ERROR Thread-5017 engine.jdbc.spi.SqlExceptionHelper:142 - Cannot insert the value NULL into column ‘native_identity’, table ‘identityiq_81p1.identityiq.spt_link’; column does not allow nulls. INSERT fails.
2024-12-04T10:16:47,837 ERROR Thread-5017 sailpoint.provisioning.PlanEvaluator:1748 - org.hibernate.exception.ConstraintViolationException: could not execute statement
sailpoint.tools.GeneralException: org.hibernate.exception.ConstraintViolationException: could not execute statement
Share all details about your problem, including any error messages you may have received.
When running joiner via Rapid Setup, I get this error during Active Directory using Logiplex. The account is created and upon next aggregation, correlates.
Front end I get An unexpected error occurred: Row was updated or deleted by another transaction (or unsaved-value mapping was incorrect) : [sailpoint.object.Link#] on the task
That worked, is there a way to ensure this works with GUID? This way if an account moves or anything it’s unique and won’t have a cannot be found error.