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) »
  • Discussion (deprecated) »
  • Alpha and Beta Release Testing »
  • 4.4 Release Testing »
  • Upgrade of 4.3.5 to 4.4 glitch
Pages: [1] 2

Author Topic: Upgrade of 4.3.5 to 4.4 glitch  (Read 4474 times)

clarkac

  • Administrator
  • Ask me questions
  • *****
  • Posts: 399
  • Karma: 11
  • CiviCRM version: 4.4.11 & 4.5.5
  • CMS version: Drupal 7
  • MySQL version: 5.1.61-cll
  • PHP version: 5.3.27
Upgrade of 4.3.5 to 4.4 glitch
August 23, 2013, 10:10:46 am
I upgraded a 4.3.5 database and got the following error at the end of the upgrade process, which otherwise went OK.  The database seems to have converted OK, although I have found at least one problem (to be posted).
Andy Clark

clarkac

  • Administrator
  • Ask me questions
  • *****
  • Posts: 399
  • Karma: 11
  • CiviCRM version: 4.4.11 & 4.5.5
  • CMS version: Drupal 7
  • MySQL version: 5.1.61-cll
  • PHP version: 5.3.27
Re: Upgrade of 4.3.5 to 4.4 glitch
September 06, 2013, 01:03:09 am
Upgrading from Alpha 3 to Beta 1 I get the following message, but everything seems to be working OK.

"Your database has already been upgraded to CiviCRM 4.4.beta1"
Andy Clark

Interpolat

  • I post frequently
  • ***
  • Posts: 140
  • Karma: -1
    • Interpolat Solutions, LLC.
  • CiviCRM version: 4.4+
  • CMS version: Wordpress
  • MySQL version: 5.5+
  • PHP version: 5.4+
Re: Upgrade of 4.3.5 to 4.4 glitch
September 11, 2013, 11:38:07 pm
I have also been getting that error as well, and also the following:

Code: [Select]
[Error: Migrate custom word-replacements]
CiviCRM_API3_Exception: "DB Error: already exists"

#0 /home/xxxx/public_html/wp-content/plugins/civicrm/civicrm/CRM/Upgrade/Incremental/php/FourFour.php(333): civicrm_api3("word_replacement", "replace", (Array:2))
#1 /home/xxxx/public_html/wp-content/plugins/civicrm/civicrm/CRM/Upgrade/Incremental/php/FourFour.php(230): CRM_Upgrade_Incremental_php_FourFour::rebuildWordReplacementTable()
#2 [internal function](): CRM_Upgrade_Incremental_php_FourFour::wordReplacements(Object(CRM_Queue_TaskContext))
#3 /home/xxxx/public_html/wp-content/plugins/civicrm/civicrm/CRM/Queue/Task.php(79): call_user_func_array((Array:2), (Array:1))
#4 /home/xxxx/public_html/wp-content/plugins/civicrm/civicrm/CRM/Queue/Runner.php(186): CRM_Queue_Task->run(Object(CRM_Queue_TaskContext))
#5 /home/xxxx/public_html/wp-content/plugins/civicrm/civicrm/CRM/Queue/Page/AJAX.php(44): CRM_Queue_Runner->runNext(TRUE)
#6 /home/xxxx/public_html/wp-content/plugins/civicrm/civicrm/CRM/Queue/ErrorPolicy.php(80): {closure}()
#7 /home/xxxx/public_html/wp-content/plugins/civicrm/civicrm/CRM/Queue/Page/AJAX.php(47): CRM_Queue_ErrorPolicy->call(Object(Closure))
#8 [internal function](): CRM_Queue_Page_AJAX::runNext((Array:5))
#9 /home/hazwe1/public_html/wp-content/plugins/civicrm/civicrm/CRM/Core/Invoke.php(289): call_user_func((Array:2), (Array:5))
#10 /home/hazwe1/public_html/wp-content/plugins/civicrm/civicrm/CRM/Core/Invoke.php(72): CRM_Core_Invoke::runItem((Array:13))
#11 /home/hazwe1/public_html/wp-content/plugins/civicrm/civicrm/CRM/Core/Invoke.php(52): CRM_Core_Invoke::_invoke((Array:5))
#12 /home/hazwe1/public_html/wp-content/plugins/civicrm/civicrm.php(463): CRM_Core_Invoke::invoke((Array:5))
#13 [internal function](): CiviCRM_For_WordPress->invoke("")
#14 /home/hazwe1/public_html/wp-includes/plugin.php(406): call_user_func_array((Array:2), (Array:1))
#15 /home/hazwe1/public_html/wp-admin/admin.php(149): do_action("toplevel_page_CiviCRM")
#16 {main}

