|
|
 |
 |
Joined: 5/14/2010
Posts: 89
|
|
|
We just installed this module on a DNN site, we want to use the AIM side of Authorize.net. Using a test account run through and using the live account (with my CC) we consistently get this error: "We couldn't complete your payment. Status: false Auth Code: Message: The underlying connection was closed: Could not establish trust relationship for the SSL/TLS secure channel." This is a secure site on a dedicated server.
Now we really want to use the recurring payments part of this module but when we turn that on we get this error: "DotNetNuke.Services.Exceptions.ModuleLoadException: 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.Registration.Confirm.ProcessARB() at Smith.DNN.Modules.Registration.Confirm.btnSubmit_Click(Object sender, EventArgs e) --- End of inner exception stack trace ---"
We are able to get it the module to "sort of" work using the SIM side of Authorize.net but it will not send us the emails from the website so we lose out on the information the user fills out. It also will not go back to the correct page of the website after a successful payment and you hit the button at the top of the receipt page. It does not matter what Redirect URL I put in Autorize.net, it tacks on a :443 at the end of the main URL and eventually times out with "Page Not Found".
This module has been nothing but time consuming to get working. If it helps, the site is on an iHost server and maybe you have encountered this problem through their servers. Any help would be appreciated.
|
|
|
|
 | |
|
|
 |
