Skip to main content
Question

Database constraint error upgrading from 2022R2 to 2023R2


etrowbridge
Freshman II

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. 

0 replies

Be the first to reply!

Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings