Error: The INSERT statement conflicted with the CHECK constraint "CK_CW_INTERSECTION_EXISTS".
Error appears when a user tries to copy an objects from one diagram into another diagram or drag a new object onto a diagram.
Error found on the evolve log :
ERROR Casewise.GraphAPI.API.cwLightObject 2018-01-24-13-37-33 – System.Runtime.InteropServices.COMException (0x80040E2F): The INSERT statement conflicted with the CHECK constraint "CK_CW_INTERSECTION_EXISTS". The conflict occurred in database "Casewise2016", table "dbo.CW_INTER_OBJECT".
To resolve this issue please ….
your insert is violating a check constraint. This is a constraint in your database that performs a specific check - that a numeric value is in a particular range, that a string is at most n characters long, or whatever.
To find out what the check constraint is:
Open SQL Management Studio
Create new query
SELECT name, definition FROM sys.check_constraints
WHERE name = 'ck_CW_INTERSECTION_EXISTS'
This will give you the expression that is being checked in the "definition" column.
From that expression, you should be able to determine why your insert is being rejected. Fix the problem and insert again.
If you really cannot fix your data, and if you do not need / want that check constraint in place, you can drop it:
To drop the CK_CW_INTERSECTION_EXISTS :
-Backup your database
- On sql management studio select your database and run the script below :
ALTER TABLE <constraint file name> DROP CONSTRAINT CK_CW_INTERSECTION_EXISTS; GO.
On our situation with the log, the script will be:
ALTER TABLE dbo.CW_INTER_OBJECT DROP CONSTRAINT ck_CW_INTERSECTION_EXISTS; GO.