Sage 100

Hi Group, As you know today was the last day of the support of Sage Exchange Desktop(SED) 1.x. But we did not expect that SED v2.0.2.31 will have an issue. It stop working today in the afternoon for one of our clients and they could not run any credit card transactions using the latest version of SED 2.0.2.31. SED was running but when we were trying to run CC transaction it was saying that SED is not started and it will run automatically. But the SED was installed properly and it was running on the server. After numerous hours of research we were able to fix the issue. We found out that SED(2.0.2.31) still running the old version TLS(1.0) which is not supported by Sage Exchange platform as of June1/2018. We fount a Window Security Patch. After installing the patch it resolved the issue. Here is the info for the patch and the link as well. If you get this issue install this patch and it will fix the problem. The MS update is KB2898850 Information can be found here: https://support.microsoft.com/en-us/help/2898850/description-of-the-security-update-for-the-net-framework-4-5-1-and-the Download can be found here: https://www.microsoft.com/en-us/download/details.aspx?id=42883

Is this at the workstation or server level (both)? Thanks for the post.

Have a client on v4.4 (off plan) that this happened to yesterday. Contacted Paya for support, they sent a link for download which did not work. I think the Virtual Terminal will become a good friend for them.

It'll be interesting, I have a client on 4.30 running the old Sage Exchange. Server is 2003 - could possibly use a 2012 R2 Terminal Server for workstations. Upgrade slated for two weeks from now, we'll see how Monday goes.

It is windows server 2012 R2 Terminal services.

Yes, on the Terminal Server question @AndyTeteyan

My client server where we were having a problem is windows server 2012 R2 Terminal services.

Looks like its Win 2016 on the Term Server.

I have an eBusiness client that could not sync orders into Sage in the afternoon Friday after Paya turned off the TLS(1.0) even though Sage Exchange installed is current. Odd they can manually process in SO entry, but not sync from web services. Hope this link will help them. Paya was not much help in solving their issues and they have tons of orders they could nt process Friday. Thanks for the info @AndyTeteyan

Thanks for this post @AndyTeteyan, this burned one of my retail clients and that patch worked perfectly.

Is that Microsoft security patch supposed to resolve the 1.x issue? My v2013 client (SED 1.x) can't process credit cards. They get the message, ""You must wait while Sage Exchange..."" even though it was already installed. Previously when we got this message we would shut the workstation down, re-start, and try again - and that usually worked, but not now. And I didn't think SED 2.x could be used for v2013.

...doesn't seem to be an issue on the server, just workstations. Actually, strike that.

Paya just posted that 2.x SED is required to resolve ""unable to complete registration"" error. But I didn't think 2.x was compatible with v2013 and v2014.

I just spoke with Sage (Vickie) who found out from Ronnie Aspe that SED 2.x should be fine with v2013+, i.e. apparently 2.x _**is**_ now compatible with versions it previously wasn't. I'm going to try it on my client's system and will let you know how I make out.

I successfully installed and tested 2.x on a v2013 workstation. And for the 1.x ""Magensa card swipe"" setting that was being used in 1.x, I had to select the ""Magtek DynaMag/DynaPad"" option under Non-EMV Devices.

The patch above appears to be for Windows 8.1 and above. I have a client on Windows 7 getting this same error and they have SED 2.0.2.31. Is there a patch for Windows 7?

Please see the link how to force .Net to use TLS 1.2. This should work for Windows 7. https://support.solarwindsmsp.com/kb/solarwinds_n-central/How-To-Force--NET-to-use-TLS-1-2

I have a client on 4.5...windows 7. getting ""Unable to communicate with Sage Payment Solutions..."" We have a test clone that it works on but their production workstations does not. We uninstalled SE 1.0, installed 2.0. We added the TLS registry fix. We rebooted. We are still getting blocked on all machines. Any other thoughts.

@RobertRussoniello Were you able to get this resolved? I am having the same issue and have also added the registry fix, etc.

no resolution yet...its odd that we have 2 systems (1 production on 2008 server - error)...4.5 on test 2012 R2 (no error).

I have 2 clients with this. One is 4.5 Standard and other is 2016 Advanced, both Windows 7 workstations. I believe both servers are 2008.

For the users that still have issues, we're running around trying to get their permissions boosted long enough to do uninstalling of old, reinstalling of new, and going at it from the TLS side too. Hope we'll have an update soon.

