CiviCRM Community Forums (archive)

*

News:

Have a question about CiviCRM?
Get it answered quickly at the new
CiviCRM Stack Exchange Q+A site
This forum was archived on 25 November 2017. Learn more.
How to get involved.
What to do if you think you've found a bug.



  • CiviCRM Community Forums (archive) »
  • Old sections (read-only, deprecated) »
  • Support »
  • Upgrading CiviCRM (Moderator: Deepak Srivastava) »
  • upgrade 4.3.5 to 4.3.6
Pages: [1]

Author Topic: upgrade 4.3.5 to 4.3.6  (Read 955 times)

tac12

  • I’m new here
  • *
  • Posts: 17
  • Karma: 0
  • CiviCRM version: 4.3.5
  • CMS version: Drupal6
  • MySQL version: 5.1.69
  • PHP version: 5.3.3
upgrade 4.3.5 to 4.3.6
September 27, 2013, 07:35:42 am
I just tried this upgrade on a clone of my production site  and it failed at the upgrade database step. complaining about DB Error: constraint violation.

I attach a screen shot,  anyone have any suggestions how to proceed?

Adrian

Coleman Watts

  • Administrator
  • I’m (like) Lobo ;)
  • *****
  • Posts: 2346
  • Karma: 183
  • CiviCRM version: The Bleeding Edge
  • CMS version: Various
Re: upgrade 4.3.5 to 4.3.6
September 27, 2013, 08:31:22 am
We had been struggling with a similar issue but we thought we had it all fixed. Perhaps your database differs in some subtle way from the ones we were testing. Could you please send me a copy of your database (my email is coleman at [the name of this software] dot org) asap so we can investigate and hopefully fix before too many people have the same problem.
Good thinking testing on a backup!
Try asking your question on the new CiviCRM help site.

sriz786

  • I post occasionally
  • **
  • Posts: 35
  • Karma: 0
Re: upgrade 4.3.5 to 4.3.6
September 27, 2013, 09:36:58 pm
we have similar problem, upgrade from 4.3.4 to 4.3.6
i will send you my database
thank you
Rizwan

Coleman Watts

  • Administrator
  • I’m (like) Lobo ;)
  • *****
  • Posts: 2346
  • Karma: 183
  • CiviCRM version: The Bleeding Edge
  • CMS version: Various
Re: upgrade 4.3.5 to 4.3.6
October 06, 2013, 05:28:21 am
Here are instructions for fixing the situation.
http://wiki.civicrm.org/confluence/display/CRMDOC/Fixing+Orphaned+Contribution+Recur+Records
Try asking your question on the new CiviCRM help site.

tac12

  • I’m new here
  • *
  • Posts: 17
  • Karma: 0
  • CiviCRM version: 4.3.5
  • CMS version: Drupal6
  • MySQL version: 5.1.69
  • PHP version: 5.3.3
Re: upgrade 4.3.5 to 4.3.6
October 06, 2013, 10:02:07 pm
Sadly that didn't do the trick,  running the SQL had no effect:

mysql> DELETE contri_recur.* FROM civicrm_contribution_recur contri_recur LEFT JOIN civicrm_contact ON contri_recur.contact_id = civicrm_contact.id WHERE civicrm_contact.id IS NULL;
Query OK, 0 rows affected (0.03 sec)

mysql> DELETE contri_recur.* FROM civicrm_contribution_recur contri_recur LEFT JOIN civicrm_campaign ON contri_recur.campaign_id = civicrm_campaign.id WHERE civicrm_campaign.id IS NULL AND contri_recur.campaign_id IS NOT NULL;
Query OK, 0 rows affected (0.00 sec)

And the upgrade fails as before  :(

Coleman Watts

  • Administrator
  • I’m (like) Lobo ;)
  • *****
  • Posts: 2346
  • Karma: 183
  • CiviCRM version: The Bleeding Edge
  • CMS version: Various
Re: upgrade 4.3.5 to 4.3.6
October 07, 2013, 03:55:51 am
Although you sent us your database it did not contain any data so we were unable to test it. Someone else did send us a complete db and the above solution does work for them.
Try asking your question on the new CiviCRM help site.

tac12

  • I’m new here
  • *
  • Posts: 17
  • Karma: 0
  • CiviCRM version: 4.3.5
  • CMS version: Drupal6
  • MySQL version: 5.1.69
  • PHP version: 5.3.3
Re: upgrade 4.3.5 to 4.3.6
October 07, 2013, 03:59:55 am
Yes I realised that I didnt send my entire database,  I was nervous to send my entire database for data protection reasons....I will email you outside the forum.
Pages: [1]
  • CiviCRM Community Forums (archive) »
  • Old sections (read-only, deprecated) »
  • Support »
  • Upgrading CiviCRM (Moderator: Deepak Srivastava) »
  • upgrade 4.3.5 to 4.3.6

This forum was archived on 2017-11-26.