Page 1 of 1

What is this error?

Posted: Thu Feb 11, 2010 4:20 pm
by Mike718NY
I got one last week and one today:

An error occurred during the checkout process. The checkout has failed 100 times and will
NOT BE attempted again. UserId: 18962 / zz_anonymous_18962@domain.xyz Customer:
xxxxxx xxxxxx / xxxxxxx@yahoo.com / 281532

Cannot insert the value NULL into column 'TotalCharges', table 'DCP8.dbo.ac_Orders';
column does not allow nulls. UPDATE fails. The statement has been terminated.

Re: What is this error?

Posted: Thu Dec 23, 2010 1:13 am
by AussieInSeattle
Anyone have a resolution to this? We are seeing this in our error logs too.

Re: What is this error?

Posted: Thu Dec 23, 2010 7:57 am
by jmestep
When I tracked it down in the past, it was because customer had hit the browser back button after they had checked out.

Re: What is this error?

Posted: Thu May 31, 2012 4:12 pm
by WylieE
Bringing an old thread back to life.

We encountered this error yesterday. (AC 7.0.7) We also noticed it caused OrderID and OrderNumber to get out of synch within the ac_Payments table.

For those that have encountered this error, did you happen to notice if OrderID and OrderNumber are now out of synch?

Thanks!

Re: What is this error?

Posted: Mon Jun 04, 2012 6:00 pm
by bsweeney
WylieE wrote:Bringing an old thread back to life.
Probably best to start a new thread, but since we're already here ...
WylieE wrote:We encountered this error yesterday. (AC 7.0.7) We also noticed it caused OrderID and OrderNumber to get out of synch within the ac_Payments table.

For those that have encountered this error, did you happen to notice if OrderID and OrderNumber are now out of synch?
This was my experience. It's not, technically, a problem for the two to get out of sync. Though it can be inconvenient. At the time I experienced this problem the order ID was being sent to my payment processor instead of the order number which made looking up orders inconvenient.

FYI, I never fully tracked down the problem as it did not occur often enough. I believe, however, that it may have been due to a credit card being rejected, resubmitted, and rejected again (we currently only process orders on the back end).