Databases
StackOverflow2013
Postsdbo
POSystem.Data.EntityException: The underlying provider failed on Commit
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POSystem.Data.EntityException: The underlying provider failed on Commit
    primarykey
    data
    text
    <p>Using Entity Framework, I received a number of the following exceptions last night in one of my applications:</p> <pre><code>System.Data.EntityException: The underlying provider failed on Commit. ---&gt; System.Data.SqlClient.SqlException: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding. at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection) at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning() at System.Data.SqlClient.TdsParserStateObject.ReadSniError(TdsParserStateObject stateObj, UInt32 error) at System.Data.SqlClient.TdsParserStateObject.ReadSni(DbAsyncResult asyncResult, TdsParserStateObject stateObj) at System.Data.SqlClient.TdsParserStateObject.ReadNetworkPacket() at System.Data.SqlClient.TdsParserStateObject.ReadBuffer() at System.Data.SqlClient.TdsParserStateObject.ReadByte() at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler,SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj) at System.Data.SqlClient.TdsParser.TdsExecuteTransactionManagerRequest(Byte[] buffer, TransactionManagerRequestType request, String transactionName, TransactionManagerIsolationLevel isoLevel, Int32 timeout, SqlInternalTransaction transaction, TdsParserStateObject stateObj, Boolean isDelegateControlRequest) at System.Data.SqlClient.SqlInternalConnectionTds.ExecuteTransactionYukon(TransactionRequest transactionRequest, String transactionName, IsolationLevel iso, SqlInternalTransaction internalTransaction, Boolean isDelegateControlRequest) at System.Data.SqlClient.SqlInternalConnectionTds.ExecuteTransaction(TransactionRequest transactionRequest, String name, IsolationLevel iso, SqlInternalTransaction internalTransaction, Boolean isDelegateControlRequest) at System.Data.SqlClient.SqlInternalTransaction.Commit() at System.Data.SqlClient.SqlTransaction.Commit() at System.Data.EntityClient.EntityTransaction.Commit() --- End of inner exception stack trace --- at System.Data.EntityClient.EntityTransaction.Commit() at System.Data.Objects.ObjectContext.SaveChanges(SaveOptions options) at System.Data.Entity.Internal.InternalContext.SaveChanges() at System.Data.Entity.Internal.LazyInternalContext.SaveChanges() </code></pre> <p>What's interesting about this error is that the data was actually written to the database. I <a href="http://social.msdn.microsoft.com/Forums/is/adodotnetentityframework/thread/34159afb-9820-43fb-8ac8-bd3e287d8b6a">found a related post on a MS site</a> that seemed to indicate that this was a network related error.</p> <p>A few questions that I could use assistance on are:</p> <ol> <li>What options do I have to trouble shoot this error?</li> <li>Is it more than likely network related or could the DB be a suspect?</li> <li>How can I tell from the code whether the transaction really did complete?</li> <li>Should I query the DB on this error to check if success or simply retry the transaction?</li> <li>If I do retry the transaction, how can this be accomplished automatically with Entity Framework or do I simply catch/retry?</li> <li>What other items should I be looking at?</li> </ol> <p>Thanks in advance.</p> <p><strong>UPDATE</strong></p> <p>Using <a href="http://www.confio.com/English/Products/Ignite_for_SQL_Server.php">Ignite for SQL</a> we were able to determine that a secondary SQL process from another group was monopolizing the CPU preventing our application from functioning properly. In short, we're moving forward with adding a secondary server to prevent further conflicts between the two teams.</p> <p>What's still interesting about the exception is that the transaction actually succeeded rather than failed.</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USRandy
    1. USRandy
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POSystem.Data.EntityException: The underlying provider failed on Commit
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POSystem.Data.EntityException: The underlying provider failed on Commit
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POSystem.Data.EntityException: The underlying provider failed on Commit
      1. This table or related slice is empty.
      1. VTUpMod
    1. COI know it's been a long time, but can you elaborate on how you used Ignite for SQL? In my case it does not always happen so it's hard to know when to watch the server.
      singulars
      1. POSystem.Data.EntityException: The underlying provider failed on Commit
      1. USgitsitgo
    2. COCan't say that I'm an ignite guru; we have a DB performance team who handles this stuff. I can say that what I typically am looking for when I get performance issues are top sql statements (as ignite states "the big bars"). Those are typically the queries hogging everything. From there it's a matter of tuning those queries. Sorry that I couldn't provide more specifics that you are looking for. Good luck.
      singulars
      1. POSystem.Data.EntityException: The underlying provider failed on Commit
      1. USRandy
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload