Skip to main content

Ran into this error while upgrading from 22.220.0026 to 23.205.0011: 


I was able to get around it by dropping the constraint and recreating it with a different name in the DB but wanted to see if anyone else has encountered this? 

Before this upgrade I did do a build update from 22.209.0011 to 22.220.0026 without any issues. 

Be the first to reply!

Reply