Server Error Messages 3900 – 3999


 This transaction uses too many databases and/or aggregates. The maximum allowed is %d. The transaction must be split into smaller sections.
 The commit transaction request has no corresponding BEGIN TRANSACTION.
 The rollback transaction request has no corresponding BEGIN TRANSACTION.
 Can't unsplit logical page %ld in object `%S_OBJID' in database `%S_DBID' - both pages together contain more data than will fit on one page.
 Can't unsplit logical page %ld in object `%S_OBJID' in database `%S_DBID' - row number %d is used on both pages.
 Attempt to BEGIN TRANsaction in database `%.*s' failed because database is READ ONLY.
 Failed to receive results from PROBE. The distributed transaction named %.*s has not been committed and data may be inconsistent across databases.
 Attempt to BEGIN TRANsaction in database `%.*s' failed because database is in BYPASS RECOVERY mode.
 While closing transaction descriptor, server found it not marked as having a kept database.
 Attempt to use an inactive internal transaction.  This is an internal system error.
 Illegal internal transaction status.  This is an internal system error.
 Attempt to make a transaction in dbid %d internal.  This is an internal system error.
 Internal transaction lock context chains mixed up.  This is an internal system error.
 An attempt was made to startup a multi-database update in database `%S_DBID' after starting up the master transaction in tempdb.  This could render the database `%S_DBID' unrecoverable and this update is therefore not allowed.
You cannot start a %s transaction in master, model, or sybsystemdb.
Attempt to start a sub transaction without a parent transaction. This is an internal system error. 
Attempt to set parallel status on transaction by non-parent thread. This is an internal error. 
Illegal attempt to start sub-transaction by a parent thread. This is an internal error. 
Attempt to set parallel status on transaction that is not in CMD mode. This is an internal error. 
Empty Parent Session Id passed to start a sub transaction. This is an internal system error. 
 Could not find an available transaction descriptor. Raise the value of the configuration parameter ’txn to pss ratio’.
An attempt was made by this thread (spid=%d) to attach to a transaction. This is illegal because this thread is already associated with a transaction. Use systransactions to find out more information. 
An attempt was made by this task (spid=%d) to detach from a transaction. This is illegal because this task is currently not associated with the transaction. Use systransactions table to obtain more information.  
Systransactions system table does not exist in this database. You need to upgrade to the correct version. The command is aborted. 
Transaction Manager API '%.*s' failed. It was invoked with a wrong transaction type '%ld'.
Attempt to begin a multi database transaction failed. It is illegal to begin a subordinate transaction in the master database.
Attempt to start an external transaction failed. It is illegal to begin an external transaction from with in the scope of a local transaction.
Transaction manager has detected a nesting failure. Number of BEGIN TRAN commands (issued after an attach operation) do not match the number of COMMIT TRAN commands (issued before a detach operation).
Fatal protocol error. xact_beginupdate() API was invoked in the wrong c ontext. The transaction is currently in '%d' state.
Heuristic completion of transaction did not succeed. After ensuring that everything is ok, use dbcc forget_xact() command to delete the entry from systransactions system table. 
Fatal protocol error. xact_begin() API was invoked in the wrong context. The distributed transaction is currently in ’%s’ state. 
Illegal attempt to rollback transaction (xactname '%.*s') that has already committed in database '%.*s', spid %d. 
The MSDTC Service is not enabled. Please consult the errorlog and restart the MSDTC Service. 
The MSDTC Interface %s failed with error 0x%lx -- %s.
Database %s is not allowed to participate in a distributed transaction. 
%s’ transactions are not allowed in an HA configuration.
Attempt to BEGIN TRANSACTION in database ’%S_DBID’ failed because the database is in standby access mode. 
You cannot begin an external transaction for a server that is in single-user mode. 
Cannot start external transaction without a DTM license.
A heuristic completion related operation failed. Please see errorlog for more details. 