True on upgrade to 4.4B2 as well.
Interpolat Solutions, LLC
Connecting the dots for you!
http://www.interpolat.com

totten

  • Administrator
  • Ask me questions
  • *****
  • Posts: 695
  • Karma: 64
Re: Upgrade of 4.3.5 to 4.4 glitch
September 12, 2013, 12:34:26 pm
@clarkac, can you locate the CiviCRM log file and see if there are more error messages that correspond to the upgrade? (In Drupal, the log file would usually be under sites/XXX/files/civicrm/ConfigAndLog.)

@jmdezigns, are you getting the error when upgrading directly from 4.3.5 => 4.4beta1? Or has the system taken a different path? Can you use an SQL client to run the query "select locale_custom_strings from civicrm_domain;" on the original database and post the result?


clarkac

  • Administrator
  • Ask me questions
  • *****
  • Posts: 399
  • Karma: 11
  • CiviCRM version: 4.4.11 & 4.5.5
  • CMS version: Drupal 7
  • MySQL version: 5.1.61-cll
  • PHP version: 5.3.27
Re: Upgrade of 4.3.5 to 4.4 glitch
September 12, 2013, 01:11:45 pm
Here's the log file with the error, attached.  (I had to rename the extension to .txt from .log)
Andy Clark

clarkac

  • Administrator
  • Ask me questions
  • *****
  • Posts: 399
  • Karma: 11
  • CiviCRM version: 4.4.11 & 4.5.5
  • CMS version: Drupal 7
  • MySQL version: 5.1.61-cll
  • PHP version: 5.3.27
Re: Upgrade of 4.3.5 to 4.4 glitch
September 12, 2013, 01:22:51 pm
Another similar problem; upgrading beta 1 to beta 2.  The following occurred, but the database appears to have converted OK.
Although I have not done any testing, just took a quick look at the data.
=======================================================

Exception: "A fatal error was triggered: Could not find valid value for qrid"

#0 /home/powyscon/public_html/cbcew/sites/all/modules/civicrm/CRM/Utils/Request.php(106): CRM_Core_Error::fatal("Could not find valid value for qrid")
#1 /home/powyscon/public_html/cbcew/sites/all/modules/civicrm/CRM/Queue/Page/AJAX.php(39): CRM_Utils_Request::retrieve("qrid", "String", NULL, TRUE, NULL, "POST")
#2 /home/powyscon/public_html/cbcew/sites/all/modules/civicrm/CRM/Queue/ErrorPolicy.php(80): {closure}()
#3 /home/powyscon/public_html/cbcew/sites/all/modules/civicrm/CRM/Queue/Page/AJAX.php(47): CRM_Queue_ErrorPolicy->call(Object(Closure))
#4 [internal function](): CRM_Queue_Page_AJAX::runNext((Array:5))
#5 /home/powyscon/public_html/cbcew/sites/all/modules/civicrm/CRM/Core/Invoke.php(289): call_user_func((Array:2), (Array:5))
#6 /home/powyscon/public_html/cbcew/sites/all/modules/civicrm/CRM/Core/Invoke.php(72): CRM_Core_Invoke::runItem((Array:13))
#7 /home/powyscon/public_html/cbcew/sites/all/modules/civicrm/CRM/Core/Invoke.php(52): CRM_Core_Invoke::_invoke((Array:5))
#8 /home/powyscon/public_html/cbcew/sites/all/modules/civicrm/drupal/civicrm.module(436): CRM_Core_Invoke::invoke((Array:5))
#9 [internal function](): civicrm_invoke("upgrade", "queue", "ajax", "runNext")
#10 /home/powyscon/public_html/cbcew/includes/menu.inc(517): call_user_func_array("civicrm_invoke", (Array:4))
#11 /home/powyscon/public_html/cbcew/index.php(21): menu_execute_active_handler()
#12 {main}
Andy Clark

