1

I have an issue with my Azure Web App that it once in a while stops communicating with our external SQL Server. Everything was working fine until a few hours ago. It's a simple setup with an asp.net website that connects to a SQL Server located on a different location.

The website works fine when I run it from my dev environment. The Virtual IP Adress, Outbound Adresses and Alternative Outbound Adresses have all been added to the firewall on the SQL Server.

The website works for weeks at a time and then, without any changes to the Web App or the SQL Server, it just stops working..

Im using the P1V2 App Service Plan and should be more than enough for the workload for our website.

Connectionstring

<add name="DefaultConnection" connectionString="Data Source=xx.xx.xxx.xxx;Initial Catalog=xyz;User ID=xyz;MultipleActiveResultSets=True;Password=xyz;" />

Error Message

System.Data.SqlClient.SqlException: 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: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)

enter image description here

enter image description here

enter image description here

enter image description here

enter image description here

Christian
  • 111
  • 1
  • I just encountered a similar problem and am looking to Microsoft support to fix it. For us, the sites (5) have worked for years with no problems, and this morning they had all stopped connecting to two different SQL Servers on two different Azure VNETs and we can't get them back up. Have you found any way to revive them even temporarily? – Tuukka Haapaniemi Jun 25 '20 at 09:55

0 Answers0