- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-04-2020 05:22 AM
I've built a scoped application and when try to import the update set I've got this error:
FAILED TRYING TO EXECUTE ON CONNECTION glide.8 (connpid=108560): com.glide.db.BatchStatement$StatementContainer@3bf852,com.glide.db.BatchStatement$StatementContainer@f28389
java.sql.BatchUpdateException: (conn=108560) Duplicate entry '1bebaa621b7d1810a59bb8481b4bcb48-global-ScopedGlideElement-scrip' for key 'source_scope_2'
How could I find the entry that originated this error?
Help Please,
Natanael O Wolf
Solved! Go to Solution.
- Labels:
-
Service Catalog
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-18-2020 01:26 PM
Hi Everyone,
Finally I've got from where the issue was comming.
I've built a new application through studio and publish it at DEV environment to QAS one.
I've successfully deployed/installed it at QAS environment.
After application installed, I've made many changes at DEV environment and I've used the Update Set to deploy those changes at QAS.
It has caused a duplicate KEY at the core application.
I was able to see both application at servicenow. One called "Internal Application" and other one (US/XML) called "External Application"
Only way I did find to fix the problem, was remove the application (Uninstall the "Internal Application") and then install all again using Update Set (XML).
No more duplicate key found. And I'm still building that application/system. 🙂
Thanks,
Natanael O. Wolf
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-04-2020 05:55 AM
Hi,
Find the below thread that might help you.
Mark helpful or correct based on impact.
Regards,
Priyanka
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-06-2020 05:22 AM
Thank you Priyanka,
Actually I walk through the link you send me, but I'd like to know how could I found the origin of the error.
Only what can I see at update set log is the message above!
Hugs m8
Wolf
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-04-2020 06:02 AM
Please check below links for help
https://hi.service-now.com/kb_view.do?sysparm_article=KB0724508
https://hi.service-now.com/kb_view.do?sysparm_article=KB0716513
It those doesn't help please raise a HI ticket with ServiceNow.
Regards
Ankur
Ankur
✨ Certified Technical Architect || ✨ 9x ServiceNow MVP || ✨ ServiceNow Community Leader
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-06-2020 05:29 AM
Thanks Ankur,
I'm following your trail. I've changed my table name and delete other one, could be some error related to this.
I keep looking for the source of the issue.
Regards
Wolf