Thomas,
EDIT: I assume Desktop 16.2.26 means they are running CIC 2016 R2 P26. In this case server 2016 would not yet be supported but I think you can probably "fix" this by enabling the older less secure TLS versions on the Server 2016 box.
This seems to be a encryption protocol issue. You will need to check to see what TLS versions both the server and client side applications support. According to
http://testlab.inin.com/ProductsPage.aspx?ProductType=20 Server 2016 is supported starting with CIC 2018 Rx and up. Doing a quick search Windows changed what TLS versions are supported with windows 10 and server 2016, take a look here
https://docs.microsoft.com/en-us/windows-server/security/tls/tls-registry-settingsThere is also this great Stackexchange post about the exact error for another C# application.
https://stackoverflow.com/questions/26742054/the-client-and-server-cannot-communicate-because-they-do-not-possess-a-common-aThanks,
------------------------------
Mark Tatera
ConvergeOne
Opinions are my own and not the views of my employer. Any suggestions or programming changes I suggest come with no warranty and should be tried at your own risk.
------------------------------
Original Message:
Sent: 04-23-2019 18:21
From: Thomas Moore
Subject: Desktop 16.2.26 error when running on Windows Server 16
A customer got the following error: The client and server cannot communicate, because they do not possess a common algrithm
I'm five9s sure this is because they are running on Windows Server 2016 (only supported thru Windows 2012 R2)....
Has anyone had a work around for this?
Found this... https://www.ryadel.com/en/asp-net-client-server-cannot-comunicate-because-they-possess-common-algorithm-how-to-fix-c-sharp/
See attach for error...
#Omni-ChannelDesktop/UserInterface
------------------------------
Thomas Moore
Avtex
------------------------------