This is a Windows Server limitation. There are 2 workarounds to get past this issue.
Workaround 1:
- Using regedit.exe browse to the following location:
- HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols
- If you see a provider for TLS 1.0 and/or TLS 1.1, backup the Protocols registry key and remove the TLS 1.0 and TLS 1.1, leaving the TLS 2.0 key
- You should now be able to connect to SQL via a UDL test and UCD now
Workaround 2:
If you have a group policy setting that is forcing the TLS 1.0 and 1.1 keys and you cannot modify that policy, you can enable another policy that will force the connection to go through TLS 2.0.
- On the UCD server Click Start | RUN | Type "gpedit.msc" without the quotes
- Browse to the following setting and enable it: Computer Configuration | Windows Settings | Security Settings | "System cryptography: Use FIPS-compliant algorithms for encryption, hashing and signing"
- Close the group policy editor
- Test your UDL file and UCD connection again. It should be working now.
- You may want to create a Group Policy for this setting to be applied to the UCD server
