Open tomaszdubiel18 opened 1 year ago
It's related to https://github.com/FirebirdSQL/firebird/issues/6038, but here the problem occurs when the Windows client name has non-ascii characters, not the user that tries to connect to Firebird database. To solve this problem you need to set locale on the server side that support non-ascii (UTF-8 recommended).
Example:
root@linux:~# locale
LANG=en_US.UTF-8
LANGUAGE=en_US:en
LC_CTYPE="en_US.UTF-8"
LC_NUMERIC="en_US.UTF-8"
LC_TIME="en_US.UTF-8"
LC_COLLATE="en_US.UTF-8"
LC_MONETARY="en_US.UTF-8"
LC_MESSAGES="en_US.UTF-8"
LC_PAPER="en_US.UTF-8"
LC_NAME="en_US.UTF-8"
LC_ADDRESS="en_US.UTF-8"
LC_TELEPHONE="en_US.UTF-8"
LC_MEASUREMENT="en_US.UTF-8"
LC_IDENTIFICATION="en_US.UTF-8"
LC_ALL=
As reported here: https://groups.google.com/g/firebird-support/c/1TNUxSQoSWw client gets the error: "Invalid connection string Cannot transliterate character between character sets. Invalid or incomplete multibyte or wide character" when it has national characters in its computer name, username and probably in Windows directory of a client. Used charset: WIN1250 Server: Linux Firebird 3.0.10, client: Windows Firebird 3.0.