"Unable to save policy" error when a policy is saved
Last Modified: 2023-03-06 05:04:41 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 save policy" error when a policy is saved
Technical Articles ID:
KB90983
Last Modified: 2023-03-06 05:04:41 Etc/GMT Environment
Data Exchange Layer (DXL) 6.x, 5.x Data Loss Prevention (DLP) Endpoint 11.x Drive Encryption (DE) 7.x Endpoint Security (ENS) Firewall 10.x ePolicy Orchestrator (ePO) 5.10.x Problem
When you try to save a policy for DE, DLP Endpoint, DXL, or ENS Firewall, a pop-up window displays either of the following messages: Error message: java.sql.SQLException: Cannot resolve the collation conflict between "SQL_Latin1_General_CP1_CI_AS" and "Latin1_General_CI_AS" in the equal to operation NOTE: The collation in the error above is just one example. The problem can be seen with different collations. Cause
There's a mismatch on the collation for the ePO database and the instance where the database is hosted. The SQL collation of the SQL Server must match the collation of the ePO database. For details, see KB73717 - ePolicy Orchestrator supported SQL Server collation types.
Solution
Move the ePO database to an instance that matches the same collation. For information about how to change the collation of an instance during or after installation, review the Microsoft SQL documentation. For details, see KB68427 - Recommended procedure to migrate or move an ePolicy Orchestrator database to a new SQL Server. WARNING: We recommend that you do not change the database collation after installation. Affected ProductsLanguages:This article is available in the following languages: |
|