I was able to successfully install a FRESH INSTALL of the latest magento software with no hitches, I used Magneticones Cart 2 Cart Importation and was able to successfully import all products,prices and images with no issues.
Now I did new Attributes and I clicked on Catalog Index Rebuild - REFRESH
I got the (Catalog Index rebuild error. Please try again later) error…
I have searched the forums and nothing really matches this issue.
Just realized most of the errors people are discussing here are for the SEARCH INDEX rebuild....My main problem is the Catalog Index Rebuild.. Hopefully someone can guide me with what I am missing.
I’m having the same problem… upgraded to 1.3.2.3, tried to assign a category to a product; got the following error: SQLSTATE[42S22]: Column not found: 1054 Unknown column ‘store_id’ in ‘where clause’
Tried to “Rebuild Catalog Index”. Got the following error: “Catalog Index rebuild error. Please try again later”
I get the same error when trying to “Rebuild Flat Catalog Product”.
I’m able to “Rebuild Flat Catalog Category” successfully.
Same problem here. Is there a way to rebuild and refresh caches manually? It seems like Magento has a hard time with a lot of things when run on a shared server. Is everybody else that has posted with this problem running on a shared server?
Use your preferred MySQL manager software: phpmyadmin for example and check the state of the tables. If a problem occurs (for the catalogsearch_fulltext table for example) you will see the problem. So just do a Repair table ‘xyz’ with your software or with a SQL query.
When I ran a database check everything checked out OK. When I went ahead and did a database repair some of the tables check out OK while others gave me this note
note : The storage engine for the table doesn’t support repair
You should check if your tables use the correct Engine for Magento 95% is InnoDB but some old tables use MyISAM. I don’t have the list. And if your check provide a OK statement it changes nothing to try to repair.
But so, in my case, I had this problem few minutes ago with the error in the title of this topic and I did this check and repair. It was necessary for the catalog_fulltext table only in my side.
In my case, I don’t know the reason of this. And i didn’t have the problem anymore. However, it’s possible that you have to dump the database and import it again. You could too update Magento to a higher version 1.3.x or even 1.4.