We are having an issue with Smith Cart when certain customers try to purchase products.  The problem is intermittent and not sure how to proceed trouble shooting.

The error on the purchase confirmation is:

"Error processing payment. Please try again.  SQLDateTime overflow.  Must be between 1/1/1753 12:00:00AM and 12/31/9999 11:59:59PM"

It is occurring when purchasing with a particular guests MasterCard, and we tried to process the payment ourselves as well with the customers card and received the same error.

We are using Smith Cart 5.68.0 and DNN Version 07.00.05 (130)

The only thing I see in the DNN Event Viewer is the following error:

Cart Error: at System.Data.SqlTypes.SqlDateTime.FromTimeSpan(TimeSpan value) at System.Data.SqlTypes.SqlDateTime..ctor(DateTime value) at System.Data.SqlClient.MetaType.FromDateTime(DateTime dateTime, Byte cb) at System.Data.SqlClient.TdsParser.WriteValue(Object value, MetaType type, Byte scale, Int32 actualLength, Int32 encodingByteSize, Int32 offset, TdsParserStateObject stateObj) at System.Data.SqlClient.TdsParser.TdsExecuteRPC(_SqlRPC[] rpcArray, Int32 timeout, Boolean inSchema, SqlNotificationRequest notificationRequest, TdsParserStateObject stateObj, Boolean isCommandProc) at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async) at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, DbAsyncResult result) at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method) at System.Data.SqlClient.SqlCommand.ExecuteScalar() at Microsoft.ApplicationBlocks.Data.SqlHelper.ExecuteScalar(String connectionString, CommandType commandType, String commandText, SqlParameter[] commandParameters) at Microsoft.ApplicationBlocks.Data.SqlHelper.ExecuteScalar(String connectionString, String spName, Object[] parameterValues) at Smith.DNN.Modules.BuyNow.SqlDataProvider.AddCustomerAdmin(CustomerInfo info) at Smith.DNN.Modules.BuyNow.Confirm.a(PaymentStatus A_0, Boolean A_1) at Smith.DNN.Modules.BuyNow.Confirm.Submit() at Smith.DNN.Modules.BuyNow.Confirm.btnSubmit_Click(Object sender, EventArgs e)

Server Name: DMZWebProd

I am unsure how to proceed in troubleshooting, can anyone please help and advise?

Thanks in advance.

Hey Kevin,

Everything you need should be attached, if you need anything else let me know.

Thanks,

Hey Kevin,

We are using Authorize.net and the zip file attached should have every screen shot  you need.  If you need anything else, let me know.

Thanks

I am using version 5.71 and getting this same error message on a localhost setup using a test account for authorize.net. Was this ever resolved and if so what was the solution?

I guess the error I'm getting is slightly different, but I consistently get it every time.  The error message that appears on the checkout screen is the same, a SqlDateTime overflow, but the error posted to the event log is different than the one above:

System.Data.SqlClient.TdsParser.TdsExecuteRPC(_SqlRPC[] rpcArray, Int32 timeout, Boolean inSchema, SqlNotificationRequest notificationRequest, TdsParserStateObject stateObj, Boolean isCommandProc, Boolean sync, TaskCompletionSource`1 completion, Int32 startRpc, Int32 startParam) at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async, Int32 timeout, Task& task, Boolean asyncWrite) at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, TaskCompletionSource`1 completion, Int32 timeout, Task& task, Boolean asyncWrite) at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method) at System.Data.SqlClient.SqlCommand.ExecuteScalar() at Microsoft.ApplicationBlocks.Data.SqlHelper.ExecuteScalar(SqlConnection connection, CommandType commandType, String commandText, SqlParameter[] commandParameters) at Microsoft.ApplicationBlocks.Data.SqlHelper.ExecuteScalar(String connectionString, CommandType commandType, String commandText, SqlParameter[] commandParameters) at Microsoft.ApplicationBlocks.Data.SqlHelper.ExecuteScalar(String connectionString, String spName, Object[] parameterValues) at Smith.DNN.Modules.BuyNow.SqlDataProvider.AddCustomerAdmin(CustomerInfo info) at Smith.DNN.Modules.BuyNow.Confirm.a(PaymentStatus A_0, Boolean A_1) at Smith.DNN.Modules.BuyNow.Confirm.Submit() at Smith.DNN.Modules.BuyNow.Confirm.btnSubmit_Click(Object sender, EventArgs e)

