CiviCRM Community Forums (archive)

I made an attempt to upgrade from 4.1.5 (Drupal 6) to 4.2.9, but inadvertently did not disable an extension module. I had already deleted the old codebase when I realized this. Disabled the extension module and then unzipped 4.2.9 codebase and attempted upgrade script. I received the "page not found" error and followed instructions from here:
http://wiki.civicrm.org/confluence/display/CRMDOC42/Upgrade+Drupal+Sites+to+4.2+-+Drupal+6
to rectify situation. Attempted the upgrade again, but it failed. So I reverted back to old codebase, renaming 4.2.9 codebase to civicrm_new.

On the Drupal modules page, CiviCRM version is showing as 4.2.9, but within CiviCRM, it's 4.1.5. And now it seems I need both the old codebase and new for CCRM to function correctly.

Any suggestions on how I can fix this?

I did have a "clean" backup, but since this happened a week ago and my client was not willing to be without their site, I had to wait until this weekend to attempt repair. I followed the instructions for "How to Deal With A Partially Upgraded Database When You Don't Have a Backup" here: http://wiki.civicrm.org/confluence/display/CRMDOC43/Ensuring+Schema+Integrity+on+Upgrades

It was a painstaking process! but glad I did. The schema was not fouled.
One issue was incorrect permissions (600) on all file-files/non-directories (?) so once permissions were changed and I deleted the /ConfigAndLog and /templates_c directories, the database was repaired.

Will attempt the upgrade again today. Thanks for responding.