Windows 7 patch: https://support.microsoft.com/en-us/help/3140245/update-to-enable-tls-1-1-and-tls-1-2-as-a-default-secure-protocols-in

Anybody else able to figure out what the issue is? I still have at least 2 clients with the issue and we have installed the Windows 7 patch, etc, but still no luck.

From: do.not.reply@sagepayments.com <do.not.reply@sagepayments.com> Sent: Tuesday, June 5, 2018 4:36 PM Subject: **Please Note: Paya has updated our TLS security protocols** The PCI DSS council mandated the transition from Secure Sockets Layer (SSL) and Transport Layer Security (TLS) v1.0, to TLS v1.2 or higher, which offers an overall increased level of security. This transition occurred on June 1, 2018. During this transition some customers using electronic solutions to process transactions experienced an issue processing payments. If you are experiencing any issues processing payments, please visit our support.paya.com webpage and click on the maintenance and alerts section to get the latest information about this transition, including FAQs. We apologize for any inconvenience this may have caused. Thank you for being a valued Paya customer. Maintenance ad Alerts: https://support.paya.com/44510-knowledgebase/308786-maintenance-and-service-interruption-alerts?from_search=24353507 Best Regards, Paya Inc

2 Widow 7 SP1 workstations running Sage 100 version 4.3 (gasp) get Error: ""Unable to communicate with Sage Payment Solutions - Exception occurred (err/ret=2/0)"" when processing a credit card transaction - but a third on Windows 10, has no issues. IT Updated TLS 1.2 and .Net 4.7.1 on these Win 7s but still can't connect. It's not SED, since 4.3 doesn't use it. The usually fixes for this error are shutting down AV, firewall, etc. and testing. The error still occurs. Convinced Win 10 has something unique that will allow CC communication, if I could only figure out what it is. Likely easier to upgrade but customer wanted to hold off until Sept. May not be able to now.

Server 2016 fix: Ran some powershell commands that made changes to the registry: Set-ItemProperty -Path 'HKLM:\SOFTWARE\Wow6432Node\Microsoft\.NetFramework\v4.0.30319' -Name 'SchUseStrongCrypto' -Value '1' -Type DWord Set-ItemProperty -Path 'HKLM:\SOFTWARE\Microsoft\.NetFramework\v4.0.30319' -Name 'SchUseStrongCrypto' -Value '1' -Type DWord

We got the users who use remote desktop working, but for those who, let's say, run Sage 100 like it's native, through the WinTerm, they still can't process CC.

Has anyone had an issue with running the Credit Card Settlement report, but still able to process credit cards? We have a client's workstation doing that. The Term Server runs both fine.

@Dana We are having that issue with one of our users. I am not sure, but I think if they tried to process a cc that was new they would have an issue, but as long as they process one that has been saved they are OK. My user is on Sage 2016, Windows 7 workstations and 2008 R2 server.

FYI - My client that was having issues running the CC Settlement all of a sudden started working again. I am wondering of Paya resolved some issues on their end?

Same here. Working as of 4:30 CDT - 4.30!

From: do.not.reply@sagepayments.com [mailto:do.not.reply@sagepayments.com] Sent: Wednesday, June 06, 2018 12:21 PM To: Subject: RESOLVED -Shopping Cart, Donate Now and ExpressPay Checkout Page Error ALERT! RESOLVED -Shopping Cart, Donate Now and ExpressPay Checkout Page Error We have resolved the issue that was causing transactions attempted through our Shopping Cart, Donate Now and ExpressPay checkout pages. We apologize for the inconvenience caused by this issue. Best Regards, Paya

Thanks, @JohnLeonard, our client received that email from Sage Payments about the issue being resolved & it started working after that. I guess it was them all along for our issue.

Any tricks for Win7? I have a stubborn workstation still giving ""The credit card transaction request to Sage Exchange cannot be processed"", even after ensuring the TLS Windows Update is installed, putting the registry entries in place (SchUseStrongCrypto / DefaultSecureProtocols), uninstalling SE 1.0 / Module SDK, installing SE2.0 (updated)... Other users for this customer are fine. Local Admin permissions are in place.

Ah! In a last ditch effort as I was typing this out, I uninstalled a previous version of workstation (2013... they are on 2016 now), then repairing 2016... and it worked!!!

