SQL Server Errors or Failures from Error: 3926 to Error: 3953



Error: 3926, Severity: 10, The transaction active in this session has been committed or aborted by another session.
Error: 3927, Severity: 10, The session had an active transaction when it tried to enlist in a Distributed Transaction Coordinator transaction.
Error: 3928, Severity: 16, The marked transaction “%.*ls” failed. A timeout occurred while attempting to place a mark in the log by committing the marked transaction. This can be caused by contention with Microsoft Distributed Transaction Coordinator (MS DTC) transactions or other

Error: 3929, Severity: 16, No distributed or bound transaction is allowed in single user database.
Error: 3930, Severity: 16, The current transaction cannot be committed and cannot support operations that write to the log file. Roll back the transaction.
Error: 3931, Severity: 16, The current transaction cannot be committed and cannot be rolled back to a savepoint. Roll back the entire transaction.
Error: 3932, Severity: 16, The save point name “%.*ls” that was provided is too long. The maximum allowed length is %d characters.
Error: 3933, Severity: 16, Cannot promote the transaction to a distributed transaction because there is an active save point in this transaction.

Error: 3934, Severity: 14, The current user cannot use this FILESTREAM transaction context. To obtain a valid FILESTREAM transaction context, use GET_FILESTREAM_TRANSACTION_CONTEXT.
Error: 3935, Severity: 16, A FILESTREAM transaction context could not be initialized. This might be caused by a resource shortage. Retry the operation. Error code: 0x%x.
Error: 3936, Severity: 16, The transaction could not be committed because an error occurred while tyring to flush FILESTREAM data to disk. A file may have been open at commit time or a disk I/O error may have occurred. ‘%.*ls’ was one of the one or more files involved. ErorrCode:
Error: 3937, Severity: 16, While rolling back a transaction, an error occurred while trying to deliver a rollback notification to the FILESTREAM filter driver. Error code: 0x%0x.
Error: 3938, Severity: 18, The transaction has been stopped because it conflicted with the execution of a FILESTREAM close operation using the same transaction. The transaction will be rolled back.
Error: 3939, Severity: 16, An uncommittable transaction was detected at the beginning of the batch. The transaction was rolled back. This was caused by an error that occurred during the processing of a FILESTREAM request in the context of this transaction.
Error: 3948, Severity: 16, The transaction was terminated because of the availability replica config/state change or because ghost records are being deleted on the primary and the secondary availability replica that might be needed by queries running under snapshot isolation. Retry
Error: 3949, Severity: 16, Transaction aborted when accessing versioned row in table ‘%.*ls’ in database ‘%.*ls’. Requested versioned row was not found because the readable secondary access is not allowed for the operation that attempted to create the version. This might be timing
Error: 3950, Severity: 16, Version store scan timed out when attempting to read the next row. Please try the statement again later when the system is not as busy.
Error: 3951, Severity: 16, Transaction failed in database ‘%.*ls’ because the statement was run under snapshot isolation but the transaction did not start in snapshot isolation. You cannot change the isolation level of the transaction to snapshot after the transaction has started u
Error: 3952, Severity: 16, Snapshot isolation transaction failed accessing database ‘%.*ls’ because snapshot isolation is not allowed in this database. Use ALTER DATABASE to allow snapshot isolation.
Error: 3953, Severity: 16, Snapshot isolation transaction failed in database ‘%.*ls’ because the database was not recovered when the current transaction was started. Retry the transaction after the database has recovered.

This is applicable on below versions of SQL Server

SQL Server 2005
SQL Server 2008 R2
SQL Server 2012
SQL Server 2014

Hope this was helpful.

SQLServerF1 Team
In-Depth Blogs on SQL Server, Information about SQL Server Conferences and Events, SQL Server Frequently asked questions, SQL Server Trainings.


Leave a Reply

Your email address will not be published. Required fields are marked *