Interpolat

  • I post frequently
  • ***
  • Posts: 140
  • Karma: -1
    • Interpolat Solutions, LLC.
  • CiviCRM version: 4.4+
  • CMS version: Wordpress
  • MySQL version: 5.5+
  • PHP version: 5.4+
Re: Upgrade of 4.3.5 to 4.4 glitch
September 12, 2013, 05:01:22 pm
@totten:  I ran the script using phpmyadmin and get this error message:

#1054 - Unknown column 'locale_custom_strings' in 'field list'
Interpolat Solutions, LLC
Connecting the dots for you!
http://www.interpolat.com

totten

  • Administrator
  • Ask me questions
  • *****
  • Posts: 695
  • Karma: 64
Re: Upgrade of 4.3.5 to 4.4 glitch
September 12, 2013, 06:01:55 pm
@clarkac, to make sure I understand: you're trying to upgrade to 4.4.beta2 but get an error that it's already upgraded to 4.4.beta1? You should make sure that there's only one copy of CiviCRM in use, e.g.

find /path/to/drupal/root -name civicrm-version.php

There should only be one match. If you have an old backup copy of the CiviCRM code in the Drupal tree, then it might confuse things.

@jmdezigns, that's quite suspicious. Are you sure that it's upgrading from 4.3.5=>4.4.x, that you ran the query against the original 4.3.5 database, and that the civicrm.settings.php points to the right database? That column has existed since CiviCRM 3.2, and your installation of 4.3.5 wouldn't work if the column were missing.

Interpolat

  • I post frequently
  • ***
  • Posts: 140
  • Karma: -1
    • Interpolat Solutions, LLC.
  • CiviCRM version: 4.4+
  • CMS version: Wordpress
  • MySQL version: 5.5+
  • PHP version: 5.4+
Re: Upgrade of 4.3.5 to 4.4 glitch
September 12, 2013, 08:29:21 pm
@totten:  The current installation does say 4.3.5, and for the most part, it appears to be a functional installation.  The only issue I have noted and have been unable to resolve is failure of dashlets to run, within the Civi dashboard.  I have rechecked my settings file, and it is pointing to the only Civi database I have.

Is there anything I can/should do to make sure the column is added?  WHat does this mean for the installation going forward.  Yes, the upgrade attempt is from 4.3.5 to 4.4.
Interpolat Solutions, LLC
Connecting the dots for you!
http://www.interpolat.com

clarkac

  • Administrator
  • Ask me questions
  • *****
  • Posts: 399
  • Karma: 11
  • CiviCRM version: 4.4.11 & 4.5.5
  • CMS version: Drupal 7
  • MySQL version: 5.1.61-cll
  • PHP version: 5.3.27
Re: Upgrade of 4.3.5 to 4.4 glitch
September 13, 2013, 12:57:51 am
I've only got one copy of CiviCRM.  I converted a production copy from 4.3.5 to Alpha1 , then Alpha2 and Alpha3 and then through to Beta1 and got the error where I attached the log for you.  I then upgraded that to Beta2 and got the error you see in my last post.  So, just one copy but each upgrade has glitched in different ways.  If you like, I could start over and upgrade again from 4.3.5 to Beta2 - would that help?
Andy Clark

totten

  • Administrator
  • Ask me questions
  • *****
  • Posts: 695
  • Karma: 64
Re: Upgrade of 4.3.5 to 4.4 glitch
September 13, 2013, 03:01:35 pm
@clarkac, yeah, it would be a good idea to try a fresher upgrade -- e.g. re-download/re-extract the tarball for 4.4.beta2, and upgrade from 4.3.5=>4.4beta2.

@jmdezigns, since you've got phpmyadmin, can you try browsing through its UI to find the "civicrm_domain" table and confirm whether the "locale_custom_strings" column exists in your 4.3.5 DB. And then:

 * If it doesn't exist, create it ("alter table civicrm_domain add column `locale_custom_strings` text COLLATE utf8_unicode_ci COMMENT 'Locale specific string overrides';")... and re-try the upgrade.
 * If does exist, then get a listing and paste the results here.

desierto

  • I’m new here
  • *
  • Posts: 12
  • Karma: 0
  • CiviCRM version: 4.6.2
  • CMS version: Drupal 7.36
Re: Upgrade of 4.3.5 to 4.4 glitch
September 13, 2013, 03:44:26 pm
I attempted the upgrade from 4.3.5 to 4.4 by deleting and uploading the new codebase, but when I tried to go through the DB upgrade I just get a white screen of death. Drupal will still work, but something with the theme was messed up. The Drupal log entry says:

