While deploying a solution I run into an error in build_and_deploy_job . In the "Import Managed Solution as Update" step. Error message is "The reason given was: Cannot insert duplicate key exception when executing non-query: System.Data.SqlClient.SqlCommand Exception: System.Data.SqlClient.SqlException (0x80131904): Violation of UNIQUE KEY constraint 'ndx_envvarval_schemaname'. Cannot insert duplicate key in object 'dbo.EnvironmentVariableValueBase'. The duplicate key value is (cco365_shared_sharepointonline_ae7433ab439a48089b1aca0a53985fed, 0, Jan 1 1900 12:00AM)." See attached logfile
Import as managed solution log.txt
Expected Behavior
I would expect not to get an duplicate key error, but that the deployment would go well.
What component are you experiencing the issue with?
ALM Accelerator Canvas App
What solution version are you using?
January 2024
Steps To Reproduce
No response
Anything else?
Also if I do the import manually I get the same error. I suspect the alm accellerator maybe has broken something in the microsoft internals?
A colleague of mine has the same issue with another solution using the same instance of ALM Accellerator. When he deleted manually the managed solution in the target environment the deployment went well. As well as subsequent deployments.
Describe the issue
While deploying a solution I run into an error in build_and_deploy_job . In the "Import Managed Solution as Update" step. Error message is "The reason given was: Cannot insert duplicate key exception when executing non-query: System.Data.SqlClient.SqlCommand Exception: System.Data.SqlClient.SqlException (0x80131904): Violation of UNIQUE KEY constraint 'ndx_envvarval_schemaname'. Cannot insert duplicate key in object 'dbo.EnvironmentVariableValueBase'. The duplicate key value is (cco365_shared_sharepointonline_ae7433ab439a48089b1aca0a53985fed, 0, Jan 1 1900 12:00AM)." See attached logfile Import as managed solution log.txt
Expected Behavior
I would expect not to get an duplicate key error, but that the deployment would go well.
What component are you experiencing the issue with?
ALM Accelerator Canvas App
What solution version are you using?
January 2024
Steps To Reproduce
No response
Anything else?
Also if I do the import manually I get the same error. I suspect the alm accellerator maybe has broken something in the microsoft internals? A colleague of mine has the same issue with another solution using the same instance of ALM Accellerator. When he deleted manually the managed solution in the target environment the deployment went well. As well as subsequent deployments.