CiviCRM Community Forums (archive)

The upgrade from 4.2.7 to 4.3.3 was really problematic - I believe I was able to complete it successfully, but with quite a few heart-stopping moments. I'll set out what happened here in some detail in the hopes that it will help.

First, I'll say that this is a multi-site setup using Drupal (D7) Domain Access and that I'm also using Varnish, so the configuration is a bit of a beast. OK - here goes...

Upon first running the upgrade script, the system threw the following error:

Warning: require_once(/home/[site]/public_html/sites/all/modules/civicrm/drupal/../CRM/Core/ClassLoader.php) [function.require-once]: failed to open stream: No such file or directory in civicrm_initialize() (line 278 of /home/[site]/public_html/sites/all/modules/civicrm/drupal/civicrm.module).

Sorry but we are not able to provide this at the moment.

DB Error: no such field
Note that the initial path seems incorrect; AFAICT, it should be /home/[site]/public_html/sites/all/modules/civicrm/CRM/Core/ClassLoader.php
(I'll note here that this error occurred only once and did not reoccur during any of the subsequent steps I took below.)

In any event, I continued with the upgrade, which executed a single step and then just hung. After a while, I opened Civi in a different window and saw I had (apparently) been upgraded to 4.3.3. I continued working, but ran into several Civi errors; after one particular error, the system showed a "need to update" warning.

So I ran the upgrade script again.

The update, once again, seemed to hang after the first update. So I continued manually running the update script each time until I reached 4.3.3.

At that point, I suspected the integrity of the database, so I created a "clean" version of the database by following the procedure from http://wiki.civicrm.org/confluence/display/CRMDOC43/Ensuring+Schema+Integrity+on+Upgrades

In importing the data, I encountered the following error:

Error

SQL query:

--
-- Dumping data for table `civicrm_payment`
--
LOCK TABLES `civicrm_payment` WRITE ;

MySQL said: Documentation
#1146 - Table '[site]_civisafety.civicrm_payment' doesn't exist
I removed the civicrm.payment statement from the data file (I had no records there, fortunately) and was able to successfully import the data; I'm currently using this new, presumably "clean" database.

I presume that the civicrm.payment table should no longer exist in the latest schema and that I should also be fine if I drop that table from the upgraded database. In any event, I'm planning on using the "clean" database for now.

I'd love to get confirmation that, indeed, the civicrm.payment table should be gone and I'm also hoping that future upgrades proceed normally; I'll also add here that disabling Varnish actually causes a different set of errors, so that doesn't seem to be a solution.

Thanks for all you do - looking forward to using 4.3.3 - whew!