Magento

Hi all,

On my dev server, I’m trying to upgrade our 1.5.1 shop to 1.6.1.  The update itself goes well and the shop seems to work fine after the update.

After some more testing I found that existing customers, who already had placed an order before, are getting a message that the order cannot be completed when they want to finish the checkout process.

After some digging I found the following error in the exceptions log:

It seems that magento wants to use the previous ordernumber of the customer to create the new order, which results in a duplicate entry.

I suspected some extensions so I disabled them before upgrading, no joy. 
Updated the extensions and then updated magento, no joy. 
Disabled the custom theme, no joy.

Anybody a clue on where to find the source of this problem?

processing the same order through magento backend seems to go fine, so i’ts only a frontent problem.

Thanks,

Tom

You can try increasing your Increment number here

eav_entity_store

Brent W Peterson - 28 October 2011 09:32 AM

You can try increasing your Increment number here

eav_entity_store

I just checked this table but it seems to be ok.  Tried to increase the number and tried again but same error.

It seems that, in my case, magento only checks this table for new customers / customers first order:

Current increment id let’s say 57
Customer A has placed 3 orders, last order was 29
Customer B has placed 1 order, last order 51

New customer places order, everything goes well, gets ordernumber 58, increment goes to 58
Customer B places order, error: log shows magento wants to use order number 51, which, off course, is duplicate
Customer A places order, error: log shows magento wants to use order number 29. Again, exactly the same number as this customers last order and off course duplicate
Another new customer places order, no problem, this will get order number 59 and increment also increases to 59

Strange ...

Did you try increasing your increment_id by 1000?

Brent W Peterson - 30 October 2011 11:07 AM

Did you try increasing your increment_id by 1000?

Just tried, same error.  New customers get the increased order number.  Existing customers that already place an order before keep getting their last order number.

@TomvH:: The problem is that the quoteId is reserved for customers who have already started an order. If you wanted to you could remove all the items from the quote’s and then the customer would not be able to order anything they had saved.

Brent W Peterson - 31 October 2011 12:25 PM

@TomvH:: The problem is that the quoteId is reserved for customers who have already started an order. If you wanted to you could remove all the items from the quote’s and then the customer would not be able to order anything they had saved.

Hi Brent,

Thanks again for your answer, but that also doesn’t seem to be the problem.  I just tried to upgrade again, but first I emptied the shopping carts of my test accounts if they had anything in it.

Same error all over again.  All the existing accounts but with no previous orders work fine, the others don’t.

Hi, I have the same problem… have you solved it?

I also see this problem
any updates?

Yes i am having same problem it shows track like this

