Help to find what is causing duplicate primary key at update set (Troubleshooting)

[Natanael Osvald]

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

[Ankur Bawiskar]

@Natanael Osvaldo Wolf 

Let me know if that answered your question or helped.

if you think there is any response that helps you please mark that helpful or accepted so that this thread can be closed.

Regards
Ankur

[Ankur Bawiskar]

@Natanael Osvaldo Wolf 

Hope you are doing good.

Let me know if that answered your question.

If so, please mark appropriate response as correct & helpful so that this thread can be closed and others can be benefited by this.

Regards
Ankur

[Natanael Osvald · Accepted solution]

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

[Natanael Osvald]

Thank you very much Ankur Bawiskar, Priyanka Vasant Asawale and also Valério Assolari for helping me!

Regards,

Natanael O. Wolf