Hi Andrew Barker,
Thanks for your solution.
I have update the MySQL side using utf8mb4 char. I think the problem is in the smarter track itself.
I think, if i just update the connection string inside SystemSettings.xml will it work ? but actually it was encrypted like this :
<ConnectionStringEnc>encrypted string </ConnectionStringEnc>
If i don't want to update the version, will it possible ? My SmarterTrack version is still 12.x. The reason for not upgrading it, because we have a lot of customization on external providers and we have train a lot of agent about the UI. We can not afford if any integration that we have get failed for unknown reason after upgrade the version.
Right now i have tons of email pulled from POP3 connection that was failed in Incoming spool. This is madness.
Every single mail that was failed contains unicode chars. Every 'retry' action just resulting an error.
If I migrate database from MySQL to MS SQL Server, will this problem get solve ?
Please tell me solution without upgrade the SmarterTrack. You can tell me any technical detail here.