The trial version I downloaded is version 5.71, but then I noticed after purchasing the license that the download link was for version 5.77. I guess the first thing to do would be to upgrade my version to the latest one.

Edit: upgraded to 5.77 but still getting the same problem.  I think I'll have to move everything to a test site and send you guys a link, since I doubt the problem will happen on your own staged site.  I get this error when logged in as host, but if I create a normal user account and then try to checkout while logged in with that I get a completely different critical error:

AssemblyVersion:7.2.1
PortalID:0
PortalName:ShowSim
UserID:2
UserName:pyronaught
ActiveTabID:98
ActiveTabName:Purchase
RawURL:/Purchase/ctl/Cart/mid/494
AbsoluteURL:/Default.aspx
AbsoluteURLReferrer:http://localhost:52120/Purchase/ctl/Cart/mid/494
UserAgent:Mozilla/5.0 (Windows NT 6.2; WOW64; rv:27.0) Gecko/20100101 Firefox/27.0
DefaultDataProvider:DotNetNuke.Data.SqlDataProvider, DotNetNuke
ExceptionGUID:59f407cb-8146-4a9c-a50d-0601870f2743
InnerException:Index was outside the bounds of the array.
FileName:
FileLineNumber:0
FileColumnNumber:0
Method:Smith.DNN.Modules.BuyNow.Cart.ad

StackTrace:

Message:

DotNetNuke.Services.Exceptions.PageLoadException: Index was outside the bounds of the array. ---> System.IndexOutOfRangeException: Index was outside the bounds of the array.
   at Smith.DNN.Modules.BuyNow.Cart.ad()
   at Smith.DNN.Modules.BuyNow.Cart.Checkout()
   at Smith.DNN.Modules.BuyNow.Cart.btnMakePayment_Click(Object sender, EventArgs e)
   at System.Web.UI.WebControls.LinkButton.OnClick(EventArgs e)
   at System.Web.UI.WebControls.LinkButton.RaisePostBackEvent(String eventArgument)
   at System.Web.UI.WebControls.LinkButton.System.Web.UI.IPostBackEventHandler.RaisePostBackEvent(String eventArgument)
   at System.Web.UI.Page.RaisePostBackEvent(IPostBackEventHandler sourceControl, String eventArgument)
   at System.Web.UI.Page.RaisePostBackEvent(NameValueCollection postData)
   at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
   --- End of inner exception stack trace ---

 Hi Kevin,

I was trying both methods actually.  I did notice that Authorize.net has it's own Test Mode that you can set from the Authorize.net account screen on a live account, which is probably a better way to prevent transactions from going through than using the Test mode on the cart settings.  The two testing scenarios that seem to work are using an Authorize.net testing account with the Test mode turned on in the cart settings and using a live Authorize.net account with the test mode turned off in the cart and the Authorize.net test mode turned on.  When using the live account with the test mode turned on in the cart, I would get an error after submitting the order which said that the account login was invalid or inactive.  Turning off the test mode in the cart and using Authorize.net's own test mode fixed that problem.

The original problem mentioned above about the "index out of bounds" error seems to have gone away and I'm not sure what fixed it.  I suspect it was something with the payment gateway settings that caused it.

Just a follow up...

We received this error again, and after digging into Authorize.net we received the same error again because the Zip Code entered did not match the Zip Code for the card. Customer was trying to use a Business Credit Card and entered the wrong information.

We also found that the first time we encountered this issue (Top of the post) that Authorize.net says the card was declined.

Might be something to look into and see if the module can return a more general card error rather than the SQLDateTime error.