Unable to install an ePO 5.10 Update (SQL Auto Close is set to True)
Last Modified: 2023-07-28 11:37:55 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 install an ePO 5.10 Update (SQL Auto Close is set to True)
Technical Articles ID:
KB94720
Last Modified: 2023-07-28 11:37:55 Etc/GMT Environment
ePolicy Orchestrator (ePO) 5.10.x Update 1 and later For details of ePO- and SQL-supported environments, see KB51569 - Supported platforms for ePolicy Orchestrator. Problem 1
When you run an ePO Update setup file, the update reports that it installs successfully. But, the cumulative update doesn't actually install. The methods below show if the ePO Update is successfully installed or not:
NOTE: If the update isn't successful, the
Problem 2
You see the following errors recorded in the info: ITEM: Description REG_SZ McAfee ePolicy Orchestrator 5.10.0 Application Server services. error: Failed to get connection..ConnectionError: Login failed for user 'xxx'. error: Failed to connect to database info: Failed to find ePOVersion .. error: Failed to get connection..ConnectionError: Failed to connect to xxx.xxxx:1433 in 15000ms info: Update EPOServerInfo failed Cause
The SQL Auto Close feature is set to True. When you Auto Close on a production SQL Server repeatedly, it makes and breaks connections to the database engine.
Solution
Disable the Auto Close option by setting it to False:
Affected ProductsLanguages:This article is available in the following languages: |
|