I have SQLServer 2017 instances on Windows 2016 Server installed on Oracle Virtualbox.
When I try to connect to the server by isql and FreeTDS driver with wrong user name or password, I get garbled(mojibake) error message as follows.
I confirmed that I could connect to the server when I set right user name and password.
If the defalut language of SQLServer is English, I get right English message. But I don't
want this option because I'm doubtful my application based on the server support it.
When I use tsql command directly, I got right Japanese error message(image file attached).
$ tsql -S Exp -U sa -P Password
locale is "en_US.UTF-8"
locale charset is "UTF-8"
using default charset "UTF-8"
Msg 18456(severity 14, state 1) from SQLSERVER\SQLEXPRESS Line 1:
"ユーザー 'sa' はログインできませんでした。"
Error 20002(severity 9):
Adaptive Server connection failed
There was a problem connecting to the server
Server OS: Windows Server 2016 Essentials
SQL Server version:
Microsoft SQL Server 2017 (RTM) - 14.0.1000.169 (X64)
Aug 22 2017 17:04:49
Copyright (C) 2017 Microsoft Corporation
Express Edition (64-bit) on Windows Server 2016 Essentials 10.0 <X64> (Build 14393: )
I have SQLServer 2017 instances on Windows 2016 Server installed on Oracle Virtualbox.
When I try to connect to the server by isql and FreeTDS driver with wrong user name or password, I get garbled(mojibake) error message as follows.
How can I get right error message?
I confirmed that I could connect to the server when I set right user name and password.
If the defalut language of SQLServer is English, I get right English message. But I don't
want this option because I'm doubtful my application based on the server support it.
When I use tsql command directly, I got right Japanese error message(image file attached).
My environment is as follows.
Client OS: CentOS Linux release 7.6.1810 (Core)
unixODBC version: 2.3.7-1
freetds version: 0.95.81-1
locale: ja_JP.UTF-8
Server OS: Windows Server 2016 Essentials
SQL Server version:
.odbc.ini:
trace log(failed login case)
trace log(successful login case)