CiviCRM Community Forums (archive)

Hi,
I am trying to upgrade 4.1.6 to 4.2.7, and have encountered "DB error: already exists" when executing "CREATE TABLE civicrm_sms_provider..." during the step labeled "[Executed: Upgrade DB to 4.2.alpha1]". I have attached a screen shot if it is useful.
I am about to try the upgrade with all themes disabled/stripped back to Garland, as per the response to garthb by lobo :-)
Is it helpful to go by smaller increments? i.e. 4.1.6 - 4.2.0, then 4.2.1, 4.2.2, etc.?

Hi Stoob,
Although the civicrm_domain table shows the version as 4.1.6, the civicrm_sms_provider table is indeed there in the db schema.

So, thanks for your reply, as it is confirmation that there is leftover crud, and it is indeed from a previous failed upgrade. I've seen the link you provided, and can deal with the instructions it contains, and appreciate the confirmation that it is the valid info to follow!

One 'curious' question. Where do you find the schema is for a given upgrade, or perhaps a diff list between upgrades?

Just fyi: There were failed attempts to upgrade three months ago, by my hosting software dev team, who decided that there were permissions issues on the server that have now apparently been fixed. The backups from then exist, but are very stale, as we have done much work since then to prepare civi for online registration of the yearly main event in February. Finally, I'm trying to go to 4.2.7 because it solves flow problems with payment options for the user, specifically between online and offline payment. As far as I can tell from testing and forums, 4.1.6 ignores the 'pay offline' checkbox and marches people to paypal anyway, and this is resolved in 4.2.x. This is our last "blocker" from going live and really beginning to use civi in a day-to-day mode, which I want to happen asap, since seeing is believing... ;-)

Again, thanks!