Server Error Messages 4200 - 4299


 DUMP TRANSACTION for database `%.*s' failed:  insufficient memory to allocate backout structure.
 Unable to continue logged version of DUMP TRAN. No space left in database; use NO_LOG option or run ALTER DATABASE. Else, an old transaction may be active; see Syslogshold table.
 Syslogs does not exist in its own segment in database `%S_DBID' with segmap `%ld' with logical start page number of `%ld'. You cannot use DUMP TRANSACTION in this case, use DUMP DATABASE instead.
 You cannot run DUMP TRANsaction WITH NO_LOG inside a user transaction.
 Dump transaction is not allowed because a non-logged operation was performed on the database. Dump your database or use dump transaction with truncate_only until you can dump your database.
 DUMP TRANsaction to a dump device is not allowed while the trunc. log on chkpt. option is enabled.  Disable the option with sp_dboption, then use DUMP DATABASE, before trying again.
 While attempting DUMP TRANsaction WITH NO_TRUNCATE, couldn't find database %.*s.
 Couldn't complete DUMP TRANsaction WITH NO_TRUNCATE on database `%.*s', because the log pointer in sysdatabases (page number %ld) is not accurate.
 Page %ld in database `%.*s' cannot be used as a truncation page because the page belongs to object ID %ld and not to the log.  Choose another page.
 Page %ld in database `%.*s' cannot be used as a truncation page because the page is not allocated.  Choose another page.
 Cannot use page %ld in database `%.*s' as the trunc page because the LTM trunc state is not set to TRUNC_VALID.  Set LTM trunc state to TRUNC_VALID with DBCC SETTRUNC.
 %s failed in database %.*s:  %ld not first log page in serially allocated log extent or allocation page.  Should be:  %ld.  Previous log record in  scan:  %ld.
 %s failed in database %.*s:  unexpected end of log encountered on page %ld while scanning for page %ld.
 Failure during DUMP TRANSACTION in database `%S_DBID': caller does not possess dump lock.
Failure during DUMP of database '%.*s':  serial log page allocation rules  broken .  Current page: %ld;  next page: %ld;  piece end: %ld;   end-of-scan: %ld.
 DUMP TRANsaction encountered an unexpected end to the log page chain. Last page in log as scanned:  %ld.
 You must be the DBO of database %.*s or have Operator (OPER) role to run DUMP TRANSACTION.
 DUMP TRANsaction to a dump device is not allowed where a truncate-only transaction dump has been performed after the last DUMP DATABASE.  Use DUMP DATABASE instead.
 DUMP TRANSACTION for database `%S_DBID' failed: log page (%ld) is on a data-only segment. This is probably due to an incomplete move of the log to a device separate from the data. Complete the log migration or contact the System Administrator.
 Deadlock occurred in SQL Process %d.
 An interruption occurred in process %d due to USER ATTENTION or connection failure.
 This database has not been dumped since it was created or upgraded. You must perform a dump database before you can dump its transaction log.
 Logged DUMP TRANSACTION cannot run in database %.*s, because that databases's log version (%d) disagrees with the SQL Server's log version (%d); use DUMP TRANSACTION WITH NO_LOG. Versions will agree once ONLINE DATABASE has run.
 No space left in database master; creating user objects in master database not recommended. Else, an old transaction may be active; see Syslogshold table.
 No space left in database `%S_DBID'; Use ALTER DATABASE to increase size of database. Else, an old transaction may be active; see Syslogshold table.
%s failed in database %.*s: Unable to find quiescent point in the log. Log backward scan start marker (%d, %d) and end marker (%d, %d). 
%s failed on database %.*s: Unable to get the secondary truncation page %ld.  
%s failed in database %.*s: Bad quiescent point was found.  
%s for database '%.*s' could not truncate the log. Either extend the log using ALTER DATABASE ... LOG ON command or eliminate the oldest active transaction in database '%. *s' shown in syslogshold table. 
Cannot dump %s database’s log as distributed transaction resolution is not complete yet. Please retry later. 

