CiviCRM Community Forums (archive)

Hello folks,

Doing an upgrade in Joomla (unfamiliar territory for me).  Made a localhost copy to test out the upgrade (though know that the same issue has occured when another dev. tried this on the live site)

Have uninstalled old Civi module 3.1.3 and re-installed new Civi module 3.2.5 (alt version)

At the Extension Manager, I got the:

"CiviCRM component files have been UPGRADED succesfully.  Please run the CiviCRM Database Upgrade Utility now. This utility will check your database and perform any needed upgrades."

Message.

Went to this URL (by clicking on the link in extension manager): http://localhost/fed/administrator/index2.php?option=com_civicrm&task=civicrm/upgrade&reset=1

Sorry. A non-recoverable error has occurred.
Database check failed - the database looks to have been partially upgraded. You may want to reload the database with the backup and try the upgrade process again.

Return to home page.

Checked the version in civicrm_domain and it is 3.1.3.  And there is no civicrm_contact.is_deleted column.

Tried a couple of times but without success.  Not sure what to try next - anyone help?

Is it a case of manually running the upgrade script?

Thanks people,
Michael

couple things --

Michael -- the db upgrade script is no different than the drupal equivalent. so the message is just stating an unsuccessful upgrade, which could have been for various reasons -- a problem with the db, a timeout during upgrade, etc. you'll need to revert to your original (hopefully backed up) db and retry. i'd suggest upgrading from 3.1.3 to 3.1.6 if you're running into issues with the jump to 3.2.5. See if you can get a successful revision upgrade first. or go through the recommended steps of installing just the 3.1. tables and then import your data into it, in order to ensure a clean schema.

one other note -- in recent versions of the joomla installer you don't need to uninstall and then install -- you can install on top of the existing installation.

Hey Brian,

Thanks for the help.  Like you said, the thing to remember is that the upgrade is no different.  Good to remember.

Seems like I have spent the whole week it seems solving (other people's FWIW ) upgrade problems.  Original problem here was some missing location types (not technically their fault) but after that, that the db was actually not downgraded completely.  They had just dropped and reimported tables leaving any new tables created during the upgrade in the downgraded db.

I worked this out by applying each query in CRM/Upgrade/Incremental/SQL one by one to the db.  Which was a pain but not too bad.  Then created a script to properly clean up and downgrade.

Only aspect of this that (I realised half way though) was a bit of a pain was that there was lots of a fair amount of smarty code in there that I had to manually parse/interpret.

Would be great if there were some way to parse that smarty.  If a method doesn't exist, I can't imagine it'd be hard to create and I'll do so next time i need to do an errrrrpgrade.

And finally, I would have probably worked that out but I wasn't getting any info on why the query was failing, which I would normally see as a DB error in Drupal.  But for some reason I couldn't see it in Joomla - probably some Joomla setting i am not familiar with or I was just being stupid