none
sqlcmd: Error: Microsoft ODBC Driver 17 for SQL Server : TCP Provider: Error code 0x2746 RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    1
    Sign in to vote

    Hi,

    i freshly installed Ubuntu Server 18.04 TLS with MS SQL Server 17 on Ubuntu. After all steps i try to execute on the localhost the command: sqlcmd -S localhost -U sa

    and get the upper error. I google a little bit and find out that the TLS 1.2 maybe is the issue.

    So i try the command: openssl s_client -connect google.com:443 -tlsl_2
    and get a handshake and verification OK

    what can i try next to solve this issue?

    kindly regards, Lars

    Friday, July 26, 2019 5:46 AM
    |

Answers

  • Question
    Sign in to vote
    2
    Sign in to vote
    Problem is solved: Deinstall MSSQL 2019, install MSSQL 2017 Server, everything is fine, after that.

    Lars Vietense

    • Marked as answer by LarsVie Wednesday, July 31, 2019 8:17 AM
    Monday, July 29, 2019 4:35 PM
    |

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote

    sqlcmd -S localhost -U sa

    Hello Lars,

    It's a SQL Server, not a web Server; localhost don't work here. Use either machine Name or for local Connection "(local)" or a simple dot "."

    Olaf Helper

    [ Blog] [ Xing] [ MVP]

    Friday, July 26, 2019 6:35 AM
    |
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi,

    i try the ip-address, (local), . and the machine name - the result is the same - i get the error.

    The firewall is off but this doen't matter when i try to conect from the local ssh-terminal.


    • Edited by LarsVie Monday, July 29, 2019 5:22 AM
    Monday, July 29, 2019 5:20 AM
    |
  • Question
    Sign in to vote
    0
    Sign in to vote
    Then have a look at MS Support: Solving Connectivity errors to SQL Server

    Olaf Helper

    [ Blog] [ Xing] [ MVP]

    Monday, July 29, 2019 7:54 AM
    |
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi,

    i have the following errorlog after restart the server:

    2019-07-29 11:30:45.85 Server      Microsoft SQL Server 2019 (CTP3.2) - 15.0.1800.32 (X64) 
	Jul 17 2019 21:29:33 
	Copyright (C) 2019 Microsoft Corporation
	Express Edition (64-bit) on Linux (Ubuntu 18.04.2 LTS) <X64>
2019-07-29 11:30:45.85 Server      UTC adjustment: 2:00
2019-07-29 11:30:45.85 Server      (c) Microsoft Corporation.
2019-07-29 11:30:45.85 Server      All rights reserved.
2019-07-29 11:30:45.85 Server      Server process ID is 32.
2019-07-29 11:30:45.85 Server      Logging SQL Server messages in file '/var/opt/mssql/log/errorlog.loc'.
2019-07-29 11:30:45.85 Server      Registry startup parameters: 
	 -d /var/opt/mssql/data/master.mdf
	 -l /var/opt/mssql/data/mastlog.ldf
	 -e /var/opt/mssql/log/errorlog
2019-07-29 11:30:45.86 Server      SQL Server detected 1 sockets with 10 cores per socket and 20 logical processors per socket, 20 total logical processors; using 8 logical processors based on SQL Server licensing. This is an informational message; no user action is required.
2019-07-29 11:30:45.86 Server      SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2019-07-29 11:30:45.86 Server      Detected 51102 MB of RAM. This is an informational message; no user action is required.
2019-07-29 11:30:45.86 Server      Using conventional memory in the memory manager.
2019-07-29 11:30:45.92 Server      Buffer pool extension is not supported on Linux platform.
2019-07-29 11:30:45.92 Server      Buffer Pool: Allocating 8388608 bytes for 7987200 hashPages.
2019-07-29 11:30:45.99 Server      Default collation: Latin1_General_CI_AS (Deutsch 1031)
2019-07-29 11:30:46.08 Server      Buffer pool extension is already disabled. No action is necessary.
2019-07-29 11:30:46.26 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'].
2019-07-29 11:30:46.28 Server      Query Store settings initialized with enabled = 1, 
2019-07-29 11:30:46.30 Server      The maximum number of dedicated administrator connections for this instance is '1'
2019-07-29 11:30:46.30 Server      Node configuration: node 0: CPU mask: 0x00000000000000ff:0 Active CPU mask: 0x00000000000000ff:0. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required.
2019-07-29 11:30:46.37 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.
2019-07-29 11:30:46.38 Server      Lock partitioning is enabled.  This is an informational message only. No user action is required.
2019-07-29 11:30:46.44 Server      [INFO] Created Extended Events session 'hkenginexesession'

