Ecart Errror Order exist in Database

What would cause a customer to get the message above while trying to place an order.

We are using data assist to store order details. The order did not process with Linkpoint nor did the Database record the order.

Secondly How can i fix this on the clients side.

2 hours later after pulling most of my hair out and getting calls from customers that cant complete their transactions.......

Turns out that Linkpoint declined a transaction and any new transaction after that got the error that the order number exist in the database. Seems Ecart tried to store the transaction even though it was declined. However thier was no transaction stored in the database.

What fix is there for this?

If there is an error with the order then no details about that order should be stored in the db, instead you should just go to the checkout failure page.

With the eCart store order summary and store order details server behaviors it will either insert a new order or update an existing one. If the order is already in the db then you should not get an error from this server behavior.

If Linkpoint is sending this error message and you attempt to run the transaction again you will get an error like this about the order having already been processed. Do you have any custom order recording or error messaging on any of these pages?

If you are getting this error closing the browser and opening it again should clear up the problem. Please let us know if you continue to have this problem and if it is something you can reproduce with a set of steps.

Originally Said By: Eric Mittman

  If there is an error with the order then no details about that order should be stored in the db, instead you should just go to the checkout failure page.

With the eCart store order summary and store order details server behaviors it will either insert a new order or update an existing one. If the order is already in the db then you should not get an error from this server behavior.

If Linkpoint is sending this error message and you attempt to run the transaction again you will get an error like this about the order having already been processed. Do you have any custom order recording or error messaging on any of these pages?

If you are getting this error closing the browser and opening it again should clear up the problem. Please let us know if you continue to have this problem and if it is something you can reproduce with a set of steps.  

I believe that Linkpoint is sending the error when a customer tries to re-submit their order and the session id (which is the order number that goes to linkpoint), does not change on their second attempt. This only happens when an order is declined by linkpoint. I do not have any custom order recording or error messages.

If you are using php then you may be able to get around this issue by recreating the session id, this is the id that is used as the unique order identifier. On your checkout failure page you will want to add this code at the bottom of the page:

<?php session_regenerate_id(); ?>

If the problem occurs because the same session id value is being used as the identifier of the order then this code should prevent this from occurring.

Originally Said By: Eric Mittman

  If you are using php then you may be able to get around this issue by recreating the session id, this is the id that is used as the unique order identifier. On your checkout failure page you will want to add this code at the bottom of the page:

php:

<?php session_regenerate_id(); ?>

If the problem occurs because the same session id value is being used as the identifier of the order then this code should prevent this from occurring.  

Would this do the same same thing on a checkout success page? I had a customer that tried to order a second order without closing their browser and got an order exist error

Yes, this would work the same on the checkout success as well and allow a user in the same session to make additional transactions.

This may be a dumb question but i get nervous adding code to the confirm page. You indicated the code should be at the bottom does that mean the very last line on the page?

You would be putting this code on the checkout success and checkout failure pages. It can be the very last line on the pages, that is ok.