Problem: User opens Sage (resulting in last estimate opened) and/or tries to open an estimate and receives the following error:




Resolution: The error might be related to a mismatch between the version of TLS that is being run on the client and the server. I found several articles that indicate basically the same thing. Here are a few:

 

SSMS 2016 error "The client and server cannot communicate, because they do not possess a common algorithm" - Stack Overflow

 

"Connection failed ... A network-related or instance-specific error... because they do not possess a common algorithm" error when testing database connections (ibm.com)

 

The client and server cannot communicate (common algorithm) (centrel-solutions.com)

 

It sounds like it is working OK for a particular user, Karen, if I am understanding the client’s notes below. If that’s the case, you could compare the TLS settings on the machine that’s working vs the one that isn’t to see what protocols are enabled. I found some information on how to determine what TLS version is supported on a particular machine, but I’m not 100% sure whether these instructions apply to just Internet/browser settings or if they are global for the machine. But this is one method I found. Go to the Search bar and type in “Internet Options” then Enter, which will display the window below. Click on the Advanced tab then down to the section that has all of the “Use TLS 1.x” options to see what is enabled. As a test, they could also just check them all to see if it starts working. The other options I found for enabling TLS versions all talked about making changes in the registry so that’s obviously not ideal.

 

 

Another article I found also indicated making sure the latest version of SQL Server Native Client was installed for whatever version of SQL they are running. The article still said the error was due to a TLS mismatch, but installing the most recent version corrected the settings.