eberswine 0 Report post Posted August 16, 2015 Trying to upgrade to 3.2.1 from 3.1.xxAny help would be great!!Getting an application error on database:error getting database definition getTableConstraintDefinition- table ox_account_preference_assoc already exists in database XXX Quote Share this post Link to post Share on other sites
eberswine 0 Report post Posted August 17, 2015 Anyone on this ?? There has got to be someone who knows what this means ???Thanks!! Quote Share this post Link to post Share on other sites
yulman 0 Report post Posted August 18, 2015 Hi, I have same problem (http://forum.revive-adserver.com/topic/1905-errors-upgrading-to-revive-32x/), i've been trying to find the reason that this happens but i can't find the solution. Quote Share this post Link to post Share on other sites
eberswine 0 Report post Posted August 18, 2015 I guess we don't upgrade ? Quote Share this post Link to post Share on other sites
marcis 0 Report post Posted September 16, 2015 any solution or ETA on this fix? Quote Share this post Link to post Share on other sites
eberswine 0 Report post Posted October 8, 2015 I will try and upgrade the latest release tonight and let you know how it goes.I am frustrated that NO ONE FROM REVIVE TEAM commented on this yet ?? Quote Share this post Link to post Share on other sites
yulman 0 Report post Posted October 13, 2015 I also reported the problem, but still I haven't found a solution, i can't upgrade to 3.2.x.https://github.com/revive-adserver/revive-adserver/issues/603 Quote Share this post Link to post Share on other sites
hussberlin 0 Report post Posted January 6, 2016 Did anyone solve this problem?I tried multiple paths from 3.0.2. and made it up to 3.1.0. Any upgrade to versions 3.2.x ended with the above mentioned error message.I also unsuccesssfully tried 3.1.0 -> 3.2.x.There must be a trick, right? Quote Share this post Link to post Share on other sites
Bastian 0 Report post Posted March 9, 2016 I must confirm this error. I see no possibility to upgrade Revive to the current 3.2.3 Version. Any ideas are welcome. Quote Share this post Link to post Share on other sites
magicmulder 1 Report post Posted March 10, 2016 Did anyone solve this problem?I tried multiple paths from 3.0.2. and made it up to 3.1.0. Any upgrade to versions 3.2.x ended with the above mentioned error message.I also unsuccesssfully tried 3.1.0 -> 3.2.x.There must be a trick, right?Did you change the default database layout in any way? We've just successfully upgraded from 3.0.2 to 3.2.3 with no installation issues. Your error message sounds like Revive is trying to install from scratch instead of updating (because it cannot successfully detect you already have Revive installed). The *_account_preference_assoc table was added in December 2007 according to version control so an update script should not try to install it as it likely predates 3.0.2. Quote Share this post Link to post Share on other sites
Bastian 0 Report post Posted March 10, 2016 Did you change the default database layout in any way? We've just successfully upgraded from 3.0.2 to 3.2.3 with no installation issues. Your error message sounds like Revive is trying to install from scratch instead of updating (because it cannot successfully detect you already have Revive installed). The *_account_preference_assoc table was added in December 2007 according to version control so an update script should not try to install it as it likely predates 3.0.2.no, we didn't change the layout. but we continously upgraded from an really early phpadsnew-Version (2.0.11 i think) to openx (latest official) and to revive 3.0.5 in 2014. i now try to upgrade from that version to 3.2.3. Underlying PHP-Version is latest 5.3. Quote Share this post Link to post Share on other sites
Segr 0 Report post Posted March 13, 2016 SQL code to correct errors in the database:ALTER TABLE `{prefix}_banners_ox_adsense` DROP INDEX `{prefix}_banners_ox_adsense_pkey`; ALTER TABLE `{prefix}_banners_ox_adsense` ADD PRIMARY KEY (`bannerid`);After that, the update runs without errors. Quote Share this post Link to post Share on other sites
eberswine 0 Report post Posted March 25, 2016 Just upgraded to 3.2.4 using the "SQL code" above from @Segr and it worked like a charm!! Thanks to you!! Quote Share this post Link to post Share on other sites