Hi!
I made fresh install of Magento 2.1.6 + UB Migration Pro 3.0.7.
Migrated data from Magento 1.9 successfully.
I can see products and edit them. But when I click ‘Add Product’ button, I’m getting ‘Invalid entity_type specified’ error and blank product details page.
Any idea on how to solve this?
Thanks.
-
rafcamera ⋅160.00 $tone May 1, 2017
P.S. Resinstalled and passed once again step-by step with reindex and cache cleaning after each step. Works now. Though I can't import reviews due to duplicate index. Will work on this issue later.
rafcamera ⋅160.00 $tone
May 1, 2017
32 answers
Hi there,
Let’s provide me information about your working. I will check further and help you out.
Regards,
Mall.
Hi Mall.
I played with it bit longer and found that this issue with invalid empty entity_type happen after I edited attribute sets.
So, I did this in fifferent way from what you decribed in manual -- I created necessary attribute sets in Magento 2 backend and executed few SQL queries to change all migrated attribute sets to native M2 sets. This ran smoothly.
Now I’m trying to import reviews and aggregated data (Step 8, first 2 items). Getting different errors so far, but will come back to these issues later today or tomorrow -- need to wait while M2E Pro mudule finish its job first. Then I’ll copy error messages here.
Thanks.
CDbCommand failed to execute the SQL statement: SQLSTATE[23000]: Integrity constraint violation: 1062 Duplicate entry ‘141-0’ for key ‘PRIMARY’
Update. Enadled debug info.
Error message for reviews says:
CDbCommand failed to execute the SQL statement: SQLSTATE[23000]: Integrity constraint violation: 1062 Duplicate entry ‘211-0’ for key ‘PRIMARY’. The SQL statement executed was: INSERT INTO `review_store` (`review_id`, `store_id`) VALUES (:yp0, :yp1)
When I uncjeck reviews and run next portin (ratings), process stucks at Magento backend. When I run step8 from SSH, error says:
Message: CDbCommand failed to execute the SQL statement: SQLSTATE[42000]: Syntax error or access violation: 1064 You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near ‘AND store_id IN (0,1)’ at line 1. The SQL statement executed was: SELECT COUNT(*) FROM `rating_option_vote_aggregated` `t` WHERE AND store_id IN (0,1)
Hi Mall.
Problem solved, thank you!
Hi Mall.
The problem I’ve satred this thread with is back.
I can’t duplicate products and can’t create new products. Error says “Invalid entity_type specified:” (nothing after colon).
Can you check what may cause this, please?
Thanks.
Hi there,
I can’t duplicate products and can’t create new products. Error says “Invalid entity_type specified:” (nothing after colon).
I can’t access your site now: http://i.prntscr.com/593a65818a464bcab6507e2b3056f7a2.png
Let’s try re-setting your attribute sets migrated as our guide at: https://www.ubertheme.com/docs/magento-2-data-migration-product-attribute-configuration/#vid
And reindex your data and clean the Magento2 cache.
And tell me know how it goes.
Regards,
Mall.
Hi there,
use php-cli instead php
Ok, i will set deploy mode in your site to developer mode to detect further. Are you ok for this action?
Regards,
Mall.
Yes, just try to keep the store working if possible. Thanks.
Hi there,
(Invalid entity_type specified)
I have enabled debug mode in your site and tried to debug but could not narrow down which specific third-party extension or customised data in your instance caused the issue as you mentioned.
As per my first reply, there’s high chance the issue related to your customized data after migrating with our tool.
For your information on a case with similar issue like yours: https://www.ubertheme.com/question/getting-error-on-import-products-in-ub-migrate-pro/ (which refered to the same issue: http://i.prntscr.com/e67b6816358143b68f1d1dd97f545067.png)
Beside, I see you are using a lot of third-party extensions in your site now. And you did use Magento migration tool before, as indicated in this screenshot: http://i.prntscr.com/5da6c010938f46ae8237d1d965d25e5d.png which might caused unexpected conflicts.
If you are still not convinced, I will get your Magento1’s database to implement a test migration at my end to confirm with you that the issue does not relate to our tool.
Regards,
Mall
Thanks for your efforts.
You can try to do test migration from Magento 1.9 database.
I did this 3 times in clean environment, and every time got same issue with inability to add products.
May be you will replicate this issue after test migration.
Thanks.
