Unable connect MS Sql Server 2019

English Applications
1

before I can connect , but after update tumbleweed become cannot.
I tried reinstall but no use

mssql server is running. firewall disable

mssql-server.service - Microsoft SQL Server Database Engine
Loaded: loaded (/usr/lib/systemd/system/mssql-server.service; enabled; vendor preset: disabled)
Active: active (running) since Fri 2019-07-26 09:54:17 +08; 1h 52min ago
Docs: https://docs.microsoft.com/en-us/sql/linux
Main PID: 3144 (sqlservr)
Tasks: 148
Memory: 618.3M
CGroup: /system.slice/mssql-server.service
├─3144 /opt/mssql/bin/sqlservr
└─3163 /opt/mssql/bin/sqlservr

Jul 26 09:54:22 linux-j7ei sqlservr[3144]: [387B blob data]
Jul 26 09:54:22 linux-j7ei sqlservr[3144]: [73B blob data]
Jul 26 09:54:22 linux-j7ei sqlservr[3144]: [77B blob data]
Jul 26 09:54:22 linux-j7ei sqlservr[3144]: [96B blob data]
Jul 26 09:54:22 linux-j7ei sqlservr[3144]: [66B blob data]
Jul 26 09:54:23 linux-j7ei sqlservr[3144]: [75B blob data]
Jul 26 09:54:23 linux-j7ei sqlservr[3144]: [96B blob data]
Jul 26 09:54:23 linux-j7ei sqlservr[3144]: [100B blob data]
Jul 26 09:54:23 linux-j7ei sqlservr[3144]: [124B blob data]
Jul 26 09:54:23 linux-j7ei sqlservr[3144]: [71B blob data]

keep getting error when connecting. using ssms also unable to connect
sqlcmd -S tcp:127.0.0.1 -U SA -P ‘Password’
Sqlcmd: Error: Microsoft ODBC Driver 17 for SQL Server : TCP Provider: Error code 0x2746.
Sqlcmd: Error: Microsoft ODBC Driver 17 for SQL Server : Client unable to establish connection.

Please Help . I don’t know what update cause this

2

Greetings,

On 1 August, Microsoft released the ‘mssql-server-14.0.3223.3-15’ update (i.e. CU16) for MS SQL Server 2017 (Linux), which promptly broke SQL Server with the following error:

Sqlcmd: Error: Microsoft ODBC Driver 17 for SQL Server : TCP Provider: Error code 0x2746.
Sqlcmd: Error: Microsoft ODBC Driver 17 for SQL Server : Client unable to establish connection.

I just checked for another another update and I noticed instead that the ‘mssql-tools’ & ‘msodbcsql17’ packages had new updates since 1 Aug. So hoping…I performed:

sudo zypper update mssql-tools unixODBC-devel msodbcsql17

Hence, I re-attempted to update SQL Server from ‘mssql-server-14.0.3192.2-2’ to CU16. And again–it broke as before where I had to revert to the previous release (i.e. CU15):

sudo zypper install --oldpackage mssql-server-14.0.3192.2-2.x86_64

This is the only fix I can locate online at this time–until Microsoft figures out what is breaking SQL Server 2017 in that specific release.
Apparently, SQL Server 2019 (Preview) recent release is probably broken as well for the same reason(s).

I would revert back and document it and notify the MS SQL Server community about our issues…

Have a great day!!

3

Problem occur on mssql-server-15.0.1800 version.

the prior version mssql-server-15.0.1700 is OK

tested on
openSUSE-Tumbleweed-DVD-x86_64-Snapshot20190810-Media

let hope the next version fix the problem or else I will stuck at 1700 :frowning:

4

the latest version

mssql-server-15.0.1900.25-1.x86_64.rpm 21-Aug-2019 13:31

Not working

version 1700