SDO Certificate error

Question

Hi 
 After a customer upgrading their Sage 50 from v27 to v28 or possibly following an update of v28, it is not possible to connect using SDO. The Sage 50 desktop application is working fine. 
 The following error is thrown. 
 E0125 11:26:30.276000000 9328 ssl_transport_security.cc:1455] Handshake failed with fatal error SSL_ERROR_SSL: error:1416F086:SSLroutines:tls_process_server_certificate:certificate verify failed. 
 And a modal dialog then appears saying 
 Unable to connect to the Sage Data Service on machine 127.0.0.1. 
 Ensure this computer is switched on or connected to your network, then click Retry. 
 
 We have somehow re-created the same problem using a PC here and we have tried uninstalling and re-installing Sage 50 v28 on this PC. We have another PC where we have installed Sage 50 v28 and the very same SDO script works fine. In both cases, the data is on the local C: drive. We have a very simple VBS script to test with that simply connects via SDO and then disconnects. 
 
 We can't work out why it fails on certain PCs 
 
 Any help appreciated. 
 Best regards 
 Keith White

Ali Al-Amiri · Answer

Hi Keith. 
 Thanks for the provided info. I have looked further into this following the details you provided by running a VBScript and a .NET/C# app that both use SDO while ESET is running with SSL/TLS filtering turned on. The VBScript fail as you've experienced, however the .NET/C# app does not. This leads me to think the issue is not with SDO, but instead related to ESET and cscript.exe. I haven't been able to figure out why ESET is blocking cscript.exe but not other apps that use SDO. 
 You can keep the SSL/TLS option in ESET on, and tell ESET to ignore SSL/TLS filtering for the specific certificate that cscript.exe tries to use to communicate with the Sage 50 data service, using the following steps: 
 
 From SSL/TLS section of ESET, change "SSL/TLS protocol filtering mode" from "Automatic mode" to "Interactive mode" (you can change it back to automatic later) 
 Run your VBScript. You'll be prompted for few certificates that you can choose the "Scan" option for and leave it to "Ask every time" 
 Eventually (or possibly at the start) you'll see a prompt similar to the image below. Choose "Remember action for this certificate" and click "Ignore" 
 Turn filtering mode back to "Automatic mode".

When you follow the above steps the VBScript will initially fail with the same error, but subsequent runs will work once the Sage 50 data service certificate is added to the list of known certificates, which you can confirm is there by clicking "Edit" next to "List of known certificates" from ESET. 
 It's worthwhile contacting our Sage Developer support in case they've come across a similar issue in the past, no harm in doing so. 
 Hope the information above is useful. 
 Thanks.

Sage 50 Accounts

SDO Certificate error

Top Replies

COMMUNITY

COMPANY

PARTNERS

SUPPORT & TRAINING