Summary
Policy deployment from Apex Central to Apex One stuck at:
Pending: Managed Server Deploying
Trend Micro Apex One integrated Service cannot start successfully.
Root Cause Analysis
The following error can be seen from ofcdebug.log file located at ...\Trend Micro\Apex One\PCCSRV\Log\
2019 09/17 13:10:25 [0444 : 004d] (00) (F) [-OSFDB-][w3wp.exe]SQLException Error = 468, Msg = Cannot resolve the collation conflict between "Modern_Spanish_CI_AS" and "SQL_Latin1_General_CP1_CI_AS" in the equal to operation. - [OSF_Data_Svc_Core.cs(74)]
2019 09/17 13:10:25 [0444 : 004d] (00) (F) [-OSFDB-][w3wp.exe][DisplaySqlErrors] Got SQL exceprion: (Index #0
Message: Cannot resolve the collation conflict between "Modern_Spanish_CI_AS" and "SQL_Latin1_General_CP1_CI_AS" in the equal to operation.
LineNumber: 87
Source: .Net SqlClient Data Provider
Procedure: osp_cb_dbUpdatePolicyStatus_V2
). - [OSF_Data_Svc_Core.cs(498)]
This happens when the Apex One SQL database is installed on a Microsoft SQL Server that users a collation method other than the default "SQL_Latin1_General_CP1_CI_AS".
What is Collation?
SQL collation specifies the bit patterns that represent each character in a dataset. Collations also determine the rules that sort and compare data. These are used with character data types, such as char and varchar, dictate the code page and corresponding characters that can be represented for that data type.
To resolve this issue, apply Apex One Hot Fix Build 2047. This hot fix updates the stored procedure osp_cb_dbUpdatePolicyStatus_V2 with correct collation. This fixes the SQL exception.
Enhanced security policies may not be sent to Security Agents across the network successfully when users manage the Apex One server from the Apex Central web console. This happens when the Apex One SQL database is installed on a Microsoft SQL Server that users a collation method other than the default "SQL_Latin1_General_CP1_CI_AS".
