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) »
  • Errors on upgrading 2.0.6 to 2.1.1
Pages: [1]

Author Topic: Errors on upgrading 2.0.6 to 2.1.1  (Read 5045 times)

jsimonis

  • I post frequently
  • ***
  • Posts: 316
  • Karma: 4
    • Forward Support, Inc.
  • CiviCRM version: 4.4-4.5
  • CMS version: Drupal 7
  • MySQL version: 5.5.37-cll
  • PHP version: 5.3.29
Errors on upgrading 2.0.6 to 2.1.1
October 26, 2008, 09:56:14 am
We were running 2.0.6.

We've upgraded to Drupal 6 and now we're ready to upgrade CiviCRM.

I've removed all the 2.0 files and unpacked the 2.1 files.

I run the upgrade script and I get this:

Code: [Select]
backTrace

/home/sandbox/public_html/sites/all/modules/civicrm/CRM/Core/Error.php, backtrace, 260
/home/sandbox/public_html/sites/all/modules/civicrm/CRM/Upgrade/TwoOne/Page/Upgrade.php, fatal, 58
/home/sandbox/public_html/sites/all/modules/civicrm/CRM/Upgrade/TwoOne/Page/Upgrade.php, runForm, 41
/home/sandbox/public_html/sites/all/modules/civicrm/install/upgrade.php, run, 48
/home/sandbox/public_html/sites/all/modules/civicrm/install/upgrade.php, run, 51


Warning: Smarty error: unable to read resource: "CRM/error.tpl" in /home/sandbox/public_html/sites/all/modules/civicrm/packages/Smarty/Smarty.class.php on line 1092
I've verified that I have the correct database name, db username, pw, etc.
« Last Edit: October 26, 2008, 10:22:44 am by jsimonis »

Donald Lobo

  • Administrator
  • I’m (like) Lobo ;)
  • *****
  • Posts: 15963
  • Karma: 470
    • CiviCRM site
  • CiviCRM version: 4.2+
  • CMS version: Drupal 7, Joomla 2.5+
  • MySQL version: 5.5.x
  • PHP version: 5.4.x
Re: Errors on upgrading 2.0.6 to 2.1.1
October 26, 2008, 11:01:40 am

can u delete ALL the files under the directory: files/civicrm/templates_c

thanx

lobo
A new CiviCRM Q&A resource needs YOUR help to get started. Visit our StackExchange proposed site, sign up and vote on 5 questions

jsimonis

  • I post frequently
  • ***
  • Posts: 316
  • Karma: 4
    • Forward Support, Inc.
  • CiviCRM version: 4.4-4.5
  • CMS version: Drupal 7
  • MySQL version: 5.5.37-cll
  • PHP version: 5.3.29
Re: Errors on upgrading 2.0.6 to 2.1.1
October 26, 2008, 06:06:20 pm
Thanks. Now we're getting this, which is odd since we haven't had any problems before with any CiviCRM upgrade on this site:

Database consistency check failed. FK constraint names not in the required format. Please rebuild your 2.0 database to ensure schema integrity.

How do I go about rebuilding the database?

Donald Lobo

  • Administrator
  • I’m (like) Lobo ;)
  • *****
  • Posts: 15963
  • Karma: 470
    • CiviCRM site
  • CiviCRM version: 4.2+
  • CMS version: Drupal 7, Joomla 2.5+
  • MySQL version: 5.5.x
  • PHP version: 5.4.x
Re: Errors on upgrading 2.0.6 to 2.1.1
October 26, 2008, 08:15:57 pm

can u send your db to deepak @ webaccess . co . in

we are pretty booked till wed, so we will not be able to respond and give the db a shot till late next week

lobo
A new CiviCRM Q&A resource needs YOUR help to get started. Visit our StackExchange proposed site, sign up and vote on 5 questions

cleit

  • I’m new here
  • *
  • Posts: 27
  • Karma: 2
Re: Errors on upgrading 2.0.6 to 2.1.1
November 01, 2008, 01:43:30 pm
I've just got exactly the same error upgrading a previously working 2.0.5 installation to 2.1.1 on Joomla 1.5.4.

Watching this space with interest...!


EDIT: OK I just re-installed all the CiviCRM tables and re-ran the upgrade script, and it all seemd to work this time.
« Last Edit: November 01, 2008, 01:55:10 pm by cleit »

