We found that this issue was caused after a monthly Microsoft Security patch. (October 2018 - KB4462923). Digging into the issue's errors and logs lead us to think it beign related to SSL connection. At first we thought it was certificates were not being validated correctly, but it ended up being that TLS client needs to be 'ENABLE' in registry by using the correct DWORD key.
I am wondering is there a way to disable TLS 1.0 in aginity and force it to use TLS 1.1 or 1.2.. This is required to prevent TLS 1.0 from being used and remain disabled.
Please let us know what changes we need to do within aginity to force to use TLS 1.1 or higher.
Let me know if you need more info.
Please sign in to leave a comment.