I rolled back to MySql ODBC 3.51 and it immediately started working.
Update: For the customer I mentioned, the solution was to install the 32-bit version of the MySQL ODBC driver version 5.1.8.
We have never seen this error ourselves but I have received a report from a customer with the same error message. His solution was to install a different version of the MySQL ODBC driver. Unfortunately, I don't know the specifics of the solution.
MySQL does not support the full UTF8 character set, 4-byte characters are not allowed. However, SMS only supports 16-bits Unicode which translates to 1-3 bytes UTF8 encoding so this should never be a problem because Diafaan SMS Server will never generate a 4 byte UTF8 character.
already deployed several installations.
This time (WinXP 32 bit, MySql 5.1.6, MysQlOdbc conn. 5.2(w)) I get into a weird problem.
If the sending table is empty, the server is "Ready to send messages".
As soon as I insert one record in the table, the server complains about "SQL Server error".
I just have one only error row in the EVENT LOG:
ERROR [HY000] [MySQL][ODBC 5.2(w) Driver][mysqld-5.1.36-community]Server does not support 4-byte encoded UTF8 characters.
Most Users Ever Online: 494
Currently Browsing this Page:
Guest Posters: 539
Newest Members:, Henk Helmantel
Administrators: Henk Helmantel: 1072