Joined: 1/1/0001
Posts: 0
|
|
|
Hi John,
Which version of the Smith Registration Pro module and DNN are you currently running?
Thanks,
|
|
|
|
| |
|
|
|
|
Joined: 5/14/2010
Posts: 89
|
|
|
4.22 smith, 5.5.1 DNN for both. We also tried it for testing in 6.1.1.
|
|
|
|
| |
|
|
|
Joined: 1/1/0001
Posts: 0
|
|
|
Hi John,
I recommend upgrading to the latest version of the module. Please email your purchase reciept and User ID to me at kevin@smith-consulting.com and I will send you the latest version of the RegPro.
Thanks,
|
|
|
|
| |
|
|
|
|
Joined: 5/14/2010
Posts: 89
|
|
|
The upgrade made no difference. Next suggestion? My 2 clients are close to asking me for a refund and that, of course, trickles down hill.
|
|
|
|
| |
|
|
|
Joined: 1/1/0001
Posts: 0
|
|
|
Hi John,
I am unable to replicate this issue on our test portal.
I believe this issue you reported is related to an issue with your SSL setup and configuration.
Who is your hosting provider?
The RegPro module does not have any specific code that manipulates or requires ssl, it is implemented in your iis web server and enabled in your dnn portal. Its posiible that you ssl cert is invalid or corrupt. If you are getting an ssl error I would try the following:
1. Delete your current ssl cert on your web server
2. Re generate your ssl cert from the provider where you purchased it
3. Download your ssl cert to your server
4. Install it to your web server again
I have googled the error returned from Auth.net and the majority of links seem to point to permissions issues with the SSL cert. installed on your server. This issue can also be caused by the following:
• Corrupt SSL Cert
• Incorrect web.config configuration
• IIS Config issues
Thanks,
|
|
|
|
| |
|
|
|
|
Joined: 5/14/2010
Posts: 89
|
|
|
We just did the upgrade to 4.27, nice improvements but a whole new set of issues. Using 6.1 DNN.
1. The setting for the module screw up in the light box: http://screencast.com/t/H79zlvtp2M1. If I go to Layout View the Lightbox settings work fine. A jquery conflict somewhere in there.
2. The main dropdown menu ceases to work. We're not using the banner, just the ribbon dropdown. See http://wowwebworks.com/Services/Subscriptions.aspx. Then go off to another page and the menu works again.
3. The site we are having the connection to Authorize.net problems is hosted on iHost. If that was the problem it would seem that our Dynamic Registration form would not work either and we successfully use that for AN payments, no problems at all. Leads me to believe it's something else.
Ideas?
|
|
|
|
| |
|
|
|
Joined: 1/1/0001
Posts: 0
|
|
|
Hi John,
I have tried to replicate this issue in our test portal and have been unsuccessful. The issue may be due to the upgrade and requires a clean installation of the module. Please email me at kevin@smith-consulting.com and I will also send you the latest release v.4.30.
Thanks,
|
|
|
|
| |
|
|
|
|
Joined: 5/14/2010
Posts: 89
|
|
|
Hi Kevin,
I have completely gone through and deleted the module and tables and then did a reinstall of v.4.27. I went and did a test payment with my sandbox account, one product and no reoccurring payment, and it worked great!
I then proceeded to set up the reoccurring payment and I get a "A critical error has occurred. Object reference not set to an instance of an object." when submitting payment.
In the "My Account" module the "Subscription ID", "Date Created", and "First Name" are missing in the payment I just set up. If I try to cancel the subscription from the "My Account" module, I get this error "A critical error has occurred. Input string was not in a correct format."
In the admin section, it does not show anything tin the "Subscriptions" section but under "Customer Payments" I can see the reoccurring payment I just submitted. The "First Name" field is filled out but the "Auth Code" and "Create Date" are empty. The status lists "OK". I also get the same error here trying to "Cancel Subscription" as I did in the "My Account" module. However I am able to delete the payment.
It seems like Authorize.net is not getting all of the information it needs (hence the blank fields) and that is why the errors are occurring. We do not have the latest version yet that you are sending over to us but I am not sure it will clear up this issue. By the way, I have tried the "Reoccurring Payment" with both a test and live account with the same result but they both work when the product is not set up as a "Reoccurring Payment".
Thanks.
|
|
|
|
| |
|
|
|
|
Joined: 5/14/2010
Posts: 89
|
|
|
The subscriptions are actually getting setup but I cannot get rid of the error "A critical error has occurred. Object reference not set to an instance of an object." after submitting payment.
Here is what is in the event log:
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.Registration.Confirm.btnSubmit_Click(Object sender, EventArgs e) at System.Web.UI.WebControls.Button.OnClick(EventArgs e) at System.Web.UI.WebControls.Button.RaisePostBackEvent(String eventArgument) at System.Web.UI.WebControls.Button.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 ---
Again, this only happens while using Reoccurring Donations, the payment goes through fine for a one time payment.
|
|
|
|
| |
|
|
|
|
Joined: 5/14/2010
Posts: 89
|
|
|
Kevin,
Any progress at all? If an update is coming let us know. Something. Silence doesn't help us communicate progress to the client waiting for us to perform promised work.
John
|
|
|
|
| |
|
|
|
Joined: 1/1/0001
Posts: 0
|
|
|
Hi John,
Programming is currently working on the lightbox issue you reported with the Settings running DNN 6.1 and RegPro v.4.27 and I will postback as soon as an update is available.
Regarding the issue you reported above with a Product setup for recurring billing, I have not been able to replicate this issue. Before sending you the latest version, can you log into our test portal www22.smith-consulting.com and try to replicate the issue. This will determine if the issue is with the latest version of RegPro or an issue with your specific DNN portal/Reg Pro install. We will email you login credentials.
Thanks,
|
|
|
|
| |
|
|
|
|
Joined: 5/14/2010
Posts: 89
|
|
|
We are still waiting for the login information for the test site but in the mean time I have figured out some of what is going on with this.
When submitting a reoccurring payment to Authorize.net, it works but we get the error on the website. I have done two installs of this on two different severs both with the same result. I have found that once I submit my payment, the module is not redirecting to the ConfirmStatus.acsx page. That is why we are getting the "Object Reference Not Set to An Instance Of An Object" error. After I get the error and replace the url I get back with http://mydomain.com/tabid/115/Default.aspx?ctlname=ConfirmStatus I can see the confirmation page with a successful payment and reoccurring donations set up.
Any thoughts on this?
|
|
|
|
| |
|
|
|
Joined: 1/1/0001
Posts: 0
|
|
|
Hi John,
Are you currently running v.4.27 or v.4.30?
We sent login credentials to the www23 test environment last week, the message may have found its way to your spam box, I will resend the credentials now please confirm if the message is received.
Thanks,
|
|
|
|
| |
|
|
|
|
Joined: 5/14/2010
Posts: 89
|
|
|
I was able to reproduce the error on the test site at http://www23.smith-consulting.com. I actually get two different errors on your test portal. These errors happen when using reoccurring payments. You can see the error in the event viewer at 5:14:54AM.
First Error:
DotNetNuke.Services.Exceptions.ModuleLoadException: 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.Registration.Confirm.PopulateSubscription(ARBCreateSubscriptionRequest request) at Smith.DNN.Modules.Registration.Confirm.CreateSubscription(Boolean forceXmlError) at Smith.DNN.Modules.Registration.Confirm.ProcessARB() at Smith.DNN.Modules.Registration.Confirm.btnSubmit_Click(Object sender, EventArgs e) --- End of inner exception stack trace ---
Second Error:
DotNetNuke.Services.Exceptions.PageLoadException: The Controls collection cannot be modified because the control contains code blocks (i.e. <% ... %>). ---> System.Web.HttpException: The Controls collection cannot be modified because the control contains code blocks (i.e. <% ... %>). at System.Web.UI.ControlCollection.Add(Control child) at DotNetNuke.Services.Exceptions.Exceptions.ProcessModuleLoadException(String FriendlyMessage, Control ctrl, Exception exc, Boolean DisplayErrorMessage) --- End of inner exception stack trace ---
|
|
|
|