matrixxdg1
Starting Member
11 Posts Pre-sales questions only (More Details...)
|
Posted - 11/16/2017 : 10:24:47
Hi All, I am trying to set up my ASP shopping cart to connect with authorize.net. The server is running II7 and is TLS 1.2 compliant. When I try to connect for authorization I get the following error:
ERROR. Couldn't connect to https://secure.authorize.net/gateway/transact.dll (-2147012739) An error occurred in the secure channel support
I have yet to get a response from Authorize.net. I have searched Google and the forum here but have not found the answer.
Any ideas?
Thanks in advance for your help. MG
|
Sinbad
ECT Moderator
USA
65937 Posts |
Posted - 11/16/2017 : 11:16:56
|
matrixxdg1
Starting Member
11 Posts Pre-sales questions only (More Details...)
|
Posted - 11/16/2017 : 11:20:07
Hi Sinbad, Thanks for the quick response. I'll check with them but I am sure it is open.
I'll let you know. Thanks...MG
|
matrixxdg1
Starting Member
11 Posts Pre-sales questions only (More Details...)
|
Posted - 11/16/2017 : 12:18:06
Hi Sinbad, Yes... the hosting company confirmed that 443 was open. I also have an SSL cert installed on this domain name.
|
Andy
ECT Moderator
95440 Posts |
Posted - 11/17/2017 : 03:16:12
|
matrixxdg1
Starting Member
11 Posts Pre-sales questions only (More Details...)
|
Posted - 11/17/2017 : 06:05:30
Hi Andy, Thanks for the help on this. Below is the response I got.
Testing URL: https://ipnpb.sandbox.paypal.com/cgi-bin/webscr Error : Error, couldn't connect to https://ipnpb.sandbox.paypal.com/cgi-bin/webscr (-2147012739). An error occurred in the secure channel support
|
Andy
ECT Moderator
95440 Posts |
Posted - 11/17/2017 : 06:25:28
|
matrixxdg1
Starting Member
11 Posts Pre-sales questions only (More Details...)
|
Posted - 11/17/2017 : 06:37:31
Hi Andy, Ok, I ran the website but I am not sure what I am looking at. Below is the PDF link for the results.
[url]https://charitydonorservices.org/images/charitydonorservices.org.pdf[/url]
Thanks for your help.
MG
|
Andy
ECT Moderator
95440 Posts |
Posted - 11/17/2017 : 08:49:35
|
matrixxdg1
Starting Member
11 Posts Pre-sales questions only (More Details...)
|
Posted - 11/17/2017 : 09:03:13
Hi Andy. I am not sure you finished your question.
I will ask for you ???? to do what?
Thanks...MG
|
Andy
ECT Moderator
95440 Posts |
Posted - 11/17/2017 : 09:22:13
|
matrixxdg1
Starting Member
11 Posts Pre-sales questions only (More Details...)
|
Posted - 11/17/2017 : 09:23:49
Oh. Ok...Thank you.
|
matrixxdg1
Starting Member
11 Posts Pre-sales questions only (More Details...)
|
Posted - 11/17/2017 : 09:28:40
Hi Andy, Not sure if this helps.... sounds pretty useless to me. Here is the response from AUTHORIZE.NET after 2 days.
+++++++++++++++++++++++++++ Thank you for contacting Authorize.Net about that connection issue. I'm sorry for any inconvenience, but I'd be glad to help.
Unfortunately, there is not enough information in your description for me to pinpoint the cause, but I can provide some additional insight related to some of the items you've mentioned.
First, TLS: Currenlty, TLS versions 1.0, 1.1, and 1.2 are accepted by our system. However, just because your system is 'capable' of using TLS 1.2 does not necessarily mean that it always does. I suggest making sure that only those versions I've mentioned are being used, and no older SSL versions are possible instead.
Next, the URL you mentioned: That URL is still valid and functional, but it is not the one used for most of our current integration options. I suggest reviewing, or having your developer review, the guide at this site, to make sure your software system is not attempting to use an outdated connection method:
https://developer.authorize.net/api/upgrade_guide/
Finally, the error message itself: That is not an error message generated by our system directly, so we can't tell what might be causing it. I suggest contacting your developer or software support for a complete explanation of what might trigger their system to display that message, and contact us back if they indicate that a response from our system was the cause. If our system did send a response that triggered that message, we will need to know the details of that response in order to investigate further from our end.
I hope this information helps. Have a great day !
Regards, Brandon B Authorize.Net Support.
|
Vince
Administrator
42756 Posts |
Posted - 11/17/2017 : 09:38:36
Hi MG This does seem to be a problem making a secure connection to Auth.net but I would imagine it is more likely a problem your host can solve for you. Have you been in touch with your host? What did they say? This site has been running for a while no? So did anything change recently when this problem started occurring? Do you know what version of operating system is running on your server? (This shouldn't be an issue as Auth.net are still accepting non-TLS1.2 connections, but just out of interest.) I'm sure your host already know what areas to look into but here are some pointers just so they know what we are talking about... https://stackoverflow.com/questions/29688026/vb6-winhhtp-error-occurred-in-the-secure-channel-support Vince Click Here for Shopping Cart SoftwareClick Here to sign up for our newsletterClick Here for the latest updater
|
matrixxdg1
Starting Member
11 Posts Pre-sales questions only (More Details...)
|
Posted - 11/17/2017 : 09:50:21
Hi Vince, Yes I have opened a ticket with them and they are pushing the issue off on anyone but themselves. The site is currently just a holder page. I added the folder CART and pushed your cart up just like I unzipped it. I think the OS is WIN Server 2012 R2 but I will ask. I had a few issues getting the DB connection set up and they had to create and APP pool to get it to connect. Then I set up the cart and tried to run a card and got the error were at now. I tried both Authorize.net SIM and AIM with the same outcome. I will reach out to them again and push the issue.
On another note I set up an account with HostTek, since ya'll recommended them, and I am having the same DB connection issue. I have opened up a support ticket with them.
Thanks for all of your help on this.
MG
|
Vince
Administrator
42756 Posts |
Posted - 11/17/2017 : 11:40:15
|
matrixxdg1
Starting Member
11 Posts Pre-sales questions only (More Details...)
|
Posted - 11/17/2017 : 13:02:11
Sinbad, Vince and Andy....thank you for your help on this. I moved the domain to Hostek and after a small DB connection issue I got everything working and Authorize.net approving orders.
Just an FYI. I did have to make a change in the sDSN in the db_conn_open.asp file:
CHANGE:
Provider=Microsoft.Jet.OLEDB.4.0; TO:
Provider=Microsoft.ACE.OLEDB.12.0;
Thanks again for your great support. Happy Thanksgiving!!!
|
Sinbad
ECT Moderator
USA
65937 Posts |
Posted - 11/17/2017 : 13:44:01
|
|
|