Error Step 7

Hi, I’m 73 percent into the migration and am getting the following error:
 
Mage2SalesOrderStatusHistory: Status is too long (maximum is 32 characters).
Mage2SalesOrderStatusHistory: Status is too long (maximum is 32 characters).
 
Please could you advise.
 
Thanks.
Kind regards,
Dacod

7 answers

Profile photo of Mall Staff 184060.00 $tone August 10, 2017
Public

Hi there,

Mage2SalesOrderStatusHistory: Status is too long (maximum is 32 characters).

That because your M1’s database has some records has bad value with new M2 database’s rules in the value of the field named status in the table named sales_order_status_history
Let’s provide me the ssh credentials and web root path of your Magento 2 instance now. I will check further and provide you workaround to solve that.
Regards,
Mall.

#1
Profile photo of jammy-git 110.00 $tone April 16, 2019
Public

What was the resolution to this problem. We have the DivideBuy module installed on our Magento 1 site which creates order statuses too long to import into M2.

#2
Profile photo of Mall Staff 184060.00 $tone April 16, 2019
Public

Hi there,

What was the resolution to this problem

You could fix for that status’s values directly in your M1 database. You could use below SQL to listing for that records in your M1 database at your end:

Select * from sales_order_status_history Where LENGTH(status) > 32;

Regards,
Mall.

#3
Profile photo of jammy-git 110.00 $tone April 17, 2019
Public

That comes up with no records returned. All the status entries in that table (was actually sales_flat_order_status_history -- sales_order_status_history does not exist), have a length of 31 characters or less.
 
Could it be another table that is causing the problem? Maybe sales_order_status?

#4
Profile photo of Mall Staff 184060.00 $tone April 18, 2019
Public

Hi there,

Could it be another table that is causing the problem? Maybe sales_order_status?

The error message referred to the bad data of the table ‘sales_order_status’ in your M2 and the associated table ‘sales_flat_order_status_history’ in your M1 database.

That comes up with no records returned.

If you got that result when running the below SQL in your M1 database, the error message is a strange one.

Select * from sales_flat_order_status_history Where LENGTH(status) >= 32;

If you couldn’t fix the bad data records in the table ‘sales_flat_order_status_history’ at your end, please provide me information below, I will help to check further:

  • URL and Admin credentials of your M2 instance
  • SSH credentials of your M2 instance
  • Let me know the path to your M2 folder

PS. Please make sure you mark your reply private or simply switch this ticket to private mode, then it’s safe to share your site info here. Only you and our technical team can access. 

Regards,
Mall.

#5
Profile photo of ubdev Staff 98370.00 $tone April 24, 2019
Public

Hi Jammy-git, 
 
Your issue refers to a bad data circumstance, yet it differs from the first question of the user ‘monetise’. 
 
If you still need our help with your issue, please submit a new ticket, we will follow up further with you. 
 
Regards,
Ubertheme team

#7

Please login or Register to Submit Answer

Written By

Comments