Join the #BuildWithBuildAgent Challenge! Get recognized, earn exclusive swag, and inspire the ServiceNow Community with what you can build using Build Agent.  Join the Challenge.

FAILED TRYING TO EXECUTE ON CONNECTION glide.6

soumya19
Tera Contributor

Hi,

 

I have updated the prefix for the auto numbering for Application service (cmdb_ci_service_auto) from "SNSVC to AS" and i have moved the updates from dev environment to staging. while previewing the update set i have recieved the below error.

 

Error:

FAILED TRYING TO EXECUTE ON CONNECTION glide.6 (connpid=1621224): INSERT INTO sys_metadata (`sys_mod_count`,`sys_updated_on`,`sys_class_name`,`sys_id`,`sys_package`,`sys_update_name`,`sys_updated_by`,`sys_created_on`,`sys_name`,`sys_scope`,`sys_created_by`,`sys_policy`) VALUES(9,'2023-01-13 14:09:31','sys_number','7274f81f975011106ee0ba67f053afeb','8b7e39db47101110232edb82e36d432f','sys_number_7274f81f975011106ee0ba67f053afeb','Soumya rikkala','2022-06-30 08:19:28','AS','global','system',NULL),INSERT INTO sys_number (`prefix`,`number`,`sys_id`,`maximum_digits`,`category`) VALUES('AS',1000,'7274f81f975011106ee0ba67f053afeb',7,'cmdb_ci_service_auto')
java.sql.BatchUpdateException: (conn=1621224) Duplicate entry 'cmdb_ci_service_auto' for key 'category'

 

I have checked the Application service (cmdb_ci_service_auto) table sys_id in dev and staging, both are different and i have also checked the record sys_id in number maintenace table there also the record sys_id's are different in both environments.

 

Can anyone suggest me the solution for this ?

0 REPLIES 0