Filenames and paths with double-byte character set (DBCS) characters display as garbled text in the Symantec Endpoint Protection Manager (SEPM).
This behavior occurs when the SEPM utilizes a Microsoft SQL 2008 or later database server. The Bulk Copy Protocol (BCP) utility included with this version of Microsoft SQL does not allow data to be transferred as UTF-8 formatted text. The SEPM uses UTF-8 formatted text in order to be able to transfer DBCS text to and from the SEPM database. When the SEPM uploads data to the database, DBCS characters (such as Japanese, Korean, Chinese or Devanagari characters) are not properly inserted into the SEPM's database.
DBCS data will display normally on a SEPM site utilizing SQL 2005 or earlier, or the embedded (SQLAnywhere) database. If a SQL 2005 or earlier, or embedded (SQLAnywhere) site Replicates with a SQL 2008 or later site, DBCS data will show incorrectly on the SQL 2008 or higher Replication partner.
To work around this issue, configure the affected SEPM to use Batch Mode processing instead of BCP.
Note: Batch Mode processing is significantly less efficient at transferring large data sets that BCP. Making this change will lower the SEPM's ability to process client log data and may cause slow SEPM response time to client requests.
This issue requires one or more SEPM Sites using Microsoft SQL server 2008 or later.