Related to my earlier question, has anyone installed the Tessitura Service, Services Dashboard on a Windows 2016 box? Is there something I'm missing with TLS? When I go to Services Dashboard, the probes for Tessitura Service all fail. Now if I use the Rest Client on the Tessitura Service site I get an error of "The underlying connection was closed: An unexpected error occurred on a send." but if I use the REST client with Firefox I can successfully connect and get data back. Further, if I point the first Probe_Id at another test environment I get a connection (even if that other server is 2016), but pointing at itself, it fails. I've even moved the cert to a different server and that was fine. Really confused? Thanks.
Hi John,
That error certainly sounds like a TLS thing. We had a hell of a time with it a while back, and if I remember correctly it was a RAMP upgrade that set our API servers to not accept old TLS versions. Since we were on RAMP all of the Tessitura stuff was fine, but a locally hosted web app server was failing. Finding the configuration settings in the registry to get our servers (mostly 2012, I believe) to default to the right TLS version for .Net apps was extremely non-trivial. Firefox would naturally work with the right TLS level, so that also fits the pattern. I can't remember if I hacked this problem out on the forums or the developer Slack channel.
--Gawain
Slack channel. I dug up this link:
https://stackoverflow.com/questions/45382254/update-net-web-service-to-use-tls-1-2/45441341#45441341
But also you need to find and set this key: SchUseStrongCrypto