CiviCRM Community Forums (archive)

*

News:

Have a question about CiviCRM?
Get it answered quickly at the new
CiviCRM Stack Exchange Q+A site

This forum was archived on 25 November 2017. Learn more.
How to get involved.
What to do if you think you've found a bug.



  • CiviCRM Community Forums (archive) »
  • Old sections (read-only, deprecated) »
  • Support »
  • Upgrading CiviCRM (Moderator: Deepak Srivastava) »
  • backTrace error on upgrade from 2.0.4 to 2.1
Pages: [1]

Author Topic: backTrace error on upgrade from 2.0.4 to 2.1  (Read 3133 times)

Durruti

  • I post occasionally
  • **
  • Posts: 49
  • Karma: 1
    • The Kindling Trust
  • CiviCRM version: 3.4
  • CMS version: Drupal 6.20
  • MySQL version: 5.0.77
  • PHP version: 5.2.17
backTrace error on upgrade from 2.0.4 to 2.1
October 22, 2008, 09:56:51 am
After successfully upgrading drupal to version 6 and copying the new civicrm files across, when check the CiviCRM checkbox on my modules page I am confronted with the following page. I've tried restoring the both databases (drupal and CiviCRM) and repeating the process, with the same results.

Any ideas about what might be causing it?
Many thanks in advance, Durruti. ???

Code: [Select]
backTrace

/home/alaskapa/public_html/drupal/sites/all/modules/civicrm/CRM/Core/Error.php, backtrace, 138
, handle,
/home/alaskapa/public_html/drupal/sites/all/modules/civicrm/packages/PEAR.php, call_user_func, 912
/home/alaskapa/public_html/drupal/sites/all/modules/civicrm/packages/DB.php, PEAR_Error, 966
/home/alaskapa/public_html/drupal/sites/all/modules/civicrm/packages/PEAR.php, DB_Error, 574
/home/alaskapa/public_html/drupal/sites/all/modules/civicrm/packages/DB/common.php, raiseError, 1903
/home/alaskapa/public_html/drupal/sites/all/modules/civicrm/packages/DB/mysql.php, raiseError, 898
/home/alaskapa/public_html/drupal/sites/all/modules/civicrm/packages/DB/mysql.php, mysqlRaiseError, 327
/home/alaskapa/public_html/drupal/sites/all/modules/civicrm/packages/DB/common.php, simpleQuery, 1216
/home/alaskapa/public_html/drupal/sites/all/modules/civicrm/packages/DB/DataObject.php, query, 2390
/home/alaskapa/public_html/drupal/sites/all/modules/civicrm/packages/DB/DataObject.php, _query, 442
/home/alaskapa/public_html/drupal/sites/all/modules/civicrm/CRM/Core/BAO/Setting.php, find, 153
/home/alaskapa/public_html/drupal/sites/all/modules/civicrm/CRM/Core/Config.php, retrieve, 337
/home/alaskapa/public_html/drupal/sites/all/modules/civicrm/CRM/Core/Config.php, _initVariables, 183
/home/alaskapa/public_html/drupal/sites/all/modules/civicrm/drupal/civicrm.module, singleton, 245
/home/alaskapa/public_html/drupal/sites/all/modules/civicrm/drupal/civicrm.module, civicrm_initialize, 366
, civicrm_user,
/home/alaskapa/public_html/drupal/includes/module.inc, call_user_func_array, 450
/home/alaskapa/public_html/drupal/modules/user/user.module, module_invoke, 2447
/home/alaskapa/public_html/drupal/modules/user/user.module, _user_forms, 2397
, user_register,
/home/alaskapa/public_html/drupal/includes/form.inc, call_user_func_array, 358
, drupal_retrieve_form,
/home/alaskapa/public_html/drupal/includes/form.inc, call_user_func_array, 102
, drupal_get_form,
/home/alaskapa/public_html/drupal/includes/menu.inc, call_user_func_array, 346
/home/alaskapa/public_html/drupal/index.php, menu_execute_active_handler, 18

