HomeHome Product Discus... Product Discus...SmithCartSmithCartError Processing Payment. Object reference not set to an instance of an object.Error Processing Payment. Object reference not set to an instance of an object.
Previous
 
Next
New Post
11/12/2012 11:42 AM
 
Hi Alex,
Please restore from backup from your last working version so your live site is not down. Setup a test site for testing module upgrades and only install the cart module on your live site after you have tested and confirm working on your test site. In the meantime we will test the manual gateway and try to confirm if the issue you are reporting is a bug in the cart.

thanks,


Scott Kelly
Project Manager
DotNetNuke Consulting, DotNetNuke Store and DNN Ecommerce
 
New Post
11/12/2012 1:18 PM
 
Hi Scott -

The nature of this error has caused an issue with my backups. We did first install the module on a temp site, and test checkout functionality on all store before moving it to live. At the time, it was functional - I doubt however that I checked the event viewer for errors. That was my mistake.

We migrated the temp site to live, and for two weeks, it did function normally. We populated our backup site with the installation. At that point we had stopped testing the checkout, only to find out a week later that it was not working. We have checked all the backups available on our temp hosting, and they all generate the same error, but only after a day or two of working normally (minus the event viewer errors being generated).

I will try downgrading our Smith Cart install tonight, to see if that has any effect. It's hard to know, because the error does not happen right away.

I appreciate you looking into this, but unfortunately, restoring a backup will not solve my problem. Let me know if there is anything at all I can do to help expedite your troubleshooting.

Alex
 
New Post
11/12/2012 4:18 PM
 
I spoke with dave tonight on the phone. We discussed several methods to tackle this problem. Thanks for your support!
 
New Post
11/26/2012 9:57 AM
 
Dave recommend that we do a clean install of DNN and Smith Cart, and re-import our products. He informed me that since they are unable to reproduce the error on their servers, they can not troubleshoot it.

I completed this and installed a fresh re-installation of my website running SmithCart 5.24 We developed on a temp installation, and then migrated this installation to our live server after testing.

After migrating the site to live, I set up the payment gateways on each buy.now module to manual, accepting all credit cards and paypal. All buy now modules are configured as "child portals" to enable product sharing between them.

After a day of working fine, the exact same error is now happening again on my live site. However, checkout is still working on my temp site.

Differences between the two for troubleshooting purposes:
1. SSL is enabled on the live site, and not on the temp.
2. The temp site has only one buy.now module set up with a payment gateway of manual, the other 33 say "-Select-"
3. The temp site has only one "payment method" added, which is telephone. The live site has Credit Card  and telephone payment methods.
4. We did change the "User E-mail Template" after the migration
5. We did configure the "Invoice Templates" after the migration

I think I remember that back in version 4.93 if you set up a payment gateway for one buy.now module, it populated to all buy.now modules on the portal. This is the reason why on my temp site I did not set up the payment gateways for each buy.now module. When/why did this change?

I am very much inclined to believe that the issue resides within the manual payment gateway, and or how the manual payment gateway interacts with other buy.now modules, when a portal has multiple instances of the buy.now module present.


Below is a reply I made to a post made by another user experiencing a similar issue. However, I have since realized that on both my temp and live site, all but one of the buy now modules are set up as being a "child portal", with a single module being set up as a "Master portal". I hope this information can help expedite the troubleshooting process.

Alex


My site is experiencing the EXACT same issue. Checkout worked fine for almost a day, and then randomly started producing the error while no work was being done to the portal. From my troubleshooting, I think the issue resides within either the manual payment gateway and/or within the child-parent-master portal setup.

On your site do you have multiple pages with the buy.now module on them? If so, how do you have them configured in the parent child relationship? Are you using the manual payment gateway?

Reasons that have lead me to this conclusion:
I have a temp site up currently that is an exact copy of my live site, only without the payment gateways and or parent/child setup. We set those up after migrating to the live server. Checkout is working fine on that temp site.

