azuredatastudio: Cannot connect

We have written the needed data into your clipboard because it was too large to send. Please paste. Issue Type: Bug

Since the upgrade to 1.26.0 I can no longer connect to any server. Downloaded again the 1.25.3 and it works just fine. Any particular change or is this a bug?

Please the error message I get here below: Microsoft.Data.SqlClient.SqlException (0x80131904): A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: TCP Provider, error: 40 - Could not open a connection to SQL Server) at Microsoft.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection, Action1 wrapCloseInAction) at Microsoft.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose) at Microsoft.Data.SqlClient.TdsParser.Connect(ServerInfo serverInfo, SqlInternalConnectionTds connHandler, Boolean ignoreSniOpenTimeout, Int64 timerExpire, Boolean encrypt, Boolean trustServerCert, Boolean integratedSecurity, Boolean withFailover, SqlAuthenticationMethod authType) at Microsoft.Data.SqlClient.SqlInternalConnectionTds.AttemptOneLogin(ServerInfo serverInfo, String newPassword, SecureString newSecurePassword, Boolean ignoreSniOpenTimeout, TimeoutTimer timeout, Boolean withFailover) at Microsoft.Data.SqlClient.SqlInternalConnectionTds.LoginNoFailover(ServerInfo serverInfo, String newPassword, SecureString newSecurePassword, Boolean redirectedUserInstance, SqlConnectionString connectionOptions, SqlCredential credential, TimeoutTimer timeout) at Microsoft.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(TimeoutTimer timeout, SqlConnectionString connectionOptions, SqlCredential credential, String newPassword, SecureString newSecurePassword, Boolean redirectedUserInstance) at Microsoft.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity identity, SqlConnectionString connectionOptions, SqlCredential credential, Object providerInfo, String newPassword, SecureString newSecurePassword, Boolean redirectedUserInstance, SqlConnectionString userConnectionOptions, SessionData reconnectSessionData, Boolean applyTransientFaultHandling, String accessToken, DbConnectionPool pool) at Microsoft.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions options, DbConnectionPoolKey poolKey, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningConnection, DbConnectionOptions userOptions) at Microsoft.Data.ProviderBase.DbConnectionFactory.CreateNonPooledConnection(DbConnection owningConnection, DbConnectionPoolGroup poolGroup, DbConnectionOptions userOptions) at Microsoft.Data.ProviderBase.DbConnectionFactory.<>c__DisplayClass47_0.<CreateReplaceConnectionContinuation>b__0(Task1 _) at System.Threading.Tasks.ContinuationResultTaskFromResultTask`2.InnerInvoke() at System.Threading.Tasks.Task.<>c.<.cctor>b__274_0(Object obj) at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state) — End of stack trace from previous location where exception was thrown — at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state) at System.Threading.Tasks.Task.ExecuteWithThreadLocal(Task& currentTaskSlot, Thread threadPoolThread) — End of stack trace from previous location where exception was thrown — at Microsoft.SqlTools.ServiceLayer.Connection.ReliableConnection.ReliableSqlConnection.<>c__DisplayClass30_0.<<OpenAsync>b__0>d.MoveNext() in D:\a\1\s\src\Microsoft.SqlTools.ManagedBatchParser\ReliableConnection\ReliableSqlConnection.cs:line 314 — End of stack trace from previous location where exception was thrown — at Microsoft.SqlTools.ServiceLayer.Connection.ConnectionService.TryOpenConnection(ConnectionInfo connectionInfo, ConnectParams connectionParams) in D:\a\1\s\src\Microsoft.SqlTools.ServiceLayer\Connection\ConnectionService.cs:line 550 ClientConnectionId:00000000-0000-0000-0000-000000000000

Here is the about screen: Version: 1.26.0 Commit: 995095f696fd9800e7e621d34daa895d57989ccd Date: 2021-02-19T03:24:52.069Z VS Code: 1.48.0 Electron: 9.4.3 Chrome: 83.0.4103.122 Node.js: 12.14.1 V8: 8.3.110.13-electron.0 OS: Darwin x64 19.6.0

Azure Data Studio version: azuredatastudio 1.26.0 (995095f696fd9800e7e621d34daa895d57989ccd, 2021-02-19T03:24:52.069Z) OS version: Darwin x64 19.6.0

System Info
Item Value
CPUs Intel® Core™ i5-8257U CPU @ 1.40GHz (8 x 1400)
GPU Status 2d_canvas: enabled
flash_3d: enabled
flash_stage3d: enabled
flash_stage3d_baseline: enabled
gpu_compositing: enabled
metal: disabled_off
multiple_raster_threads: enabled_on
oop_rasterization: enabled
opengl: enabled_on
protected_video_decode: unavailable_off
rasterization: enabled
skia_renderer: disabled_off_ok
video_decode: enabled
webgl: enabled
webgl2: enabled
Load (avg) 2, 6, 6
Memory (System) 8.00GB (0.13GB free)
Process Argv
Screen Reader no
VM 0%
Extensions (8)
Extension Author (truncated) Version
admin-pack Mic 0.0.2
admin-tool-ext-win Mic 0.0.2
agent Mic 0.48.0
dacpac Mic 1.6.0
import Mic 1.2.0
profiler Mic 0.11.0
server-report Mic 0.2.3
whoisactive Mic 0.1.4

About this issue

  • Original URL
  • State: closed
  • Created 3 years ago
  • Comments: 43 (20 by maintainers)

Most upvoted comments

@Code-DJ thanks for the update! I’m not sure the exact plans for trying the driver update again at the moment. The last two releases required hotfixing a driver rollback, so we may wait a little to try to avoid pulling in additional regressions next month. I believe there are some fixes for AlwaysEncrypted Secure Enclaves we’re trying to pickup with the driver update.

Update 1.26.1 is available that rolls back the SQL Client driver. Please let us know if there are still connectivity issues with the latest build.

We’ll be releasing a hotfix to roll back the driver change to unblock folks hitting this with ADS.

But for anyone running into this issue it would be helpful if you could go over to https://github.com/dotnet/SqlClient/issues/926 and comment there to try and track down this issue so that we’re able to update to the new driver version in the future without breaking everyone again 😄

It is - we were using the latest 2.1.1 release which contains that fix.

https://github.com/dotnet/SqlClient/releases/tag/v2.1.1

@kburtram I have verified the macOS zip file. It works fine.

BTW, on Windows I don’t have any issues with 1.26 Stable build, it connects fine using Windows Authentication.

@cssuh

kinit does not throw any errors. klist shows the following output:

Credentials cache: API:983E4737-ED75-4D12-8323-A20D9CAEE53C
        Principal: username@DOMAIN.COM

  Issued                Expires               Principal
Feb 22 16:14:26 2021  Feb 23 02:14:26 2021  krbtgt/DOMAIN.COM@DOMAIN.COM

@kburtram Yes, I am using a Mac. I am using On-Prem SQL Servers. kinit works without issue as I can authenticate with other services. I have no issue connecting to the same sql servers using python, pyodbc + latest version of Microsoft ODBC drivers (which also authenticate using kerberos). Only Azure Data Studio is having issues.