SQL Server 2017 on Linux: SSMS connection attempt throws error 10054
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ margin-bottom:0;
}
I have just installed SQL Server 2017 on a Linux machine, when I connect locally it is working. But on trying to connect from SSMS it says:
Error 10054: A connection was successfully established with the server, but then an error occurred during the login process.
Please tell me what's wrong?
root@vps188507:~# cat /var/opt/mssql/log/errorlog
2018-06-07 14:08:50.38 Server Microsoft SQL Server 2017 (RTM-CU7) (KB4229789) - 14.0.3026.27 (X64)
May 10 2018 12:38:11
Copyright (C) 2017 Microsoft Corporation
Developer Edition (64-bit) on Linux (Debian GNU/Linux 8 (jessie))
2018-06-07 14:08:50.39 Server UTC adjustment: -4:00
2018-06-07 14:08:50.39 Server (c) Microsoft Corporation.
2018-06-07 14:08:50.39 Server All rights reserved.
2018-06-07 14:08:50.39 Server Server process ID is 4124.
2018-06-07 14:08:50.39 Server Logging SQL Server messages in file '/var/opt/mssql/log/errorlog'.
2018-06-07 14:08:50.39 Server Registry startup parameters:
-d /var/opt/mssql/data/master.mdf
-l /var/opt/mssql/data/mastlog.ldf
-e /var/opt/mssql/log/errorlog
2018-06-07 14:08:50.40 Server SQL Server detected 2 sockets with 1 cores per socket and 1 logical processors per socket, 2 total logical processors; using 2 logical processors based on SQL Server licensing. This is an informational message; no user action is required.
2018-06-07 14:08:50.40 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2018-06-07 14:08:50.40 Server Detected 6251 MB of RAM. This is an informational message; no user action is required.
2018-06-07 14:08:50.40 Server Using conventional memory in the memory manager.
2018-06-07 14:08:50.60 Server Buffer pool extension is already disabled. No action is necessary.
2018-06-07 14:08:50.78 Server InitializeExternalUserGroupSid failed. Implied authentication will be disabled.
2018-06-07 14:08:50.78 Server Implied authentication manager initialization failed. Implied authentication will be disabled.
2018-06-07 14:08:50.80 Server Successfully initialized the TLS configuration. Allowed TLS protocol versions are ['1.0 1.1 1.2']. Allowed TLS ciphers are ['ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-AES128-SHA256:ECDHE-ECDSA-AES256-SHA384:ECDHE-ECDSA-AES256-SHA:ECDHE-ECDSA-AES128-SHA:AES256-GCM-SHA384:AES128-GCM-SHA256:AES256-SHA256:AES128-SHA256:AES256-SHA:AES128-SHA:!DHE-RSA-AES256-GCM-SHA384:!DHE-RSA-AES128-GCM-SHA256:!DHE-RSA-AES256-SHA:!DHE-RSA-AES128-SHA'].
2018-06-07 14:08:50.85 Server The maximum number of dedicated administrator connections for this instance is '1'
2018-06-07 14:08:50.85 Server Node configuration: node 0: CPU mask: 0x0000000000000003:0 Active CPU mask: 0x0000000000000003:0. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required.
2018-06-07 14:08:50.88 Server Using dynamic lock allocation. Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node. This is an informational message only. No user action is required.
2018-06-07 14:08:50.90 Server In-Memory OLTP initialized on lowend machine.
2018-06-07 14:08:50.97 Server Database Instant File Initialization: enabled. For security and performance considerations see the topic 'Database Instant File Initialization' in SQL Server Books Online. This is an informational message only. No user action is required.
2018-06-07 14:08:50.99 Server Query Store settings initialized with enabled = 1,
2018-06-07 14:08:51.01 spid6s Starting up database 'master'.
2018-06-07 14:08:51.01 Server Software Usage Metrics is disabled.
2018-06-07 14:08:51.35 spid6s Resource governor reconfiguration succeeded.
2018-06-07 14:08:51.35 spid6s SQL Server Audit is starting the audits. This is an informational message. No user action is required.
2018-06-07 14:08:51.35 spid6s SQL Server Audit has started the audits. This is an informational message. No user action is required.
2018-06-07 14:08:51.46 spid6s SQL Trace ID 1 was started by login "sa".
2018-06-07 14:08:51.50 spid6s Server name is 'vps188507'. This is an informational message only. No user action is required.
2018-06-07 14:08:51.56 spid9s Starting up database 'mssqlsystemresource'.
2018-06-07 14:08:51.56 spid22s Always On: The availability replica manager is starting. This is an informational message only. No user action is required.
2018-06-07 14:08:51.56 spid22s Always On: The availability replica manager is waiting for the instance of SQL Server to allow client connections. This is an informational message only. No user action is required.
2018-06-07 14:08:51.57 spid6s Starting up database 'msdb'.
2018-06-07 14:08:51.57 spid9s The resource database build version is 14.00.3026. This is an informational message only. No user action is required.
2018-06-07 14:08:51.60 spid9s Starting up database 'model'.
2018-06-07 14:08:51.89 spid9s Polybase feature disabled.
2018-06-07 14:08:51.89 spid9s Clearing tempdb database.
2018-06-07 14:08:51.89 spid19s A self-generated certificate was successfully loaded for encryption.
2018-06-07 14:08:51.90 spid19s Server is listening on [ 'any' <ipv6> 1433].
2018-06-07 14:08:51.90 spid19s Server is listening on [ 'any' <ipv4> 1433].
2018-06-07 14:08:51.90 Server Server is listening on [ ::1 <ipv6> 1434].
2018-06-07 14:08:51.90 Server Server is listening on [ 127.0.0.1 <ipv4> 1434].
2018-06-07 14:08:51.91 Server Dedicated admin connection support was established for listening locally on port 1434.
2018-06-07 14:08:51.92 spid19s SQL Server is now ready for client connections. This is an informational message; no user action is required.
2018-06-07 14:08:52.39 spid9s Starting up database 'tempdb'.
2018-06-07 14:08:52.60 spid9s The tempdb database has 1 data file(s).
2018-06-07 14:08:52.60 spid24s The Service Broker endpoint is in disabled or stopped state.
2018-06-07 14:08:52.61 spid24s The Database Mirroring endpoint is in disabled or stopped state.
2018-06-07 14:08:52.62 spid24s Service Broker manager has started.
2018-06-07 14:08:52.65 spid6s Recovery is complete. This is an informational message only. No user action is required.
sql-server linux sql-server-2017
edited Jun 8 '18 at 15:27
MDCCL
6,87331845
asked Jun 7 '18 at 19:25
Ilse HölIlse Höl
92
bumped to the homepage by Community♦ 9 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
|
show 1 more comment
I have just installed SQL Server 2017 on a Linux machine, when I connect locally it is working. But on trying to connect from SSMS it says:
Error 10054: A connection was successfully established with the server, but then an error occurred during the login process.
Please tell me what's wrong?
root@vps188507:~# cat /var/opt/mssql/log/errorlog
2018-06-07 14:08:50.38 Server Microsoft SQL Server 2017 (RTM-CU7) (KB4229789) - 14.0.3026.27 (X64)
May 10 2018 12:38:11
Copyright (C) 2017 Microsoft Corporation
Developer Edition (64-bit) on Linux (Debian GNU/Linux 8 (jessie))
2018-06-07 14:08:50.39 Server UTC adjustment: -4:00
2018-06-07 14:08:50.39 Server (c) Microsoft Corporation.
2018-06-07 14:08:50.39 Server All rights reserved.
2018-06-07 14:08:50.39 Server Server process ID is 4124.
2018-06-07 14:08:50.39 Server Logging SQL Server messages in file '/var/opt/mssql/log/errorlog'.
2018-06-07 14:08:50.39 Server Registry startup parameters:
-d /var/opt/mssql/data/master.mdf
-l /var/opt/mssql/data/mastlog.ldf
-e /var/opt/mssql/log/errorlog
2018-06-07 14:08:50.40 Server SQL Server detected 2 sockets with 1 cores per socket and 1 logical processors per socket, 2 total logical processors; using 2 logical processors based on SQL Server licensing. This is an informational message; no user action is required.
2018-06-07 14:08:50.40 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2018-06-07 14:08:50.40 Server Detected 6251 MB of RAM. This is an informational message; no user action is required.
2018-06-07 14:08:50.40 Server Using conventional memory in the memory manager.
2018-06-07 14:08:50.60 Server Buffer pool extension is already disabled. No action is necessary.
2018-06-07 14:08:50.78 Server InitializeExternalUserGroupSid failed. Implied authentication will be disabled.
2018-06-07 14:08:50.78 Server Implied authentication manager initialization failed. Implied authentication will be disabled.
2018-06-07 14:08:50.80 Server Successfully initialized the TLS configuration. Allowed TLS protocol versions are ['1.0 1.1 1.2']. Allowed TLS ciphers are ['ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-AES128-SHA256:ECDHE-ECDSA-AES256-SHA384:ECDHE-ECDSA-AES256-SHA:ECDHE-ECDSA-AES128-SHA:AES256-GCM-SHA384:AES128-GCM-SHA256:AES256-SHA256:AES128-SHA256:AES256-SHA:AES128-SHA:!DHE-RSA-AES256-GCM-SHA384:!DHE-RSA-AES128-GCM-SHA256:!DHE-RSA-AES256-SHA:!DHE-RSA-AES128-SHA'].
2018-06-07 14:08:50.85 Server The maximum number of dedicated administrator connections for this instance is '1'
2018-06-07 14:08:50.85 Server Node configuration: node 0: CPU mask: 0x0000000000000003:0 Active CPU mask: 0x0000000000000003:0. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required.
2018-06-07 14:08:50.88 Server Using dynamic lock allocation. Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node. This is an informational message only. No user action is required.
2018-06-07 14:08:50.90 Server In-Memory OLTP initialized on lowend machine.
2018-06-07 14:08:50.97 Server Database Instant File Initialization: enabled. For security and performance considerations see the topic 'Database Instant File Initialization' in SQL Server Books Online. This is an informational message only. No user action is required.
2018-06-07 14:08:50.99 Server Query Store settings initialized with enabled = 1,
2018-06-07 14:08:51.01 spid6s Starting up database 'master'.
2018-06-07 14:08:51.01 Server Software Usage Metrics is disabled.
2018-06-07 14:08:51.35 spid6s Resource governor reconfiguration succeeded.
2018-06-07 14:08:51.35 spid6s SQL Server Audit is starting the audits. This is an informational message. No user action is required.
2018-06-07 14:08:51.35 spid6s SQL Server Audit has started the audits. This is an informational message. No user action is required.
2018-06-07 14:08:51.46 spid6s SQL Trace ID 1 was started by login "sa".
2018-06-07 14:08:51.50 spid6s Server name is 'vps188507'. This is an informational message only. No user action is required.
2018-06-07 14:08:51.56 spid9s Starting up database 'mssqlsystemresource'.
2018-06-07 14:08:51.56 spid22s Always On: The availability replica manager is starting. This is an informational message only. No user action is required.
2018-06-07 14:08:51.56 spid22s Always On: The availability replica manager is waiting for the instance of SQL Server to allow client connections. This is an informational message only. No user action is required.
2018-06-07 14:08:51.57 spid6s Starting up database 'msdb'.
2018-06-07 14:08:51.57 spid9s The resource database build version is 14.00.3026. This is an informational message only. No user action is required.
2018-06-07 14:08:51.60 spid9s Starting up database 'model'.
2018-06-07 14:08:51.89 spid9s Polybase feature disabled.
2018-06-07 14:08:51.89 spid9s Clearing tempdb database.
2018-06-07 14:08:51.89 spid19s A self-generated certificate was successfully loaded for encryption.
2018-06-07 14:08:51.90 spid19s Server is listening on [ 'any' <ipv6> 1433].
2018-06-07 14:08:51.90 spid19s Server is listening on [ 'any' <ipv4> 1433].
2018-06-07 14:08:51.90 Server Server is listening on [ ::1 <ipv6> 1434].
2018-06-07 14:08:51.90 Server Server is listening on [ 127.0.0.1 <ipv4> 1434].
2018-06-07 14:08:51.91 Server Dedicated admin connection support was established for listening locally on port 1434.
2018-06-07 14:08:51.92 spid19s SQL Server is now ready for client connections. This is an informational message; no user action is required.
2018-06-07 14:08:52.39 spid9s Starting up database 'tempdb'.
2018-06-07 14:08:52.60 spid9s The tempdb database has 1 data file(s).
2018-06-07 14:08:52.60 spid24s The Service Broker endpoint is in disabled or stopped state.
2018-06-07 14:08:52.61 spid24s The Database Mirroring endpoint is in disabled or stopped state.
2018-06-07 14:08:52.62 spid24s Service Broker manager has started.
2018-06-07 14:08:52.65 spid6s Recovery is complete. This is an informational message only. No user action is required.
sql-server linux sql-server-2017
edited Jun 8 '18 at 15:27
MDCCL
6,87331845
asked Jun 7 '18 at 19:25
Ilse HölIlse Höl
92
bumped to the homepage by Community♦ 9 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
How are you connecting - using IP or host name ?
– Kin
Jun 7 '18 at 19:29
Please edit your question to include the contents of '/var/opt/mssql/log/errorlog' and a brief description of your login process.
– DrA7
Jun 7 '18 at 19:35
both. not workin if connecting via IP or hostname too
– Ilse Höl
Jun 7 '18 at 19:36
see troubleshooting connection issues .. most likely related to firewall
– Kin
Jun 7 '18 at 19:42
Try clicking on the options at the login window there and changing the default database.
– Jacob H
Jun 7 '18 at 19:44
|
show 1 more comment
I have just installed SQL Server 2017 on a Linux machine, when I connect locally it is working. But on trying to connect from SSMS it says:
Error 10054: A connection was successfully established with the server, but then an error occurred during the login process.
Please tell me what's wrong?
root@vps188507:~# cat /var/opt/mssql/log/errorlog
2018-06-07 14:08:50.38 Server Microsoft SQL Server 2017 (RTM-CU7) (KB4229789) - 14.0.3026.27 (X64)
May 10 2018 12:38:11
Copyright (C) 2017 Microsoft Corporation
Developer Edition (64-bit) on Linux (Debian GNU/Linux 8 (jessie))
2018-06-07 14:08:50.39 Server UTC adjustment: -4:00
2018-06-07 14:08:50.39 Server (c) Microsoft Corporation.
2018-06-07 14:08:50.39 Server All rights reserved.
2018-06-07 14:08:50.39 Server Server process ID is 4124.
2018-06-07 14:08:50.39 Server Logging SQL Server messages in file '/var/opt/mssql/log/errorlog'.
2018-06-07 14:08:50.39 Server Registry startup parameters:
-d /var/opt/mssql/data/master.mdf
-l /var/opt/mssql/data/mastlog.ldf
-e /var/opt/mssql/log/errorlog
2018-06-07 14:08:50.40 Server SQL Server detected 2 sockets with 1 cores per socket and 1 logical processors per socket, 2 total logical processors; using 2 logical processors based on SQL Server licensing. This is an informational message; no user action is required.
2018-06-07 14:08:50.40 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2018-06-07 14:08:50.40 Server Detected 6251 MB of RAM. This is an informational message; no user action is required.
2018-06-07 14:08:50.40 Server Using conventional memory in the memory manager.
2018-06-07 14:08:50.60 Server Buffer pool extension is already disabled. No action is necessary.
2018-06-07 14:08:50.78 Server InitializeExternalUserGroupSid failed. Implied authentication will be disabled.
2018-06-07 14:08:50.78 Server Implied authentication manager initialization failed. Implied authentication will be disabled.
2018-06-07 14:08:50.80 Server Successfully initialized the TLS configuration. Allowed TLS protocol versions are ['1.0 1.1 1.2']. Allowed TLS ciphers are ['ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-AES128-SHA256:ECDHE-ECDSA-AES256-SHA384:ECDHE-ECDSA-AES256-SHA:ECDHE-ECDSA-AES128-SHA:AES256-GCM-SHA384:AES128-GCM-SHA256:AES256-SHA256:AES128-SHA256:AES256-SHA:AES128-SHA:!DHE-RSA-AES256-GCM-SHA384:!DHE-RSA-AES128-GCM-SHA256:!DHE-RSA-AES256-SHA:!DHE-RSA-AES128-SHA'].
2018-06-07 14:08:50.85 Server The maximum number of dedicated administrator connections for this instance is '1'
2018-06-07 14:08:50.85 Server Node configuration: node 0: CPU mask: 0x0000000000000003:0 Active CPU mask: 0x0000000000000003:0. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required.
2018-06-07 14:08:50.88 Server Using dynamic lock allocation. Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node. This is an informational message only. No user action is required.
2018-06-07 14:08:50.90 Server In-Memory OLTP initialized on lowend machine.
2018-06-07 14:08:50.97 Server Database Instant File Initialization: enabled. For security and performance considerations see the topic 'Database Instant File Initialization' in SQL Server Books Online. This is an informational message only. No user action is required.
2018-06-07 14:08:50.99 Server Query Store settings initialized with enabled = 1,
2018-06-07 14:08:51.01 spid6s Starting up database 'master'.
2018-06-07 14:08:51.01 Server Software Usage Metrics is disabled.
2018-06-07 14:08:51.35 spid6s Resource governor reconfiguration succeeded.
2018-06-07 14:08:51.35 spid6s SQL Server Audit is starting the audits. This is an informational message. No user action is required.
2018-06-07 14:08:51.35 spid6s SQL Server Audit has started the audits. This is an informational message. No user action is required.
2018-06-07 14:08:51.46 spid6s SQL Trace ID 1 was started by login "sa".
2018-06-07 14:08:51.50 spid6s Server name is 'vps188507'. This is an informational message only. No user action is required.
2018-06-07 14:08:51.56 spid9s Starting up database 'mssqlsystemresource'.
2018-06-07 14:08:51.56 spid22s Always On: The availability replica manager is starting. This is an informational message only. No user action is required.
2018-06-07 14:08:51.56 spid22s Always On: The availability replica manager is waiting for the instance of SQL Server to allow client connections. This is an informational message only. No user action is required.
2018-06-07 14:08:51.57 spid6s Starting up database 'msdb'.
2018-06-07 14:08:51.57 spid9s The resource database build version is 14.00.3026. This is an informational message only. No user action is required.
2018-06-07 14:08:51.60 spid9s Starting up database 'model'.
2018-06-07 14:08:51.89 spid9s Polybase feature disabled.
2018-06-07 14:08:51.89 spid9s Clearing tempdb database.
2018-06-07 14:08:51.89 spid19s A self-generated certificate was successfully loaded for encryption.
2018-06-07 14:08:51.90 spid19s Server is listening on [ 'any' <ipv6> 1433].
2018-06-07 14:08:51.90 spid19s Server is listening on [ 'any' <ipv4> 1433].
2018-06-07 14:08:51.90 Server Server is listening on [ ::1 <ipv6> 1434].
2018-06-07 14:08:51.90 Server Server is listening on [ 127.0.0.1 <ipv4> 1434].
2018-06-07 14:08:51.91 Server Dedicated admin connection support was established for listening locally on port 1434.
2018-06-07 14:08:51.92 spid19s SQL Server is now ready for client connections. This is an informational message; no user action is required.
2018-06-07 14:08:52.39 spid9s Starting up database 'tempdb'.
2018-06-07 14:08:52.60 spid9s The tempdb database has 1 data file(s).
2018-06-07 14:08:52.60 spid24s The Service Broker endpoint is in disabled or stopped state.
2018-06-07 14:08:52.61 spid24s The Database Mirroring endpoint is in disabled or stopped state.
2018-06-07 14:08:52.62 spid24s Service Broker manager has started.
2018-06-07 14:08:52.65 spid6s Recovery is complete. This is an informational message only. No user action is required.
sql-server linux sql-server-2017
edited Jun 8 '18 at 15:27
MDCCL
6,87331845
asked Jun 7 '18 at 19:25
Ilse HölIlse Höl
92
I have just installed SQL Server 2017 on a Linux machine, when I connect locally it is working. But on trying to connect from SSMS it says:
Error 10054: A connection was successfully established with the server, but then an error occurred during the login process.
Please tell me what's wrong?
root@vps188507:~# cat /var/opt/mssql/log/errorlog
2018-06-07 14:08:50.38 Server Microsoft SQL Server 2017 (RTM-CU7) (KB4229789) - 14.0.3026.27 (X64)
May 10 2018 12:38:11
Copyright (C) 2017 Microsoft Corporation
Developer Edition (64-bit) on Linux (Debian GNU/Linux 8 (jessie))
2018-06-07 14:08:50.39 Server UTC adjustment: -4:00
2018-06-07 14:08:50.39 Server (c) Microsoft Corporation.
2018-06-07 14:08:50.39 Server All rights reserved.
2018-06-07 14:08:50.39 Server Server process ID is 4124.
2018-06-07 14:08:50.39 Server Logging SQL Server messages in file '/var/opt/mssql/log/errorlog'.
2018-06-07 14:08:50.39 Server Registry startup parameters:
-d /var/opt/mssql/data/master.mdf
-l /var/opt/mssql/data/mastlog.ldf
-e /var/opt/mssql/log/errorlog
2018-06-07 14:08:50.40 Server SQL Server detected 2 sockets with 1 cores per socket and 1 logical processors per socket, 2 total logical processors; using 2 logical processors based on SQL Server licensing. This is an informational message; no user action is required.
2018-06-07 14:08:50.40 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2018-06-07 14:08:50.40 Server Detected 6251 MB of RAM. This is an informational message; no user action is required.
2018-06-07 14:08:50.40 Server Using conventional memory in the memory manager.
2018-06-07 14:08:50.60 Server Buffer pool extension is already disabled. No action is necessary.
2018-06-07 14:08:50.78 Server InitializeExternalUserGroupSid failed. Implied authentication will be disabled.
2018-06-07 14:08:50.78 Server Implied authentication manager initialization failed. Implied authentication will be disabled.
2018-06-07 14:08:50.80 Server Successfully initialized the TLS configuration. Allowed TLS protocol versions are ['1.0 1.1 1.2']. Allowed TLS ciphers are ['ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-AES128-SHA256:ECDHE-ECDSA-AES256-SHA384:ECDHE-ECDSA-AES256-SHA:ECDHE-ECDSA-AES128-SHA:AES256-GCM-SHA384:AES128-GCM-SHA256:AES256-SHA256:AES128-SHA256:AES256-SHA:AES128-SHA:!DHE-RSA-AES256-GCM-SHA384:!DHE-RSA-AES128-GCM-SHA256:!DHE-RSA-AES256-SHA:!DHE-RSA-AES128-SHA'].
2018-06-07 14:08:50.85 Server The maximum number of dedicated administrator connections for this instance is '1'
2018-06-07 14:08:50.85 Server Node configuration: node 0: CPU mask: 0x0000000000000003:0 Active CPU mask: 0x0000000000000003:0. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required.
2018-06-07 14:08:50.88 Server Using dynamic lock allocation. Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node. This is an informational message only. No user action is required.
2018-06-07 14:08:50.90 Server In-Memory OLTP initialized on lowend machine.
2018-06-07 14:08:50.97 Server Database Instant File Initialization: enabled. For security and performance considerations see the topic 'Database Instant File Initialization' in SQL Server Books Online. This is an informational message only. No user action is required.
2018-06-07 14:08:50.99 Server Query Store settings initialized with enabled = 1,
2018-06-07 14:08:51.01 spid6s Starting up database 'master'.
2018-06-07 14:08:51.01 Server Software Usage Metrics is disabled.
2018-06-07 14:08:51.35 spid6s Resource governor reconfiguration succeeded.
2018-06-07 14:08:51.35 spid6s SQL Server Audit is starting the audits. This is an informational message. No user action is required.
2018-06-07 14:08:51.35 spid6s SQL Server Audit has started the audits. This is an informational message. No user action is required.
2018-06-07 14:08:51.46 spid6s SQL Trace ID 1 was started by login "sa".
2018-06-07 14:08:51.50 spid6s Server name is 'vps188507'. This is an informational message only. No user action is required.
2018-06-07 14:08:51.56 spid9s Starting up database 'mssqlsystemresource'.
2018-06-07 14:08:51.56 spid22s Always On: The availability replica manager is starting. This is an informational message only. No user action is required.
2018-06-07 14:08:51.56 spid22s Always On: The availability replica manager is waiting for the instance of SQL Server to allow client connections. This is an informational message only. No user action is required.
2018-06-07 14:08:51.57 spid6s Starting up database 'msdb'.
2018-06-07 14:08:51.57 spid9s The resource database build version is 14.00.3026. This is an informational message only. No user action is required.
2018-06-07 14:08:51.60 spid9s Starting up database 'model'.
2018-06-07 14:08:51.89 spid9s Polybase feature disabled.
2018-06-07 14:08:51.89 spid9s Clearing tempdb database.
2018-06-07 14:08:51.89 spid19s A self-generated certificate was successfully loaded for encryption.
2018-06-07 14:08:51.90 spid19s Server is listening on [ 'any' <ipv6> 1433].
2018-06-07 14:08:51.90 spid19s Server is listening on [ 'any' <ipv4> 1433].
2018-06-07 14:08:51.90 Server Server is listening on [ ::1 <ipv6> 1434].
2018-06-07 14:08:51.90 Server Server is listening on [ 127.0.0.1 <ipv4> 1434].
2018-06-07 14:08:51.91 Server Dedicated admin connection support was established for listening locally on port 1434.
2018-06-07 14:08:51.92 spid19s SQL Server is now ready for client connections. This is an informational message; no user action is required.
2018-06-07 14:08:52.39 spid9s Starting up database 'tempdb'.
2018-06-07 14:08:52.60 spid9s The tempdb database has 1 data file(s).
2018-06-07 14:08:52.60 spid24s The Service Broker endpoint is in disabled or stopped state.
2018-06-07 14:08:52.61 spid24s The Database Mirroring endpoint is in disabled or stopped state.
2018-06-07 14:08:52.62 spid24s Service Broker manager has started.
2018-06-07 14:08:52.65 spid6s Recovery is complete. This is an informational message only. No user action is required.
sql-server linux sql-server-2017
sql-server linux sql-server-2017
edited Jun 8 '18 at 15:27
MDCCL
6,87331845
asked Jun 7 '18 at 19:25
Ilse HölIlse Höl
92
edited Jun 8 '18 at 15:27
MDCCL
6,87331845
asked Jun 7 '18 at 19:25
Ilse HölIlse Höl
92
edited Jun 8 '18 at 15:27
MDCCL
6,87331845
edited Jun 8 '18 at 15:27
MDCCL
6,87331845
edited Jun 8 '18 at 15:27
MDCCL
6,87331845
6,87331845
asked Jun 7 '18 at 19:25
Ilse HölIlse Höl
92
asked Jun 7 '18 at 19:25
Ilse HölIlse Höl
92
asked Jun 7 '18 at 19:25
Ilse HölIlse Höl
92
92
bumped to the homepage by Community♦ 9 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
bumped to the homepage by Community♦ 9 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
How are you connecting - using IP or host name ?
– Kin
Jun 7 '18 at 19:29
Please edit your question to include the contents of '/var/opt/mssql/log/errorlog' and a brief description of your login process.
– DrA7
Jun 7 '18 at 19:35
both. not workin if connecting via IP or hostname too
– Ilse Höl
Jun 7 '18 at 19:36
see troubleshooting connection issues .. most likely related to firewall
– Kin
Jun 7 '18 at 19:42
Try clicking on the options at the login window there and changing the default database.
– Jacob H
Jun 7 '18 at 19:44
|
show 1 more comment
How are you connecting - using IP or host name ?
– Kin
Jun 7 '18 at 19:29
Please edit your question to include the contents of '/var/opt/mssql/log/errorlog' and a brief description of your login process.
– DrA7
Jun 7 '18 at 19:35
both. not workin if connecting via IP or hostname too
– Ilse Höl
Jun 7 '18 at 19:36
see troubleshooting connection issues .. most likely related to firewall
– Kin
Jun 7 '18 at 19:42
Try clicking on the options at the login window there and changing the default database.
– Jacob H
Jun 7 '18 at 19:44
How are you connecting - using IP or host name ?
– Kin
Jun 7 '18 at 19:29
How are you connecting - using IP or host name ?
– Kin
Jun 7 '18 at 19:29
Please edit your question to include the contents of '/var/opt/mssql/log/errorlog' and a brief description of your login process.
– DrA7
Jun 7 '18 at 19:35
Please edit your question to include the contents of '/var/opt/mssql/log/errorlog' and a brief description of your login process.
– DrA7
Jun 7 '18 at 19:35
both. not workin if connecting via IP or hostname too
– Ilse Höl
Jun 7 '18 at 19:36
both. not workin if connecting via IP or hostname too
– Ilse Höl
Jun 7 '18 at 19:36
see troubleshooting connection issues .. most likely related to firewall
– Kin
Jun 7 '18 at 19:42
see troubleshooting connection issues .. most likely related to firewall
– Kin
Jun 7 '18 at 19:42
Try clicking on the options at the login window there and changing the default database.
– Jacob H
Jun 7 '18 at 19:44
Try clicking on the options at the login window there and changing the default database.
– Jacob H
Jun 7 '18 at 19:44
|
show 1 more comment
1 Answer
1
active
oldest
votes
Let's try a few things:
Option 1: First on the source SQL server (trying to connect to your Linux SQL Server) check to make sure named pipes (and TCP/IP) is enabled on the source SQL Server via SQL Server Configuration Manager (if the source SQL Server (SSMS) runs on Windows). I have two client protocols to enable on Windows both 32bit and 64bit:
Option 2: Try changing SQL Server to mixed mode and try logging in with a SQL account (but I'm assuming you've done this already).
Option 3: Just saw these various changes some people tried. Some of these changes look quite odd but worked for some people:
https://stackoverflow.com/questions/27267658/no-process-is-on-the-other-end-of-the-pipe-sql-server-2012?utm_medium=organic&utm_source=google_rich_qa&utm_campaign=google_rich_qa
Option 4: Open ports 1433 and 1434 on Linux (might need to do this on source AND target servers):
http://stevestedman.com/2016/11/allow-port-1433-ubuntu-linux-sql-server/
Option 5: (You may have said this a different way), but connect via SSMS using the target SQL Server's IP address.
Option 6: Use the fully qualified SQL Server name (FQDN) to connect to the target SQL Server. (i.e. the way you'd connect to SQL Server on Azure).
Option 7: Try using tcp:servername,1433 within SQL Server Management Studio to connect to the target Linux SQL Server
answered Jun 8 '18 at 15:19
StingSting
2,262516
2
this is sql server on linux .. so no configuration manager GUI exists.
– Kin
Jun 8 '18 at 15:28
Thanks! I clarified that. IF you're connecting to a target SQL Server running on Windows in Option 1.
– Sting
Jun 8 '18 at 16:14
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "182"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fdba.stackexchange.com%2fquestions%2f209031%2fsql-server-2017-on-linux-ssms-connection-attempt-throws-error-10054%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
Let's try a few things:
Option 1: First on the source SQL server (trying to connect to your Linux SQL Server) check to make sure named pipes (and TCP/IP) is enabled on the source SQL Server via SQL Server Configuration Manager (if the source SQL Server (SSMS) runs on Windows). I have two client protocols to enable on Windows both 32bit and 64bit:
Option 2: Try changing SQL Server to mixed mode and try logging in with a SQL account (but I'm assuming you've done this already).
Option 3: Just saw these various changes some people tried. Some of these changes look quite odd but worked for some people:
https://stackoverflow.com/questions/27267658/no-process-is-on-the-other-end-of-the-pipe-sql-server-2012?utm_medium=organic&utm_source=google_rich_qa&utm_campaign=google_rich_qa
Option 4: Open ports 1433 and 1434 on Linux (might need to do this on source AND target servers):
http://stevestedman.com/2016/11/allow-port-1433-ubuntu-linux-sql-server/
Option 5: (You may have said this a different way), but connect via SSMS using the target SQL Server's IP address.
Option 6: Use the fully qualified SQL Server name (FQDN) to connect to the target SQL Server. (i.e. the way you'd connect to SQL Server on Azure).
Option 7: Try using tcp:servername,1433 within SQL Server Management Studio to connect to the target Linux SQL Server
answered Jun 8 '18 at 15:19
StingSting
2,262516
2
this is sql server on linux .. so no configuration manager GUI exists.
– Kin
Jun 8 '18 at 15:28
Thanks! I clarified that. IF you're connecting to a target SQL Server running on Windows in Option 1.
– Sting
Jun 8 '18 at 16:14
add a comment |
Let's try a few things:
Option 1: First on the source SQL server (trying to connect to your Linux SQL Server) check to make sure named pipes (and TCP/IP) is enabled on the source SQL Server via SQL Server Configuration Manager (if the source SQL Server (SSMS) runs on Windows). I have two client protocols to enable on Windows both 32bit and 64bit:
Option 2: Try changing SQL Server to mixed mode and try logging in with a SQL account (but I'm assuming you've done this already).
Option 3: Just saw these various changes some people tried. Some of these changes look quite odd but worked for some people:
https://stackoverflow.com/questions/27267658/no-process-is-on-the-other-end-of-the-pipe-sql-server-2012?utm_medium=organic&utm_source=google_rich_qa&utm_campaign=google_rich_qa
Option 4: Open ports 1433 and 1434 on Linux (might need to do this on source AND target servers):
http://stevestedman.com/2016/11/allow-port-1433-ubuntu-linux-sql-server/
Option 5: (You may have said this a different way), but connect via SSMS using the target SQL Server's IP address.
Option 6: Use the fully qualified SQL Server name (FQDN) to connect to the target SQL Server. (i.e. the way you'd connect to SQL Server on Azure).
Option 7: Try using tcp:servername,1433 within SQL Server Management Studio to connect to the target Linux SQL Server
answered Jun 8 '18 at 15:19
StingSting
2,262516
2
this is sql server on linux .. so no configuration manager GUI exists.
– Kin
Jun 8 '18 at 15:28
Thanks! I clarified that. IF you're connecting to a target SQL Server running on Windows in Option 1.
– Sting
Jun 8 '18 at 16:14
add a comment |
Let's try a few things:
Option 1: First on the source SQL server (trying to connect to your Linux SQL Server) check to make sure named pipes (and TCP/IP) is enabled on the source SQL Server via SQL Server Configuration Manager (if the source SQL Server (SSMS) runs on Windows). I have two client protocols to enable on Windows both 32bit and 64bit:
Option 2: Try changing SQL Server to mixed mode and try logging in with a SQL account (but I'm assuming you've done this already).
Option 3: Just saw these various changes some people tried. Some of these changes look quite odd but worked for some people:
https://stackoverflow.com/questions/27267658/no-process-is-on-the-other-end-of-the-pipe-sql-server-2012?utm_medium=organic&utm_source=google_rich_qa&utm_campaign=google_rich_qa
Option 4: Open ports 1433 and 1434 on Linux (might need to do this on source AND target servers):
http://stevestedman.com/2016/11/allow-port-1433-ubuntu-linux-sql-server/
Option 5: (You may have said this a different way), but connect via SSMS using the target SQL Server's IP address.
Option 6: Use the fully qualified SQL Server name (FQDN) to connect to the target SQL Server. (i.e. the way you'd connect to SQL Server on Azure).
Option 7: Try using tcp:servername,1433 within SQL Server Management Studio to connect to the target Linux SQL Server
answered Jun 8 '18 at 15:19
StingSting
2,262516
Let's try a few things:
Option 1: First on the source SQL server (trying to connect to your Linux SQL Server) check to make sure named pipes (and TCP/IP) is enabled on the source SQL Server via SQL Server Configuration Manager (if the source SQL Server (SSMS) runs on Windows). I have two client protocols to enable on Windows both 32bit and 64bit:
Option 2: Try changing SQL Server to mixed mode and try logging in with a SQL account (but I'm assuming you've done this already).
Option 3: Just saw these various changes some people tried. Some of these changes look quite odd but worked for some people:
https://stackoverflow.com/questions/27267658/no-process-is-on-the-other-end-of-the-pipe-sql-server-2012?utm_medium=organic&utm_source=google_rich_qa&utm_campaign=google_rich_qa
Option 4: Open ports 1433 and 1434 on Linux (might need to do this on source AND target servers):
http://stevestedman.com/2016/11/allow-port-1433-ubuntu-linux-sql-server/
Option 5: (You may have said this a different way), but connect via SSMS using the target SQL Server's IP address.
Option 6: Use the fully qualified SQL Server name (FQDN) to connect to the target SQL Server. (i.e. the way you'd connect to SQL Server on Azure).
Option 7: Try using tcp:servername,1433 within SQL Server Management Studio to connect to the target Linux SQL Server
answered Jun 8 '18 at 15:19
StingSting
2,262516
edited Jun 8 '18 at 16:25
answered Jun 8 '18 at 15:19
StingSting
2,262516
answered Jun 8 '18 at 15:19
StingSting
2,262516
answered Jun 8 '18 at 15:19
StingSting
2,262516
2,262516
2
this is sql server on linux .. so no configuration manager GUI exists.
– Kin
Jun 8 '18 at 15:28
Thanks! I clarified that. IF you're connecting to a target SQL Server running on Windows in Option 1.
– Sting
Jun 8 '18 at 16:14
add a comment |
2
this is sql server on linux .. so no configuration manager GUI exists.
– Kin
Jun 8 '18 at 15:28
Thanks! I clarified that. IF you're connecting to a target SQL Server running on Windows in Option 1.
– Sting
Jun 8 '18 at 16:14
2
2
this is sql server on linux .. so no configuration manager GUI exists.
– Kin
Jun 8 '18 at 15:28
this is sql server on linux .. so no configuration manager GUI exists.
– Kin
Jun 8 '18 at 15:28
Thanks! I clarified that. IF you're connecting to a target SQL Server running on Windows in Option 1.
– Sting
Jun 8 '18 at 16:14
Thanks! I clarified that. IF you're connecting to a target SQL Server running on Windows in Option 1.
– Sting
Jun 8 '18 at 16:14
add a comment |
Thanks for contributing an answer to Database Administrators Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fdba.stackexchange.com%2fquestions%2f209031%2fsql-server-2017-on-linux-ssms-connection-attempt-throws-error-10054%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
How are you connecting - using IP or host name ?
– Kin
Jun 7 '18 at 19:29
Please edit your question to include the contents of '/var/opt/mssql/log/errorlog' and a brief description of your login process.
– DrA7
Jun 7 '18 at 19:35
both. not workin if connecting via IP or hostname too
– Ilse Höl
Jun 7 '18 at 19:36
see troubleshooting connection issues .. most likely related to firewall
– Kin
Jun 7 '18 at 19:42
Try clicking on the options at the login window there and changing the default database.
– Jacob H
Jun 7 '18 at 19:44