Difference between revisions of "TB/TB-2007-03-PGCHARS"
m (→Problem Description) |
m (→Problem Description) |
||
| Line 11: | Line 11: | ||
ERROR: character 0xe28099 of encoding "UTF8" has no equivalent in "LATIN1" | ERROR: character 0xe28099 of encoding "UTF8" has no equivalent in "LATIN1" | ||
</pre> | </pre> | ||
| − | This issue can result in slower loading times for SWA clients, and in some cases prevents users from being able to login into SWA or the Mobile client. More detailed information is available in [[http://bugzilla.scalix.com/show_bug.cgi?id=14282|bug 14282]] | + | This issue can result in slower loading times for SWA clients, and in some cases prevents users from being able to login into SWA or the Mobile client. More detailed information is available in [[http://bugzilla.scalix.com/show_bug.cgi?id=14282 |bug 14282]] |
Revision as of 23:22, 3 May 2007
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"
This issue can result in slower loading times for SWA clients, and in some cases prevents users from being able to login into SWA or the Mobile client. More detailed information is available in [|bug 14282]
