question

sammsoft-7976 avatar image
sammsoft-7976 asked ·

Azure SQL Database Connection error since today

I receive the following error since today in the morning (yesterday all was fine, no changes):
System.Data.SqlClient.SqlException (0x80131904): 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.) ---> System.ComponentModel.Win32Exception (0x80004005): An existing connection was forcibly closed by the remote host

I saw some new firewall settings in the portal, that I have never seen before.
Deny public network access. I disabled this already (it was not set).

Can you help me?

azure-sql-database
6 comments
10 |1000 characters needed characters left characters exceeded
Toggle Comment visibility. Current Visibility: Visible to all users

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Nickels-1150 avatar image Nickels-1150 ·

I have the exact same issue... Let's hope for a quick resolve...

0 Votes 0 · ·
MX1-5145 avatar image MX1-5145 ·

I have the exact same issue...


0 Votes 0 · ·
DrJensenmann-9929 avatar image DrJensenmann-9929 ·

Also we, the same issue, no access to the databases/server anymore. Each database server is impacted.
I guess Azure updated firewall stuff and this with worst impact. My pulse is 180. Azure servises can still connect to the databases/server (at the moment), external connections are affected till now.

It seems solved, they are working on it (Azure Health Status). Our databases are available again, "at the moment".

0 Votes 0 · ·
MarkRudChristensen-2348 avatar image MarkRudChristensen-2348 ·

We are having the exact same issue. Have raised a ticket to Microsoft.


0 Votes 0 · ·
JackEvens-6739 avatar image JackEvens-6739 ·

Same issue here. Connection problems to 3 different servers/databases.
When i want to connect with management studio to my Azure database i recieve the message :
Database 'XXXX' on server 'XXXX.database.windows.net' is not currently available. Please retry the connection later. If the problem persists, contact customer support, and provide them the session tracing ID of '{1A5671E4-69E7-4896-B8B8-E4BCE1C49426}'. (Microsoft SQL Server, Error: 40613)

0 Votes 0 · ·
Show more comments

2 Answers

LaurenceMee-3146 avatar image
LaurenceMee-3146 answered ·

I raised this on here 12 hours ago too. It seems to have been resolved.
https://docs.microsoft.com/en-us/answers/questions/32697/error-when-connecting-to-azure-sql-database-from-c.html

Share
10 |1000 characters needed characters left characters exceeded
Toggle Comment visibility. Current Visibility: Visible to all users

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

pituach avatar image
pituach answered ·

Good day all,

@LaurenceMee-3146 is correct �� +5 point Laurence :-)

Let me elaborate on the topic... In short there was an issue and I wrote a posy and followed till it was solved. I updated my post every few minutes with the status until it was solve, and once it was solved I published all the information including what was the issue and how Microsoft solved it

You can check the post if you want, in this link. I will copy the main summery from there.

Summary of issue


Between 23:51 UTC on 05 June 2020 and 09:55 UTC on 06 Jun 2020, multiple customers encountered issue to connect SQL Database / SQL Data Warehouse in West Europe region.

Microsoft confirmed that some instances of a gateway service became unhealthy and were unable to process connections. They mitigated the issue by restarting the unhealthy instances of the gateway service, and validated that traffic was flowing as expected, mitigating the issue.

Share
10 |1000 characters needed characters left characters exceeded
Toggle Comment visibility. Current Visibility: Visible to all users

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.