The Symantec Endpoint Protection Manager (SEPM) AgentLogCollector process monitors the client, traffic, behavior and other sub-folders under data/inbox/log/ directory for new logs uploaded by Symantec Endpoint Protection (SEP) client computers, then imports them into the database.
The following error is spotted in the AgentLogCollector-0.log file under the tomcat/logs sub-directory of where SEPM is installed:
2010-10-10 18:12:21.123 FINE: SQLException: Failed to load data: SQLState = S1000, NativeError = 0
Error = [Microsoft][SQL Server Native Client 10.0] This version of SQL Server Native Client does not support UTF-8 encoding (code page 65001)
Using batch handler
Per Microsoft documentation, the Microsoft SQL Server 2008 does not support the UTF-8 encoding used in the SEPM client logs:
This in itself is not an issue - when SEPM finds that the SQL Server Native Client (bcp.exe) has failed to import the log, it will use a backup method (SEPM batch handler) and the SEP client logs should still be uploaded to the database properly.
The RU7 MP1 release of the SEP 11.0 product, and the RU1 MP1 release of the SEP 12.1 product, has been changed to not specify the UTF-8 encoding on the BCP.EXE command line with Microsoft SQL Server 2008. Upgrading to one of these versions (or later) should stop the error being written to the AgentLogCollector log files on the SEPM.
Imported Document ID: TECH145952
Subscribing will provide email updates when this Article is updated. Login is required.