I think I remember that back in version 4.93 if you set up a payment gateway for one buy.now module, it populated to all buy.now modules on the portal. This is the reason why on my temp site I did not set up the payment gateways for each buy.now module. When/why did this change?

After moving my temp site to live, I went into each buy.now module and set each one up for the manual payment gateway, accepting all credit cards, and added paypal checkout. I then went into each buy.now module and set each one to be a child portal, so that products could be shared in-between them.

I really hope that someone from SmithCart can help us out here. This is at least the fourth thread I've seen on my issue. I even received a phone call from another Smith Cart user last weekend experiencing the same issue.
 
New Post
11/26/2012 2:09 PM
 
Hi Alex,
Just wanted to confirm our phone conversation this morning that we have a test plan to try and replicate the issue you reported and we are both testing now. We have setup up multiple instances of the buynow module on both a parent and child portals and configured sharing products between buynow modules in order to try and replicate the issue. Also, we are testing with different payment gateways and payment methods for each buynow module instance.

I will post back with a status update after testing and hopefully we can replicate the issue you reported.

At your service,
Dave Smith
DotNetNuke Consulting, DotNetNuke Store and DNN Ecommerce
 
New Post
11/26/2012 2:37 PM
 
Yes Dave - Thanks for looking into this.

I am currently also testing on my site, and trying to pin down specifically what is causing the issue. I'll report if/when I can reproduce the error with hopefully some useful information.
 
New Post
11/26/2012 3:36 PM
 
Ok.

As of 5:30 PM today, both my temp site and live site have a working checkout.

I have just added the manual payment gateway to each buy.now module instance. I have not yet added the paypal payment option to the checkout.

I will wait till tomorrow, and test if the error crops up again tonight. It usually takes a while. If it does not, then I will attempt to add the paypal checkout option.

This time, I have each buy.now module set as a "child portal". Before I had one module with the "master portal" option selected.

I noticed that my temp site already has email templates setup, so I think we can rule that out. I did add an invoice template. I will report in again tomorrow morning.
 
New Post
11/26/2012 7:13 PM
 
Hi Alex,

Thank you for the update. Can you confirm if there are any errors being logged to your DNN Event Viewer while your checkout is working?

Thanks
 
New Post
11/27/2012 7:14 AM
 
I just completed a checkout at 8:30 AM. More than 12 hours since the last test. Checkout is still working for both a user creating a login during checkout and a pre-logged in user. I still anticipate the error to come back within the next 24 hours on it's own, so I will not change any smith modules in any way during that time. I would also like to point out that currently my DNN scheduler is enabled. On previous instances where the error occurred, I had the scheduler disabled.

I checked my event viewer to see if any errors were generated during the checkout process. During my two checkout attempts there were none. However, I did notice a few things that are noteworthy in the event viewer. 90% of the new users registered on my portal do so during the checkout process. Last night I had two such users.

Immediately following the registration log entry of a new user, I had the following "Page Load Exception" logged in my event viewer.


AssemblyVersion: 6.2.4

PortalID: 0

PortalName: YandasMusic.com - Online Music Web Store

UserID: 15

UserName: syahmi

ActiveTabID: 229

ActiveTabName: 01

RawURL: /01/tabid/229/ctl/Step2/mid/634/Default.aspx

AbsoluteURL: /Default.aspx

AbsoluteURLReferrer: https://www.yandasmusic.com/01/tabid/229/ctl/Step2/mid/634/Default.aspx

UserAgent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:13.0) Gecko/20100101 Firefox/13.0

DefaultDataProvider: DotNetNuke.Data.SqlDataProvider, DotNetNuke.SqlDataProvider

ExceptionGUID: 1471e939-5569-4add-a82c-a9cc2ef54870

InnerException: Object reference not set to an instance of an object.

FileName:

FileLineNumber: 0

FileColumnNumber: 0

Method: Smith.DNN.Modules.BuyNow.Step2.ibNext_Click

