"error: 19 - Physical connection is not used" when I change my Staging and Production deployments on Windows Azure

Every time I change my deployments between Staging and Production, I get this error:

[Wed Oct 09 18: 43: 51.9519 +00: 00 2013] [Error] [Zappiti.BaseApi] error updating records. See Internal Exception for details.

System.Data.Entity.Infrastructure.DbUpdateException: Error updating records. See Internal Exception for Details. ---> System.Data.UpdateException: An error occurred while updating records. See Internal Exception for more details. ---> System.Data.SqlClient.SqlException: transport-level error when receiving results from the server. (provider: Supplier session, error: 19 - Physical connection is not used)

in System.Data.SqlClient.SqlConnection.OnError (SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)

in System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning (TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose)

in System.Data.SqlClient.TdsParserStateObject.ReadSniError (TdsParserStateObject stateObj, error UInt32)

in System.Data.SqlClient.TdsParserStateObject.ReadSniSyncOverAsync ()

in System.Data.SqlClient.TdsParserStateObject.TryReadNetworkPacket ()

in System.Data.SqlClient.TdsParserStateObject.TryPrepareBuffer ()

in System.Data.SqlClient.TdsParserStateObject.TryReadByte (byte & value)

in System.Data.SqlClient.TdsParser.TryRun (RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj, Boolean & dataRead)

in System.Data.SqlClient.SqlCommand.FinishExecuteReader (SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString)

in System.Data.SqlClient.SqlCommand.RunExecuteReaderTds (CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async, Int32 timeout, Task & task, Boolean asyncWrite)

in System.Data.SqlClient.SqlCommand.RunExecuteReader (CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, completion TaskCompletionSource`1, Int32 timeout, Task & task, Boolean asyncWrite)

in System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery (TaskCompletionSource`1 completion, String methodName, Boolean sendToPipe, Int32 timeout, Boolean asyncWrite)

in System.Data.SqlClient.SqlCommand.ExecuteNonQuery ()

in System.Data.Mapping.Update.Internal.DynamicUpdateCommand.Execute (UpdateTranslator translator, connection EntityConnection, dictionary 2 identifierValues, List 1 generatedValues)

in System.Data.Mapping.Update.Internal.UpdateTranslator.Update (IEntityStateManager stateManager, IEntityAdapter adapter)

--- End of internal exception stack trace ---

in System.Data.Mapping.Update.Internal.UpdateTranslator.Update (IEntityStateManager stateManager, IEntityAdapter adapter)

in System.Data.Objects.ObjectContext.SaveChanges (SaveOptions options)

in System.Data.Entity.Internal.InternalContext.SaveChanges ()

--- End of internal exception stack trace ---

in System.Data.Entity.Internal.InternalContext.SaveChanges ()

on Zappiti.BaseApi.PutVideo (PutVideo putVideo, Guid userId, String queueName, Boolean isBeta)

I am deploying my package using the standard build definition from TFS.

Is there a way to avoid these connection errors?

+6
source share
1 answer

I just found this feature in the EF 6.x change summary:

http://msdn.microsoft.com/en-us/data/dn456835

I'll try.

Stay with us.

0
source

Source: https://habr.com/ru/post/955617/


All Articles