SQL Server Errors or Failures from Error: 3903 to Error: 3925

SQLServerF1

 

Error: 3903, Severity: 16, The ROLLBACK TRANSACTION request has no corresponding BEGIN TRANSACTION.
Error: 3904, Severity: 21, Cannot unsplit logical page %S_PGID in object ‘%.*ls’, in database ‘%.*ls’. Both pages together contain more data than will fit on one page.
Error: 3906, Severity: 16, Failed to update database “%.*ls” because the database is read-only.
Error: 3908, Severity: 16, Could not run BEGIN TRANSACTION in database ‘%.*ls’ because the database is in emergency mode or is damaged and must be restarted.
Error: 3909, Severity: 16, Session binding token is invalid.

Error: 3910, Severity: 16, Transaction context in use by another session.
Error: 3912, Severity: 16, Cannot bind using an XP token while the server is not in an XP call.
Error: 3913, Severity: 16, TDS reset connection protocol error. Client driver requested both ResetConnectionKeepLocalXact and ResetConnectionKeepDTCXact at the same time. This is not expected in server.
Error: 3914, Severity: 16, The data type “%s” is invalid for transaction names or savepoint names. Allowed data types are char, varchar, nchar, varchar(max), nvarchar, and nvarchar(max).
Error: 3915, Severity: 16, Cannot use the ROLLBACK statement within an INSERT-EXEC statement.

Error: 3916, Severity: 16, Cannot use the COMMIT statement within an INSERT-EXEC statement unless BEGIN TRANSACTION is used first.
Error: 3917, Severity: 16, Session is bound to a transaction context that is in use. Other statements in the batch were ignored.
Error: 3918, Severity: 16, The statement or function must be executed in the context of a user transaction.
Error: 3919, Severity: 16, Cannot enlist in the transaction because the transaction has already been committed or rolled back.
Error: 3920, Severity: 10, The WITH MARK option only applies to the first BEGIN TRAN WITH MARK statement. The option is ignored.
Error: 3921, Severity: 16, Cannot get a transaction token if there is no transaction active. Reissue the statement after a transaction has been started
Error: 3922, Severity: 16, Cannot enlist in the transaction because the transaction does not exist.
Error: 3923, Severity: 10, Cannot use transaction marks on database ‘%.*ls’ with bulk-logged operations that have not been backed up. The mark is ignored.
Error: 3924, Severity: 10, The session was enlisted in an active user transaction while trying to bind to a new transaction. The session has defected from the previous user transaction.
Error: 3925, Severity: 16, Invalid transaction mark name. The ‘LSN:’ prefix is reserved.

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.

Thanks,
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 *