2012-06-12T14:05:51+00:00 ERR (3):
exception ‘PDOException’ with message ‘SQLSTATE[23000]: Integrity constraint violation: 1062 Duplicate entry ‘1242’ for key ‘UNQ_SALES_FLAT_ORDER_INCREMENT_ID’’ in /public_html/lib/Zend/Db/Statement/Pdo.php:228
Stack trace:
#0 /public_html/lib/Zend/Db/Statement/Pdo.php(228): PDOStatement->execute(Array)
#1 /public_html/lib/Varien/Db/Statement/Pdo/Mysql.php(110): Zend_Db_Statement_Pdo->_execute(Array)
#2 /public_html/lib/Zend/Db/Statement.php(300): Varien_Db_Statement_Pdo_Mysql->_execute(Array)
#3 /public_html/lib/Zend/Db/Adapter/Abstract.php(479): Zend_Db_Statement->execute(Array)
#4 /public_html/lib/Zend/Db/Adapter/Pdo/Abstract.php(238): Zend_Db_Adapter_Abstract->query(’INSERT INTO `sa...’, Array)
#5 /public_html/lib/Varien/Db/Adapter/Pdo/Mysql.php(419): Zend_Db_Adapter_Pdo_Abstract->query(’INSERT INTO `sa...’, Array)
#6 /public_html/lib/Zend/Db/Adapter/Abstract.php(574): Varien_Db_Adapter_Pdo_Mysql->query(’INSERT INTO `sa...’, Array)
#7 /public_html/app/code/core/Mage/Core/Model/Resource/Db/Abstract.php(453): Zend_Db_Adapter_Abstract->insert(’sales_flat_orde...’, Array)
#8 /public_html/app/code/core/Mage/Sales/Model/Resource/Order/Abstract.php(425): Mage_Core_Model_Resource_Db_Abstract->save(Object(Mage_Sales_Model_Order))
#9 /public_html/app/code/core/Mage/Core/Model/Abstract.php(318): Mage_Sales_Model_Resource_Order_Abstract->save(Object(Mage_Sales_Model_Order))
#10 /public_html/app/code/core/Mage/Core/Model/Resource/Transaction.php(151): Mage_Core_Model_Abstract->save()
#11 /public_html/app/code/core/Mage/Sales/Model/Service/Quote.php(189): Mage_Core_Model_Resource_Transaction->save()
#12 /public_html/app/code/core/Mage/Sales/Model/Service/Quote.php(249): Mage_Sales_Model_Service_Quote->submitOrder()
#13 /public_html/app/code/core/Mage/Checkout/Model/Type/Onepage.php(774): Mage_Sales_Model_Service_Quote->submitAll()
#14 /public_html/app/code/core/Mage/Checkout/controllers/OnepageController.php(511): Mage_Checkout_Model_Type_Onepage->saveOrder()
#15 /public_html/app/code/core/Mage/Core/Controller/Varien/Action.php(419): Mage_Checkout_OnepageController->saveOrderAction()
#16 /public_html/app/code/core/Mage/Core/Controller/Varien/Router/Standard.php(250): Mage_Core_Controller_Varien_Action->dispatch(’saveOrder’)
#17 /public_html/app/code/core/Mage/Core/Controller/Varien/Front.php(176): Mage_Core_Controller_Varien_Router_Standard->match(Object(Mage_Core_Controller_Request_Http))
#18 /public_html/app/code/core/Mage/Core/Model/App.php(354): Mage_Core_Controller_Varien_Front->dispatch()
#19 /public_html/app/Mage.php(683): Mage_Core_Model_App->run(Array)
#20 /public_html/index.php(90): Mage::run(’’, ‘store’)
#21 {main}

Hi,

I am having the same issue. It seems magento is trying to insert a row to SALES_FLAT_ORDER with the increment_id of the previous order of the customer.

Any luck finding a solution?

Thanks,
Michael

Ok, I did the following: I update the conflicting line in the SALES_FLAT_ORDER table and changed the increment_id to 99999999. I then tried placing the order again and it succeeded. BUT the increment_id of the new order is the same as the increment_id of the last order the customer had placed!! This is a major bug, and unless it is caused by a misbehaving addon I am surprised it hasn’t been caught by the magento development team.

Michael

Same here and question is this critical important bug or critical important addon error bug.

But it might be magento error, since we sometimes get errors for sagepay payments with duplicated order id numbers, but payments are different and taken (but those two payments should contain different order number? or not?).

Nope. Bug is still there… It’s not just the flat_order table you need to update, but any associated eav_entity_store values too.

So, go to the admin->sales->orders screen and look for the last successful order id.
go into eav_entity_store and in the last_increment_id column look for increments that match the last good order and update them by 2.

Hope this helps.

try This:

http://www.morningtime.nl/kb/173

copy /app/code/core/Mage/Sales/Model/Resource/Quote.php to /app/code/local/Mage/Sales/Model/Resource/Quote.php

change $bind = array(’:increment_id’ => (int)$orderIncrementId); to $bind = array(’:increment_id’ => $orderIncrementId);

this should fix the problem!

pschmidt - 21 September 2012 06:35 AM

Nope. Bug is still there… It’s not just the flat_order table you need to update, but any associated eav_entity_store values too.

So, go to the admin->sales->orders screen and look for the last successful order id.
go into eav_entity_store and in the last_increment_id column look for increments that match the last good order and update them by 2.

Hope this helps.

I know I’m late on this but I just had to say.. this has saved me.  I was having this duplication error and pulling out my hair, other solutions suggested removing all logs, quotes, and removing the MYSQL unique check..  All I did was increment eav_entity_store and it fixed my problem right away…

Thank you!