-
Notifications
You must be signed in to change notification settings - Fork 197
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to migrate from 1.7.0.2 and 1.9.2.2: SQLSTATE[42000]: Syntax error or access violation: 1103 Incorrect table name '' #36
Comments
By default the table catalog_product_entity should not contain store_id field neither on Magento 1 nor on Magento 2. I suppose some of your extension added it |
Did you find a solution for that? We have the same error when trying to click on the category products lis in the backend. Our reindex is working well but we cannot access the products in then backend also they are shown correct in the frontend. |
@andidhouse |
Try |
HI Victor, the table catalog_eav_attribute exists in the magneto2 database and has 392 entries. Is it possible that maybe the table has some entries from old magento 1.7 extensions which cause the error? |
The issue is on Magento 2 side and I suppose something wrong with cache.
|
We just did that (go to the admin panel before migration and click the product grid) - no effect. We now completely remove magento 2.0 from the system and try again. |
Ok we completely deleted magento 2.0 and installed from scratch again - same error. Many thanks! |
Ok. Let's go further. Please show one record (with |
hey! |
I'm having an issue migrating my current store over to Magento 2.0. The store is currently at v1.7.0.2 and I've taken the following steps
All of the above migrate without any issues reported in the migration log. If I clean out all modules and associated tables/columns I utilize the base map.xml.dist file instead of a custom map.xml file.
All of the above cause the same error on the backend/frontend of the Magento 2.0 store. I cannot access any product details as they produce the same error. The backend displays 0 customers. There are over 13K products and over 17K customers that migrate over to the 2.0 database. When running the indexer I get the following output:
When attempting to view products on the backend, or any page on the frontend, or REST API endpoints that deal w/ Products I get the following error:
Migration Log
The text was updated successfully, but these errors were encountered: