4.2 Stable[Error: Upgrade DB to 4.2.alpha1: Price Sets] DB Error: already exists

[DerekL]

Hi All,

Almost immediately after starting the upgrade process I receive this lovely message: 

[Error: Upgrade DB to 4.2.alpha1: Price Sets]
DB Error: already exists

Some googling turned up these:

http://issues.civicrm.org/jira/browse/CRM-10253

http://issues.civicrm.org/jira/browse/CRM-10613

Although they bugs are reported as squashed, I'm getting this show-stopper error...


Any ideas?

[Dave Greenberg]

Are you actually using the 4.2.alpha1 download? Quite a few download bugs were fixed in subsequent 4.2 alpha and beta releases - AND 4.2 stable was released today. Best to download 4.2 stable and start the upgrade again (of course on a test copy of your site :-) ).

[DerekL]

Hi Dave,

Yes, I'm referring to 4.2 stable. I downloaded it upon release as we've been waiting for a non-beta release anxiously.

I'm really sorta stuck as the error message doesn't provide any details + I can't seem to find any upgrade logs.

When I skipped through the error (+ all the additional ones caused by skipping the first one I'm sure) civicontribute crashes out due to a missing field in a sql query.  (Our production environment is safe and sound.)

What can I do to get to the bottom of this?

(Any help whatsoever would be super appreciated.)

[Dave Greenberg]

Derek - Fastest way to figure this out is if you can email a dump of your DB so we can run the upgrade and see what's happening. I'll send you a PM with more info.

[Rar9]

This look similar to my error that  just posted... http://forum.civicrm.org/index.php/topic,25756.0.html

[Deepak Srivastava]

We investigated the DB and filed an issue here - http://issues.civicrm.org/jira/browse/CRM-10702.

An immediate work around could be applying the below patch ( would recommend to take patch from the jira issue once ready ) -

Code: [Select]

Index: CRM/Upgrade/Incremental/php/FourTwo.php
===================================================================
--- CRM/Upgrade/Incremental/php/FourTwo.php (revision 42061)
+++ CRM/Upgrade/Incremental/php/FourTwo.php (working copy)
@@ -375,7 +375,7 @@
       $setParams['name'] = $pageTitle;
     }
     else {
-      $setParams['name'] = $pageTitle . '_' . rand(1, 99);
+      $setParams['name'] = $pageTitle . '_' . rand(1, 40000);
     }


[DerekL]

Hi Deepak,

I appreciate the help!

I downloaded the 4 raw files from the jira ticket and replaced my stock 4.2 files with them.

Unfortunately, I'm still getting an error:

[Error: Upgrade DB to 4.2.alpha1: SQL]
DB: Error: already exists

message, and a hard stop.
---
Note: The error is now no longer [Error: Upgrade DB to 4.2.alpha1: Price Sets], but [Error: Upgrade DB to 4.2.alpha1: SQL].


In addition, I tried replacing the timestamp append with the expanded rand range suggested above, with the same results. 

Any ideas? Any way to make the errors more verbose?

[Deepak Srivastava]

Derek, you will also need to restore your database from backup before re-trying the upgrade.

[DerekL]

Deepak, thanks for the response. I'm restoring a fully blank-slate snapshot of the site onto my local dev to test again now.

[ylavoie]

I am also experimenting the same problem when upgrading from 4.1.5 to 4.2.

I have a multi-lingual system and upgrade was initialy failing with 8 invalid views (probably leftovers from previous updates). After removal of civicrm_group_en_US view and 7 other similar (it_IT, es_ES, fr_CA and same for civicrm_survey_en_US...), and now have DB Error: already exists during the DB upgrade.

The error happens when passing through the 4.2alpha1 step.

Any suggestions?

Thanks,

Yves

[Deepak Srivastava]

Yves,

Check the logs to see the detailed error messages.

Also apply the patch from http://issues.civicrm.org/jira/browse/CRM-10702 and see if that helps.

[DerekL]

I stand very gratefully corrected!

The patch resolved my situation handily, Civi 4.1.1 to 4.2 complete!

( First failure must have been caused by my not dropping the db before restoring. )

Thanks Deepak!

[ylavoie]

CRM-10702 was part of the solution.

After carefull examination, I found out that table civicrm_sms_provider was already there and was preventing 4.2alpha1 to succeed. After both fixes, everything went well.

Thanks

[Rar9]

CRM-10702 was part of the solution.

After carefull examination, I found out that table civicrm_sms_provider was already there and was preventing 4.2alpha1 to succeed. After both fixes, everything went well.

Thanks

Just a quick question... are the fixes in the current 4.20 download version? 
If not how can I apply these to upgrade without errors?

[Deepak Srivastava]

Rar9, You will still have to apply patch from - http://issues.civicrm.org/jira/browse/CRM-10702 or wait for v4.2.1.