Warning: call_user_func_array() expects parameter 1 to be a valid callback, function 'civicrm_invoke' not found or invalid function name in menu_execute_active_handler() (line 517 of /home3/desierto/public_html/includes/menu.inc).

I'm also getting:

DatabaseDriverNotSpecifiedException: Driver not specified for this database connection: backup_migrate_tmp_52338e49b5ac8 in Database::openConnection() (line 1679 of /home3/desierto/public_html/includes/database/database.inc).

I will return to 4.3.5 codebase and re-attempt another time.

clarkac

  • Administrator
  • Ask me questions
  • *****
  • Posts: 399
  • Karma: 11
  • CiviCRM version: 4.4.11 & 4.5.5
  • CMS version: Drupal 7
  • MySQL version: 5.1.61-cll
  • PHP version: 5.3.27
Re: Upgrade of 4.3.5 to 4.4 glitch
September 14, 2013, 05:48:33 am
I reloaded the latest copy of my 4.3.5 production database and upgraded it to 4.4.  It upgraded without any problems or error messages.  Thanks!

I found a problem with custom fields that I'll post separately.
Andy Clark

Interpolat

  • I post frequently
  • ***
  • Posts: 140
  • Karma: -1
    • Interpolat Solutions, LLC.
  • CiviCRM version: 4.4+
  • CMS version: Wordpress
  • MySQL version: 5.5+
  • PHP version: 5.4+
Re: Upgrade of 4.3.5 to 4.4 glitch
September 14, 2013, 06:41:44 am
@totten.

So the column does exist. 

I re-ran the sql script you asked me to run earlier, and on the resulting window, I get the message:
Quote
This table does not contain a unique column. Grid edit, checkbox, Edit, Copy and Delete features are not available.

I have attached a screenshot of this resulting window.

By "get a listing" I assume you were asking for this:

Code: [Select]
Rows locale_custom_strings
Locale specific string overrides
1 a:1:{s:5:"en_US";a:2:{s:7:"enabled";a:2:{s:13:"wildcardMatch";a:5:{s:12:"Contribution";s:8:"Donation";s:10:"Contribute";s:6:"Donate";s:12:"contribution";s:8:"donation";s:10:"contribute";s:6:"donate";s:16:"Your Donation(s)";s:23:"Your Recent Donation(s)";}s:10:"exactMatch";a:11:{s:5:"Grant";s:12:"Disbursement";s:5:"grant";s:12:"disbursement";s:18:"Your Membership(s)";s:43:"Your Donor's Club & Other HAZ Membership(s)";s:24:"Edit Contact Information";s:34:"Edit Related Contact's Information";s:29:"Your Contacts / Organizations";s:37:"Your Related Contacts / Organizations";s:20:"Confirm Contribution";s:7:"Confirm";s:19:"Contribution Amount";s:15:"Donation Amount";s:7:"grants ";s:14:"disbursements ";s:14:"Amount Granted";s:16:"Amount Disbursed";s:4:"Save";s:6:"Submit";s:10:"Contribute";s:6:"Submit";}}s:8:"disabled";a:2:{s:13:"wildcardMatch";a:0:{}s:10:"exactMatch";a:0:{}}}}
« Last Edit: September 14, 2013, 12:31:20 pm by jmdezigns »
Interpolat Solutions, LLC
Connecting the dots for you!
http://www.interpolat.com

Interpolat

  • I post frequently
  • ***
  • Posts: 140
  • Karma: -1
    • Interpolat Solutions, LLC.
  • CiviCRM version: 4.4+
  • CMS version: Wordpress
  • MySQL version: 5.5+
  • PHP version: 5.4+
Re: Upgrade of 4.3.5 to 4.4 glitch
September 18, 2013, 10:14:33 pm
Any help, anyone!!? ???
Interpolat Solutions, LLC
Connecting the dots for you!
http://www.interpolat.com

Pages: [1] 2
  • CiviCRM Community Forums (archive) »
  • Old sections (read-only, deprecated) »
  • Discussion (deprecated) »
  • Alpha and Beta Release Testing »
  • 4.4 Release Testing »
  • Upgrade of 4.3.5 to 4.4 glitch

This forum was archived on 2017-11-26.