Sorry. A non-recoverable error has occurred. The error trace below might help to resolve the issue

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

    [code] => -18
    [message] => DB Error: no such table
    [mode] => 16
    [debug_info] => SELECT  config_backend, locales 
 FROM civicrm_domain
 
 
 
 
 
 [nativecode=1146 ** Table 'alaskapa_civicrm.civicrm_domain' doesn't exist]
    [type] => DB_Error
    [user_info] => SELECT  config_backend, locales 
 FROM civicrm_domain
 
 
 
 
 
 [nativecode=1146 ** Table 'alaskapa_civicrm.civicrm_domain' doesn't exist]
    [to_string] => [db_error: message="DB Error: no such table" code=-18 mode=callback callback=CRM_Core_Error::handle prefix="" info="SELECT  config_backend, locales 
 FROM civicrm_domain
 
 
 
 
 
 [nativecode=1146 ** Table 'alaskapa_civicrm.civicrm_domain' doesn't exist]"]
)



[/code]
http://feedingmanchester.org.uk

Kurund Jalmi

  • Administrator
  • I’m (like) Lobo ;)
  • *****
  • Posts: 4169
  • Karma: 128
    • CiviCRM
  • CiviCRM version: 4.x, future
  • CMS version: Drupal 7, Joomla 3.x
  • MySQL version: 5.5.x
  • PHP version: 5.4.x
Re: backTrace error on upgrade from 2.0.4 to 2.1
October 22, 2008, 11:11:40 am
Can you check if you have correct CiviCRM database settings in civicrm.settings.php

Kurund
Found this reply helpful? Support CiviCRM

Durruti

  • I post occasionally
  • **
  • Posts: 49
  • Karma: 1
    • The Kindling Trust
  • CiviCRM version: 3.4
  • CMS version: Drupal 6.20
  • MySQL version: 5.0.77
  • PHP version: 5.2.17
Re: backTrace error on upgrade from 2.0.4 to 2.1
October 22, 2008, 02:03:54 pm
Hi Kurund, thanks for responding. I am using my civicrm.settings file from the previous installation, is this where I am going wrong (I note it makes reference to versions of drupal). It definitely has the correct database listed. Should I be getting a different version of the settings file from somewhere?
Many thanks,
Matt
http://feedingmanchester.org.uk

Kurund Jalmi

  • Administrator
  • I’m (like) Lobo ;)
  • *****
  • Posts: 4169
  • Karma: 128
    • CiviCRM
  • CiviCRM version: 4.x, future
  • CMS version: Drupal 7, Joomla 3.x
  • MySQL version: 5.5.x
  • PHP version: 5.4.x
Re: backTrace error on upgrade from 2.0.4 to 2.1
October 22, 2008, 04:08:37 pm
Using civicrm.settings.php from previous installation should not be problem. You should make sure that you have changed civicrm database name in civicrm.settings.php according to your new installation.

HTH

Kurund

Found this reply helpful? Support CiviCRM

Durruti

  • I post occasionally
  • **
  • Posts: 49
  • Karma: 1
    • The Kindling Trust
  • CiviCRM version: 3.4
  • CMS version: Drupal 6.20
  • MySQL version: 5.0.77
  • PHP version: 5.2.17
Re: backTrace error on upgrade from 2.0.4 to 2.1
October 23, 2008, 01:25:58 am
Hi Kurund, thanks for your help.
I am using the same database as in the previous installation, my understanding is that I should just be able to use the existing database and use update.php. Is this not right? Do I need to create a new database and then import the data? Is there anything I can usefully post that might help others to identify where I'm going wrong?
Many thanks again,
durruti
http://feedingmanchester.org.uk

Donald Lobo

  • Administrator
  • I’m (like) Lobo ;)
  • *****
  • Posts: 15963
  • Karma: 470
    • CiviCRM site
  • CiviCRM version: 4.2+
  • CMS version: Drupal 7, Joomla 2.5+
  • MySQL version: 5.5.x
  • PHP version: 5.4.x
Re: backTrace error on upgrade from 2.0.4 to 2.1
October 23, 2008, 05:34:39 am

the error basically says:

Code: [Select]
Table 'alaskapa_civicrm.civicrm_domain' doesn't exist

I'd check the db alaskapa_civicrm and see if civicrm_domain does exist? I suspect not. Do other civicrm tables exist in that db? If so, where/how did civicrm_domain disappear

lobo
A new CiviCRM Q&A resource needs YOUR help to get started. Visit our StackExchange proposed site, sign up and vote on 5 questions

Durruti

  • I post occasionally
  • **
  • Posts: 49
  • Karma: 1
    • The Kindling Trust
  • CiviCRM version: 3.4
  • CMS version: Drupal 6.20
  • MySQL version: 5.0.77
  • PHP version: 5.2.17
Re: backTrace error on upgrade from 2.0.4 to 2.1
October 23, 2008, 02:10:27 pm
Hi Lobo,
I think you are getting to the nub of this problem, following on from what kurund (but that I didn't fully understand at the time). I do have a 'civicrm_domain' in my database but my database is not called 'alaskapa_civicrm' but 'mrsn_civicrm'.

In my civicrm.settings.php my database is set to;

$civicrm_root = '/data01/mrsn/public_html/directory/sites/all/modules/civicrm';

Where as the error is showing it as:

/home/alaskapa/public_html/drupal/sites/all/modules/civicrm

The site is hosted on a UK web host and I don't have access to the first two directories here, the first I see is the public_html folder. Do I need to put the new file directory listing in my settings.php (and where do I start from)? Also I haven't changed webhost, do you have any idea how this might have happened?

Many thanks for all your help, things are starting to seem less hopeless (though the site is still down).
durruti
http://feedingmanchester.org.uk

Kurund Jalmi

  • Administrator
  • I’m (like) Lobo ;)
  • *****
  • Posts: 4169
  • Karma: 128
    • CiviCRM
  • CiviCRM version: 4.x, future
  • CMS version: Drupal 7, Joomla 3.x
  • MySQL version: 5.5.x
  • PHP version: 5.4.x
Re: backTrace error on upgrade from 2.0.4 to 2.1
October 23, 2008, 03:13:24 pm
Quote
$civicrm_root = '/data01/mrsn/public_html/directory/sites/all/modules/civicrm';
This is file system path.

Quote
define( 'CIVICRM_DSN', 'mysql://crm_db_username:crm_db_password@db_server/crm_database?new_link=true');
This are database settings.

HTH

Kurund
Found this reply helpful? Support CiviCRM

Pages: [1]
  • CiviCRM Community Forums (archive) »
  • Old sections (read-only, deprecated) »
  • Support »
  • Upgrading CiviCRM (Moderator: Deepak Srivastava) »
  • backTrace error on upgrade from 2.0.4 to 2.1

This forum was archived on 2017-11-26.