I have following problems after upgrade (manual upgrade by SSH):
(Update passed with no error.)
1. url rewrites was bad
I solved it manually, probably it’s not a good solution, i must try ($mysql> truncate core_url_rewrite;)
Same problem as here> http://www.magentocommerce.com/boards/viewthread/244508/
2. Now I don\’t see any orders on dashboard
I tried “php shell/indexer.php reindexall” (passed sucessfully), report->refresh statistic (rebuild all), clean cache, delete cache folders, reindex in index management....but i still don’t see orders in \"pending\" state.
3. I know it\’s OT, but AW_BLOG module was and now is not working, after upgrade is AW_Blog module disabled in administration, and can\’t be enabled. This module is marked as 1.6 compatible, so I not sure, if is it a problem at my side. http://ecommerce.aheadworks.com/free-stuff/blog.html (Reinstallation doesn\’t help)
4. Shop is working, but now (in 1.6) Im getting this reports>
I have two remarks to 1.6.
1) backup takes a much longer in 1.6 (i was not able to create backup till I cleaned logs)
(Backup before upgrade passed successfully (85MB), after upgrade it timed out, i solved it by truncate log tables(17MB), but it takes a much longer now than before. Same situation on 2 VPS - only change is a new version of Magento.)
2) memory usage of 1.6 is bit higher, my VPS with 512 ram has only 5-13 MB free after one day, with 1.5.1 i had about 50-100 MB free ram after few days.
I had the same error when upgrading from 126.96.36.199 to 188.8.131.52.
The issue lies in table \\\’magentoreport_viewed_product_index\\\’. Specifically, magento is trying to run this SQL:
\\\"ALTER TABLE `magentoreport_viewed_product_index` MODIFY COLUMN `customer_id` int UNSIGNED NOT NULL COMMENT ‘’\\\"
I looked in my table \\\’report_viewed_product_index\\\’ and found the key magento was complaining about. The key was found in the product_id column. The first record that had a null value in column \\\’customer_id\\\’ was the same record that possessed the \\\"duplicate key\\\”.
I restored backups of my running 184.108.40.206 installation / database and truncated the whole table \\\’report_viewed_product_index\\\’.
Then I move the 220.127.116.11 files out of the way, then downloaded a fresh 18.104.22.168 installation. I copied the app/etc/local.xml from my working 22.214.171.124 installation to the new blank 126.96.36.199 installation, likewise I copied my .htaccess file from my working 188.8.131.52 installation to the new blank 184.108.40.206 installation.
Then I initiated the update process with:
nohup php index.php > magento-update-log
It appears truncating the table \\\’report_viewed_product_index\\\’ or in your case \\\’magentoreport_viewed_product_index\\\’ fixes this duplicate problem issue
I have problem with upgrading my website from 1.5.0 to 220.127.116.11. I tried make it through Instalatron on the SimpleHellix webhosting.
Error in file: “/home/christia/domains/christianrussianbook.com/public_html/bookstore/app/code/core/Mage/Sales/sql/sales_setup/mysql4-upgrade-18.104.22.168-22.214.171.124.php” - SQLSTATE[HY000]: General error: 1025 Error on rename of ‘./christia_mage15/#sql-2da5_7f2af’ to ‘./christia_mage15/sales_flat_order_item’ (errno: 150)
I tried all methods that was described here and in all magenta threads, but no luck.
Also I found some commands, but I don’t know if it is for MQL or for SSH?:
ALTER TABLE sales_flat_order_item DROP INDEX IDX_ORDER , ADD INDEX IDX_SALES_FLAT_ORDER_ITEM_ORDER_ID ( order_id )
ALTER TABLE sales_flat_order_item DROP INDEX IDX_STORE_ID , ADD INDEX IDX_SALES_FLAT_ORDER_ITEM_STORE_ID ( store_id )
ALTER TABLE sales_flat_order_item DROP INDEX IDX_PRODUCT_ID
The biggest problem that I have tried all that on my live website and now it shouted down.
Just encountered exactly the same problem as others on this thread:
“Error in file: “/xxx/app/code/core/Mage/Sales/sql/sales_setup/mysql4-upgrade-126.96.36.199-188.8.131.52.php” - SQLSTATE[HY000]: General error: 1025 Error on rename of ‘./magento/#sql-25de_742’ to ‘./magento/sales_flat_order_item’ (errno: 150)”
I have the same issue - I have worked out that there is an issue with the DB.
I have a magento 1.4.2 database
I have used to magento DB checker to ensure that it is consistent with the 1.4.2 vanilla DB - came out clean
I extract the SQL query that is causing the issue and run that in phpmyadmin specifically against the 1.4.2 database.
SQL query: ALTER TABLE `sales_flat_order_item` DROP INDEX `IDX_STORE_ID` #1025 - Error on rename of './magento/#sql-a94_107' to './magento/sales_flat_order_item' (errno: 150)
Hay presto I have the same error that I get when I try my 184.108.40.206 upgrade.
So, next I compare the two reference installs that I have made of v220.127.116.11 and v18.104.22.168
I changed the sales_flat_order_item indexes of my 22.214.171.124 site to match the 126.96.36.199 reference site and then run the upgrade and pulled the home page.
ALTER TABLE sales_flat_order_item DROP INDEX IDX_ORDER , ADD INDEX IDX_SALES_FLAT_ORDER_ITEM_ORDER_ID ( order_id ) ALTER TABLE sales_flat_order_item DROP INDEX IDX_STORE_ID , ADD INDEX IDX_SALES_FLAT_ORDER_ITEM_STORE_ID ( store_id ) ALTER TABLE sales_flat_order_item DROP INDEX IDX_PRODUCT_ID
Completed with no errors - Yeeeerrrhhh.
So can anyone throw stones at this solution then?
I have similar problem.
Where did ran these commands?
So many issues connected with Magento update! seriously, guys, why don’t you get assistance. There are a lot of third party applications or services that can help you out and save a lot of time. I used this one - http://www.shopping-cart-migration.com/supported-carts/55-magento
and strongly recommend it for migration to Magento and update. The procedure is actually the same - install fresh magento, and move your dfatabase from the old store. the service I used allows to do it without downtime