Could not open connection to SQL Server Error:53 the network path was not found


i am trying to migrate database from sql server 2008 sp1 and 2012, in management studio, i am trying to connect to sql azure db, for this, Connect to database engine, enter my server name, login and pwd, sql server authentication used.
details: ***.database.windows.net, sql server authentication, loginid@, pwd.
i got the error.

TITLE: Connect to Server

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


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) (Microsoft SQL Server, Error: 53)
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft%20SQL%20Server&EvtSrc=MSSQLServer&EvtID=53&LinkId=20476
The network path was not found
this is one problem, but if i do not attach sql azure db in my local management studio , i directly started process from tool, in end step , after created script , finl step also getting like similar error,
please help me in this. tried with 2008 and 2012 also in win 2008 r2 server. firewall stopped also. added 1433 outbound port also.


ghuey wrote Sep 12, 2012 at 3:22 AM


Just to clarify, you are getting this error using SQL Server Management Studio when trying to connect to SQL Azure? I have seen this kind of problem before and it is usually on a company corporate network. I had this problem on my machines and found that when I took my work machine home and ran on my home network, I had no problem. If I would run when connected to my corporate network, then I would see the issue you described above. Anyway, I just want to verify that the issue you are seeing also occurs in SQL Server Management Studio and then I was curious if you could try this on a public internet and see how it works.


chinnarao wrote Sep 14, 2012 at 9:34 PM

you are right, now i am able to connect to sql azure db every where (local sql management stuido and from migration tool).

Thank you very much for your time and help, mainly for 2hour response george.

we are golden, this is best tool in my list from several.

wrote Feb 21, 2013 at 11:59 PM