Eileen

  • Forum Godess / God
  • I’m (like) Lobo ;)
  • *****
  • Posts: 4195
  • Karma: 218
    • Fuzion
Re: Errors on upgrading 2.0.6 to 2.1.1
November 01, 2008, 07:28:41 pm
The same error got this answer on another thread - ie. doing the quick solution below will expose the underlying error as the error you are seeing is that it can't report on the error.

Quote
The reason could be that upgrade script noticed some problem while doing the upgrade and wanted to display that error using the error-template which is templates/CRM/error.tpl in CiviCRM v2.0 and templates/CRM/common/fatal.tpl in CiviCRM v2.1.

While/before upgrading, your code-base is 2.1 but config still has old values. And when an error is encountered during/before upgrade it tries to display it using "templates/CRM/error.tpl" file which in v2.1 has actually changed to "templates/CRM/common/fatal.tpl".

Upgrade script does try to update config values at the end of upgrade script, which looks too late for this case. We 'll fix it as soon as possible.

Your temporary solution could be copy templates/CRM/common/fatal.tpl as templates/CRM/error.tpl and re-run the upgrade script to check for errors upgrade-script wanted to notify you.
Make today the day you step up to support CiviCRM and all the amazing organisations that are using it to improve our world - http://civicrm.org/contribute

kyle.vh

  • Guest
Re: Errors on upgrading 2.0.6 to 2.1.1
November 20, 2008, 04:49:08 pm
Quote from: jsimonis on October 26, 2008, 06:06:20 pm
Thanks. Now we're getting this, which is odd since we haven't had any problems before with any CiviCRM upgrade on this site:

Database consistency check failed. FK constraint names not in the required format. Please rebuild your 2.0 database to ensure schema integrity.

How do I go about rebuilding the database?
I am having the exact same issue as jsimonis. First with the Smarty error. Then after following David Lobos suggestion, the underlying error is exposed: Database consistency check failed.
My db unames, pws, base urls are correct. Was there any work around here?
Eileen: I don't understand your suggestion. Once deleting the cache as lobo suggests the underlying error is reported.

kyle.vh

  • Guest
Re: Errors on upgrading 2.0.6 to 2.1.1
November 20, 2008, 05:12:53 pm
lol, so my boss says: "well, we can just start fresh with civic 2.1 in Drupal 6 cause we don't have much data at all"
 :o
so please don't give this attention.
Thanks!

polestar

  • I post frequently
  • ***
  • Posts: 162
  • Karma: 11
    • Target Integration
Re: Errors on upgrading 2.0.6 to 2.1.1
December 01, 2008, 10:04:58 pm
I am next in queue watching this space. Same error for me,

Code: [Select]
Sorry. A non-recoverable error has occurred.

Database consistency check failed. FK constraint names not in the required format. Please rebuild your 2.0 database to ensure schema integrity.
CiviCRM - Installation & Support | Virtual Private Servers (VPS) with Joomla/Drupal and CiviCRM | SugarCRM & vTiger CRM Installation and Support
Target Integration | www.targetintegration.com
Subscribe to Knowledgement - Your guide to effective business | http://www.knowledgement.ie

Deepak Srivastava

  • Moderator
  • Ask me questions
  • *****
  • Posts: 677
  • Karma: 65
Re: Errors on upgrading 2.0.6 to 2.1.1
December 02, 2008, 02:30:58 am
Quote
Sorry. A non-recoverable error has occurred.

Database consistency check failed. FK constraint names not in the required format. Please rebuild your 2.0 database to ensure schema integrity.
Here is the post which shows exact steps to rebuild a 2.0 db.

There is also a wiki doc for this, but only valid for 1.8->1.9->2.0 upgrades ( i.e for 1.8/1.9 or earlier dbs).
« Last Edit: December 02, 2008, 02:48:07 am by Deepak Srivastava »
Found this reply helpful? Contribute NOW and help us improve CiviCRM with the Make it Happen! initiative.
Pages: [1]
  • CiviCRM Community Forums (archive) »
  • Old sections (read-only, deprecated) »
  • Support »
  • Upgrading CiviCRM (Moderator: Deepak Srivastava) »
  • Errors on upgrading 2.0.6 to 2.1.1

This forum was archived on 2017-11-26.