Deployment Scanner fails to make a connection to SQL

Problem

Deployment Scanner reports "Unable to connect to server" when testing SQL Collation, SQL Database Compatibility, SQL Server Permissions, and SQL Server Version.  Also, SQL Server Connectivity reports TCP/IP is not enabled even if it is.

Error Message

The list of SQL Server computers or listeners below shows the network protocols that are supported by each server. Enterprise Vault requires at least one of the network protocols to be supported on each SQL Server.
SQLServer01: NamedPipes (NO), TCP/IP (NO)

Cause

This can happen when the server environment is configured to use TLS 1.1 or higher and TLS 1.0 is disabled. Enterprise Vault uses the Microsoft OLE DB Provider for SQL Server for communication with the Enterprise Vault SQL databases.  When TLS 1.0, SSL, and earlier security protocols are disabled on the server, any connection to a SQL database using the Microsoft OLE DB Provider for SQL Server fails.  This scenario also applies for any connection attempts to any SQL database using Microsoft OLE DB Provider for SQL Server, not just for connections by Enterprise Vault.

A test of the ODBC Connection to the SQL instance fails:

Solution

Either of the following solutions can be used to workaround this scenario:

•  Leave TLS 1.0 enabled on the server.
  Set the following registry keys - values: ​
  • [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.0]
  • [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.0\Client]”
    • Enabled"=dword:00000001”
    • DisabledByDefault"=dword:00000000
  • [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.0\Server]”
    • Enabled"=dword:00000001”
    • DisabledByDefault"=dword:00000000
•  If TLS 1.0, SSL, and all earlier protocols are disabled on the server, the security option System cryptography: Use FIPS compliant algorithms for encryption, hashing, and signing must be enabled on the server.

Note: More information about this security option may be found in the following Microsoft article:  https://technet.microsoft.com/en-us/library/jj852197(v=ws.11).aspx