Error in category migration

Hi, I’m trying to migrate the categories and products and I’m facing this errors:

2020/12/10 17:09:19 [error] [ub_data_migration] CDbCommand failed to execute the SQL statement: SQLSTATE[HY000]: General error: 1364 Field ‘entity_id’ doesn’t have a default value. The SQL statement executed was: INSERT INTO `catalog_category_entity` (`attribute_set_id`, `parent_id`, `level`, `created_in`, `updated_in`, `created_at`, `updated_at`, `path`, `position`, `children_count`) VALUES (:yp0, :yp1, :yp2, :yp3, :yp4, :yp5, :yp6, :yp7, :yp8, :yp9)

2020/12/10 17:13:17 [error] [ub_data_migration] CDbCommand failed to execute the SQL statement: SQLSTATE[42S22]: Column not found: 1054 Unknown column ‘entity_id’ in ‘where clause’. The SQL statement executed was: SELECT * FROM `catalog_product_entity_int` `t` WHERE entity_id = 1 AND attribute_id = 248 AND store_id = 0 LIMIT 1

Could you help us? please.

The Magento 1 version is 1.9.2.4 and the Magento 2 is 2.4.1

9 answers

Profile photo of Mall Staff 159450.00 $tone December 11, 2020
Public

Hi there,

General error: 1364 Field ‘entity_id’ doesn’t have a default value. The SQL statement executed was: INSERT INTO `catalog_category_entity`
….
Column not found: 1054 Unknown column ‘entity_id’ in ‘where clause’. The SQL statement executed was: SELECT * FROM `catalog_product_entity_int` `t` WHERE entity_id = 1 AND attribute_id = 248 AND store_id = 0 LIMIT 1

The issues you mentioned are strange.

Please note that the catalog_category_entity.entity_id is a core field in the ‘catalog_category_entity’ table and its value is AUTOINCREMENT as per the default setting in DB of M2: http://prntscr.com/w07gua

So please check your M2 database again and make sure that the table ‘catalog_category_entity’ has the right setting like the above screenshot.
 
Also, the catalog_product_entity_int.entity_id is a core field in the ‘catalog_product_entity_int’ table in M2 database: http://prntscr.com/w07hur
 
Where did you download the source code of the Magento ver2.4.1? And can you re-download the Magento ver2.4.1 directly via this post and then, re-perform data migration in all steps of our migration tool?

Regards,
Mall.
 

#1
Profile photo of Mall Staff 159450.00 $tone December 13, 2020
Public

Hi there,

I notice now that the Magento 2.4.1 is commerce version.

Please note that our migration tool doesn’t support the Magento commerce at the moment.
As you can see, the Magento versions that our product supports are stated clearly on our product page. For your convenience, we include the version info below: 

The tool supports the following Magento versions:

    • Magento CE 1.x: 1.6.0.2 and later, 1.7.x, 1.8.x, 1.9.x
    • Magento CE 2.0.0 and later

NOTE:

    In case you use Magento CE 1.6.0.1 or older, you can upgrade your database to version 1.6.0.2 or later, then proceed with migration from this newly upgraded instance.

 
Regards,
Mall.

#3
Profile photo of ubdev Staff 76860.00 $tone December 15, 2020
Public

Hi there, 
Some of our users did use our UB Data Migration Pro module for their Magento EE-related projects. However, they all resolved the issues (if any) during the migration process at their ends. 
We wonder if you consider moving forward with that option. Otherwise, we will proceed with the refund asp as per your inquiry.
Regards,
Ubertheme team
 

#5
Profile photo of ubdev Staff 76860.00 $tone December 16, 2020
Public

Hi there,
We’ve just refunded as per your inquiry. As we use the Stripe Refund functionality, it might take up to 5 to 7 days for the fund to reach you.
Regards,
Ubertheme team

#7
Profile photo of ubdev Staff 76860.00 $tone December 16, 2020
Public

Hi there, 
 
If you have any Magento CE-related project in the future, please take a look at our module again. It definitely saves you pretty much time. 
 
Meanwhile, we also sent you an email asking one quick question about Magento 2 development. We hope you can spare some time to share your feedback. 
 
Regards,
Ubertheme team

#9

Please login or Register to Submit Answer

Written By

Comments