We recently migrated our 4 SQL DB Servers to v12 of the SQL DB. All seems to work just fine but ever since the migration (5/21) we have been seeing a new error quite regularly (4 or 5 times a day). The error is "26078 Client disconnected during login". We are using the Entity Framework retry logic to handle transient errors, but this error code is not considered transient and retriable by EF, even though it "feels" like it might be.

Can anyone shed any light on this error? It really seems highly correlated to the v12 (SQL 2014) migration we did. I had never seen this error before then.

Here is a stack trace of the error (excluding our code):

 ---> System.Data.Entity.Core.EntityCommandExecutionException: An error occurred while executing the command definition. See the inner exception for details. ---> System.Data.SqlClient.SqlException: Client disconnected during login
A severe error occurred on the current command.  The results, if any, should be discarded.
   at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)
   at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)
   at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose)
   at System.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj, Boolean& dataReady)
   at System.Data.SqlClient.SqlDataReader.TryConsumeMetaData()
   at System.Data.SqlClient.SqlDataReader.get_MetaData()
   at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString)
   at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async, Int32 timeout, Task& task, Boolean asyncWrite, SqlDataReader ds)
   at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, TaskCompletionSource`1 completion, Int32 timeout, Task& task, Boolean asyncWrite)
   at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method)
   at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior behavior, String method)
   at System.Data.SqlClient.SqlCommand.ExecuteDbDataReader(CommandBehavior behavior)
   at System.Data.Common.DbCommand.ExecuteReader(CommandBehavior behavior)
   at System.Data.Entity.Infrastructure.Interception.DbCommandDispatcher.<Reader>b__c(DbCommand t, DbCommandInterceptionContext`1 c)
   at System.Data.Entity.Infrastructure.Interception.InternalDispatcher`1.Dispatch[TTarget,TInterceptionContext,TResult](TTarget target, Func`3 operation, TInterceptionContext interceptionContext, Action`3 executing, Action`3 executed)
   at System.Data.Entity.Infrastructure.Interception.DbCommandDispatcher.Reader(DbCommand command, DbCommandInterceptionContext interceptionContext)
   at System.Data.Entity.Internal.InterceptableDbCommand.ExecuteDbDataReader(CommandBehavior behavior)
   at System.Data.Common.DbCommand.ExecuteReader(CommandBehavior behavior)
   at System.Data.Entity.Core.EntityClient.Internal.EntityCommandDefinition.ExecuteStoreCommands(EntityCommand entityCommand, CommandBehavior behavior)
   --- End of inner exception stack trace ---
   at System.Data.Entity.Core.EntityClient.Internal.EntityCommandDefinition.ExecuteStoreCommands(EntityCommand entityCommand, CommandBehavior behavior)
   at System.Data.Entity.Core.Objects.Internal.ObjectQueryExecutionPlan.Execute[TResultType](ObjectContext context, ObjectParameterCollection parameterValues)
   at System.Data.Entity.Core.Objects.ObjectQuery`1.<>c__DisplayClass7.<GetResults>b__6()
   at System.Data.Entity.Core.Objects.ObjectContext.ExecuteInTransaction[T](Func`1 func, IDbExecutionStrategy executionStrategy, Boolean startLocalTransaction, Boolean releaseConnectionOnSuccess)
   at System.Data.Entity.Core.Objects.ObjectQuery`1.<>c__DisplayClass7.<GetResults>b__5()
   at System.Data.Entity.SqlServer.DefaultSqlExecutionStrategy.Execute[TResult](Func`1 operation)
   at System.Data.Entity.Core.Objects.ObjectQuery`1.GetResults(Nullable`1 forMergeOption)
   at System.Data.Entity.Core.Objects.ObjectQuery`1.<System.Collections.Generic.IEnumerable<T>.GetEnumerator>b__0()
   at System.Data.Entity.Internal.LazyEnumerator`1.MoveNext()
   at System.Collections.Generic.List`1..ctor(IEnumerable`1 collection)
   at System.Linq.Enumerable.ToList[TSource](IEnumerable`1 source)

Hi,

Apologies for the inconvenience.

Is your Database hosted in West US?

If so, we have a Partial Service Interruption going on for SQL database.

[5/29/2015 12:05:20 AM PDT]  - Starting at 29 MAY, 2015 04:00 UTC customers using V12 SQL Database in West US will experience failures when attempting to perform CRUD operations (create, rename, update or delete). Current SQL runtime operations are not impacted by this issue. We have identified a potential root cause, and are working to restore service. The next update will be provided in 60 minutes.

Regards,

Mekh. 

No or primary database is in US North Central, though we have a replica in US West. We've been seeing this error consistently since migration last Thursday (a week ago).

Any other thoughts?

We are getting a lot of "Client disconnected during login" on several databases in EU West today.

It started 2315UTC yesterday and it is still happening, so something is obviously wrong, but azure service dashboard has nothing.

• Edited by Eivind Tjore Tuesday, June 16, 2015 7:49 AM

We are getting a lot of "Client disconnected during login" on several databases in EU West today.

It started 2315UTC yesterday and it is still happening, so something is obviously wrong, but azure service dashboard has nothing.

• Edited by Eivind Tjore Tuesday, June 16, 2015 7:49 AM

We are getting a lot of "Client disconnected during login" on several databases in EU West today.

It started 2315UTC yesterday and it is still happening, so something is obviously wrong, but azure service dashboard has nothing.

• Edited by Eivind Tjore Tuesday, June 16, 2015 7:49 AM

We are getting a lot of "Client disconnected during login" on several databases in EU West today.

It started 2315UTC yesterday and it is still happening, so something is obviously wrong, but azure service dashboard has nothing.

• Edited by Eivind Tjore Tuesday, June 16, 2015 7:49 AM

We are getting a lot of "Client disconnected during login" on several databases in EU West today.

It started 2315UTC yesterday and it is still happening, so something is obviously wrong, but azure service dashboard has nothing.

• Edited by Eivind Tjore Tuesday, June 16, 2015 7:49 AM

We are getting a lot of "Client disconnected during login" on several databases in EU West today.

It started 2315UTC yesterday and it is still happening, so something is obviously wrong, but azure service dashboard has nothing.

• Edited by Eivind Tjore Tuesday, June 16, 2015 7:49 AM

We are getting a lot of "Client disconnected during login" on several databases in EU West today.

It started 2315UTC yesterday and it is still happening, so something is obviously wrong, but azure service dashboard has nothing.

• Edited by Eivind Tjore Tuesday, June 16, 2015 7:49 AM

We are getting a lot of "Client disconnected during login" on several databases in EU West today.

It started 2315UTC yesterday and it is still happening, so something is obviously wrong, but azure service dashboard has nothing.

• Edited by Eivind Tjore Tuesday, June 16, 2015 7:49 AM

We have not resolved it but have a mitigation in place. It is a transient error so we've added the error code to our list of retriable errors and redeployed our systems. All is well now. We're logging the event but retrying the database operation and so far it succeeds on the first retry every time.

The Azure SQL DB team is aware of the issue and working on a fix, but I have no idea when that will come. If you all are not content with retrying the error I would suggest you submit a support ticket so that Microsoft can gauge how often it is being seen and how bothered customers are by it.

• Proposed as answer by Silvia Doomra [MSFT]Microsoft employee Wednesday, June 17, 2015 6:02 AM

We have not resolved it but have a mitigation in place. It is a transient error so we've added the error code to our list of retriable errors and redeployed our systems. All is well now. We're logging the event but retrying the database operation and so far it succeeds on the first retry every time.

The Azure SQL DB team is aware of the issue and working on a fix, but I have no idea when that will come. If you all are not content with retrying the error I would suggest you submit a support ticket so that Microsoft can gauge how often it is being seen and how bothered customers are by it.

• Proposed as answer by Silvia Doomra [MSFT]Microsoft employee Wednesday, June 17, 2015 6:02 AM

We have not resolved it but have a mitigation in place. It is a transient error so we've added the error code to our list of retriable errors and redeployed our systems. All is well now. We're logging the event but retrying the database operation and so far it succeeds on the first retry every time.

The Azure SQL DB team is aware of the issue and working on a fix, but I have no idea when that will come. If you all are not content with retrying the error I would suggest you submit a support ticket so that Microsoft can gauge how often it is being seen and how bothered customers are by it.

• Proposed as answer by Silvia Doomra [MSFT]Microsoft employee Wednesday, June 17, 2015 6:02 AM

We have not resolved it but have a mitigation in place. It is a transient error so we've added the error code to our list of retriable errors and redeployed our systems. All is well now. We're logging the event but retrying the database operation and so far it succeeds on the first retry every time.

The Azure SQL DB team is aware of the issue and working on a fix, but I have no idea when that will come. If you all are not content with retrying the error I would suggest you submit a support ticket so that Microsoft can gauge how often it is being seen and how bothered customers are by it.

• Proposed as answer by Silvia Doomra [MSFT]Microsoft employee Wednesday, June 17, 2015 6:02 AM
• Marked as answer by Casey KarstMicrosoft employee, Moderator 12 hours 10 minutes ago

We have not resolved it but have a mitigation in place. It is a transient error so we've added the error code to our list of retriable errors and redeployed our systems. All is well now. We're logging the event but retrying the database operation and so far it succeeds on the first retry every time.

The Azure SQL DB team is aware of the issue and working on a fix, but I have no idea when that will come. If you all are not content with retrying the error I would suggest you submit a support ticket so that Microsoft can gauge how often it is being seen and how bothered customers are by it.

• Proposed as answer by Silvia Doomra [MSFT]Microsoft employee Wednesday, June 17, 2015 6:02 AM
• Marked as answer by Casey KarstMicrosoft employee, Moderator Monday, June 22, 2015 6:57 PM

We have not resolved it but have a mitigation in place. It is a transient error so we've added the error code to our list of retriable errors and redeployed our systems. All is well now. We're logging the event but retrying the database operation and so far it succeeds on the first retry every time.

The Azure SQL DB team is aware of the issue and working on a fix, but I have no idea when that will come. If you all are not content with retrying the error I would suggest you submit a support ticket so that Microsoft can gauge how often it is being seen and how bothered customers are by it.

• Proposed as answer by Silvia Doomra [MSFT]Microsoft employee Wednesday, June 17, 2015 6:02 AM
• Marked as answer by Casey KarstMicrosoft employee, Moderator Monday, June 22, 2015 6:57 PM

We have not resolved it but have a mitigation in place. It is a transient error so we've added the error code to our list of retriable errors and redeployed our systems. All is well now. We're logging the event but retrying the database operation and so far it succeeds on the first retry every time.

The Azure SQL DB team is aware of the issue and working on a fix, but I have no idea when that will come. If you all are not content with retrying the error I would suggest you submit a support ticket so that Microsoft can gauge how often it is being seen and how bothered customers are by it.

• Proposed as answer by Silvia Doomra [MSFT]Microsoft employee Wednesday, June 17, 2015 6:02 AM
• Marked as answer by Casey KarstMicrosoft employee, Moderator Monday, June 22, 2015 6:57 PM

We have not resolved it but have a mitigation in place. It is a transient error so we've added the error code to our list of retriable errors and redeployed our systems. All is well now. We're logging the event but retrying the database operation and so far it succeeds on the first retry every time.

The Azure SQL DB team is aware of the issue and working on a fix, but I have no idea when that will come. If you all are not content with retrying the error I would suggest you submit a support ticket so that Microsoft can gauge how often it is being seen and how bothered customers are by it.

• Proposed as answer by Silvia Doomra [MSFT]Microsoft employee Wednesday, June 17, 2015 6:02 AM
• Marked as answer by Casey KarstMicrosoft employee, Moderator Monday, June 22, 2015 6:57 PM

We have not resolved it but have a mitigation in place. It is a transient error so we've added the error code to our list of retriable errors and redeployed our systems. All is well now. We're logging the event but retrying the database operation and so far it succeeds on the first retry every time.

The Azure SQL DB team is aware of the issue and working on a fix, but I have no idea when that will come. If you all are not content with retrying the error I would suggest you submit a support ticket so that Microsoft can gauge how often it is being seen and how bothered customers are by it.

• Proposed as answer by Silvia Doomra [MSFT]Microsoft employee Wednesday, June 17, 2015 6:02 AM
• Marked as answer by Casey KarstMicrosoft employee, Moderator Monday, June 22, 2015 6:57 PM

We have not resolved it but have a mitigation in place. It is a transient error so we've added the error code to our list of retriable errors and redeployed our systems. All is well now. We're logging the event but retrying the database operation and so far it succeeds on the first retry every time.

The Azure SQL DB team is aware of the issue and working on a fix, but I have no idea when that will come. If you all are not content with retrying the error I would suggest you submit a support ticket so that Microsoft can gauge how often it is being seen and how bothered customers are by it.

• Proposed as answer by Silvia Doomra [MSFT]Microsoft employee Wednesday, June 17, 2015 6:02 AM
• Marked as answer by Casey KarstMicrosoft employee, Moderator Monday, June 22, 2015 6:57 PM

We have not resolved it but have a mitigation in place. It is a transient error so we've added the error code to our list of retriable errors and redeployed our systems. All is well now. We're logging the event but retrying the database operation and so far it succeeds on the first retry every time.

The Azure SQL DB team is aware of the issue and working on a fix, but I have no idea when that will come. If you all are not content with retrying the error I would suggest you submit a support ticket so that Microsoft can gauge how often it is being seen and how bothered customers are by it.

• Proposed as answer by Silvia Doomra [MSFT]Microsoft employee Wednesday, June 17, 2015 6:02 AM
• Marked as answer by Casey KarstMicrosoft employee, Moderator Monday, June 22, 2015 6:57 PM

It seems to be resolved today on Japan East.

• Proposed as answer by Silvia Doomra [MSFT]Microsoft employee Wednesday, June 17, 2015 6:02 AM

It seems to be resolved today on Japan East.

• Proposed as answer by Silvia Doomra [MSFT]Microsoft employee Wednesday, June 17, 2015 6:02 AM

It seems to be resolved today on Japan East.

• Proposed as answer by Silvia Doomra [MSFT]Microsoft employee Wednesday, June 17, 2015 6:02 AM

It seems to be resolved today on Japan East.

• Proposed as answer by Silvia Doomra [MSFT]Microsoft employee Wednesday, June 17, 2015 6:02 AM

It seems to be resolved today on Japan East.

• Proposed as answer by Silvia Doomra [MSFT]Microsoft employee Wednesday, June 17, 2015 6:02 AM

It seems to be resolved today on Japan East.

• Proposed as answer by Silvia Doomra [MSFT]Microsoft employee Wednesday, June 17, 2015 6:02 AM

It seems to be resolved today on Japan East.

• Proposed as answer by Silvia Doomra [MSFT]Microsoft employee Wednesday, June 17, 2015 6:02 AM

It seems to be resolved today on Japan East.

• Proposed as answer by Silvia Doomra [MSFT]Microsoft employee Wednesday, June 17, 2015 6:02 AM

Did you get this resolved?

I am experiencing the exact same problem on a EU West database today. There is nothing on the service dashboard this time.

/ Johan

We are getting a lot of "Client disconnected during login" on several databases in EU West today.

It started 2315UTC yesterday and it is still happening, so something is obviously wrong, but azure service dashboard has nothing.

• Edited by Eivind Tjore 23 hours 22 minutes ago

We are getting a lot of "Client disconnected during login" on several databases in EU West today.

It started 2315UTC yesterday and it is still happening, so something is obviously wrong, but azure service dashboard has nothing.

• Edited by Eivind Tjore 23 hours 15 minutes ago

I'm facing to the same problem on Japan East (V12).
Audit log shows
"Err 26078, Level 14, State 1, Server SQL Azure, Line 1 Client disconnected during login"

Metrics shows 35% of connection failed.
I can't find the detail of error code 26078.

We also see these issues in some of our West EU V12 databases. Right now it looks like only our databases using multiple active result sets in their connection strings are affected, but it may not be related.

• Edited by mikkark Wednesday, June 17, 2015 6:16 AM

• Edited by mikkark Wednesday, June 17, 2015 6:16 AM

• Edited by mikkark Wednesday, June 17, 2015 6:16 AM

• Edited by mikkark Wednesday, June 17, 2015 6:16 AM

• Edited by mikkark Wednesday, June 17, 2015 6:16 AM

• Edited by mikkark Wednesday, June 17, 2015 6:16 AM

• Edited by mikkark Wednesday, June 17, 2015 6:16 AM

• Edited by mikkark Wednesday, June 17, 2015 6:16 AM

Hi all, 

im having the same problem in EU West.

We have not resolved it but have a mitigation in place. It is a transient error so we've added the error code to our list of retriable errors and redeployed our systems. All is well now. We're logging the event but retrying the database operation and so far it succeeds on the first retry every time.

The Azure SQL DB team is aware of the issue and working on a fix, but I have no idea when that will come. If you all are not content with retrying the error I would suggest you submit a support ticket so that Microsoft can gauge how often it is being seen and how bothered customers are by it.

• Proposed as answer by Silvia Doomra [MSFT]Microsoft employee 1 hour 9 minutes ago

We have not resolved it but have a mitigation in place. It is a transient error so we've added the error code to our list of retriable errors and redeployed our systems. All is well now. We're logging the event but retrying the database operation and so far it succeeds on the first retry every time.

The Azure SQL DB team is aware of the issue and working on a fix, but I have no idea when that will come. If you all are not content with retrying the error I would suggest you submit a support ticket so that Microsoft can gauge how often it is being seen and how bothered customers are by it.

• Proposed as answer by Silvia Doomra [MSFT]Microsoft employee 1 hour 3 minutes ago

It seems to be resolved today on Japan East.

• Proposed as answer by Silvia Doomra [MSFT]Microsoft employee 1 hour 9 minutes ago

It seems to be resolved today on Japan East.

• Proposed as answer by Silvia Doomra [MSFT]Microsoft employee 1 hour 2 minutes ago

• Edited by mikkark 55 minutes ago

• Edited by mikkark 48 minutes ago