Author Topic: Database partially upgraded from drupal 4.0.8 to 4.1 - error (Read 1478 times)

nsummy · February 23, 2012, 01:51:07 pm

I just upgraded from 4.0.8 to 4.1 on drupal 7. During the database upgrade an error popped up (could be because my database is over 200 megs?) Anyways I go and run the script again and get this error:

Sorry. A non-recoverable error has occurred.
Database check failed - the database looks to have been partially upgraded. You may want to reload the database with the backup and try the upgrade process again.

Of course then I find out that my "backup" is only 1 KB so I cannot restore. Everything seems to be working right now but now I'm not sure what to do, because sooner or later I'm going to have to upgrade again. or worse, something may not work. Any recommendations as to what I should do? Thanks!

Hershel · February 24, 2012, 04:42:15 am

Hmmm, interesting situation. If you lack a full backup, there's not much you can do. I would suggest you may just have to wait until an error appears, which it may not. Then when the next upgrade comes out, try that also and see what happens.

But be sure to get a full backup before doing any further upgrades.

jhofer · February 24, 2012, 10:20:49 am

I have this as well.. I get the same error message everytime I run the Contact sync between civil and drupal. It still seems to sync correctly. For me the upgrade was from 3.4 to 4.0 (drupal 6.x)

Please keep this thread posted as to and other errors you get.

chrisc · March 02, 2012, 05:33:42 am

I had this error as well when upgrading from V 3.4 to V4.1 following moving host. (Using Drupal V6.25) However, after following the advise to modify the version number back in the CiviCRM data base table civicrm_domain and doing this three times between running upgrade after each occation , it seem to have worked and it now reports I am in 4.1.

However, I do still have a problem as the site refuses to allow me to write to certain key files and folders and I can not upload images in CiviCRM (although I can in Drupal User area). It seem that the .htaccess Drupal access system is preventing CiviCRM from writing to some key files and folders so, for instance, if I try and enable a new CiviCRM component and press save CiviCRM reports :"Your changes have been saved. Do not have permission to write to file: latest-version-cache.txt" despite repeatedly checking that there are write permissions using my FTP client. This is just one example

Further investigation shows that the .htaccess file is being rewritten "deny from all" and this is happening in a number of key folders thus preventing CiviCRM from changing or completing its upgrade. This happed despite the fact that the "sync Drupal and CiviCRM role being disabled during the upgrade! I suspect this module as the Civi Member Role sync in Drupal reports:" CiviMember Membership Types or Status Rules have not been configured. Please do so on the "Administer CiviCRM" page." However, they have but no amount of re-entering fresh configurations into CiviCRM produces Civi membership types to select in the Drupal module. I have tried disabling the Path access and Civi-Druple role sync modules at various time to try and get myself out of this circular problem but still no joy.

Any thoughts? HELP!

CiviCRM Community Forums (archive)

News:

Author Topic: Database partially upgraded from drupal 4.0.8 to 4.1 - error (Read 1478 times)

nsummy

Database partially upgraded from drupal 4.0.8 to 4.1 - error

Hershel

Re: Database partially upgraded from drupal 4.0.8 to 4.1 - error

jhofer

Re: Database partially upgraded from drupal 4.0.8 to 4.1 - error

chrisc

Re: Database partially upgraded from drupal 4.0.8 to 4.1 - error