TB/TB-2007-03-PGCHARS

Problem Description

There is a known issue that can occur when attempting to insert Unicode characters into the Platform database. This error occurs when UTF8 characters are used in a message, but the destination database’s character encoding does not contain the character or provide a suitable conversion. When this error occurs, it will create an entry similar to the following in the scalix-api.log file:

WARN [RestServlet.sendError:28] Sending error
M00005 full folder sync failed
Message:java.sql.BatchUpdateException: Batch entry 1,198 insert into message
values ...

If logging is enabled on the PostgreSQL server (logging is disabled by default on some Linux distributions), its logs will contain a corresponding entry similar to this:

ERROR: character 0xe28099 of encoding "UTF8" has no equivalent in "LATIN1"