CiviCRM Community Forums (archive)

Hi all,
This error is related to the civicrm_subscription_history table and it appears that on login for several but not all Drupal users. There are only 2 groups but it appears to try to do an insert for a group #6

Here's the error from one login
Error Details:

Array
(
    [callback] => Array
        (
            [0] => CRM_Core_Error
            [1] => handle
        )

    [code] => -3
    [message] => DB Error: constraint violation
    [mode] => 16
    [debug_info] => INSERT INTO civicrm_subscription_history (contact_id , group_id , date , method , status ) VALUES ( 51 ,  6 ,  20100723011246 , 'API' , 'Added' )  [nativecode=1452 ** Cannot add or update a child row: a foreign key constraint fails (`civicrm/civicrm_subscription_history`, CONSTRAINT `FK_civicrm_subscription_history_group_id` FOREIGN KEY (`group_id`) REFERENCES `civicrm_group` (`id`) ON DELETE CASCADE)]
    [type] => DB_Error
    [user_info] => INSERT INTO civicrm_subscription_history (contact_id , group_id , date , method , status ) VALUES ( 51 ,  6 ,  20100723011246 , 'API' , 'Added' )  [nativecode=1452 ** Cannot add or update a child row: a foreign key constraint fails (`civicrm/civicrm_subscription_history`, CONSTRAINT `FK_civicrm_subscription_history_group_id` FOREIGN KEY (`group_id`) REFERENCES `civicrm_group` (`id`) ON DELETE CASCADE)]
    [to_string] => [db_error: message="DB Error: constraint violation" code=-3 mode=callback callback=CRM_Core_Error::handle prefix="" info="INSERT INTO civicrm_subscription_history (contact_id , group_id , date , method , status ) VALUES ( 51 ,  6 ,  20100723011246 , 'API' , 'Added' )  [nativecode=1452 ** Cannot add or update a child row: a foreign key constraint fails (`civicrm/civicrm_subscription_history`, CONSTRAINT `FK_civicrm_subscription_history_group_id` FOREIGN KEY (`group_id`) REFERENCES `civicrm_group` (`id`) ON DELETE CASCADE)]"]
)


Here's another
Array
(
    [callback] => Array
        (
            [0] => CRM_Core_Error
            [1] => handle
        )

    [code] => -3
    [message] => DB Error: constraint violation
    [mode] => 16
    [debug_info] => INSERT INTO civicrm_subscription_history (contact_id , group_id , date , method , status ) VALUES ( 1 ,  6 ,  20100723012615 , 'API' , 'Added' )  [nativecode=1452 ** Cannot add or update a child row: a foreign key constraint fails (`civicrm/civicrm_subscription_history`, CONSTRAINT `FK_civicrm_subscription_history_group_id` FOREIGN KEY (`group_id`) REFERENCES `civicrm_group` (`id`) ON DELETE CASCADE)]
    [type] => DB_Error
    [user_info] => INSERT INTO civicrm_subscription_history (contact_id , group_id , date , method , status ) VALUES ( 1 ,  6 ,  20100723012615 , 'API' , 'Added' )  [nativecode=1452 ** Cannot add or update a child row: a foreign key constraint fails (`civicrm/civicrm_subscription_history`, CONSTRAINT `FK_civicrm_subscription_history_group_id` FOREIGN KEY (`group_id`) REFERENCES `civicrm_group` (`id`) ON DELETE CASCADE)]
    [to_string] => [db_error: message="DB Error: constraint violation" code=-3 mode=callback callback=CRM_Core_Error::handle prefix="" info="INSERT INTO civicrm_subscription_history (contact_id , group_id , date , method , status ) VALUES ( 1 ,  6 ,  20100723012615 , 'API' , 'Added' )  [nativecode=1452 ** Cannot add or update a child row: a foreign key constraint fails (`civicrm/civicrm_subscription_history`, CONSTRAINT `FK_civicrm_subscription_history_group_id` FOREIGN KEY (`group_id`) REFERENCES `civicrm_group` (`id`) ON DELETE CASCADE)]"]
)

I'm not sure why it would be referencing a group with an id of 6 because as far as I know we've only had 2 groups.... Administrators and a Test Group.

Any thoughts?

Thanks,[/code][/code]

Oh, you're absolutely right... We enabled groups/synch and I'll be someone mapped it and then deleted the groups they made. I'll check that out.

Thanks!

We seem to have run into the same sort of trouble, reported here: http://forum.civicrm.org/index.php/topic,19427.msg80863.html

I tried turning off the "CiviMember Roles Sync" mod, same error. Was it necessary to do more than merely disable that mod?

The mod does not seem to support granularity of syncing for only certain Civi contact types... Members and not Organizations. If disabling the mod had corrected this error, I would have been inclined to try hacking the mod to only sync when the ID was a member ID. As-is, I can not be sure this really is what is happening.

Suggestions please?

awasson: You did not have some Civi contacts that had no corresponding Drupal account in your case?

I verified the Civi Custom Data fields. All (3) are working properly and are really needed. Two custom fields are specifically for these Organization records in Civi that do not have corresponding Drupal ID's. The last custom field is associated with Members and that Civi type does have corresponding Drupal ID's.

awasson: Lobo was able to quickly figure out what was going on. I guess a handful of our contact records mysteriously ended up with contact_sub_type data, which was causing the same type of error that you had reported here.

<dlobo>   so the mystery is how/why did the db have contact_sub_type set to people's names
<dlobo>   that was causing our code to do the wrong thing (bug)
<dlobo>   and we were not reporting it nicely
<dlobo>   i'll file an issue and fix for 3.4
<dlobo>   so future folks dont spend forever on this

We really are not using contact_sub_type capabilities, and him NULLing that column cleared up the troubles. Glad it was not the "CiviMember Roles Sync" mod causing the troubles!

I am also having this same problem, which appeared immediately following a server migration (rather than clean install).

It appears whenever a user logs into the site, or when they create/edit their Drupal account. The site uses 2 custom profiles users must complete when creating a new Drupal account.

The site uses CiviMember and CiviRoles Group synch. I have not tried disabling them, based on the above comment.

We are about a week from going live, but this is a real show-stopper since users can't create an account without seeing a "Fatal Error: Database Constraint" message.

We are using Civi 3.2 and Drupal 6.2. I've attached the error log details to this post and would really, really appreciate some help debugging it!

Follow Up Note: When I first installed  Civi, it created the demo database. I then went in and deleted all those contacts/events/groups/etc.  Some of the deletions probably occurred after installing the OG Group synch module.

Follow Up: Case Solved. In the end, the "DB Error: constraint violation" problem turned out to be a simple Drupal Permissions issue, which were set incorrectly. Once the permissions were updated correctly, the error disappeared.