Thread

I have decided to do a clean install and start all over. Going to suck manually entering all the data again but there doesn’t seem to be a solution to this problem coming anytime soon.

Kevin,

have you proceeded with the clean install yet?

So I started again, first upgraded to 1.6.9, but got the same error.

Can you confirm this error was upgrading from 1.6.9 to 2.1 and not 1.6.8 to 1.6.9?

Can you confirm the version in your 1.6.9 config file please?

When you are getting these errors do you refresh the page or use the back button?

Have you been reverting your db as well when attempting the upgrade or using the already upgraded database?

That was somebody else posting that they upgraded to 1.6.9. I was on 1.6.8 trying to upgrade to 2.1. No need to use the back or refresh button because once the 1050 error comes up your SOL. You have to restore files and database back to original before you can do anything.

Jean-Michel, just to clarify, you were able to successfully upgrade from 1.6.8 to 1.6.9?

Kevin, we apologize for the inconvenience as we are still looking for the common thread here. Let us know if you want to continue troubleshooting.

DB error for me upgrading from 2.0.2pb01 to 2.1.0.

A Database Error Occurred
    Error Number: 1060

    Duplicate column name ‘can_access_fieldtypes’

    ALTER TABLE `exp_member_groups` ADD `can_access_fieldtypes` char(1) NOT NULL DEFAULT ‘n’ AFTER `can_access_files`

Any more info on what might be causing it??

For all of those who were getting a database error when upgrading to 2.1 from the 2.0 Public Beta, please download the latest build today (20100720) and try again. This should be fixed.

I’m running into the exact same problem.  I’m upgrading from 1.6.8 and getting error 1050 on at the same point.  I have a question though.  In another thread it was suggested that the database changes on some systems end up being run twice for some reason.  If that’s the case, then in the config.php file where it says:

$config[‘ud_next_step’] = “database_changes”;

maybe we can bypass the problem by entering the next step in the installation process.  If the database changes are already made, then skipping the second run shouldn’t matter.  So that leaves the question, what is the next value normally for ud_next_step?

Thanks

PJCweb, you’d need to ensure that all of the database changes happened the first time around, which isn’t guaranteed. Can you confirm the version and build you’re attempting to upgrade to? Go ahead and roll back your database and files to 1.6.8 in the meantime.

I believe the version is 2.1, i’m not 100% on the build.  Whichever is the newest, (I downloaded the update files earlier today)

Is there any other way around this?  I’ve been looking through the thread/forum, and I haven’t seen anyone solve this problem except through a clean install, which may not be feasible for us if we have to re-enter all of the data from our existing site.

Hi PJCweb,

You should be able to download version 1.6.9 in your download area. Can you rollback to 1.6.8 and then make sure that you can upgrade to 1.6.9 first? That’ll help us figure out where it is failing for you and why.

Cheers

Greg

Ok i was able to update successfully to 1.6.9 from 1.6.8.  What’s next?

PJCweb,

Next, lets have you go from 1.6.9 to 2.1

EE Docs : Updating from 1.x to 2.x

Let us know how you get on.

Bah, exact same error.

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`) )

Hi PJCweb,

Please ensure the database was rolled back to a pure 1.6.9 state before attempting the upgrade. Snippets are a new feature in EE2; there should not be an exp_snippets table in an EE1.x database.

*sigh* that seems to be the problem.  The table is still there and our hosting service no longer has the backup since it was a week ago.  I can roll-back to 1.6.8 and overwrite all tables that existed previously, however the new tables are still there. 

Do you have a list of all of the newly created tables in 2.1?  It seems i may have to manually go in and pick them out.  (or if you have another, more elegant solution i’d be happy to hear it).