Thread

Error: The following error was encountered
MySQL ERROR:

Error Number: 1060

Description: Duplicate column name ‘username’

Query: ALTER TABLE `exp_password_lockout` ADD `username` VARCHAR(50) NOT NULL AFTER `user_agent`

Do any one know way I can’t update.
Furthermore I can’t neither upgrade to version 2

4F,

To confirm you are trying an upgrade to EE1.7.1 first?
When you ran the upgrade wizard was at what stage did you see this error?

Did this error appear the very first time you tried the upgrade?

How did you then try the EE2.x upgrade? Did you roll back everything to EE1.6.8 and try from there?

Make sure that system/config.php and system/config_bak.php are at 644 permissions , and system/cache is at 755. Can you confirm that please?

Now roll back to where you were at 1.6.8 and we will try again

John,

When I click on Update from version 1.6.8 to version 1.6.9 (although the update I am using is 1.7.1)

Yes, every time.

Yes, I roll back to 1.6.8 after upgrading to version 2 was unsuccessful.

Permissions are as indicate. Again the same error.

Meny thanks

4F
Francisco

Hi Francisco,

Can you confirm that you’re also restoring your database backup from 1.6.8 into a completely empty database, and not one that might already have data from the partial upgrade, before trying the upgrade again? See this troubleshooting document as well.

Hi Brandon.

The problem is: my database backup is as old as the introduction of version 2, I will lost all data introduce since then, furthermore is working fine with 1.6.8., with no apparent errors. I guess I am stock at this version forever, or… there is another solution?

Thanks anyway,
Francisco

Hi Francisco,

Before attempting an upgrade, it’s best practice to always back up your files and your database. It’s so important, in fact, that it’s the first thing we tell you to do when preparing for an upgrade. There may be instances where you need to roll back your installation, and this is one of them. Here’s why:

EE 2 introduces some new database tables and columns that don’t exist in EE 1. There are also some database tables from EE 1 that will be removed as you upgrade into EE 2, but if your installer hadn’t gotten that far, then your database would consist of all your EE 1 tables plus some new EE 2 tables. In this case, your installation at 1.6.8 would still work fine, but if you try to upgrade that installation, the EE 2 upgrade script will try to add new tables, columns, etc. to the database that already exist, and you’ll encounter some big MySQL errors.

So until you can restore your database to exactly the way it was in 1.6.8, you’re going to encounter problems trying to upgrade. Does this make sense?

Sometimes web hosts do routine backups of their clients’ databases. Perhaps you could work with your host to see if you can get a recent backup restored.

Hi Kevin,

The problem is my database backup from 1.6.8 before I try to upgrade to version 2 is almost one year old, I have other back. ups but will have the same problem I have now. I am afraid that I will need to manually correct my database, but I don’t know were to begin in the first place since I don’t know what kind of mess version 2 has down on my database.

Do you happened to know a professional freelance welling to do this job for me?

Thanks

Hi 4F,

Yes, I roll back to 1.6.8 after upgrading to version 2 was unsuccessful.

You mention here that you have already rolled back once before. Does that mean you imported the database that is over a year old?

Can you confirm please?

Hi John,

No, I rolled back to 1.6.8 but live the database as it was, never restore the database, thats the problem. I don’t realize at the moment the importance and necessity of doing so.

thanks
Francisco

Hi Francisco,

Unfortunately, this falls outside of the support we’re able to offer here on the forums. This may be a good opportunity to post to the EE Job Board to get a skilled EE pro in there to help you store your database to 1.x condition and then help you upgrade.