Thread: Missing orders?

Going through the Orders table in the database I noticed that we have been missing numerous orders. The order numbers skip in no particular pattern eg:
127381
127382
127383
127385

I am unable to think of any way by which orders would be "missing". Anyone noticed similar issues or know of the cause? BTW we are currently using the older ML v7.1

Thanks

For us, in v8, it's because there's been a failed payment gateway transaction.

Originally Posted by esedirect

For us, in v8, it's because there's been a failed payment gateway transaction.

We don't authorize transactions on our website. They are downloaded into our Catalog Manager and then authorized.

Are you using multistore? I believe it will use order numbers across all stores.

We are not using Multistore. We use V7.1 (officially unsupported)

Check your FailedTransactions table in the DB and see if your missing orders are in there. Even without a live gateway hooked up, there are a few rare issues that could arise that would prevent an order from going through.

Wow, I didn't even know that FailedTransaction table existed! Unfortunately it is empty, something strange is going on..

Can you check the orders.dbo within SQL to check?

OP would be better checking the OrderNumbers table like this:

Code:

select ONo.*, O.OrderNumber
FROM OrderNumbers ONo (NOLOCK)
LEFT JOIN Orders O (NOLOCK) ON ONo.OrderNumber = O.OrderNumber
WHERE o.OrderNumber IS NULL

if [dbo].[OrderNumbers] exists in ML7.1, of course.

This will show what OrderNumber was generated, but not used. Also you could then use the CreatedOn date/time to maybe pinpoint something in your IIS logs as to any errors.

We have the same problem in ML v7.x. The order appears in the database in the OrderNumbers table, but not in the Orders table. The order doesn't appear in the FailedTransactions table. The payment processor is Authorize.Net and they receive the charge and charge it successfully.

UPDATE: I found an error log that shows the user in question with the missing order experienced a general exception during checkout:

InnerException: Thread was being aborted.
Message: System.Threading.ThreadAbortException: Thread was being aborted.at System.Threading.Thread.AbortInternal()at System.Threading.Thread.Abort(Object stateInfo)at System.Web.HttpResponse.End()at System.Web.HttpResponse.Redirect(String url, Boolean endResponse)at System.Web.HttpResponse.Redirect(String url)at AspDotNetStorefront.Modules.ASPDNSF_Checkout.check outreview.ProcessCheckout()

Any ideas how to prevent this in the future? Thanks!

UPDATE #2: Maybe that above error is unrelated. It looks like Response.Redirect *Always* throws an thread aborted exception (which is expected, according to Microsoft).