Error in file: “/usr/local/sites/client/magento_site/app/code/core/Mage/Customer/sql/customer_setup/mysql4-upgrade-1.4.0.0.7-1.4.0.0.8.php” - SQLSTATE[42S01]: Base table or view already exists: 1050 Table ‘customer_form_attribute’ already exists
I tried upgrading this using a tutorial (http://turnkeye.com/blog/magento-upgrade-from-1-4-version-to-magento-1-5-magento-1-6/) from turnkeye to go from 1.4.1 -> 1.4.2 and then to 1.6 but after all the mage upgrading was complete, when I hit the website to upgrade the database I get errors about database tables that already exist and it appears to be running a database upgrade script for a version of magento before 1.4.2. I know this error is extremely common and I have seen many blogs posts about it and read all that I have found—I see no resolution besides starting a fresh install.
I’ve heard people say this can happen if a previous upgrade didn’t complete successfully but I don’t think that is the case here—it was a fresh install at 1.4.1. Anyone know why this is happening or how to fix it?
Why does Magento not supply an up to date upgrade guide??
Note: I also tried the upgrade by overwriting the 1.4.1 files via SSH with successive version of magento—always the same database errors though. If I remove the mysql-upgrade script that is failing, then another one fails in its place with a simliar ‘table already exists’ error.
Note 2: I also made sure I cleared /var/cache and /var/session and even tried reindexing. No success.
I tried dropping the database, recreating, and reloading my dump before I upgraded from 1.4.1 to 1.4.2 successfully, but still had the same issue when upgrading to 1.6.
I then tried dropping/recreating/reloading the database at version 1.4.2 and upgrading to 1.6, but still the same issue. Ugh
Here is my upgrade process in case this shows signs of a problem:
Can anyone confirm that if my code is supposedly upgraded to version 1.4.2 that the database version should indeed be 1.4.0.0.7 (as in the upgrade script it is trying to run)? I see there are upgrade scripts for version 1.4.0.8, 1.4.0.0.9, and 1.4.0.0.10. Is that the source of my problem? The DB version didn’t get configured correctly?
Always Backup your store files and database before starting upgarde.
I just upgraded my magento to 1.6. Following are the issues i faced while upgrading:
1) First of all i tried to upgarde magento using magento connect manager, but id didn\’t work as for most of modules were skipped by connect manager with message no upgrade available or dependency errors.
2) After that i try to upgrade it by downloading complete 1.6 package from magentocommerce.com and upload all the files to my magento (website) directory through FTP client.
3) After all files were uplaoded, i run my website again from browser, but it did not work and i got some server timeout errors, so i fixed timeout errors by editing by nginx conf file.
4) After inreasing timeout in server conf file, i restarted the upgarde by again accessing my website url from browser.
5) This time, i get some mysql errors after approx. 1 hour and upgrade did n\’t work.
6) So, i dropped my magento database and restored it back from my dump which was taken before starting upgrade .
7) After restoring my shop data, i again started upgarde by accessing my website from browser, this time it took a long time (approx. 10 hours), for approx. 8 hours page kept on loading, so i did not stop/close my browser window assuming that my upgarde is going on.
8) After approx . 8 hours, upgrade was still not completes, but i tried to open my website in another browser and it worked, my store was sucessfully upgarded to 1.6.
9) I tested whole site after this, and everything is working fine. Hurray.
Hope this will help someone struggling with upgarde.
W3sols Team (w3sols.com)
We customize magento community edition
Thanks for the info. I too had a similar experience when upgrading a previous magento site—the upgrade appeared to hang, but when I opened it in another window the store loaded and the upgrade appeared to be complete. So there is probably a bug somewhere in there. I agree about the Connect Manager as well—it doesn’t work well. When I did get it to work, it claimed to have upgraded the site but the footer on the admin page still had the old version so something didn’t complete. Frustrating.
Too bad there doesn’t appear to be a solution to the SQL errors we get during the upgrade. It has forced us to abandon the upgrade project for the time being.
Did you restart your install? If you restarted your install you are bound to get some errors like this. The best and safest course of action is to get a fresh dump of you data base and restart the install. Remember to drop the database before you restore again.
Always Backup your store files and database before starting upgarde.
I just upgraded my magento to 1.6. Following are the issues i faced while upgrading:
1) First of all i tried to upgarde magento using magento connect manager, but id didn\’t work as for most of modules were skipped by connect manager with message no upgrade available or dependency errors.
2) After that i try to upgrade it by downloading complete 1.6 package from magentocommerce.com and upload all the files to my magento (website) directory through FTP client.
3) After all files were uplaoded, i run my website again from browser, but it did not work and i got some server timeout errors, so i fixed timeout errors by editing by nginx conf file.
4) After inreasing timeout in server conf file, i restarted the upgarde by again accessing my website url from browser.
5) This time, i get some mysql errors after approx. 1 hour and upgrade did n\’t work.
6) So, i dropped my magento database and restored it back from my dump which was taken before starting upgrade .
7) After restoring my shop data, i again started upgarde by accessing my website from browser, this time it took a long time (approx. 10 hours), for approx. 8 hours page kept on loading, so i did not stop/close my browser window assuming that my upgarde is going on.
8) After approx . 8 hours, upgrade was still not completes, but i tried to open my website in another browser and it worked, my store was sucessfully upgarded to 1.6.
9) I tested whole site after this, and everything is working fine. Hurray.
Hope this will help someone struggling with upgarde.
W3sols Team (w3sols.com)
We customize magento community edition
I think this is the imporant information that I overlooked. When first trying to access the website in a browser the browser load wheel kept spining… it just takes a long time (hours) to update and needs to be left alone.
I also had problems upgrading from 1.4.2 to 1.6, my problem was that I activated the Google shopping tool in Magento 1.4.2, the Google shopping tool made some major code changes to my install of Magento 1.4.2 after the default install was setup. When I tried to upgrade to 1.6.0 the install would fail, I had to go back and and reinstall 1.4.2 and then perform the upgrade.
One thing to check on is what extra modules you have installed onto Magento, a hidden code rewrite has taken place, that will cause your upgrade to fail.