关于Mogento 填写运单号后,出现无法保存运送方式“Cannot save shipment.”
2017-09-15 10:43
369 查看
由于项目的需要,更换新服务器后出现后台订单填写运单号后无法保存的问题:
找到其他人的相关分析:
After googling the exception log messages and error codes, I found an issue on StackOverflow which was pretty similar. I write it down here since it’s not 100 % the same in my case.
Admin > Sales > Orders: Look up the highest order number (for each store view) and write it down. e.g. 100000054, which means that there are 54 placed orders in the system.
Admin > System > Manage Stores: Hover your mouse over your Store View Names to see their ID:s. Write them down. e.g. ID for Store View English is usually 1.
Open your database in phpMyAdmin or your preferred db admin tool.
Open the table eav_entity_type which tells you what is the id number for different entities. Now we are interested in rows with entity_type_code is order and shipment (and maybe also invoice and creditmemo, if your problem is related to those. My problem was about shipping). Write down the entity_type_id values of those rows. In my case they were 5for order and 8for shipment.
Open the table eav_entity_store. Look for rows that match the entity_type_ids of order and shipment AND also match your Store View ID:s. Now you can change the value of increment_last_id to your last actual order number. Since my store isn’t open yet, I played it safe and gave a value much bigger for both order and shipment related rows. e.g. if the increment_last_ids were 100000053 for orders and 100000040 for shipments, I gave them both the same new value 100000100 to start over from a clean table. N.B. In my case there was no a row with my local store view and correct shipment entity_type_id. So I copied the row of store view id 1, gave it new values (store id -> 4 and also increment_prefix to match store_id -> 4, and of course increment_last_id -> 400000100) and saved it as a new row in the table.
And that’s it. I’ve now placed a few test orders and everything seems to work. I was also able to ship some older test orders that were lagging behind in Processing mode. That resulted in the fact that order ID:s and shipment ID:s aren’t running side-by-side, but they wouldn’t do that for long anyway so it’s not a problem.
进入数据库,打开eav_entity_store表-更改对应的entity_type_id后面的increment_last_id 给大点的新值,让它能够重新开始;
参考:https://magento.stackexchange.com/questions/31262/cannot-save-shipment-error-with-non-sample-orders-1062-duplicate-entry-for
找到其他人的相关分析:
After googling the exception log messages and error codes, I found an issue on StackOverflow which was pretty similar. I write it down here since it’s not 100 % the same in my case.
Admin > Sales > Orders: Look up the highest order number (for each store view) and write it down. e.g. 100000054, which means that there are 54 placed orders in the system.
Admin > System > Manage Stores: Hover your mouse over your Store View Names to see their ID:s. Write them down. e.g. ID for Store View English is usually 1.
Open your database in phpMyAdmin or your preferred db admin tool.
Open the table eav_entity_type which tells you what is the id number for different entities. Now we are interested in rows with entity_type_code is order and shipment (and maybe also invoice and creditmemo, if your problem is related to those. My problem was about shipping). Write down the entity_type_id values of those rows. In my case they were 5for order and 8for shipment.
Open the table eav_entity_store. Look for rows that match the entity_type_ids of order and shipment AND also match your Store View ID:s. Now you can change the value of increment_last_id to your last actual order number. Since my store isn’t open yet, I played it safe and gave a value much bigger for both order and shipment related rows. e.g. if the increment_last_ids were 100000053 for orders and 100000040 for shipments, I gave them both the same new value 100000100 to start over from a clean table. N.B. In my case there was no a row with my local store view and correct shipment entity_type_id. So I copied the row of store view id 1, gave it new values (store id -> 4 and also increment_prefix to match store_id -> 4, and of course increment_last_id -> 400000100) and saved it as a new row in the table.
And that’s it. I’ve now placed a few test orders and everything seems to work. I was also able to ship some older test orders that were lagging behind in Processing mode. That resulted in the fact that order ID:s and shipment ID:s aren’t running side-by-side, but they wouldn’t do that for long anyway so it’s not a problem.
进入数据库,打开eav_entity_store表-更改对应的entity_type_id后面的increment_last_id 给大点的新值,让它能够重新开始;
参考:https://magento.stackexchange.com/questions/31262/cannot-save-shipment-error-with-non-sample-orders-1062-duplicate-entry-for
相关文章推荐
- 在pycharm中添加插件的时候,保存时出现Cannot Save Settings:Please specify a different SDK name
- 关于Nhibernate在wpf中的使用:Session.Save()无法保存数据到数据库中
- hibernate的各种保存方式的区别 (save,persist,update,saveOrUpdte,merge,flush,lock)等
- 关于数据保存的方式(沙盒,解档归档(swift方法))
- NHibernate的各种保存方式的区别 (save,persist,update,saveOrUpdte,merge,flush,lock)
- 在Eclipse下,出现“找不到或无法加载主类 ”的问题的解决方式
- 关于Xutils框架出现无法访问HttpRequestBase 找不到org.apache.http.client.metho
- 编写代码时出现无法保存,GBK问题
- 关于VS2008+Win7出现error MSB3216: Cannot register assembly
- 关于IPad,Iphone“无法加入网络”的可能出现的问题解决办法
- 关于Apache服务器启动出现 The Requested Operation has failed的解决方式
- 关于IE登录FTP站点,选择"保存密码"后,登录窗口不在出现的解决方法
- MindManager无法保存 提示参数不正确 打开时老出现Runtime Error
- 关于最近出现的病毒导致桌面无法显示的问题
- hibernate的各种保存方式的区别 (save,persist,update,saveOrUpdte,merge,flush,lock)等
- Linux下Firefox无法保存书签(Can not save bookmark)的解决办法
- 《关于在MFC中使用ODBC方式连接数据库可能出现的问题》第一篇
- Android;sql数据库:关于删除数据库数据无法刷新listview并且新listview的修改增加功能出现bug的问题
- myeclipse 编码后无法保存 save could not be completed.
- 关于win32绘图出现无法显示彩色问题的解决