Error when connecting to Azure SQL Database from Client

Laurence Mee 156

This has just started happening, it was fine up until about an hour ago. Nothing was changed. Then suddenly I started getting the following error from SSMS:

===================================

Cannot connect to *****.database.windows.net.

===================================

A connection was successfully established with the server, but then an error occurred during the login process. (provider: TCP Provider, error: 0 - An existing connection was forcibly closed by the remote host.) (.Net SqlClient Data Provider)

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft%20SQL%20Server&EvtSrc=MSSQLServer&EvtID=10054&LinkId=20476

Server Name: *****.database.windows.net
Error Number: 10054
Severity: 20
State: 0

Program Location:

at System.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity identity, SqlConnectionString connectionOptions, SqlCredential credential, Object providerInfo, String newPassword, SecureString newSecurePassword, Boolean redirectedUserInstance, SqlConnectionString userConnectionOptions, SessionData reconnectSessionData, DbConnectionPool pool, String accessToken, Boolean applyTransientFaultHandling, SqlAuthenticationProviderManager sqlAuthProviderManager)
at System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions options, DbConnectionPoolKey poolKey, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningConnection, DbConnectionOptions userOptions)
at System.Data.ProviderBase.DbConnectionFactory.CreateNonPooledConnection(DbConnection owningConnection, DbConnectionPoolGroup poolGroup, DbConnectionOptions userOptions)
at System.Data.ProviderBase.DbConnectionFactory.TryGetConnection(DbConnection owningConnection, TaskCompletionSource1 retry, DbConnectionOptions userOptions, DbConnectionInternal oldConnection, DbConnectionInternal& connection) at System.Data.ProviderBase.DbConnectionInternal.TryOpenConnectionInternal(DbConnection outerConnection, DbConnectionFactory connectionFactory, TaskCompletionSource1 retry, DbConnectionOptions userOptions)
at System.Data.ProviderBase.DbConnectionClosed.TryOpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory, TaskCompletionSource1 retry, DbConnectionOptions userOptions) at System.Data.SqlClient.SqlConnection.TryOpenInner(TaskCompletionSource1 retry)
at System.Data.SqlClient.SqlConnection.TryOpen(TaskCompletionSource`1 retry)
at System.Data.SqlClient.SqlConnection.Open()
at Microsoft.SqlServer.Management.SqlStudio.Explorer.ObjectExplorerService.ValidateConnection(UIConnectionInfo ci, IServerType server)
at Microsoft.SqlServer.Management.UI.ConnectionDlg.Connector.ConnectionThreadUser()

===================================

An existing connection was forcibly closed by the remote host

Laurence Mee 156 Reputation points

2020-06-06T01:33:02.203+00:00

This is on all Azure SQL Databases I've got on several subscriptions, and the Client IP being allowed through the firewall is still correct.
Ronen Ariely 15,096 Reputation points

2020-06-06T01:36:19.25+00:00

Hi,

Are you using azure database serverless?
Laurence Mee 156 Reputation points

2020-06-06T01:38:02.627+00:00

No, they all have a SQL Server instance.
Laurence Mee 156 Reputation points

2020-06-06T01:49:31.143+00:00

I'm in the UK connecting to Azure SQL Databases (on SQL Servers) in West Europe.
Laurence Mee 156 Reputation points

2020-06-06T01:53:19.26+00:00

It seems that the databases can be connected to by Azure Apps, just not external clients through the firewall.
Tolga Pehlivan 1 Reputation point

2020-06-06T01:59:29.667+00:00

I am having the same problem ( on 3 different Azure SQL Database ). In the last 30 minutes.

I get the same error locally; but Azure Web app connection is working.
Laurence Mee 156 Reputation points

2020-06-06T02:02:45.053+00:00

Looks like an Azure issue. Lets hope someone reports it and it gets fixed soon.

Pedro Mendes 1

True.
Just ran the "Azure SQL Connectivity Checker v1.4" ps script and all is fine until it reads:

Testing connecting to master database:
 Error:  10054 State: 0 : A connection was successfully established with the server, but then an error occurred during the login process. (provider: TCP Provider, error: 0 - An existing connection was forcibly closed by the remote host.)

Zone: West Europe

Laurence Mee 156 Reputation points

2020-06-06T02:17:53.027+00:00

Yes, I get the same.
Ronen Ariely 15,096 Reputation points

2020-06-06T02:33:36.38+00:00

Seems like issue in "West Europe". I also have issue with West Europe. I am waiting to see if other regions are reported as well.

Drazen Mrvos 1

We have te same problem on regular (DTU-based) database in West Europe:

 ===================================
 
 A connection was successfully established with the server, but then an error occurred during the login process. (provider: TCP Provider, error: 0 - An existing connection was forcibly closed by the remote host.) (.Net SqlClient Data Provider)
 
 ------------------------------
 Server Name: XXXXXXXXXX.database.windows.net
 Error Number: 10054
 Severity: 20
 State: 0

Rien van Leeuwen 1 Reputation point

2020-06-06T07:01:43.583+00:00

Can confirm the same problem on services in West_europe
M@X1 1 Reputation point

2020-06-06T07:21:43.86+00:00

I have the same problem on regular (DTU-based) database in West Europe. I confirmed that there is probably an issue with the service at this time.
Richard Bell 1 Reputation point

2020-06-06T07:31:13.07+00:00

I have the same problem on Azure SQL Server database in West Europe.

Connection works ok for some applications, but not SSMS, as at 9:41 6/6/2020 Western European time
Karl Huijbrechts 1 Reputation point

2020-06-06T07:48:24.033+00:00

I have the same problem on Azure SQL Server database in West Europe. 3 databases , 4/5 logins fail

problem still going on now
Fernando Mattivi 1 Reputation point

2020-06-06T07:55:15.32+00:00

I still have same issue on Azure SQL in West Europe. I have 3 server instances and all with that problem. Not resolved, as at 9:55 6/6/2020 Western European time
Abderrahman Ezzamri 1 Reputation point

2020-06-06T07:55:49.493+00:00

We are facing the same Issue with Sql azure in West Europe. Something is wrong on their service. A connection was successfully established with the server, but then an error occurred during the login process
Joe81 1 Reputation point

2020-06-06T08:01:13.227+00:00

Same here. Problem still NOT resolved 10:00 6/6/2020 Western European time. Azure SQL Server and database in West Europe.
dsch 1 Reputation point

2020-06-06T08:09:30.3+00:00

We are also having the same severe issues with a DTU database in the West Europe region. Any updates??
Sebastian Borchert 1 Reputation point

2020-06-06T08:16:57.027+00:00

Same Problem here. we can connect via Azure Portal but not via SSMS or SSIS. Azure SQL Server and DBs in West Europe.
Gareth Williams 1 Reputation point

2020-06-06T08:19:45.733+00:00

I am also having the same issue.
Thomas Fraefel 15 Reputation points

2020-06-06T08:25:21.14+00:00

Having the exact same problem here :( On datacenter West Europe...
SH 1 Reputation point

2020-06-06T08:25:48.393+00:00

Same here, there was a health issue around 2am that was supposedly resolved on our server and since then the 10054 error
Bert Kooij 16 Reputation points

2020-06-06T08:29:20.67+00:00

We have the same problem for West Europe SQL database.

There is a similar question asked on StackOverflow. I have tested the answer there but it doesn't seem to make any difference:
https://stackoverflow.com/questions/62226331/08s01-odbc-driver-17-for-sql-server-tcp-provider-error-code-0x2746-10054

Nothing has changed on our side of the application, so my guess for now is some kind of issue or change on the Azure side.
Thomas Fraefel 15 Reputation points

2020-06-06T08:43:39.893+00:00

Hmmmm, changing default settings to no connectivity over night - that's a really bad choice...

Following the stackoverflow answer, made me able to access my databases again (y)
Thomas Fraefel 15 Reputation points

2020-06-06T08:48:07.957+00:00

Oh, have to add that I added a sql restart by temporarily reconfigure the database to another level and back again.
Andrew Cumming 1 Reputation point

2020-06-06T09:01:56.293+00:00

I cannot connect to West-Europe DBs using SSMS. Looks like the same issue.
Thomas Fraefel 15 Reputation points

2020-06-06T09:11:21.23+00:00

And looks like I now have to force the encryption parameter on the SQL connection to make it work.
Rudy van Schubert 1 Reputation point

2020-06-06T09:12:42.593+00:00

We are experiencing the same problem stating about 03:00 in the Netherlands
Microsoft.Data.SqlClient.SqlException (0x80131904): A connection was successfully established with the server, but then an error occurred during the login process.
Bartek Woznica 1 Reputation point

2020-06-06T09:21:44.15+00:00

ny other idea how to connect to sql database and run some script..? client is escalating the issue...
Tomasz Pawełczyk 1 Reputation point

2020-06-06T09:25:16.087+00:00

Hi, what do you mean by 'temporarily reconfigure the database to another level'. Could you please elaborate?
Максим Айдин 1 Reputation point

2020-06-06T09:29:12.05+00:00

Same Problem. We can't connect via SSMS to Azure DB in West Europe from today.
Bert Kooij 16 Reputation points

2020-06-06T09:30:10.4+00:00

Yes, you're right, reconfiguring the amount of reserved DTU and back indeed triggered something. I am now able to connect through Management Studio. Our application is also able to connect, but it seems to be very unstable and fails around 50% of the time.
Denis Sowa 11 Reputation points

2020-06-06T09:30:20.53+00:00

For me it just started working again.
SMC 6 Reputation points

2020-06-06T09:32:00.693+00:00

New firewall settings for the SQL server in Azure portal seemed to be blocking public access. Set that to the correct setting and TLS default level.

Changed my PDO connection string to the example in Azure Portal (which includes the encryption flag, and seems to be working again now.

Edit - actually seems to fail intermittently still, can only assume now a problem Azure-side?
dsch 1 Reputation point

2020-06-06T09:37:01.597+00:00

We are still experiencing the same issue here, and our systems our down. Has any one received any official feedback yet?
dsch 1 Reputation point

2020-06-06T09:37:01.597+00:00

We are still experiencing the same issue here, and our systems our down. Has any one received any official feedback yet?
Patrick Deman 1 Reputation point

2020-06-06T09:37:13.55+00:00

Same problem here. Connectivity went down during last night.
Bert Kooij 16 Reputation points

2020-06-06T10:01:12.503+00:00

See my answer: https://learn.microsoft.com/answers/comments/32804/view.html

Go to your SQL instance (like an elastic pool) > Configuration > Increase the eDTU's and save. Wait till it's finished. Than you can decrease the instance back to the normal configuration.
Tomasz Pawełczyk 1 Reputation point

2020-06-06T10:02:47.557+00:00

Thank you! :)
Thomas Fraefel 15 Reputation points

2020-06-06T10:40:10.353+00:00

Hi,

Just changed level from S0 to S1 to S0 - this normally resets all processes and connections.

\Thomas
Thomas Fraefel 15 Reputation points

2020-06-06T10:43:19.677+00:00

Started running again on the old apps without any modification at 11:25 local time (DK)
Haven't seen any official statement on the outage yet ?
Allan Svelmøe Hansen 1 Reputation point

2020-06-06T11:38:38.46+00:00

It doesn't look like we've gotten an error message on our end in a couple of hours, but I have not seen or heard any official feedback on this issue.
Ronen Ariely 15,096 Reputation points

2020-06-06T12:22:31.763+00:00

Same here.

I post update in my blog and I just updated the status to officially still exits but seems to work well for all our servers
Armand Brunelle 491 Reputation points

2020-06-06T14:08:33.18+00:00

Yes, depending from where you are login, there is differential command panel in ''Preview Mode'' concurrently still working in parallel with actual command center, user, Admin and such. Right now, some options might not be available, will be temporally and some partially deprecated.

I can suggest you to have a different approach with your browser and simply can alternatively use two sources if one is arising a constant unwanted situation. If the problem persist specifically to this Tag number, further investigation will be required.
Ronen Ariely 15,096 Reputation points

2020-06-06T16:55:10.697+00:00

Good day @Armand Brunelle ,

It is not clear who you speak to. Please use the comment to response to someone and do not post a new answer each time you publish a message. The forum have a clear hierarchy structure to see who respond to whom. So please use it and replay to specific message and don;t post your response as an answer each time.

Thanks

p.s.

If you can clarify to which message you responded then I (or any other Moderator) can move your message to the right place in the hierarchy
Armand Brunelle 491 Reputation points

2020-06-06T17:06:11.14+00:00

Thank you sir for the detailed answer. I will do so and if anything i can do better, please send me feedback. Sorry about this.

Have a good day sir ! @Ronen Ariely
Ronen Ariely 15,096 Reputation points

2020-06-06T17:25:15.773+00:00

You are most welcome @Armand Brunelle 👍 😀
Rudy van Schubert 1 Reputation point

2020-06-08T10:22:11.68+00:00

Today we had the same problem agagin @ Monday 12:10

We are experiencing the same problem stating about 03:00 in the Netherlands Microsoft.Data.SqlClient.SqlException (0x80131904): A connection was successfully established with the server, but then an error occurred during the login process.
Navtej Singh Saini 4,216 Reputation points Microsoft Employee

2020-06-08T17:11:02.617+00:00

The underlying problem for which this issue was raised is solved. Your issue looks specific to your resources. Please raise a support ticket for the same.
Thanks
Navtej S

9 answers

Ashley Turing 1 Reputation point

2020-07-09T21:51:34.787+00:00

We are still receiving this error the database is West Europe can you please advise?
Please sign in to rate this answer.

0 comments No comments
Sign in to comment
BJN 6 Reputation points

2020-07-16T06:43:07.51+00:00

have you tried switching to the microsoft.data client (if applicable) and use the retry/timeout parameter?
https://github.com/dotnet/SqlClient/blob/master/release-notes/2.0/2.0.0.md#new-connection-string-property-synonyms
Please sign in to rate this answer.

0 comments No comments
Sign in to comment
Kumari Shivam (RBEI/PJ-HoT-BE1) 1 Reputation point

2020-10-03T15:27:43.307+00:00

Hi Team,

I am trying to connect to Azure SQL database by .net core API and getting below mentioned error . Same while connecting with SSMS 2018 as well

System.Data.SqlClient.SqlException
HResult=0x80131904
Message=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: 0 - No such host is known.)
Source=Core .Net SqlClient Data Provider
StackTrace:
at System.Data.ProviderBase.DbConnectionPool.CheckPoolBlockingPeriod(Exception e)
at System.Data.ProviderBase.DbConnectionPool.CreateObject(DbConnection owningObject, DbConnectionOptions userOptions, DbConnectionInternal oldConnection)
at System.Data.ProviderBase.DbConnectionPool.UserCreateRequest(DbConnection owningObject, DbConnectionOptions userOptions, DbConnectionInternal oldConnection)
at System.Data.ProviderBase.DbConnectionPool.TryGetConnection(DbConnection owningObject, UInt32 waitForMultipleObjectsTimeout, Boolean allowCreate, Boolean onlyOneCheckConnection, DbConnectionOptions userOptions, DbConnectionInternal& connection)
at System.Data.ProviderBase.DbConnectionPool.TryGetConnection(DbConnection owningObject, TaskCompletionSource1 retry, DbConnectionOptions userOptions, DbConnectionInternal& connection) at System.Data.ProviderBase.DbConnectionFactory.TryGetConnection(DbConnection owningConnection, TaskCompletionSource1 retry, DbConnectionOptions userOptions, DbConnectionInternal oldConnection, DbConnectionInternal& connection)
at System.Data.ProviderBase.DbConnectionInternal.TryOpenConnectionInternal(DbConnection outerConnection, DbConnectionFactory connectionFactory, TaskCompletionSource1 retry, DbConnectionOptions userOptions) at System.Data.ProviderBase.DbConnectionClosed.TryOpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory, TaskCompletionSource1 retry, DbConnectionOptions userOptions)
at System.Data.SqlClient.SqlConnection.TryOpen(TaskCompletionSource`1 retry)
at System.Data.SqlClient.SqlConnection.Open()
at RADARTool.Controllers.ProjectDetailsController.Get() in C:\Users\UHM3KOR\Desktop\RadarFiles\RADARTool\RADARTool\Controllers\ProjectDetailsController.cs:line 24
at Microsoft.Extensions.Internal.ObjectMethodExecutor.Execute(Object target, Object[] parameters)
at Microsoft.AspNetCore.Mvc.Infrastructure.ActionMethodExecutor.SyncObjectResultExecutor.Execute(IActionResultTypeMapper mapper, ObjectMethodExecutor executor, Object controller, Object[] arguments)
at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.InvokeActionMethodAsync()
at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.Next(State& next, Scope& scope, Object& state, Boolean& isCompleted)
at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.InvokeNextActionFilterAsync()

Inner Exception 1:
Win32Exception: No such host is known.
Please sign in to rate this answer.
KalyanChanumolu-MSFT 8,316 Reputation points

2020-10-19T08:10:13.997+00:00

@Kumari Shivam (RBEI/PJ-HoT-BE1) Are you still facing this issue?
Please create a new question and post the code sample for us to investigate.
Sign in to comment
Evandro Boa Semedo 366 Reputation points

2021-04-15T19:15:32.907+00:00

try this man.

https://productsupport.red-gate.com/hc/en-us/articles/360014572498
Please sign in to rate this answer.

0 comments No comments
Sign in to comment