Number	Severity	Text and Explanation
4201	17	DUMP TRANSACTION for database `%.s' failed: insufficient memory to allocate backout structure. 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.
4204	17	Unable to continue logged version of DUMP TRAN. No space left in database; use NO_LOG option or run ALTER DATABASE. Else, an old transaction may be active; see Syslogshold table. Explanation: Refer to the writeup for this error.
4205	16	Syslogs does not exist in its own segment in database `%S_DBID' with segmap `%ld' with logical start page number of `%ld'. You cannot use DUMP TRANSACTION in this case, use DUMP DATABASE instead. Explanation: A database maintenance operation failed. Take any corrective action indicated by the message. Check the Adaptive Server error log.
4206	16	You cannot run DUMP TRANsaction WITH NO_LOG inside a user transaction. Explanation: Command failed due to invalid or illegal request. Check syntax, semantics, and permissions. Take any corrective action indicated by message.
4207	16	Dump transaction is not allowed because a non-logged operation was performed on the database. Dump your database or use dump transaction with truncate_only until you can dump your database. Explanation: Refer to the writeup for this error.
4208	16	DUMP TRANsaction to a dump device is not allowed while the trunc. log on chkpt. option is enabled. Disable the option with sp_dboption, then use DUMP DATABASE, before trying again. Explanation: A database maintenance operation failed. Take any corrective action indicated by the message. Check the Adaptive Server error log.
4210	16	While attempting DUMP TRANsaction WITH NO_TRUNCATE, couldn't find database %.s. Explanation:* A database maintenance operation failed. Take any corrective action indicated by the message. Check the Adaptive Server error log.
4211	23	Couldn't complete DUMP TRANsaction WITH NO_TRUNCATE on database `%.s', because the log pointer in sysdatabases (page number %ld) is not accurate. Explanation:* The database may be corrupt. Report the error to your System Administrator. Adaptive Server must be restarted and dbcc diagnostics run.
4212	16	Page %ld in database `%.s' cannot be used as a truncation page because the page belongs to object ID %ld and not to the log. Choose another page. 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.
4213	16	Page %ld in database `%.s' cannot be used as a truncation page because the page is not allocated. Choose another page. 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.
4214	16	Cannot use page %ld in database `%.s' as the trunc page because the LTM trunc state is not set to TRUNC_VALID. Set LTM trunc state to TRUNC_VALID with DBCC SETTRUNC. Explanation:* Contact your System Administrator to address the Replication Server LTM setting.
4215	21	%s failed in database %.s: %ld not first log page in serially allocated log extent or allocation page. Should be: %ld. Previous log record in scan: %ld. 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.
4216	21	%s failed in database %.s: unexpected end of log encountered on page %ld while scanning for page %ld. Explanation:* Refer to the writeup for Error 4216.
4217	26	Failure during DUMP TRANSACTION in database `%S_DBID': caller does not possess dump lock. Explanation: An internal locking/synchronization rule was broken. Report the error to your System Administrator. Shut down and restart Adaptive Server.
4218	21	Failure during DUMP of database '%.s': serial log page allocation rules broken . Current page: %ld; next page: %ld; piece end: %ld; end-of-scan: %ld. 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.
4219	21	DUMP TRANsaction encountered an unexpected end to the log page chain. Last page in log as scanned: %ld. 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.
4220	14	You must be the DBO of database %.s or have Operator (OPER) role to run DUMP TRANSACTION. 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.
4221	16	DUMP TRANsaction to a dump device is not allowed where a truncate-only transaction dump has been performed after the last DUMP DATABASE. Use DUMP DATABASE instead. Explanation: Refer to the writeup for Error 4221.
4222	16	DUMP TRANSACTION for database `%S_DBID' failed: log page (%ld) is on a data-only segment. This is probably due to an incomplete move of the log to a device separate from the data. Complete the log migration or contact the System Administrator. Explanation: Refer to the writeup for Error 4222.
4223	18	Deadlock occurred in SQL Process %d. Explanation: Command failed due to internal Adaptive Server problem. Perform any diagnostic action indicated by message. Report the error to your System Administrator.
4224	16	An interruption occurred in process %d due to USER ATTENTION or connection failure. Explanation: Adaptive Server could not perform the requested action. Contact your System Administrator.
4225	16	This database has not been dumped since it was created or upgraded. You must perform a dump database before you can dump its transaction log. Explanation: If this is a new database or one that was recently upgraded, it would be invalid to attempt to dump the transaction log since there is no database dump. This error is raised if you try to do dump transaction and no database dump exists. First dump the database, then dump the transaction log.
4226	16	Logged DUMP TRANSACTION cannot run in database %.s, because that databases's log version (%d) disagrees with the SQL Server's log version (%d); use DUMP TRANSACTION WITH NO_LOG. Versions will agree once ONLINE DATABASE has run. Explanation:* A database maintenance operation failed. Take any corrective action indicated by the message. Check the Adaptive Server error log.
4227	17	No space left in database master; creating user objects in master database not recommended. Else, an old transaction may be active; see Syslogshold table. 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.
4228	17	No space left in database `%S_DBID'; Use ALTER DATABASE to increase size of database. Else, an old transaction may be active; see Syslogshold table. 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.
4233	19	%s failed in database %.s: Unable to find quiescent point in the log. Log backward scan start marker (%d, %d) and end marker (%d, %d). Explanation:* Report the resource error to your System Administrator.
4234	21	%s failed on database %.s: Unable to get the secondary truncation page %ld. Explanation:* Adaptive Server encountered an internal error affecting all processes using the current database. Report the error to your System Administrator.
4235	20	%s failed in database %.s: Bad quiescent point was found. Explanation:* Adaptive Server encountered an internal error affecting the current process. Report the error to your System Administrator.
4236	10	%s for database '%.s' could not truncate the log. Either extend the log using ALTER DATABASE ... LOG ON command or eliminate the oldest active transaction in database '%. s' shown in syslogshold table. Explanation: Database maintenance operation failed. Take specified action.
4237	16	Cannot dump %s database’s log as distributed transaction resolution is not complete yet. Please retry later. Explanation: A database maintenance operation failed. Take any corrective action indicated by the message. Check the Adaptive Server error log.