Details: When navigating to CBOE Inventory or ChemACX applications, an error similar to the following can potentially appear:
System.Web.Services error '80131509'
The request was aborted: Could not create SSL/TLS secure channel
/\cfserverasp\source\cs_security/cs_security_login_utils_vbs.asp, line 20
or
System.Web.Services error '80131509'
The underlying connection was closed. Could not establish that relationship for the SSL/TLS secure channel.
/\cfserverasp\source\cs_security/cs_security_login_utils_vbs.asp, line 20
This issue can seemingly appear out of nowhere in a system that was working before. While the exact root cause is still undetermined, essentially a change is introduced in the operating system that breaks the auto-negotiation of secure protocols.
To prevent this behavior, please add the registry keys mentioned on the following Microsoft article:
https://learn.microsoft.com/en-us/mem/configmgr/core/plan-design/security/enable-tls-1-2-client
To the application server's registry:
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\v2.0.50727]
"SystemDefaultTlsVersions" = dword:00000001
"SchUseStrongCrypto" = dword:00000001
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\v4.0.30319]
"SystemDefaultTlsVersions" = dword:00000001
"SchUseStrongCrypto" = dword:00000001
[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\.NETFramework\v2.0.50727]
"SystemDefaultTlsVersions" = dword:00000001
"SchUseStrongCrypto" = dword:00000001
[HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\.NETFramework\v4.0.30319]
"SystemDefaultTlsVersions" = dword:00000001
"SchUseStrongCrypto" = dword:00000001Then restart the application server.