SQL Server Errors or Failures from Error: 3974 to Error: 3993

SQLServerF1

 

Error: 3974, Severity: 16, State: 1, Line: 1
Msg 3974, Level 16, State 1, Line 1
The number of databases in exclusive mode usage under a workspace is limited. Because the limit has been exceeded, the operation failed.
Error: 3975, Severity: 16, State: 1, Line: 1
Msg 3975, Level 16, State 1, Line 1
The varchar(max) data type is not supported for sp_getbindtoken. The batch has been aborted.
Error: 3976, Severity: 16, State: 1, Line:
Msg 3976, Level 16, State , Line
The transaction name has the odd length %d. The batch has been aborted.
Error: 3977, Severity: 16, State: 1, Line: 1,
Msg 3977, Level 16, State 1, Line 1,
The savepoint name cannot be NULL. The batch has been aborted.
Error: 3978, Severity: 16, State: 1, Line: 1
Msg 3978, Level 16, State 1, Line 1
Beginning a new transaction after rollback to save point is not allowed.

Error: 3979, Severity: 16, The TM request is longer than expected. The request is not processed.
Error: 3980, Severity: 16, The request failed to run because the batch is aborted, this can be caused by abort signal sent from client, or another request is running in the same session, which makes the session busy.
Error: 3981, Severity: 16, The transaction operation cannot be performed because there are pending requests working on this transaction.
Error: 3982, Severity: 16, New transaction is not allowed to be started while DTC or bound transaction is active.

Error: 3983, Severity: 16, The operation failed because the session is not single threaded.
Error: 3984, Severity: 16, Cannot acquire a database lock during a transaction change.
Error: 3985, Severity: 16, An error occurred during the changing of transaction context. This is usually caused by low memory in the system. Try to free up more memory.
Error: 3986, Severity: 19, The transaction timestamps ran out. Restart the server.
Error: 3987, Severity: 10, SNAPSHOT ISOLATION is always enabled in this database.
Error: 3988, Severity: 16, New transaction is not allowed because there are other threads running in the session.
Error: 3989, Severity: 16, New request is not allowed to start because it should come with valid transaction descriptor.
Error: 3990, Severity: 16, Transaction is not allowed to commit inside of a user defined routine, trigger or aggregate because the transaction is not started in that CLR level. Change application logic to enforce strict transaction nesting.
Error: 3991, Severity: 16, The context transaction which was active before entering user defined routine, trigger or aggregate “%.*ls” has been ended inside of it, which is not allowed. Change application logic to enforce strict transaction nesting.
Error: 3992, Severity: 16, Transaction count has been changed from %d to %d inside of user defined routine, trigger or aggregate “%.*ls”. This is not allowed and user transaction will be rolled back. Change application logic to enforce strict transaction nesting.
Error: 3993, Severity: 16, The user transaction that has been started in user defined routine, trigger or aggregate “%.*ls” is not ended upon exiting from it. This is not allowed and the transaction will be rolled back. Change application logic to enforce strict transaction nesting

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 *