CODEWITHSUNDEEP
azureazure-sql-database
Prashanth Subramanian
Prashanth Subramanian

Reputation: 653

SQLAzure database server - named pipes provider, error: 40 - the network path was not found

enter image description here

We access our database that is in SQL Azure, and every so often we hit this error while trying to connect. We connect from a corporate network, using SSMS or API.

The weird part is how it always successfully and instantly connects on retrying. We retry just 1 second after and it works.

We saw that the DTU Usage % was high and scaled our server up, but that did not help. We have employed a SqlAzureRetry policy while accessing the database from our API, which seems to be helping in mitigating the issue - but the root cause is still not identified.

Has anyone employed a configuration or strategy or faced a similar issue? (the underlying provider failed to open / network path not found).

Thanks!

Upvotes: 4

Views: 2320

Answers (1)

Prashanth Subramanian
Prashanth Subramanian

Reputation: 653

The solution was to change the format of the server name to use TCP:

tcp:servername.database.windows.net,1433;

Also, if you're connecting from code, you should change to the above format in your connection string.

Upvotes: 5

Related Questions