Number	Severity	Text and Explanation
3901	17	This transaction uses too many databases and/or aggregates. The maximum allowed is %d. The transaction must be split into smaller sections. Explanation: Command failed due to resource limitation. Modify the command to fit available resources, retry when the resource is available, or contact your System Administrator to address the resource problem.
3902	13	The commit transaction request has no corresponding BEGIN TRANSACTION. Explanation: Adaptive Server detected an invalid transaction context for the commands. Check your commands.
3903	13	The rollback transaction request has no corresponding BEGIN TRANSACTION. Explanation: Adaptive Server detected an invalid transaction context for the commands. Check your commands.
3904	21	Can't unsplit logical page %ld in object `%S_OBJID' in database `%S_DBID' - both pages together contain more data than will fit on one page. Explanation: Refer to the writeup for this error.
3905	21	Can't unsplit logical page %ld in object `%S_OBJID' in database `%S_DBID' - row number %d is used on both pages. Explanation: Adaptive Server encountered an internal error affecting all processes in the current database. Report the error to your System Administrator. Adaptive Server must be restarted and dbcc diagnostics run.
3906	16	Attempt to BEGIN TRANsaction in database `%.s' failed because database is READ ONLY. Explanation:* Command failed due to invalid or illegal request. Check syntax, semantics, and permissions. Take any corrective action indicated by message.
3907	21	Failed to receive results from PROBE. The distributed transaction named %.s has not been committed and data may be inconsistent across databases. Explanation:* Adaptive Server encountered an internal error with a distributed transaction affecting all processes using the current database. Report the error to your System Administrator.
3908	16	Attempt to BEGIN TRANsaction in database `%.s' failed because database is in BYPASS RECOVERY mode. Explanation:* Command failed due to invalid or illegal request. Check syntax, semantics, and permissions. Take any corrective action indicated by message.
3909	18	While closing transaction descriptor, server found it not marked as having a kept database. Explanation: Command failed due to internal Adaptive Server problem. Perform any diagnostic action indicated by message. Report the error to your System Administrator.
3913	26	Attempt to use an inactive internal transaction. This is an internal system error. Explanation: An internal locking/synchronization rule was broken. Report the error to your System Administrator. Shut down and restart Adaptive Server.
3914	26	Illegal internal transaction status. This is an internal system error. Explanation: An internal locking/synchronization rule was broken. Report the error to your System Administrator. Shut down and restart Adaptive Server.
3915	26	Attempt to make a transaction in dbid %d internal. This is an internal system error. Explanation: An internal locking/synchronization rule was broken. Report the error to your System Administrator. Shut down and restart Adaptive Server.
3916	26	Internal transaction lock context chains mixed up. This is an internal system error. Explanation: An internal locking/synchronization rule was broken. Report the error to your System Administrator. Shut down and restart Adaptive Server.
3917	16	An attempt was made to startup a multi-database update in database `%S_DBID' after starting up the master transaction in tempdb. This could render the database `%S_DBID' unrecoverable and this update is therefore not allowed. Explanation: Command failed due to invalid or illegal request. Check the database context for the transaction. Take any corrective action indicated by message.
3921	14	You cannot start a %s transaction in master, model, or sybsystemdb. Explanation: You do not have the permission to execute this command. Have the object owner or a user with the needed role run this command.
3922	26	Attempt to start a sub transaction without a parent transaction. This is an internal system error. Explanation: An internal locking/synchronization rule was broken. Report the error to your System Administrator. Shut down and restart Adaptive Server.
3923	26	Attempt to set parallel status on transaction by non-parent thread. This is an internal error. Explanation: An internal locking/synchronization rule was broken. Report the error to your System Administrator. Shut down and restart Adaptive Server.
3924	26	Illegal attempt to start sub-transaction by a parent thread. This is an internal error. Explanation: An internal locking/synchronization rule was broken. Report the error to your System Administrator. Shut down and restart Adaptive Server.
3925	26	Attempt to set parallel status on transaction that is not in CMD mode. This is an internal error. Explanation: An internal locking/synchronization rule was broken. Report the error to your System Administrator. Shut down and restart Adaptive Server.
3926	26	Empty Parent Session Id passed to start a sub transaction. This is an internal system error. Explanation: An internal locking/synchronization rule was broken. Report the error to your System Administrator. Shut down and restart Adaptive Server.
3927	17	Could not find an available transaction descriptor. Raise the value of the configuration parameter ’txn to pss ratio’. Explanation: Command failed when a configurable limit was exceeded. Report the error to your System Administrator.
3928	16	An attempt was made by this thread (spid=%d) to attach to a transaction. This is illegal because this thread is already associated with a transaction. Use systransactions to find out more information. Explanation: Query failed. Take any corrective action indicated by the message.
3929	16	An attempt was made by this task (spid=%d) to detach from a transaction. This is illegal because this task is currently not associated with the transaction. Use systransactions table to obtain more information. Explanation: Query failed. Take any corrective action indicated by the message.
3930	20	Systransactions system table does not exist in this database. You need to upgrade to the correct version. The command is aborted. Explanation: Adaptive Server encountered an internal error affecting the current process. Report the error to your System Administrator.
3931	16	Transaction Manager API '%.s' failed. It was invoked with a wrong transaction type '%ld'. Explanation:* Command failed due to invalid or illegal request. Check syntax and semantics.
3932	16	Attempt to begin a multi database transaction failed. It is illegal to begin a subordinate transaction in the master database. Explanation: Command failed due to invalid or illegal request. Check semantics and working context.
3933	16	Attempt to start an external transaction failed. It is illegal to begin an external transaction from with in the scope of a local transaction. Explanation: Command failed due to invalid or illegal request. Check semantics and working context.
3934	16	Transaction manager has detected a nesting failure. Number of BEGIN TRAN commands (issued after an attach operation) do not match the number of COMMIT TRAN commands (issued before a detach operation). Explanation: Command failed due to invalid or illegal request. Check semantics and working context.
3935	16	Fatal protocol error. xact_beginupdate() API was invoked in the wrong c ontext. The transaction is currently in '%d' state. Explanation: Adaptive Server encountered an internal error affecting the current process. Report the error to your System Administrator.
3936	0	Heuristic completion of transaction did not succeed. After ensuring that everything is ok, use dbcc forget_xact() command to delete the entry from systransactions system table. Explanation: Refer to the Adaptive Server Reference Manual for information about the stored procedure you were running when you got this message.
3938	20	Fatal protocol error. xact_begin() API was invoked in the wrong context. The distributed transaction is currently in ’%s’ state. Explanation: Adaptive Server encountered an internal error affecting the current process. Reconnect to Adaptive Server. Report the error to your System Administrator so DBCC diagnostics can be run.
3939	10	Illegal attempt to rollback transaction (xactname '%.s') that has already committed in database '%.s', spid %d. Explanation: Check command semantics and processing logic of your query.
3940	10	The MSDTC Service is not enabled. Please consult the errorlog and restart the MSDTC Service. Explanation: Check command semantics and processing logic of your query.
3941	10	The MSDTC Interface %s failed with error 0x%lx -- %s. Explanation: Check command semantics and processing logic of your query.
3942	16	Database %s is not allowed to participate in a distributed transaction. Explanation: Command failed due to invalid or illegal request. Check semantics and working context.
3943	14	%s’ transactions are not allowed in an HA configuration. Explanation: Command failed due to invalid or illegal request. Adaptive Server cannot perform the requested action. Take any corrective action indicated by the message.
3944	16	Attempt to BEGIN TRANSACTION in database ’%S_DBID’ failed because the database is in standby access mode. Explanation: Command failed due to invalid or illegal request. Check semantics and working context.
3945	16	You cannot begin an external transaction for a server that is in single-user mode. Explanation: Command failed due to invalid or illegal request. Check semantics and working context.
3946	16	Cannot start external transaction without a DTM license. Explanation: Command failed due to invalid or illegal request. Check semantics and working context.
3947	16	A heuristic completion related operation failed. Please see errorlog for more details. Explanation: Command failed due to invalid or illegal request. Check semantics and working context.