2019-07-29 11:30:46.44 Server      Database Instant File Initialization: aktiviert. 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.
2019-07-29 11:30:46.45 Server      Total Log Writer threads: 2. This is an informational message; no user action is required.
2019-07-29 11:30:46.46 Server      clwb is selected for pmem flush operation.
2019-07-29 11:30:46.47 Server      Software Usage Metrics is disabled.
2019-07-29 11:30:46.47 spid10s     Starting up database 'master'.
2019-07-29 11:30:46.81 spid10s     SQL Server Audit is starting the audits. This is an informational message. No user action is required.
2019-07-29 11:30:46.81 spid10s     SQL Server Audit has started the audits. This is an informational message. No user action is required.
2019-07-29 11:30:46.84 Server      Common language runtime (CLR) functionality initialized.
2019-07-29 11:30:46.90 spid10s     SQL Trace ID 1 was started by login "sa".
2019-07-29 11:30:46.94 spid10s     Server name is 'panga'. This is an informational message only. No user action is required.
2019-07-29 11:30:46.96 spid23s     Always On: The availability replica manager is starting. This is an informational message only. No user action is required.
2019-07-29 11:30:46.97 spid10s     Starting up database 'msdb'.
2019-07-29 11:30:46.97 spid12s     Starting up database 'mssqlsystemresource'.
2019-07-29 11:30:46.97 spid23s     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.
2019-07-29 11:30:46.97 spid12s     The resource database build version is 15.00.1800. This is an informational message only. No user action is required.
2019-07-29 11:30:46.99 spid12s     Starting up database 'model'.
2019-07-29 11:30:47.03 Server      Failed to verify the Authenticode signature of 'C:\binn\secforwarder.dll'. Signature verification of SQL Server DLLs will be skipped. Genuine copies of SQL Server are signed. Failure to verify the Authenticode signature might indicate that this is not an authentic release of SQL Server. Install a genuine copy of SQL Server or contact customer support.
2019-07-29 11:30:47.08 spid22s     A self-generated certificate was successfully loaded for encryption.
2019-07-29 11:30:47.09 spid22s     Server is listening on [ 'any' <ipv6> 1433].
2019-07-29 11:30:47.09 spid22s     Server is listening on [ 'any' <ipv4> 1433].
2019-07-29 11:30:47.10 spid22s     Dedicated administrator connection support was not started because it is disabled on this edition of SQL Server. If you want to use a dedicated administrator connection, restart SQL Server using the trace flag 7806. This is an informational message only. No user action is required.
2019-07-29 11:30:47.10 spid22s     Error: 39002, Severity: 16, State: 1.
2019-07-29 11:30:47.10 spid22s     SQL failed to boot extensibility for error code 0x80070005.
2019-07-29 11:30:47.11 spid22s     InitializeXdbPkgLauncher failed. ErrorCode: 0x80004005.
2019-07-29 11:30:47.11 spid22s     SQL Server is now ready for client connections. This is an informational message; no user action is required.
2019-07-29 11:30:47.16 spid12s     Clearing tempdb database.
2019-07-29 11:30:47.31 Server      Failed to verify the Authenticode signature of 'C:\binn\msoledbsql.dll'. Signature verification of SQL Server DLLs will be skipped. Genuine copies of SQL Server are signed. Failure to verify the Authenticode signature might indicate that this is not an authentic release of SQL Server. Install a genuine copy of SQL Server or contact customer support.
2019-07-29 11:30:47.37 Server      Fehler: 37308, Schweregrad: 16, Status: 1.
2019-07-29 11:30:47.37 Server      Loaded None enclave for always encrypted.
2019-07-29 11:30:47.51 spid12s     Starting up database 'tempdb'.
2019-07-29 11:30:48.46 spid12s     The tempdb database has 8 data file(s).
2019-07-29 11:30:48.47 spid27s     The Service Broker endpoint is in disabled or stopped state.
2019-07-29 11:30:48.47 spid27s     The Database Mirroring endpoint is in disabled or stopped state.
2019-07-29 11:30:48.51 spid27s     Service Broker manager has started.
2019-07-29 11:30:48.51 spid10s     Recovery is complete. This is an informational message only. No user action is required.

    Lars Vietense

    Monday, July 29, 2019 9:37 AM
    |
  • Question
    Sign in to vote
    1
    Sign in to vote

    This is the tutorial i worked with:

    https://docs.microsoft.com/de-de/sql/linux/quickstart-install-connect-ubuntu?view=sql-server-2017

    Lars Vietense

    • Proposed as answer by Ashin_c Tuesday, July 30, 2019 8:36 AM
    Monday, July 29, 2019 11:41 AM
    |
  • Question
    Sign in to vote
    2
    Sign in to vote
    Problem is solved: Deinstall MSSQL 2019, install MSSQL 2017 Server, everything is fine, after that.

    Lars Vietense

    • Marked as answer by LarsVie Wednesday, July 31, 2019 8:17 AM
    Monday, July 29, 2019 4:35 PM
    |
  • Question
    Sign in to vote
    0
    Sign in to vote
    please kindly mark helpful replies as answers.
    Tuesday, July 30, 2019 8:36 AM
    |
  • Question
    Sign in to vote
    0
    Sign in to vote
    there isn't any helpful replies, sorry

    Lars Vietense

    Tuesday, July 30, 2019 11:12 AM
    |
  • Question
    Sign in to vote
    0
    Sign in to vote
    If you solve your problem, and in order to close the thread, you can mark yourself
    • Edited by Ashin_c Wednesday, July 31, 2019 7:51 AM
    Wednesday, July 31, 2019 7:51 AM
    |
  • Question
    Sign in to vote
    0
    Sign in to vote

    Thanks Lars! 

    Can you pl give the commands you used to achieve this deinstall and install?

    Wednesday, October 16, 2019 7:23 AM
    |