Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Haven't yet done this, but seems like installing this <a href="http://www.magentocommerce.com/magento-connect/fooman-sameorderinvoicenumber.html" rel="nofollow">Fooman extension</a> would potentially fix the quotes using the wrong/old Order #. Does that work for you?</p> <p>Love to hear either way. I'm getting set to tackle this and make our PayPal exceptions more legible (using some of PayPal's explanations from <a href="https://cms.paypal.com/us/cgi-bin/?cmd=_render-content&amp;content_ID=developer/e_howto_api_nvp_errorcodes" rel="nofollow">here</a>. So if you do find it helps, would love to know.</p> <p>Edit: Found some further info <a href="http://www.bigdune.net/geek-blog/3-magento/6-magento-paypal-ipn-wrong-order-id.html" rel="nofollow">here</a>. Apparently the Fooman extension helps, but doesn't fix the problems completely. Does this help solve your problem?</p> <p>Edit: Per the <a href="http://www.magentocommerce.com/download/release_notes#Release%20Notes%20-%20Magento%201.7.0.0%20%28Apr%2024,%202012%29" rel="nofollow">change log for Magento 1.7.0.0</a> (which came out in April), they think they've fixed the problem:</p> <pre><code>Fixed: “Wrong order ID” exception in PayPal Express module under heavy load </code></pre> <p>Can anyone confirm that upgrading to Magento 1.7 does indeed fix the problem? Every time I've looked at it, it does seem to be a PayPal Express issue (our payments normally go through PayPal Pro and that doesn't seem to have errors).</p>
    singulars
    1. This table or related slice is empty.
    1. POMagento PayPal Duplicate Invoice Error
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USacorncom
    1. USacorncom
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. CONo, we already had the Fooman extension and it didn't help. I am 99% sure the problem is caused by the following... When a customer attempts an order and it fails, PP considers the Invoice # as already used while Magento does not. The next time the customer attempts an order, Magento finds the old record in the quote table and attempts to use it. PP returns the dup error, which Magento ignores and continues to use the same number. I have "patched" it by incrementing the number if I receive the dup error, but it doesn't address the root cause, so customers still see at least one error.
      singulars
      1. PO
      1. USBrianVPS
    2. COIf you find any good info or a real fix for this, please post it here as this is still an issue for us.
      singulars
      1. PO
      1. USBrianVPS
    3. COBrian, just found out that Magento 1.7 may have the fix (see my edit). Have you tried upgrading to it yet?
      singulars
      1. PO
      1. USacorncom
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload