Error encountered when merging constituent records that are both registrants for the same event: ‘The INSERT statement conflicted with the CHECK constraint CK_REGISTRANT_VALIDUNKNOWNGUEST". The conflict occurred in database "databasename"’"

When constiteunt X and constituent Y are identified as duplicates and merged, either manually or in bulk, if both are registered for the same event, the following error is encountered: ‘The INSERT statement conflicted with the CHECK constraint "CK_REGISTRANT_VALIDUNKNOWNGUEST". The conflict occurred in database "databasename"’.

Merge was performed without error in version 2.91 and only started occurring after upgrade to version 3. 
Download and install the latest patch, which contains all fixes from previous patches. If you are running an older version, download and install the latest version and then the patch. 

The validation message now reads:
The constituents could not be merged because both constituents have registrations for the same event and one or both of the constituents have event registration payments or event registration payments pending in an uncommitted batch. The payments may be duplicates.

Environment

 3.0.516.30
 3.0.516, Service Pack 7

Was this article helpful?