This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(25.6, 22%, 12%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ENS%3C/text%3E%3C/svg%3E)
Latest Version of SQLCMD cannot be used in "TLS1.2 only" environment, because it is still using ODBC Driver 17.
Wherein we have now ODBC Driver 19 available which works well with database hosted with "TLS1.2 only" connectivity.
For such SQL servers, SQLCMD cannot connect successfully, if we disable TLS1.0 and TLS1.1, but keep TLS1.2 enabled
We get this error:
"SSL Error: unable to establish connection and underlying connection is closed by server"
If I enable TLS1.0 and TLS1.1 also, SQLCMD connects well.
SSMS connects well whether you enable TLS1.0/1.1 or not
Any Idea when the new build of SQLCMD with ODBC Driver 19 be available, MS does not seem to be paying any attention towards it ?
Additional SQL Server features and topics not covered by specific categories
FYI, SQLCMD uses ODBC, not OLE DB. The current SQLCMD version 15 uses Microsoft ODBC Driver 17 for SQL Server, which does support TLS 1.2.
Add the error message to your question.
Thanks. you pointed right. that's not OLE DB, but ODBC, I have edited question.
However. ODBC Driver 17 does not support "TLS1.2 Only" environment, it still need TLS 1.0 and 1.1 be enabled below TLS1.2.
if you disable, it wont connect the database server. try it
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(67.2, 1%, 16%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ETP%3C/text%3E%3C/svg%3E)
What version of Windows is the CLIENT using?
The error you are getting, indicates the CLIENT is not setup to support TLS 1.2. This is not a problem with the SQL Server. The reason it works when you enable 1.0/1.1 is because is it connecting using 1.1.
https://learn.microsoft.com/en-us/windows/win32/secauthn/protocols-in-tls-ssl--schannel-ssp-
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(163.2, 84%, 25%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EYM%3C/text%3E%3C/svg%3E)
Hi @Neeraj Saxena ，
ODBC Driver for SQL Server 18.1 released on Aug, 2022, it is the latest version, what is the ODBC Driver 19 available you said
About the error you can see this doc:
KB3135244 - TLS 1.2 support for Microsoft SQL Server
You can try to manually create the registry key on the system that hosts the Reporting services configuration manager
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.2\Client : "Enabled"=dword:00000001
-------------
If the answer is the right solution, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.
I see from your question edit that you are using PowerShell Invoke-sqlcmd. This does not use the SQLCMD command-line utility nor OLE DB or ODBC drivers. The PowerShell cmdlet uses the .NET framework SqlClient API. Make sure you client machine is up-to-date with the latest .NET Framework patches that support TLS 1.2
Sorry again, I pasted wrong Error, now corrected the error. the error goes away if I enable TLS1.0 and TLS1.1
@Neeraj Saxena , check to ensure TLS 1.2 registry entry @YufeiShao-msft mentioned exists on the client machine. Include the full error message returned by SQLCMD in your question.