Errors Upgrading 2.2.8 to 3.0 beta: "Page not found" / "...Unknown column..."

[régulo]

Hi,

Initial info:
Drupla 6.13
CiviCRM 2.2.8
MySQL version = 5.1.30
PHP version = 5.2.9

Situation:
Trying to upgrade from CiviCRM 2.2.8 to 3.0 beta 3 over Drupal. (But the same problem happened yesterday when trying to upgrade to 3.0 beta 2)


Problem 1:

When I try to run the upgrade script it says:

"Page not found"

Just to be sure, I check both options indicated after changing correspontdingly the status of my CleanURLs.

...............................................................................
*- If "clean URLs" are enabled

http://<your_drupal_home>/civicrm/upgrade?reset=1

*- If "clean URLs" are NOT enabled

http://<your_drupal_home>/?q=civicrm/upgrade&reset=1
...............................................................................

Both ways gave the same problem -"Page cannot be found"


Problem 2:

I tried to enabled CiviCRM module BEFORE running the upgrade script (according to a suggestion I read in the forum -is that correct?) but then it showed the following error:

Problem 2:
....................................

Code:

unrecoverable error
    Sorry. A non-recoverable error has occurred.

    DB Error: no such field

    Return to home page.

Error Details:

Array
(
    [callback] => Array
        (
            [0] => CRM_Core_Error
            [1] => handle
        )

    [code] => -19
    [message] => DB Error: no such field
    [mode] => 16
    [debug_info] => SELECT *
 FROM civicrm_preferences
 
 WHERE (  civicrm_preferences.domain_id = 1 )  AND (  civicrm_preferences.is_domain = 1 )
 
 
 
 [nativecode=1054 ** Unknown column 'civicrm_preferences.domain_id' in 'where clause']
    [type] => DB_Error
    [user_info] => SELECT *
 FROM civicrm_preferences
 
 WHERE (  civicrm_preferences.domain_id = 1 )  AND (  civicrm_preferences.is_domain = 1 )
 
 
 
 [nativecode=1054 ** Unknown column 'civicrm_preferences.domain_id' in 'where clause']
    [to_string] => [db_error: message="DB Error: no such field" code=-19 mode=callback callback=CRM_Core_Error::handle prefix="" info="SELECT *
 FROM civicrm_preferences
 
 WHERE (  civicrm_preferences.domain_id = 1 )  AND (  civicrm_preferences.is_domain = 1 )
 
 
 
 [nativecode=1054 ** Unknown column 'civicrm_preferences.domain_id' in 'where clause']"]
)

................................................................................
 
I found that a similar problem (with same error message) was found (and fixed) over a joomla installation:
and for Civicrm 3.0.alpha1-joomla:

http://forum.civicrm.org/index.php?topic=9230.0

http://forum.civicrm.org/index.php/topic,9191.msg39707.html#msg39707 (Solution)

...But I wouldn't know how to deal with this in the case of my Drupal installation. Don't understand if the patch would be exactly the same or even the details of how to apply it in my case -or if there is something basic that I'm missing.

Many thanks in advance,

régulo.
[/code]

[StudentsHelpingHonduras]

Hi regulo,

We're having the exact same problem...identical.  Upgrading from 2.2.8 to 3.0 beta2.  Going to try beta3 today, but likely will incur the same problem.

Lobo, any advice?



Best,

Bobby

[régulo]

Hi Bobby,


I just found that somebody else had had the same problem before:
    
DB Error when upgrading to Civicrm 3.0

Best regards,

régulo

[Deepak Srivastava]

"Page not found"

CiviCRM upgrade is part of civicrm functionality and works only if you have civicrm module enabled.

Unknown column 'civicrm_preferences.domain_id' in 'where clause'

Even if you get that error and if you have civicrm module successfully enabled, visiting the upgrade url should suppress that error and allow you to upgrade. Did you try visiting upgrade again and check ?

Disabling / Enabling civicrm module is not required and is also not mentioned in the doc.
Can you make sure you following the doc in the exact order - http://wiki.civicrm.org/confluence/display/CRMUPCOMING/Upgrade+Drupal+Sites+to+3.0

[régulo]

Hi Deepak Srivastava,

Thank you for your time and response.

I've found the cause. I had disabled CiviCRM module BEFORE trying to upgrade it.
(I did that following the "common" practice in Drupal -following for example the general recommendations found in drupal site (http://drupal.org/node/250790) or other places (like here: Upgrading Drupal modules)
I now realize  that that practice is questioned (e.g. How to upgrade a module? -see discussion on point 2.5 in that document)

In any case, you are right when you say:
 "Disabling / Enabling civicrm module is not required and is also not mentioned in the doc."

I paid attention to that and keep the CiviCRM 2.2.9 ENABLED and then the upgrade run perfectly.

What I would say is that YOU MUST keep the module enabled before deleting the initial civicrm version in order for the update script to run later.
If you disable the original (2.2.*) module before deleting it, then when you try to enable it again (after the expanding the 3.* version) you received the error message mentioned before:
...........................
 -unrecoverable error
    Sorry. A non-recoverable error has occurred.

    DB Error: no such field

    Return to home page.

Error Details:

{etc}
..................................

Than you very much again.

régulo.

[StudentsHelpingHonduras]

Hi all,

Thank you for posting so much info here.  I've gone through and tried to follow everything I see here, but now we're only getting a white screen.  Cannot load anything once we delete the old files and replace them with new files.

When I run the upgrade script, both with and without clean URLs, all I see is a white screen.

Has this happened to anyone else?


Regards,

Bobby

[régulo]

Hi Bobby,

Some times the White screen is because your configuration (core + contributer modules, etc) has reach the PHP memory limits.
Check this article for that and other causes

The White Screen of Death (Completely Blank Page)

Make a search on "drupal white page" and you'll find several articles about that problem.

Sometimes, when you install additional modules or a more consuming new upgrade of one already installed and enabled, you can have that error (lack of memory and white page).

You can try editing by hand the "system" in your drupal database table (browse (with phpMyAdmin for example) and change (from 1 to 0) the "Status" field of some modules that you don't need much in order to verify if that's the problem. Don't forget making a backup before, of course.

Hope everything goes well,

régulo