We are having some issues with IDNOW for Service Catalog 3.2. After all approvals we are getting error and the request is canceled in Servicenow.
Our workflow stopped on the step that he needs a “202 response”
any suggestions to resolve this issue?
We are receiving this error:
Unique Key violation detected by database ((conn=2316034) Duplicate entry '$ID' for key 'PRIMARY')
: java.sql.SQLIntegrityConstraintViolationException: (conn=2316034) Duplicate entry '$ID' for key 'PRIMARY':
Hi @nicollasviggiano ,
There might be database constraint violation, specifically a Unique Key violation. It’s possible that when IDN or ServiceNow tries to create or update a record in the database, it is attempting to insert a value that already exists in a column that requires unique entries.
Enable the logs and see if it captured any traffic regarding this which can be used to resolve the issue!
Logs in VAs or in the plugin @Prashanth0707 ?
The database that u say its on Servicenow or Sailpoint? We enabled the log in servicenow plugin, but it doesn’t help so much.
Is that from the ServiceNow system log?
I can see where in the script include SP_SPNT_SNOW_INT_WORKFLOW_CreateAccessRequest it is hitting the catch block but there’s not a ton of information it seems to be putting out.
catch (ex) {
current.x_sap_intidn_workflow_response = true;
current.comments = 'Failed creating access request. Error during execution';
gs.error(ex.message);
}
If it were me, I would
If you don’t want to do that, this sounds like a good opportunity to open a support case.
People do anything for me points lol that is what that error means.
Nicollas, you need to check what the script body is sending. It appears that when the script tries to retrieve the values to do the call it gets a Null value and exit.
As far as i remember is not even being sent to ISC at all. Have you tried to change the SN governance connector to the correct environment. isn’t poiting to another env? that could be the issue as it is required.
Quote: " * A source of ServiceNow accounts that SailPoint can load account information from, so each account can be associated with an identity and access for each identity can be governed."
It could be it;
Hi mark,
For the first question, yes this is from Servicenow system logs, here more details from the log, i just removed some IDs / emails that was in the log
FAILED TRYING TO EXECUTE ON CONNECTION glide.18 (connpid=2325450): INSERT INTO task (`short_description`,`a_str_10`,`made_sla`,`upon_reject`,`a_ref_1`,`sys_updated_on`,`task_effective_number`,`sys_class_name`,`number`,`sys_id`,`contact_type`,`sys_updated_by`,`opened_by`,`urgency`,`a_num_3`,`sys_created_on`,`sys_domain`,`state`,`reassignment_count`,`sys_created_by`,`knowledge`,`a_str_11`,`approval`,`impact`,`due_date`,`sys_mod_count`,`active`,`priority`,`sys_domain_path`,`opened_at`,`a_str_1`,`a_str_3`,`escalation`,`upon_approval`,`approval_set`) VALUES('Requested for Sailpoint IdentityNow Access Request','Brasil',1,'cancel','$id','2024-10-18 18:33:33','REQ0778380','sc_request','REQ0778380','$ID',NULL,'[email protected]','$ID',3,0,'2024-10-18 18:33:33','global',1,0,'[email protected]',0,NULL,'not requested',3,'2024-10-19 08:33:30',0,1,4,'/','2024-10-18 18:33:33','requested','requested',0,'proceed',NULL) /* dev008, gs:ID, tx:ID */
Unique Key violation detected by database ((conn=2325450) Duplicate entry '%ID' for key 'PRIMARY')
: java.sql.SQLIntegrityConstraintViolationException: (conn=2325450) Duplicate entry '$ID' for key 'PRIMARY': org.mariadb.jdbc.internal.util.exceptions.ExceptionMapper.get(ExceptionMapper.java:229)
org.mariadb.jdbc.internal.util.exceptions.ExceptionMapper.getException(ExceptionMapper.java:165)
The ID that he’s saying its duplicated belongs to the REQ sysID, its possible that the sailpoint script have a problem? Its the sa
I will reach my snow team to do this some steps that u say, to see if we got some additionals informations
Hi Ivan,
The Source and the connector was configured to the same SNOW instance, it was working fine for the begining.
We tried to remove the source and stay only with the connector configured, but the error persists.
Nicollas,
Try reinstall the plugin in SN and configure it again.
Yeah. It appears so.. lol
This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.