I had this same exception in Magento 1.6.1 showing up in exception.log. The problem for us was that the Order Number and Invoice Numbers were out of sync.
Thanks for a great extension from Fooman! Just install their “SameOrderInvoiceNumber” extension, remember to enable it in “Configuration | Sales | Order Numbers” and you’re all set!
Solved the problem for us on Magento 1.6.1… don’t mess with core code!
OK… so I have to take back that it’s all solved after the solution posted above. It definitely helped to reduce the errors, but didn’t solve it.
EDIT: For those of you who have been following this thread, we’ve posted a variety of solutions for this problem, but have yet to find one that completely solves the “Wrong Order ID” error in the Paypal IPN.
With a lot of input from the community on our blog, we’ve concluded for now that the primary cause of this error is related to lack of server performance. There’s definitely some big quirks to Magento’s Paypal IPN module, but with each update they continue to make improvements.
For a full breakdown of our analysis on this error, see this blog post:
Hope that helps! Been running for a day on one of our client’s sites with a high transaction turnover and not a single error so far.
Hi there, I apologize if I seem a bit thick, but I’ve read over almost all the posts I could find on you discussing this topic and I have read your website’s article extensively, but I still fail to see the solution...unless it’s just to improve the server’s hardware and resources? Is that the only way to fix this issue?
I apologize if I seem a bit thick, but I’ve read over almost all the posts I could find on you discussing this topic and I have read your website’s article extensively, but I still fail to see the solution...unless it’s just to improve the server’s hardware and resources? Is that the only way to fix this issue?
After a few weeks of running a “code fix” we had posted on our site previously it ended up not truly solving the source of the error. For now, our conclusion is that there is a definite close relationship with server load and this error showing up. On our higher performance dedicated servers we have never had this error show up.
Sorry there’s no quick “code-fix” for this… not from what we’ve found so far.