CiviCRM Community Forums (archive)

Looks like upgrade is not run hence you get errors. Can you clear media/civicrm/templates_c directory and re-try upgrade.

Kurund

hey steve:

2 things:

1. Can u check the version column in civicrm_domain

2. Can u check the logs in media/civicrm/ConfigAndLog/ and see what the bad query is.

the above should give us a few more clues

lobo

hey steve:

dont see what joomla tables u r referring to

in the recent few releases, we've made a strong effort to use the cms specific funcitons and avoid making and db calls to the cms database

might be easier to chat on irc.  i cant see what is going on

lobo

Trying to replace the tables is not working out well because then latter on in the process the upgrade says that  "it appears you started this upgrade before"

Lobo, you told me about  the files in civicrm/CRM/Upgrade/Incremental (in IRC) but I am not sure how to execute them.   

Thanks,
Steve

I am receiving the same error symptoms as described in this topic.  I am on Joomla 2.5.14 with Civi 4.1.3, trying to upgrade to 4.3.5.
I have went through the process three times now with the same results - I am unable to access my website front or back ends now, receiving the "DB Error:  No Such Table".

This is after performing the extension upgrade and then running the database upgrade.

I have not tried going from 4.1.3 to 4.2 then 4.3.5 as the poster suggests, but I guess I will do that next.  I would really like to understand what the issue is though!

Craig

Thanks Steve.   I have made sure that all settings files were modified properly.   I just tried 4.1.3 to 4.2.10, and got another error on the database upgrade...

[Error: Create financial records for contributions]
Error 1: Call to undefined method CRM_Core_PseudoConstant::accountOptionValues() in /var/www/vhosts/vps-1101739-10368.manage.myhosting.com/httpdocs/administrator/components/com_civicrm/civicrm/CRM/Upgrade/Incremental/php/FourThree.php, line 422

Logs talk about a missing civicrm_extensions table, but it exists, and then something about an array field missing.

I am going to try an older 4.2.x image next.  This is driving me crazy.

Craig

if you are backing things out in order to rerun an upgrade with a lower version, you will need to manually delete the civicrm core files. here's what is happening.

- you're running 4.1
- you install 4.3, which copies the new codebase to /administrator/components/com_civicrm
- you run into a problem, so you decide to reinstall 4.1. you do so from the joomla extension installer
- joomla copies 4.1 codebase to the folder above. however... it does not delete what was already there -- which means your 4.1 files overwrite 4.3 (as expected), but any files found in 4.3 and NOT in 4.1 are left in place
- you run the DB upgrader, which has an auto-find function that says something like, "let me look for all the DB upgrade files in the upgrade folder and process them in order...". but the problem is, you left some of the 4.3 DB files in place, so the upgrader sees them and believes that they are valid, and tries to process them. consequently, you're triggering 4.2 and 4.3 upgrades while working with a (primarily) 4.1 codebase -- and things start erroring.

the same may be true of the DB. if you did not drop all civi tables before importing your backup, there may be 4.3 tables added in your original attempt that stick around and cause the upgrade to fail.

if you want to back things out and reinstall 4.1, you need to be complete about it:
- drop all civi tables
- reinstall from your backup
- drop all files in /administrator/components/com_civicrm (to be complete, you should remove files from /components/com_civicrm too -- though those files haven't really changed much in the last several civi versions)
- install the 4.1 codebase

at that point you should be back where you started from.
if the above seems like a pain, after getting things back and working at that point, you could use Akeeba Backup to generate a full file+DB backup. if you have the Pro version, there is a fairly painless restore tool, which helps you rollback to where the code and DB were. of course -- if you're running this on a production site, you need to be aware that Akeeba backs up the entire site, so any non-civicrm changes would be restored as well.

personally, I do the manual route as I have more control over the process, even if it's a bit more work.

as an aside -- the above is sort of the blessing/curse of Joomla's extension installer. it supports the concept of an upgrade, where you can install a new version of an extension on top of the old (something that was not possible in v1.5 without a lot of work by the extension developer). however, it does exactly that -- installs on top of the existing version -- it doesn't clean out the old files, thus creating the possibility of non-version files.

going back to the original post --
an error like that most likely has more details present in the civi log. check out /media/civicrm/ConfigAndLog and view the current log file. might be worth tailing that file in the command line while you rerun the upgrade if you suspect the error may reoccur.