StackTrace:

Message: DotNetNuke.Services.Exceptions.PageLoadException: Object reference not set to an instance of an object. ---> System.NullReferenceException: Object reference not set to an instance of an object. at Smith.DNN.Modules.BuyNow.Step2.ibNext_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 ---

Source:

Server Name: CLOUD278



And in similar fashion, right after another user had registered, my event viewer logged the following error:

AssemblyVersion: 6.2.4

PortalID: 0

PortalName: YandasMusic.com - Online Music Web Store

UserID: 13

UserName: Toxicus

ActiveTabID: 241

ActiveTabName: 13

RawURL: /13/tabid/241/ctl/Step2/mid/727/Default.aspx

AbsoluteURL: /Default.aspx

AbsoluteURLReferrer: https://www.yandasmusic.com/13/tabid/241/ctl/Step2/mid/727/Default.aspx

UserAgent: Mozilla/5.0 (compatible; MSIE 9.0; Windows NT 6.1; Trident/5.0)

DefaultDataProvider: DotNetNuke.Data.SqlDataProvider, DotNetNuke.SqlDataProvider

ExceptionGUID: fb3b4ab0-ecf1-4eeb-97c5-1f210ce72319

InnerException: Object reference not set to an instance of an object.

FileName:

FileLineNumber: 0

FileColumnNumber: 0

Method: Smith.DNN.Modules.BuyNow.Step2.ibNext_Click

StackTrace:

Message: DotNetNuke.Services.Exceptions.PageLoadException: Object reference not set to an instance of an object. ---> System.NullReferenceException: Object reference not set to an instance of an object. at Smith.DNN.Modules.BuyNow.Step2.ibNext_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 ---

Source:

Server Name: CLOUD278


 
New Post
11/27/2012 2:49 PM
 
As of 5 PM today, checkout is still functioning normally. We are still running only the manual payment gateway, accepting all credit cards. I have not added PayPal checkout option to the cart's yet.

In my event viewer I saw that three more users registered today. Again, following the registration of all three, there is a page load error of the exact same nature as the two listed above. I have tried every combination I can think of, but when I create a new user during checkout, the event viewer does not log an error. I tried this at two different locations. It might be specific to a certain browser. This error might be unrelated, but it is referencing an "object reference not set to an instance of an object" which is the same message the faulty checkout would produce.

We are now on 30+ hours of checkout working normally. I will wait 24 more hours before attempting to add the paypal checkout option.

Hope this information is of some use.
Alex
 
New Post
11/27/2012 8:23 PM
 
Hi Alex,

Thanks again for the update and this is sounding promising. Please keep us posted.

Could you also please specify what your Sign In And Registration configuration is in your store? I will look into the errors which are being logged when a user registers and will try in different browsers.

Thanks
 
New Post
11/28/2012 6:36 AM
 
My Sign In & Registration settings are as follows:
Radio Button Selected: Show Sign In Page
Check Box Checked: Require Login

That is all. Let me know if I can help in any way! I want this to work just as badly as you ;)
 
New Post
11/28/2012 2:11 PM
 
Many thanks!

We will keep you posted!
 
New Post
11/29/2012 6:40 AM
 
Just reporting back in,

I am now at 3 days of having a working checkout. I can still see in my event viewer that new users are still getting that same object reference error on the step 2 checkout page after creating an account.
 
New Post
11/30/2012 2:06 PM
 
Hi Alex,

Just checking to see how your store is processing orders.

We are still trying to determine the cause of the errors which are being recorded to your DNN Event Viewer when a new user registers through checkout but we have been unable to trigger the error on my test site. As a possible solution we may need to deploy some files to your site to log the exact line of code throwing the error.

Please let me know if you have any questions.

Thanks
 
Previous
 
Next
HomeHome Product Discus... Product Discus...SmithCartSmithCartError Processing Payment. Object reference not set to an instance of an object.Error Processing Payment. Object reference not set to an instance of an object.