Question
Lumios001 on Tue, 10 Jan 2012 11:30:08
Hello. I'm new to Windows Azure and I'm trying to connect to my Azure server using Management studio but I get this error when I try to connect:
"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.) (Microsoft SQL Server, Error: 10054)"
- I've created a server/DB and can connect to it using the Azure portal.
- I can connect to my server on port 1433 using telnet.
- I've added firewall rules to allow my connection through.
- I'm using SQL Server 2008 R2
Any ideas on what the problem is?
Sponsored
Replies
Vitor Faria Tomaz on Tue, 10 Jan 2012 13:55:27
Hi,
Since you are new to Azure I suggest you read this:
http://social.technet.microsoft.com/wiki/contents/articles/sql-azure-connection-management.aspx
Hope it helps
Ira Bell, Nimbo on Tue, 10 Jan 2012 16:22:24
This blog posting by the SQL Azure team would probably be more helpful for you in this case: http://blogs.msdn.com/b/sqlazure/archive/2010/03/22/9982979.aspx
- Ira Bell
-Ira Bell
Shaun Xu on Wed, 11 Jan 2012 02:17:59
Did you met this problem every time you connect to SQL Azure, or just occasionally?
SQL Azure will kill the idle connect from server side, so this would not be a surprise when connecting to SQL Azure to me.
Lumios001 on Wed, 11 Jan 2012 08:50:25
Did you met this problem every time you connect to SQL Azure, or just occasionally?
SQL Azure will kill the idle connect from server side, so this would not be a surprise when connecting to SQL Azure to me.
I get it everytime I try to connect using SSMS. I can connect perfectly fine using the Azure portal and haven't had any problems connecting that way.
I've read through the blog posts but neither seemed to help :(.
Also I get this error sometimes too:
"A connection was successfully established with the server, but then an error occurred during the login process. (provider: TCP Provider, error: 0 - The specified network name is no longer available.) (Microsoft SQL Server, Error: 64)"
Stephanie Lv on Mon, 16 Jan 2012 09:44:56
Hi Duckiah,
For this type of error, please have a look at this blog for troubleshooting: SQL Azure Connection Management.