Unable to make a connection to the database server with TLS 1.2
Last Modified: 2021-12-02 20:36:39 Etc/GMT
Affected Products
Languages:
This article is available in the following languages:
Trellix CEO, Bryan Palma, explains the critical need for security that’s always learning.
As per Gartner, "XDR is an emerging technology that can offer improved threat prevention, detection and response."
Trellix announced the establishment of the Trellix Advanced Research Center to advance global threat intelligence.
Trellix Advanced Research Center analyzes threat data on ransomware, nation-states, sectors, vectors, LotL, MITRE ATT&CK techniques, and emails.
As of May 14, 2024, Knowledge Base (KB) articles will only be published and updated in our new Trellix Thrive Knowledge space.
Log in to the Thrive Portal using your OKTA credentials and start searching the new space. Legacy KB IDs are indexed and you will be able to find them easily just by typing the legacy KB ID.
Unable to make a connection to the database server with TLS 1.2
Technical Articles ID:
KB92364
Last Modified: 2021-12-02 20:36:39 Etc/GMT Environment
ePolicy Orchestrator (ePO) 5.10.x
Problem 1
Installation of ePO fails when you try to install ePO on a computer where:
Testing NT Authentication to SQL Server. Failed to connect to SQL Server [<SQL server name>] with error code [0x80004005] Description for error code is [TCP Provider: An existing connection was forcibly closed by the remote host.] Failed in connectToSQLServer with error code [0]. Where <SQL_Server_Name> is the name of the SQL Server being used
Problem 2
ePO stops functioning, even after ePO was successfully installed on a computer, where:
When the ePO application server service is started, the service starts, but the WARN [main] jni.LoadJniInitTask - Unable to load native library:C:\Program Files (x86)\McAfee\ePolicy Orchestrator\Server\extensions\installed\EPOCore\5.10.0.2428\webapp/WEB-INF/lib/DownloadJNI java.lang.UnsatisfiedLinkError Orion_OnLoad returned an error. ERROR [main] plugin.PluginManager - Initialization of plugin EPOCore failed. When the ePO server service is started, the service starts, but the server log contains many instances of the following message: Followed by: MOD_EPOREPO D:\BUILD_764249\BUILD\ePO\dev\src\server\include\ePOData.inl(461): Database initialization: Failed (hr=0x80004005). MOD_EPOREPO mod_eporepo.cpp(240): Failed to connect to database, shutting down repository module, system error 0x80004005 Cause
ePO uses the SQL 2012 Native Client to make connections to SQL. When the client isn’t present at the time that ePO is installed, the ePO installer installs the correct version. But, if an existing version with a lower minor version number is installed, the ePO installer doesn’t upgrade it. If the previously installed version only supports TLS 1.0, ePO is unable to connect to an SQL Server that has TLS 1.0 disabled. This fact can cause the following problems:
Solution
The solution to both these problems is the same. You must upgrade the SQL 2012 Native Client on the ePO server to a version that supports TLS 1.2. You can either obtain the client from Microsoft, or obtain it from the ePO install set. ePO includes the installer version 11.3.6538.0:
Affected ProductsLanguages:This article is available in the following languages: |
|