Frequently Asked Questions
Frequently Asked Questions
Encryption not supported on the client while connecting to MS SQL Server
Posted by Ariful Mahmud (M-Files) on 16 December 2019 12:35 PM

Overview / Work Notes

In some situations when you are using MS SQL Server as vault database you might get " Encryption not supported on the client". A sample error stack can be as following:

 

Vault.cpp, 3556, Connection to the Microsoft SQL Server database "Test" failed. (0x8004044B)

MSSQLServerServices.cpp, 2933, Connection to the Microsoft SQL Server database " Test" failed. (0x8004044B)

MSSQLServerServices.cpp, 2933, Unspecified error. (A network-related or instance-specific error has occurred while establishing a connection to SQL Server. Server is not found or not accessible. Check if instance name is correct and if SQL Server is configured to allow remote connections. For more information see SQL Server Books Online. (ERROR: 0, SQLSTATE: 08001)) (0x80004005)

DBSession.cpp, 513, Unspecified error. (A network-related or instance-specific error has occurred while establishing a connection to SQL Server. Server is not found or not accessible. Check if instance name is correct and if SQL Server is configured to allow remote connections. For more information see SQL Server Books Online. (ERROR: 0, SQLSTATE: 08001)) (0x80004005)

DBSession.cpp, 473, Unspecified error. (A network-related or instance-specific error has occurred while establishing a connection to SQL Server. Server is not found or not accessible. Check if instance name is correct and if SQL Server is configured to allow remote connections. For more information see SQL Server Books Online. (ERROR: 0, SQLSTATE: 08001)) (0x80004005)

DBSession.cpp, 473, Client unable to establish connection (ERROR: 21, SQLSTATE: 08001) (0x89790002)

DBSession.cpp, 473, Encryption not supported on the client. (ERROR: 21, SQLSTATE: 08001) (0x89790003)

 

Solution / Workaround

If you use TLS 1.1 or 1.2 as default secure protocols instead of TLS 1.0 and use older release of SQL Server Native Client 2012 then this issue can occur. This will result in unusable vault as M-Files services won't be able to communicate with MS SQL server and will result in failing to bring the vault online.

You must update your SQL Server Native Client to build 11.3.6538.0 or higher for enabling support for TLS 1.1 and 1.2. Older versions don't support TLS 1.1 or TLS 1.2. Further reading on this:

 

Update to enable TLS 1.1 and TLS 1.2 as default secure protocols in WinHTTP in Windows:

https://support.microsoft.com/fi-fi/help/3140245/update-to-enable-tls-1-1-and-tls-1-2-as-default-secure-protocols-in-wi

(0 vote(s))
This article was helpful
This article was not helpful

Help Desk Software by Kayako case