The v 4.3 with 2 Windows 7 workstations that weren't processing CC just reported they can process again.

We installed some not so recent hotfixes and haven't heard a peep today. Fingers crossed. Hot fix to make Sage 100 compatible with Sage Exchange Desktop 2.0. oFor Sage 100 2015.1 or higher, see KB 77093 for Hot fix AR5006T. oFor Sage 100 2016.1 or higher, see KB 77092 for Hot fix AR5005T

Has anyone heard any official update from PAYA about whether v4.5 or earlier Sage 100 systems will continue working after June 30?

Did any of these issues occur with a processor OTHER than PAYA?

@WayneSchulz, I thought Sage Exchange first came into play with the v2013 release. And yes, PAYware (Verifone) had a similar issue which apparently they had communicated with customers (attached) - which impacted a client of ours about a month ago. Too bad _Sage_ didn't notify _their_ customers about this; I think that could have certainly proved to be beneficial, but at least they're consistent (ha!). However, @AndyTeteyan's original post states, ""As you know today was the last day of the support of Sage Exchange Desktop(SED) 1.x."" @AndyTeteyan, how/where did you hear about this?

I saw this back in April, but have no memory of where...

@WayneSchulz - I received this yesterday.

How great would it have been it Paya sent out notice BEFORE all this happened. Personally I advise customers to get a quote from a different processor and if it makes sense $$ then switch. I think Paya has a very very tough life ahead of them if they play this type of catch up communication. It may work when you are dealing with a locked-in audience (aka Sage 100cloud subscription) but when you have a highly competitive service like payments you can be making after-the-fact communications and expect that your customers are going to stick around. Source: see history of Sage Payments and eventual sale of that business segment.

I agree. I spent several hours trying to troubleshoot this for a couple of clients and then after 2 1/2 days things just starting working again. I could have saved myself and my clients a lot of headache if they had only communicated they were having issues.

I sent Christina Wedge an email asking for any background info on cause and resolution

@BrettZimmerman I do think there was notification but not in the days leading up to this - which are arguably the most important. I think Paya is going to lose some customers over this. I know one of mine who went down is actively looking at APS and they probably do a fair volume. This is a very competitive market and Paya/Sage or any processing company cannot sit back and act like customers are locked in. Unlike ERP where there are not many options there are several for payments and each is willing to compete.

Obviously _**their communication completely sucked**_ because there seems to only be a handful of people who knew about this. It just boggles my mind how Sage operates. Clearly they knew about this ahead of time. What reason could there possibly have been for them not properly proactively communicating about this beforehand? Oh wait, I forgot they're the epitome of ""cart before the horse"".

The tiny notice I saw somewhere (?) implied if you were on SE 2.0 that all would be fine... but we all know that is not the case. Sage / Paya not doing proper testing in real world type conditions is just asking for problems, which of course affect us all.

The only communication channels from Sage are marketing related. This is why I specifically asked for a technical information feed during the Q&A at MOTM.

**Update:** I emailed the reply address in the Paya email @JohnLeonard received asking for further clarification. Aside from two emails saying how busy the person was and that I'd have something very soon - I've heard nothing more.

Sage published a KB article dealing with TLS - https://support.na.sage.com/selfservice/viewdocument.do?noCount=true&externalId=75186&sliceId=1&noCount=true&isLoadPublishedVer=&docType=kc&docTypeID=DT_Article&stateId=12388&cmd=displayKC&dialogID=501749&ViewedDocsListHelper=com.kanisa.apps.common.BaseViewedDocsListHelperImpl&openedFromSearchResults=true

I've received an explanation from Paya about their outage and will post shortly. I think the reason some of the older versions of Sage 100 suddenly came back with credit card processing is that Paya temporarily turned the old TLS compatibility back on. Paya says this older TLS will be allowed until 6/25. That likely means anyone who suddenly had credit card processing return without explanation may face another outage on 6/25. From what I can tell the biggest gotcha might be that SED 2.0 is required. Sage claims it's not compatible with 2013 or 2014 but I think we have had people use it. SED 2.0 is not compatible with Windows XP which also means Windows Server 2008 or lower. This could be what's catching some of these older Sage installs. https://paya.com/tlsinformation/

More info from the Paya site - https://support.paya.com/321475-sage-100-tls-compliance