Checkout failures

[joebeazelman]

Some of my customers are complaining that they are having checkout failures. It occurs after they enter their credit card number. They claim nothing happens, sometimes they see the "processing" message and it stays there forever. It doesn't seem to be browser specific as it is happening on both FF and IE. I am using the "AbleCommerce Test Gateway" as a gateway so there shouldn't be any gateway issues. The only way I can see this happening is if they have javascript turned off, but they wouldn't have made it that far.

I haven't been able to reproduce this on my machine and I have tried every major browser. The error is flooded with Invalid viewstate errors which are common, but I did see this which may not be related to my issue:

11/13/2009 10:01:32 AM Error An error has occured at http://www.asdf.com/WebResource.axd?d=O ... ycemRBipV0 Invalid length for a Base-64 char array.


Here's what I'm running:
PLATFORM: ASP.NET
VERSION: 7.0.3
BUILD: 12458
MSSQL v2005
AC SCHEMA v2005

[joebeazelman]

Just checked the log a couple of hours after customer called about the problem. Here's the error dump:

11/16/2009 12:19:10 PM Error An error has occured at http://www.asdf.com/WebResource.axd?d=O ... OHTUGT4hZv('ASP.NET Ajax client-side framework failed to load.');//]]></script><script src= Invalid viewstate.


Any suggestions?

[dappy2]

I have been researching a similar issue.

I've had a few conclusions:
1. I have some javascript functions set to run in a way that allowed them to function even after a partial postback. This caused issues.
2. One customer said it occurred when trying to create an account during checkout (anonymous checkout is allowed). I'm still working on this one.

Dappy

[joebeazelman]

Thanks for the reply. Do you think this may have anything to do with the viewstate? I disabled viewstate encryption and the problem still occurs. I've been reading about the base-64 error message and some folks have mentioned that it has something to do with the ViewState being so long that some some network filtering software software or browser truncate them. Indeed, the viewstate variable can be quite large during a checkout. My logs are flooded with viewstate errors and none of the solutions mentioned on other threads has resolved the problem.

http://stackoverflow.com/questions/8587 ... char-array