ExpressionEngine CMS
Open, Free, Amazing

Thread

This is an archived forum and the content is probably no longer relevant, but is provided here for posterity.

The active forums are here.

Error when upgrading 1.6.8 to 2.1.3

February 02, 2011 4:43pm

Subscribe [4]
  • #1 / Feb 02, 2011 4:43pm

    Kenny Fraser

    25 posts

    This question may be related to a resolved thread.

    I receive this error during the database upgrade part of the update process.  I use Solspace Super Search.  Should I upgrade to v1.7.0 first rather than 1.6.8 to 2.1.3? Thanks.

    {"error":"
    
    Error Number: 1050
    \n\n
    
    Table 'exp_snippets' already exists
    \n\n
    
    CREATE TABLE `exp_snippets` (\n `snippet_id` int(10) unsigned NOT NULL auto_increment,\n `site_id` int(4) NOT NULL,\n `snippet_name` varchar(75) NOT NULL,\n `snippet_contents` text NULL,\n PRIMARY KEY (`snippet_id`),\n KEY `site_id` (`site_id`)\n )
    \n\n
    
    Filename: updates/ud_200.php
    \n\n
    
    Line Number: 1382
    "}
  • #2 / Feb 03, 2011 6:36am

    Kenny Fraser

    25 posts

    I have upgraded my SolSpace Super Search module now and have tried again, with the same error. 

    I note the post by Ingmar here.

    If I want to try upgrading to v1.7.0 first, where can I download this?

    Thanks.

  • #3 / Feb 03, 2011 5:46pm

    Sue Crocker

    26054 posts

    Hi, Ken. See: HowTo Download 1.x Version of EE

    NOTE: The screen shot is slightly different, since now there is a 2.1.4 beta to download too.

    Does that help?

  • #4 / Feb 20, 2011 9:45am

    Kenny Fraser

    25 posts

    Thanks Sue, I’ll try it.

  • #5 / Feb 21, 2011 8:06am

    Sue Crocker

    26054 posts

    Sounds good. Let us know what happens. Make sure you clear out your database container before putting back in your 1.x database so that you don’t have any in process 2.x database tables in there. Does that help?

  • #6 / Apr 26, 2011 9:15pm

    Kenny Fraser

    25 posts

    Hi Sue (or others),

    I’m almost at the point of giving up with the upgrade to v2.1.3 unless I can get some further help here.  I managed to upgrade to v.1.7.1 but I believe my backup database DOES include some in-process 2.x tables, since I didn’t clear out the container after the original aborted attempt a while back to go from 1.6.8 to 2.1.3.

    When I try to upgrade to 2.1.3 I receive a number of database error messages.  I can bypass these by commenting out the lines one by one in the appropriate update files.  The upgrade to 2.1.3 seems to finish, the new control panel appears, as does the home page external template again - though with no weblog content, just blank. All weblogs in the control panel appear to be empty other than a single placeholder.  Comments do appear to be there though.

    Is there any hope for this database now?  Can I alternatively ‘export’ the existing weblog data, then import it into a fresh installation of 2.1.3, rather than have to try and ‘upgrade’ the existing database again?

    Thanks.

  • #7 / Apr 27, 2011 7:41am

    John Henry Donovan

    12339 posts

    Kenny,

    The upgrade to 2.1.3 seems to finish, the new control panel appears, as does the home page external template again - though with no weblog content, just blank. All weblogs in the control panel appear to be empty other than a single placeholder.  Comments do appear to be there though.

    Just to confirm here. Do your templates appear under Design?
    What do you mean by a single placeholder?
    When you goto Content -> Edit do you see a list of your entries?

  • #8 / Apr 27, 2011 8:11am

    Kenny Fraser

    25 posts

    Hi John,

    I’ve reverted the site now but yes, the Design templates were there and elements of the frontend design appeared in a browser, though not any weblog articles.  The ‘placeholder’ was one single default-looking entry, named something like ‘new-entry+1’ or similar.  There were no other entries in Content > Edit.  Other modified data (eg settings) in the control panel seemed to be there, just not any weblog entries.

    I can run the upgrade again but want to minimise downtime.

  • #9 / Apr 27, 2011 4:35pm

    Brandon Jones

    5500 posts

    Hi Kenny,

    I’d suggest getting a copy of the 1.7 website up and running locally, so that you can upgrade without impacting the live site. The upgrade has a better chance of running locally if you were hitting any sever limitations or timeouts on the live site. Please see this troubleshooting article and let us know how you progress.

.(JavaScript must be enabled to view this email address)

ExpressionEngine News!

#eecms, #events, #releases