About an hour ago we lost access to our databases. That is, no access from SSMS, from the SQL Azure Management Portal (Test Connectivity) and our app is throwing errors.
It's a bummer that the silverlight portal doesn't support copy and paste - so I won't retype that - but it says connectivity was established by there was an error in the login process. Our app reports: SqlException:The instance of SQL Server you attempted
to connect to does not support encryption. SSMS reporsts (long text below:)
Note the application is running under a different login than the admin accounts that error in SSMS and the portal.
I logged a support request and I'm told someone will contact me within four hours. Our app isn't live (thanks be to someone), but...
We did a deployment on Sunday but all has been well since then, though we're going to check the logs and see if this has occurred previously and been transient.
TITLE: Connect to Server
Cannot connect to cn1ovy8299.database.windows.net.
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)
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=64&LinkId=20476
The SQL Azure team received a small number (think single digits) of customers reporting that their databases were unaccessable last night. We are actively performing a root cause analysis but it appears that all databases are currently up and healthy.
Five days later and we still see issues with our SQL Azure databases in North Central US - mainly that all of a sudden we can't connect through SSMS and we get errors from our applications. This comes and goes - it works, all of sudden it stops working,
then it works again, etc... This does not happen on all of our databases - only some.
has now updated most of the SQL Servers with something like -
SQL Azure Investigation
3:04 AM UTC We are currently investigating a potential problem impacting SQL Azure Database
7:31 PM UTC We continue to investigate a potential problem impacting SQL Azure Database
See, you should have listened to us.
You shouldn't mark your answer as the answer - that's just wrong and may byte you later. ;-)
count us among the single digits. and this is today as well, the 7th. site is dead, (due to sql azure) struggling to figure out how to get it back live. as of right now, can't communicate with my sql azure databases, at all.
The single digits were from earlier this week. From what I can gather this outage is quite significant. After contacting support I've been told that it's been looked into as a high priority. I suspect that is understating the situation
with 5 data centres affected.
We have identified the issue, although small and as I stated earlier affecting only a small number of users, it is still an issue. We are implementing the fix as we speak and expect the fix to be in place in the next few hours. Microsoft is dedicated to
providing people with a trusted computing experience and we apologize for any inconvenience this causes our customers. Our support staff is available 24x7 should you experience any issues and we treat every issue, no matter how small it is, with the highest
If anyone is experiencing problems in a data center, is it possible to do a snapshot-replication to another data center, and then run from that database untill the issue is resolved? (Of course this assumes that the DB is available to replicate, and latency
may be an issue). This may be a way to stay up and running if there are issues.
http://www.CloudCasts.net - Community Webcasts Powered by Azure
That would be an awesome idea if you could do a snapshot from one data centre to another. Unfortunately at the moment SQL Azure only supports snapshots (or database copy which is what the command is called) within a data centre.