DEBUG SugarCRM - Localization: translating

[sugarstefano]

I migrated our Sugar from a little machine P3@800Mz running Wiin2000 SP4 to a server machine Xeon5400 running Win2003 SBS.

Version 4.5.1g (Build 1003)
PHP 5.2.8
Apache 2.0.63
MySql 5.0.24

Since the migration i'm having problems with Inbound email retriving the following error into the log file
-----------------------------------------------------------------------------
INFO SugarCRM - Insert: INSERT into emails set ....etc. etc.
FATAL SugarCRM - MySQL error 1406: Data too long for column <may_vary_each_time>
-----------------------------------------------------------------------------

on my new Win2003 SBS noticed tha befor the insert Sugar do
-------------------------------------------------------------------------------
DEBUG SugarCRM - Localization: translating [ <_message_email_> ] into UTF-8
-------------------------------------------------------------------------------

conversely on my old Win200 SP4 (where all was workig excellent) it was doing
-------------------------------------------------------------------------------
DEBUG SugarCRM - Localization: translating [ <_message_email_> ] into iso-8859-1
------------------------------------------------------------------------------

i think that if Sugar will transalte again into iso-8859-1 it will works fine again
by the way till now did not understand where to set this if
sugar config, or mysql config or php config

Any help would be appreciated.

Thanks in advance,
Stefano Campri

[SugarDev.net]

You should check the database structure first, then Sugar. Are you sure that your old db wasn't manually altered outside of Sugar?

[sugarstefano]

About the structure i checked emails table expecially.
I used MySQL Administator and fields definition for eamils table seems to be the same on both systems. The default table charset say utf8.
Is it possible that stack installer created the structure as iso-8859-1 and i'm not able to see it ? how to chek it 100% ?

i don't remember if i altered sugar db by MySQL Administrator over the old Win2000 platform : i think i did not.
By the way it should have been migrated as it was. i use mysqldump and restored on new Win2003 sbs

I was going in deep to try to solve tthis issue : the old installation was made using the stack installer conversely the new one has been installed by sourcecode.
i found that "stack installation" does not set STRICT MODE for MySQLserver conversely default installation of MySQLserver set STRICT MODE.

Disabling STRICT MODE on the new platform too it become to works by the way i'm aving the same drawback as in my old platform : many message are truncated.

Searching for old post i found that the error it's occurring enabling MySQL STRICT MODE seems to be a MySQL bug.

What's is still strange for me now is why on old platform Sugar was translating into iso-8859-1conversely now is translating into utf-8.
Which translating should be the default ?
I tried to look into the many settings but did not found wich should act in this way.
Could you switch on any light on this ? :-)
Any help would be appreciated.

Thanks in advance,
Stefano Campri