| title | description | author | ms.author | ms.date | ms.service | ms.subservice | ms.topic | helpviewer_keywords | |
|---|---|---|---|---|---|---|---|---|---|
MSSQLSERVER_41301 |
MSSQLSERVER_41301 |
MashaMSFT |
mathoma |
04/04/2017 |
sql |
supportability |
reference |
|
[!INCLUDE SQL Server]
| Attribute | Value |
|---|---|
| Product Name | [!INCLUDEssNoVersion] |
| Event ID | 41301 |
| Event Source | MSSQLSERVER |
| Component | SQLEngine |
| Symbolic Name | COMMIT_DEPENDENCY_FAILURE |
| Message Text | A previous transaction that the current transaction took a dependency on has aborted, and the current transaction can no longer commit. |
The transaction encountered a dependency failure, and is now doomed.
This error can also be caused by too many dependent transactions. Any write transaction can have a limited number of dependent transactions. For example, this error can occur if too many read transactions try to take a dependency on the update transaction.
Don't do any work on the transaction. Call ROLLBACK TRAN to roll back the transaction. For more information, see In-Memory OLTP (In-Memory Optimization).
Enable and Disable Always On Availability Groups (SQL Server)