The following error is seen when trying to run a task, like an imaging task, on a client machine:
An unknown exception was thrown on server side.
System.Net.WebException: The underlying connection was closed: An exception error occurred on a receive. --> System.ComponentModel.Win32Exception: The client and server cannot communicate, because they do not possess a common algorithm.
ITMS 8.x
Deployment Solution 8.x
TLS version mismatch. The
The following error usually refers to a TLS mismatch between the SMP, Task Server, and possibly the client machine(s), and sometimes it could be caused if FIPS is in use:
"The client and server cannot communicate, because they do not possess a common algorithm"
Usually, if TLS 1.2 is the only version to use all around, Microsoft suggests making sure the following regkeys are set this way:
https://docs.microsoft.com/en-us/mem/configmgr/core/plan-design/security/enable-tls-1-2-client
In some scenarios, if allowing only TLS 1.2 on the SMP, SQL, and Task Server, .NET tries to use TLS 1.0 by default and TLS 1.2 needs to be properly called by it. There are certain places in the registry that needs to be modified to force TLS 1.2 to be the only one in use by .NET.
Add (or modify if these already exists) the following registry keys with the specified values:
Windows Registry Editor Version 5.00
[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:00000001
[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