Error -Upgrading from 4.0.7 to 4.3.5 fails

[Aahar]

Trying to upgrade civicrm 4.0.7 to 4.3.5 I get a kind of incomplete info page. Please see the screenshot in the attached file.

Clicking on "Retry" or "Skip" does not respond.

And when I try to access civicrm it says "Fatal DB error, exiting, seems like your schema does not have civicrm_setting table"

I have followed the steps mentioned in "http://wiki.civicrm.org/confluence/display/CRMDOC43/Upgrade+Drupal+Sites+to+4.3+-+Drupal+7#UpgradeDrupalSitesto4.3-Drupal7-6.DisableLogging"

Where could I be going wrong. Please suggest.

[Hershel]

This is a problem with your JS files not being included correctly on the upgrade page. What you should do is be sure to remove all template files and clear any caches and perhaps delete the Config.IDS.ini file which is in sites/default/files/civicrm/upload/ I think. Then try again.

If that fails, then you should revert to the previous version, try all these cache clearing items, and try visiting the URL Resources page in CiviCRM admin and make sure it's correct and then try again.

[Aahar]

I did all that you suggested. But I continue to get the same error.

1) When you said " clean all templates", I assumed you mean clean all files under "template_c". Is that correct?
2) Another thing, in Drupal Configuration, Media, File System, the temporary directory is /tmp. Is that correct?

[Hershel]

1 Yes
2 Yes, in your case, that is correct

[Aahar]

Wtih no other option left I tried upgrading to 4.1 from 4.07 and it has upgraded successfully to 4.1

I can now see the civicrm_setting table.

Now I will try to upgrade to 4.2

[Aahar]

Upgrade to 4.2 from 4.1 was successful.

Upgrade to 4.3 from 4.2 was smooth... .but...

 the Contacts View are not displayed correctly .. the tabs does not work fine... [ see image attached]
And it does not do a in-page edit. Clicking on the fields does not respond.   Clicking on tabs loads a new page with plain text....

[Aahar]

The Contacts View (tabs) are not displayed and not working correctly on upgrading from 4.2.0 to 4.3.0 (on drupal 7.22). See Screenshot.

I found following errors in Browser Console
===============================
GET http://mysite/sites/all/modules/civicrm/packages/jquery/jquery-ui-1.8.11/css/smoothness/jquery-ui-1.8.11.custom.css 404 (Not Found) (program):107
GET http://mysite/sites/all/modules/civicrm/packages/jquery/plugins/jsTree.v.1.0rc2/themes/default/jstree.css 404 (Not Found) (program):115
GET http://mysite/sites/all/modules/civicrm/packages/jquery/plugins/DataTables-1.7.6/media/css/demo_table_jui.css 404 (Not Found)
===========================================

I am on Drupal 7.22 CiviCRM 4.3.0

And when I checked the path "sites/all/modules/civicrm/packages/jquery/" it had a higher verison of jQuery i.e., "jquery-ui-1.9.0" instead of jquery-ui-1.8.11.

and in place of  "jsTree.v.1.0rc2" it has "jquery.jstree.js"
and in place of "DataTables-1.7.6" it is has "DataTables"


Starting a new topic: http://forum.civicrm.org/index.php/topic,29515.0.html

[mlampard]

OK, I spent a few hours with this "[ ] retry skip" issue, so am posting what I did in the hope that others may benefit....

I tried upgrading from version 4.0 to 4.3.5 and received the above very unhelpful "[ ] retry skip" page. I was using the documentation here: http://wiki.civicrm.org/confluence/display/CRMDOC/Upgrade+Drupal+Sites+to+4.3+-+Drupal+7
which specifically states that you need version 2.2 or above of civiCRM to upgrade to 4.3

So, I upgraded from 4.0 to 4.1 successfully (used same documentation - the process is the same). Note - I did not roll back to 4.0 after the 4.3.5 failure, I simply deleted sites/all/modules/civicrm and started the upgrade from step 8 in the documentation. This saved me a bunch of time.
Then I upgraded from 4.1.0 to 4.2.0 successfully
Then from 4.2.0 to 4.2.9 (I avoided 4.2.10, as the date stamp indicated it had been modified recently, so I didn't trust it)
Then from 4.2.9 to 4.3.5 was successful.

It looks like there's quite a significant change between the 4.2 and 4.3 releases, especially around jquery/AJAX/JS, so doing the staged upgrade may be necessary on some systems. I'm also running a Mac server for my implementation, so perhaps that also played into it.