SEPM: Errors regarding code page 65001 or UTF-8 when logs are imported to SQL 2000

Products

• Endpoint Protection

Issue/Introduction

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-11-05 17:48:32.463 FINE: SQLException:  BCP copy in failed:
Starting copy...
SQLState = S1000, NativeError = 0
Error = [Microsoft][ODBC SQL Server Driver][SQL Server]Code page 65001 is not supported by SQL Server
SQLState = S1000, NativeError = 0
Error = [Microsoft][ODBC SQL Server Driver]Unable to resolve column level collations BCP copy in failed
Using batch handler   

Resolution

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.

For the same situation with Microsoft SQL 2008 please see article SEPM: Errors regarding code page 65001 or UTF-8 when logs are imported to SQL 2008.