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) »
  • Upgrading CiviCRM 4.3 RC1 to 4.3 Final problems
Pages: [1]

Author Topic: Upgrading CiviCRM 4.3 RC1 to 4.3 Final problems  (Read 672 times)

NASC2009

  • I post occasionally
  • **
  • Posts: 32
  • Karma: 0
Upgrading CiviCRM 4.3 RC1 to 4.3 Final problems
April 20, 2013, 08:15:17 am
After upgrading our Wordpress 3.51 site from CiviCRM 4.3 RC1 to 4.3 final we get a message at the top of the page (admin side) "Update Available, new version of CiviCRM 4.3.0 download now" , it says the same thing at the bottom of the page.

We thought we followed the upgrade instructions very carefully.

When we try it again it says it can't upgrade because the DB is partially upgraded. Use a Backup. We tried the BU, it did the same thing.

1. How can we tell what the real version is? RC1 or 4.3.0
2. Should we just wait until 4.3.1 becomes available to try it again
3. Is there a workaround, or a solution to our problem without losing our custom profiles (some have over 50 custom fields)

Thanks,

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: Upgrading CiviCRM 4.3 RC1 to 4.3 Final problems
April 20, 2013, 08:28:42 am

1. civi does not have RC releases, so not sure where u got RC1 from

2. 4.3.1 is out and fixes the erroneous update available message

if your DB is in a partial upgrade state, it means the previous upgrade did not finish / aborted. You'll need to figure out what/where it died and manually fix the DB

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

NASC2009

  • I post occasionally
  • **
  • Posts: 32
  • Karma: 0
Re: Upgrading CiviCRM 4.3 RC1 to 4.3 Final problems
April 20, 2013, 08:35:44 am
Thanks for the quick reply.

Then two questions:

Will upgrading to 4.3.1 fix the problem or will it still say the db is partially upgraded?

If we can't find why the update failed, is there any way to save our profiles and start from scratch?

How would we go about finding out where the upgrade failed. What do we ask our developer to do?

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: Upgrading CiviCRM 4.3 RC1 to 4.3 Final problems
April 20, 2013, 08:43:53 am

1. upgrading will not fix the partially upgraded DB issue

2. There are a few scripts that can help you with it, but they are all developer based and dont have any clean UI. You can use the API and/or the scripts in bin/migrate

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

Michael McAndrew

  • Forum Godess / God
  • I live on this forum
  • *****
  • Posts: 1274
  • Karma: 55
    • Third Sector Design
  • CiviCRM version: various
  • CMS version: Nearly always Drupal
  • MySQL version: 5.5
  • PHP version: 5.3
Re: Upgrading CiviCRM 4.3 RC1 to 4.3 Final problems
April 20, 2013, 11:31:57 pm
Quote
If we can't find why the update failed, is there any way to save our profiles and start from scratch?

do you have a copy from before you tried the upgrade? if so you could start again there (in general, you should always do thorough testing before upgrading a live DB)

Quote
How would we go about finding out where the upgrade failed. What do we ask our developer to do?

The database upgrade is basically a series of SQL statements that you can have a look at.  If you know mysql, you should be able to work out at what point the upgrade failed by looking at your DB and looking at what the upgrade scripts would do, and then working out what the last one to be applied was.

Obviously you or your developer will need to be comfortable with SQL to do this.
Service providers: Grow your business, build your reputation and support CiviCRM. Become a partner today
Pages: [1]
  • CiviCRM Community Forums (archive) »
  • Old sections (read-only, deprecated) »
  • Support »
  • Upgrading CiviCRM (Moderator: Deepak Srivastava) »
  • Upgrading CiviCRM 4.3 RC1 to 4.3 Final problems

This forum was archived on 2017-11-26.