Thread

Greetings el mysterioso, and welcome to the forums!

Can you clarify the error you’re getting? Those are just SQL statements in your post above. Also, can you clarify which version of EE 1.x you are upgrading from, and what version of EE 2.x you are upgrading to?

Hi Brandon,

Thanks for getting back to me so quickly. I am upgrading EE 1.6.7 to EE 2.1.3.

The error I am getting is this:

A Database Error Occurred
Error Number: 1050

Table 'exp_snippets' already exists

CREATE TABLE `exp_snippets` ( `snippet_id` int(10) unsigned NOT NULL auto_increment, `site_id` int(4) NOT NULL, `snippet_name` varchar(75) NOT NULL, `snippet_contents` text NULL, PRIMARY KEY (`snippet_id`), KEY `site_id` (`site_id`) )

Filename: updates/ud_200.php

Line Number: 1382

Hi el mysterioso,

There are several possible reasons for a duplicate table, column or key error:

If you had previously restored your database, ensure it was restored into a completely empty database. Otherwise there will be duplicate data.

Never use your browser’s Back button during an upgrade, as that can cause actions to run twice.

Your server’s PHP max_execution_time may be set too low, forcing the upgrade script to end prematurely. Check with your host about increasing this value from the typical default of 30 seconds.

If you’re using Firefox to perform the upgrade, try using Chrome or Safari instead. In some cases Firefox can re-send requests following a server error, effectively preventing the error from being seen.

Can you try upgrading to EE1.7.1 first and then perform the upgrade to EE21.3?

Hi el mysterioso–

Did you get your upgrade completed successfully?

el mysterioso,

If you’re still having trouble with your upgrade, please make sure to wipe your database clean before restoring it to EE 1.6.x. Then upgrade your installation to EE 2. Not doing so could result in some tables that were added in a botched EE 2 upgrade still being present and causing errors like the one you’re seeing.

I’m closing this thread out since it’s been a while since the last update, but if you’re still experiencing issues, please feel free to open up a new thread.