Migration Issues

[prakharcse]

Hi

I have migrated civicrm 3.2 to civicrm 4.2.13 from d6 to d7 . I have migrated successfully. But  some links are broken inside the crm and showing following error

Sorry but we are not able to provide this at the moment.
DB Error: no such field
Return to home page.

For example page like
?q=civicrm/member&reset=1
?q=civicrm/event&reset=1
etc. are showing same error.

Also going through configandlog of civicrm i found following errors:

Feb 06 00:56:55  [info] $Fatal Error Details = Array
(
    [callback] => Array
        (
           

• => CRM_Core_Error
[1] => handle
        )

   

Code: [Select]

=> -18
    [message] => DB Error: no such table
    [mode] => 16
    [debug_info] => SELECT MAX(id) FROM civicrm_sms_provider WHERE is_active = 1 [nativecode=1146 ** Table 'final.civicrm_sms_provider' doesn't exist]
    [type] => DB_Error
    [user_info] => SELECT MAX(id) FROM civicrm_sms_provider WHERE is_active = 1 [nativecode=1146 ** Table 'final.civicrm_sms_provider' 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 MAX(id) FROM civicrm_sms_provider WHERE is_active = 1 [nativecode=1146 ** Table 'final.civicrm_sms_provider' doesn't exist]"]
)

Please Help me out of this.

[Erik Hommel]

Did you migrate step by step? There is a link on migration D6 -> D7 and Civi at the same time:
https://civicrm.org/blogs/spidersilk/best-practices-upgrading-drupal-6-7-and-civicrm-3-4-same-time

[prakharcse]

Yes I have performed migration same way as mentioned in that blog.

[Erik Hommel]

Hmm most cases I have heard off when tables where not there where caused by not following the incremental path when upgrading. I assume all your database rights were OK so tables could have been created?

[prakharcse]

Is there any other way to get rid from this error.

[balleyne]

Are you sure it's 4.2.13?

In your first message ( http://forum.civicrm.org/index.php/topic,31553.msg135193.html#msg135193 ), you said:

I am migrating d6 to d7 same time i have to migrate civicrm 3.2 to civicrm 4.4.3

But in this thread, you said:

I have migrated civicrm 3.2 to civicrm 4.2.13 from d6 to d7

And, then, in your first post to the other thread, you said the error message was:

Your database is marked with an unexpected version number: 4.4.3. The v4.2.13 codebase may not be compatible with your database state.

So...

• Assuming you followed in instructions the same way as mentioned in the blog, which version of CiviCRM did you actually upgrade to under Drupal 6? 4.2.13 or 4.4.3?
• When you moved from D6 to D7, are you sure that you changed from the D6 version of CiviCRM to the same corresponding D7 version of CiviCRM? (i.e. civicrm-4.2.13-drupal6 => civicrm-4.2.13-drupal OR civicrm-4.4.3-drupal6 => civicrm-4.4.3-drupal)
  

It seems like you may have mixed up the versions during your process... See Hershel's recommendations here as well, for getting a fresh copy of the correct code: http://forum.civicrm.org/index.php/topic,31565.msg135223.html#msg135223


As Erik mentioned, this is often a problem with the upgrade path, I think. I'm pretty sure that the table civicrm_sms_provider does not exist in CiviCRM 3.2 (I don't see any reference to it in the CiviCRM 3.2 codebase when I search the entire codebase for "sms_provider", nor do I see it in the database of an operational 3.2 CiviCRM installation.) My guess is that this table (and likely some others?) should have been created at some point during the proper incremental upgrade path...

Did you follow the official upgrade documentation, in particular around running the CiviCRM Upgrade Script e.g. for 4.4.x
http://wiki.civicrm.org/confluence/display/CRMDOC/Upgrade+Drupal+Sites+to+4.4+-+Drupal+6#UpgradeDrupalSitesto4.4-Drupal6-9.RuntheUpgradescript
http://wiki.civicrm.org/confluence/display/CRMDOC/Upgrade+Drupal+Sites+to+4.4+-+Drupal+7#UpgradeDrupalSitesto4.4-Drupal7-10.RuntheUpgradescript

Note that this is not the same as Drupal's update.php. Also, I'm not sure whether it'd be safe or wise to just run that at this point, as I'm not sure what the current state of the CiviCRM installation is like... not sure what to suggest, beyond making backups before trying anything in case you need to revert.

Hope that helps...

[prakharcse]

hi balleyne,

Actually now i am upgrading 3.4.4 to 4.2.13 civicrm. Now when I start upgrading the version of civicrm on drupal6  it gives me error which i am sharing with you in this  post. Also when i enable the debugger of civicrm then on error pages i got following db errors.

[Eileen]

So, the first screen shot is telling you it is about to do some clean ups on your data which you might like to read about & renew. These include things like more than one membership linked to one contribution.  Did you click on the link to do the cleanup?

I think if I were you I would upgrade to 4.1, possibly do those cleanups, get your db all backed up. Update the UF_NAME setting in your civicrm.settings.php and then proceed.