MSSQLSERVER_41301
Applies to: 
SQL Server
Details
| Attribute | Value |
|---|---|
| Product Name | SQL Server |
| 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. |
Explanation
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.
User Action
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).
See Also
Enable and Disable Always On Availability Groups (SQL Server)
Feedback
Coming soon: Throughout 2024 we will be phasing out GitHub Issues as the feedback mechanism for content and replacing it with a new feedback system. For more information see: https://aka.ms/ContentUserFeedback.
Submit and view feedback for