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) »
  • Can't upgrade site due to past upgrade error
Pages: [1]

Author Topic: Can't upgrade site due to past upgrade error  (Read 750 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
Can't upgrade site due to past upgrade error
January 18, 2011, 04:48:26 pm
Apparently someone at some point attempted to upgrade a copy of CiviCRM that I am working on, yet ran into a bunch of errors. They didn't replace the db with the backup, they just left it like it was. Now it's been a considerable amount of time since then, so going back to the backup is no longer an option.

CiviCRM thinks it is version civicrm-3.0.2, yet in the db it thinks it is 3.1.alpha1.upgrade. I tried using db tools, but I get errors:

<code>#!/usr/bin/php CiviCRM DB Tools Version 1.2
Notice: Use of undefined constant resolve_civicrm - assumed 'resolve_civicrm' in /home/resolve/public_html/civicrm_dbtools/civicrm_db_utils.php on line 59

Notice: Undefined index: USER in /home/resolve/public_html/civicrm_dbtools/civicrm_db_utils.php on line 2164

Notice: Undefined index: argc in /home/resolve/public_html/civicrm_dbtools/civicrm_db_utils.php on line 2168
Can't connect to MySQL server on localhost: SQLSTATE[28000] [1045] Access denied for user 'nobody'@'localhost' (using password: NO)
</code>

I really need to find a way to get this fixed so I can get it upgraded. They are running into a number of errors because of it.

xavier

  • Forum Godess / God
  • I’m (like) Lobo ;)
  • *****
  • Posts: 4453
  • Karma: 161
    • Tech To The People
  • CiviCRM version: yes probably
  • CMS version: drupal
Re: Can't upgrade site due to past upgrade error
January 18, 2011, 11:16:37 pm
This tool hasn't been updated for a while on the wiki, check on dharmatech (the authors)

http://dharmatech.org/tools/index.html

and grab the latest version.

Looks like you don't run the tool from the right place. Compare with the doc.

If you can make it work, could you update the wiki to upload the latest version and clarify what is needed?

Good luck
X+
-Hackathon and data journalism about the European parliament 24-26 jan. Watch out the result

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: Can't upgrade site due to past upgrade error
January 19, 2011, 03:21:54 am
Ok, I see from the other instructions that this something that has to run via command line.

It didn't recognize "3.1.alpha1.upgrade" in the domain table, so I changed it to the correct version - 3.0.2.

I did that and then repaired a bunch of stuff in the database.

Then I back it up and try to upgrade.

It fails the db check and the domain table is changed back to version 3.1.alpha1.upgrade

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: Can't upgrade site due to past upgrade error
January 19, 2011, 03:37:49 am
Ok, ran it again, this time I deleted the few rows instead of updating them.

Then I rebuilt the database (new db, load sql, load dump from old db, etc.).

Just ran the upgrade and it worked. YAY!

Pages: [1]
  • CiviCRM Community Forums (archive) »
  • Old sections (read-only, deprecated) »
  • Support »
  • Upgrading CiviCRM (Moderator: Deepak Srivastava) »
  • Can't upgrade site due to past upgrade error

This forum was archived on 2017-11-26.