Unable to connect to server
- Lingua principale
- Python
- Stelle
- 1.4k
- Fork
- 191
- Metriche di merge delle PR
- Nessuna PR unita negli ultimi 30g
Descrizione
Hi,
I am unable to connect to a SQL Server 2016 running on the standard port 1433 on a Windows Server, but succeed in connecting with sqlcmd.
- **Expected**: Successful connection to SQL Server as with sqlcmd on port 1433.
- **Actual**: Error, Connection reset by peer.
I have installed mssql-cli v0.15 using Direct Download and the RHEL default pkg manager yum.
- Distribution: Red Hat Enterprise Linux Server release 7.6 (Maipo)
- System: Linux 3.10.0-957.5.1.el7.x86_64 #1 SMP Wed Dec 19 10:46:58 EST 2018 x86_64 x86_64 GNU/Linux
- MSSQL-CLI version: 0.15 (mssql-cli-0.15.0-1.el7.x86_64)
- Python version: Python 2.7.5 (python-2.7.5-76.el7.x86_64)
- sqlcmd version: Version 17.3.0000.1 Linux (mssql-tools-17.3.0.1-1.x86_64)
- ODBC version: 2.3.7 (unixODBC-2.3.7-1.rh.x86_64, unixODBC-devel-2.3.7-1.rh.x86_64)
- SQL Server: Microsoft SQL Server 2016 (SP1-CU3) - 13.0.4435.0 (X64)
The command being run is
`mssql-cli -S server.hostname.tld -U actual_username -P $MSSQL_CLI`
I have also run the same but with manual password prompting (i.e. without the -P flag).
The error presented is
`Error message: One or more errors occurred. (Unable to write data to the transport connection: Connection reset by peer.)`
With sqlcmd, I am running the following string and I get a command prompt on the server
`$ sqlcmd -S server.hostname.tld -U actual_username -P $MSSQL_CLI`
This allows me to execute SQL statements.
>1>
Guida per i contributori
Nessuna guida per i contributori indicizzata per questo repository
Direzione di ricerca
Start at the mssql-cli connection entry point and compare its SQL Server/ODBC connection path with the working sqlcmd command, using the reported RHEL 7.6 and SQL Server 2016 setup. Reproduce the connection-reset error on port 1433 and trace the differing behavior; done means mssql-cli connects successfully under the reported conditions.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Valutazione
- Stack tecnologico
- python, sql
- Ambito
- cli, databases, networking
- Tipo di issue
- Bug
- Difficoltà
- 4/5
- Tempo stimato
- 3-5 giorni
- Stato di attività
- Ferma
- Chiarezza
- Da chiarire
- Idoneità per principianti
- 35/100