Server Error Messages 1200-1299


lock_logical was called with illegal locktype %d. 
Caller of lock manager is incorrectly trying to release or downgrade a lock which it doesn't hold. spid=%d loc ktype=%d dbid=%d page number (or objid for table lock)=%ld, objid (if not a table lock)=%ld, row number=%ld.
 SQL Server has run out of LOCKS.  Re-run your command when there are fewer active users, or contact a user with System Administrator (SA) role to reconfigure SQL Server with more LOCKS.
 Your server command (process id #%d) was deadlocked with another process and has been chosen as deadlock victim. Re-run your command.
 Lock free chain linkage has been corrupted.
 A non lock is linked on the free chain.
 Lock hash table linkage has been corrupted.
 A structure from outside the lock area has been linked onto a lock hash chain.
 Lock record chain linkage has been corrupted.
 A non lock record is linked onto a semaphore cursor.
 Semaphore cursor chain linkage has been corrupted.
 A non semaphore cursor is linked onto a semaphore.
 The actual number of free locks does not match the free lock count.
 A semaphore cursor has no lock records linked to it.
 An incorrect lock structure is linked on the free chain.
 An incorrect lock structure is linked onto a hash chain.
 An incorrect lock structure is linked a chain of lock structures.
 An incorrect lock structure is linked to a semaphore.
 A semaphore cursor at the head of a semaphore queue is marked as waiting.
 A semaphore cursor not at the head of a semaphore queue is marked as not waiting.
 A semaphore cursor has mutually incompatible lock records linked to it.
 %d locks not accounted for.
 %d extra locks found.
 A semaphore cursor refers to a different semaphore than the one it is linked to.
 A lock record refers to a different semaphore cursor than the one it is linked to.
 Couldn't find object to be released.
 Could not find address lock at address 0x%lx while trying to release it.
 Lock record and process disagree.
 Process attempting to wait on a lock that does not belong to it.
 Process attempting to wait on a lock that has already been waited for.
 Process became runnable before lock it was waiting for was released.
 A non-preallocated semaphore cursor encountered while trying to obtain a semaphore.
 An in-use preallocated semaphore cursor was encountered.
 Lock header linkage has been corrupted.
 The wrong number of lock records was found on a semaphore cursor.
 While following the lock record chain for a process, a lock record belonging to a different process was encountered.
 Unlinking a duplicate lock caused a task to be awakened.
 Encountered a non-preallocated semaphore cursor on a chain that should only have preallocated semaphore cursors.
 A process is not waiting for a lock that it should be waiting for.
 A process is waiting for a lock that has been granted.
 A process is waiting for a lock that it did not request.
 Attempt to promote from page to table locking on objid %ld encountered an internal error.
 No matching xdes found.  Lock was requested for objid %ld, dbid %d, type %d, by process %d.
 A process was found to be waiting for the same object twice.
A lock manager routine expected a lock record as an argument but was passed something else. lr=0x%x, lrmagic=% c.
 Upgrade of lock on object id or page number %ld left the lock ungranted.
 A lock record at the head of a semaphore queue is not marked as granted.
 A lock record is marked as granted, but isn't at the head of the semaphore queue.
 Temporary buffer overflow occurred while scanning the lock table.  Rows will be missing in syslocks for one or more objects.
 A task attempted to release a semaphore that it had not previously obtained.
 A task attempted to acquire a semaphore with a preallocated semaphore cursor that did not belong to it.
 Invalid parameter(s) passed to lock manager.
 Syntax error at line %d of file %s starting at `%s'.
 Error with input file %s: %s.
 The lock unit test can only be run with a single engine on line.
 Attempt to acquire a lock in dbid %d while in an internal transaction.  This is an internal error.
 In a call to lock_multiple(), the lock requests were out of order.  They should be sorted by object id, dbid.
 This semawait (1st) should only have one lockrec.
 SQL Server has run out of locks on engine %d. Re-run your command when there are fewer active users, or contact a user with System Administrator (SA) role to reconfigure maximum engine freelocks or number of locks.
Lock sleeptask (or waittask) chain has been corrupted. 
A structure of the wrong type is linked to the lock sleeptask (or waittask) chain. 
 An incorrect lock sleeptask structure is linked to the Lock Sleeptask chain.
 Could not change deadlock checking period because SQL Server has run out of alarms. Please retry the command later.
 Used Lock Sleeptask Entry not in Chain.
 Un-used Lock Sleeptask Entry in Lock Sleeptask Chain.
 Missing Preallocated Lock Sleeptask Entry.
 Freelock transfer block size (%d) cannot be more than half the number of freelocks allowed per engine (%d). To increase the number of freelocks allowed per engine please increase maximum engine freelocks.
 Setting maximum engine freelocks to %d allows only %d freelocks per engine. This value cannot be less than twice the value of freelock transfer block size. Please reduce freelock transfer block size to %d and reattempt this command.
Internal Error in lock manager routine: Invalid lock mode %s, requested by task (family id %d, spid %d) conflicts with existing family request mode %s belonging to task (family id %d, spid %d).
Internal Error in lock manager routine: Attempted lock upgrade from %s to %s in parallel query thread (family id %d, spid %d) is Illegal.
Internal Error in lock manager routine: Attempted lock anti-inheritance is an illegal operation for a non-parent thread (fid %d, spid %d).
Internal Error in lock manager routine: Thread (fid %d, spid %d) incorrectly attempted to acquire a non-queueing %s lock when thread (fid %d, spid %d) in its family already holds an insufficient %s lock on objid %d, dbid %d.
Internal Error in lock manager routine: Process (fid %d, spid %d) incorrectly attempted to transfer locks to itself, from a process (fid %d, spid %d) belonging to a different family.
Lock_logical was called with an illegal 'op' parameter: %d. 
Unconditional lock request for table or page %d, dbid %d was made while holding a latch.
Unexpected position for NKL semawait. This indicates a programmer error. 
NKL semawait is at an improper position in the queue. 

Number	Severity	Text and Explanation
1201	20	lock_logical was called with illegal locktype %d. 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.
1203	20	Caller of lock manager is incorrectly trying to release or downgrade a lock which it doesn't hold. spid=%d loc ktype=%d dbid=%d page number (or objid for table lock)=%ld, objid (if not a table lock)=%ld, row number=%ld. Explanation: Refer to the writeup for this error.
1204	19	SQL Server has run out of LOCKS. Re-run your command when there are fewer active users, or contact a user with System Administrator (SA) role to reconfigure SQL Server with more LOCKS. Explanation: Refer to the writeup for this error.
1205	13	Your server command (process id #%d) was deadlocked with another process and has been chosen as deadlock victim. Re-run your command. Explanation: Refer to the writeup for this error.
1221	26	Lock free chain linkage has been corrupted. Explanation: An internal locking/synchronization rule was broken. Report the error to your System Administrator. Shut down and restart Adaptive Server.
1222	26	A non lock is linked on the free chain. Explanation: An internal locking/synchronization rule was broken. Report the error to your System Administrator. Shut down and restart Adaptive Server.
1223	26	Lock hash table linkage has been corrupted. Explanation: An internal locking/synchronization rule was broken. Report the error to your System Administrator. Shut down and restart Adaptive Server.
1224	26	A structure from outside the lock area has been linked onto a lock hash chain. Explanation: An internal locking/synchronization rule was broken. Report the error to your System Administrator. Shut down and restart Adaptive Server.
1225	26	Lock record chain linkage has been corrupted. Explanation: An internal locking/synchronization rule was broken. Report the error to your System Administrator. Shut down and restart Adaptive Server.
1226	26	A non lock record is linked onto a semaphore cursor. Explanation: An internal locking/synchronization rule was broken. Report the error to your System Administrator. Shut down and restart Adaptive Server.
1227	26	Semaphore cursor chain linkage has been corrupted. Explanation: An internal locking/synchronization rule was broken. Report the error to your System Administrator. Shut down and restart Adaptive Server.
1228	26	A non semaphore cursor is linked onto a semaphore. Explanation: An internal locking/synchronization rule was broken. Report the error to your System Administrator. Shut down and restart Adaptive Server.
1229	26	The actual number of free locks does not match the free lock count. Explanation: An internal locking/synchronization rule was broken. Report the error to your System Administrator. Shut down and restart Adaptive Server.
1230	26	A semaphore cursor has no lock records linked to it. Explanation: An internal locking/synchronization rule was broken. Shut down and restart Adaptive Server. Report the error to Sybase Technical Support.
1231	26	An incorrect lock structure is linked on the free chain. Explanation: An internal locking/synchronization rule was broken. Report the error to your System Administrator. Shut down and restart Adaptive Server.
1232	26	An incorrect lock structure is linked onto a hash chain. Explanation: An internal locking/synchronization rule was broken. Report the error to your System Administrator. Shut down and restart Adaptive Server.
1233	26	An incorrect lock structure is linked a chain of lock structures. Explanation: An internal locking/synchronization rule was broken. Report the error to your System Administrator. Shut down and restart Adaptive Server.
1234	26	An incorrect lock structure is linked to a semaphore. Explanation: An internal locking/synchronization rule was broken. Shut down and restart Adaptive Server. Report the error to Sybase Technical Support.
1235	26	A semaphore cursor at the head of a semaphore queue is marked as waiting. Explanation: An internal locking/synchronization rule was broken. Report the error to your System Administrator. Shut down and restart Adaptive Server.
1236	26	A semaphore cursor not at the head of a semaphore queue is marked as not waiting. Explanation: An internal locking/synchronization rule was broken. Report the error to your System Administrator. Shut down and restart Adaptive Server.
1237	26	A semaphore cursor has mutually incompatible lock records linked to it. Explanation: An internal locking/synchronization rule was broken. Report the error to your System Administrator. Shut down and restart Adaptive Server.
1238	26	%d locks not accounted for. Explanation: An internal locking/synchronization rule was broken. Report the error to your System Administrator. Shut down and restart Adaptive Server.
1239	26	%d extra locks found. Explanation: An internal locking/synchronization rule was broken. Report the error to your System Administrator. Shut down and restart Adaptive Server.
1241	26	A semaphore cursor refers to a different semaphore than the one it is linked to. Explanation: An internal locking/synchronization rule was broken. Report the error to your System Administrator. Shut down and restart Adaptive Server.
1242	26	A lock record refers to a different semaphore cursor than the one it is linked to. Explanation: An internal locking/synchronization rule was broken. Report the error to your System Administrator. Shut down and restart Adaptive Server.
1243	26	Couldn't find object to be released. Explanation: Refer to the writeup for this error.
1244	20	Could not find address lock at address 0x%lx while trying to release it. Explanation: An internal locking/synchronization rule was broken. Report the error to Sybase Technical Support.
1245	26	Lock record and process disagree. Explanation: An internal locking/synchronization rule was broken. Report the error to Sybase Technical Support.
1246	26	Process attempting to wait on a lock that does not belong to it. Explanation: An internal locking/synchronization rule was broken. Report the error to your System Administrator. Shut down and restart Adaptive Server.
1247	26	Process attempting to wait on a lock that has already been waited for. Explanation: An internal locking/synchronization rule was broken. Report the error to your System Administrator. Shut down and restart Adaptive Server.
1249	20	Process became runnable before lock it was waiting for was released. Explanation: Adaptive Server encountered an internal error affecting the current process. Report the error to Sybase Technical Support.
1250	26	A non-preallocated semaphore cursor encountered while trying to obtain a semaphore. Explanation: An internal locking/synchronization rule was broken. Report the error to your System Administrator. Shut down and restart Adaptive Server.
1251	26	An in-use preallocated semaphore cursor was encountered. Explanation: An internal locking/synchronization rule was broken. Report the error to Sybase Technical Support.
1252	26	Lock header linkage has been corrupted. Explanation: An internal locking/synchronization rule was broken. Report the error to your System Administrator. Shut down and restart Adaptive Server.
1253	26	The wrong number of lock records was found on a semaphore cursor. Explanation: An internal locking/synchronization rule was broken. Report the error to your System Administrator. Shut down and restart Adaptive Server.
1254	26	While following the lock record chain for a process, a lock record belonging to a different process was encountered. Explanation: An internal locking/synchronization rule was broken. Report the error to your System Administrator. Shut down and restart Adaptive Server.
1255	26	Unlinking a duplicate lock caused a task to be awakened. Explanation: An internal locking/synchronization rule was broken. Report the error to your System Administrator. Shut down and restart Adaptive Server.
1256	26	Encountered a non-preallocated semaphore cursor on a chain that should only have preallocated semaphore cursors. Explanation: An internal locking/synchronization rule was broken. Report the error to your System Administrator. Shut down and restart Adaptive Server.
1258	26	A process is not waiting for a lock that it should be waiting for. Explanation: An internal locking/synchronization rule was broken. Report the error to Sybase Technical Support.
1259	26	A process is waiting for a lock that has been granted. Explanation: An internal locking/synchronization rule was broken. Report the error to your System Administrator. Shut down and restart Adaptive Server.
1260	26	A process is waiting for a lock that it did not request. Explanation: An internal locking/synchronization rule was broken. Report the error to your System Administrator. Shut down and restart Adaptive Server.
1261	20	Attempt to promote from page to table locking on objid %ld encountered an internal error. 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.
1262	20	No matching xdes found. Lock was requested for objid %ld, dbid %d, type %d, by process %d. 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.
1263	26	A process was found to be waiting for the same object twice. Explanation: An internal locking/synchronization rule was broken. Report the error to your System Administrator. Shut down and restart Adaptive Server.
1265	20	A lock manager routine expected a lock record as an argument but was passed something else. lr=0x%x, lrmagic=% c. Explanation: Refer to the writeup for this error.
1266	20	Upgrade of lock on object id or page number %ld left the lock ungranted. Explanation: Adaptive Server encountered an internal error affecting the current process. Reconnect to Adaptive Server. If the problem persists, report it to your System Administrator.
1267	26	A lock record at the head of a semaphore queue is not marked as granted. Explanation: An internal locking/synchronization rule was broken. Report the error to your System Administrator. Shut down and restart Adaptive Server.
1268	26	A lock record is marked as granted, but isn't at the head of the semaphore queue. Explanation: An internal locking/synchronization rule was broken. Report the error to your System Administrator. Shut down and restart Adaptive Server.
1269	10	Temporary buffer overflow occurred while scanning the lock table. Rows will be missing in syslocks for one or more objects. Explanation: This is an informational message. A non-configurable limit was exceeded but processing continues. No action is required.
1270	26	A task attempted to release a semaphore that it had not previously obtained. Explanation: An internal locking/synchronization rule was broken. Report the error to your System Administrator. Shut down and restart Adaptive Server.
1271	26	A task attempted to acquire a semaphore with a preallocated semaphore cursor that did not belong to it. Explanation: An internal locking/synchronization rule was broken. Report the error to your System Administrator. Shut down and restart Adaptive Server.
1272	20	Invalid parameter(s) passed to lock manager. 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.
1273	16	Syntax error at line %d of file %s starting at `%s'. Explanation: Command failed due to invalid or illegal request. Check syntax, semantics, and permissions. Take any corrective action indicated by message.
1274	16	Error with input file %s: %s. Explanation: Command failed due to invalid or illegal request. Check syntax, semantics, and permissions. Take any corrective action indicated by message.
1275	16	The lock unit test can only be run with a single engine on line. Explanation: Command failed due to invalid or illegal request. Check syntax, semantics, and permissions. Take any corrective action indicated by message.
1276	26	Attempt to acquire a lock in dbid %d while in an internal transaction. 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.
1277	20	In a call to lock_multiple(), the lock requests were out of order. They should be sorted by object id, dbid. 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.
1278	26	This semawait (1st) should only have one lockrec. Explanation: An internal locking/synchronization rule was broken. Report the error to your System Administrator. Shut down and restart Adaptive Server.
1279	19	SQL Server has run out of locks on engine %d. Re-run your command when there are fewer active users, or contact a user with System Administrator (SA) role to reconfigure maximum engine freelocks or number of locks. Explanation: Refer to the writeup for this error.
1280	26	Lock sleeptask (or waittask) chain has been corrupted. Explanation: An internal locking/synchronization rule was broken. Report the error to your System Administrator. Shut down and restart Adaptive Server.
1281	26	A structure of the wrong type is linked to the lock sleeptask (or waittask) chain. Explanation: An internal locking/synchronization rule was broken. Report the error to Sybase Technical Support.
1282	26	An incorrect lock sleeptask structure is linked to the Lock Sleeptask chain. Explanation: An internal locking/synchronization rule was broken. Report the error to your System Administrator. Shut down and restart Adaptive Server.
1283	19	Could not change deadlock checking period because SQL Server has run out of alarms. Please retry the command later. Explanation: This is an informational message. Unless otherwise specified, no action is required. Contact your System Administrator about any warning issued in the message.
1284	26	Used Lock Sleeptask Entry not in Chain. Explanation: An internal locking/synchronization rule was broken. Report the error to your System Administrator. Shut down and restart Adaptive Server.
1285	26	Un-used Lock Sleeptask Entry in Lock Sleeptask Chain. Explanation: An internal locking/synchronization rule was broken. Report the error to your System Administrator. Shut down and restart Adaptive Server.
1286	26	Missing Preallocated Lock Sleeptask Entry. Explanation: An internal locking/synchronization rule was broken. Report the error to your System Administrator. Shut down and restart Adaptive Server.
1287	16	Freelock transfer block size (%d) cannot be more than half the number of freelocks allowed per engine (%d). To increase the number of freelocks allowed per engine please increase maximum engine freelocks. Explanation: See the System Administration Guide for more information about `max engine freelocks'.
1288	16	Setting maximum engine freelocks to %d allows only %d freelocks per engine. This value cannot be less than twice the value of freelock transfer block size. Please reduce freelock transfer block size to %d and reattempt this command. Explanation: See the System Administration Guide for more information about `freelock transfer block size'.
1289	20	Internal Error in lock manager routine: Invalid lock mode %s, requested by task (family id %d, spid %d) conflicts with existing family request mode %s belonging to task (family id %d, spid %d). Explanation: Adaptive Server encountered an internal error affecting the current process. Reconnect to Adaptive Server. Report the error to your System Administrator.
1290	20	Internal Error in lock manager routine: Attempted lock upgrade from %s to %s in parallel query thread (family id %d, spid %d) is Illegal. Explanation: Adaptive Server encountered an internal error affecting the current process. Reconnect to Adaptive Server. Report the error to your System Administrator.
1291	20	Internal Error in lock manager routine: Attempted lock anti-inheritance is an illegal operation for a non-parent thread (fid %d, spid %d). Explanation: Adaptive Server encountered an internal error affecting the current process. Reconnect to Adaptive Server. Report the error to your System Administrator.
1292	20	Internal Error in lock manager routine: Thread (fid %d, spid %d) incorrectly attempted to acquire a non-queueing %s lock when thread (fid %d, spid %d) in its family already holds an insufficient %s lock on objid %d, dbid %d. Explanation: Adaptive Server encountered an internal error affecting the current process. Reconnect to Adaptive Server. Report the error to your System Administrator.
1293	20	Internal Error in lock manager routine: Process (fid %d, spid %d) incorrectly attempted to transfer locks to itself, from a process (fid %d, spid %d) belonging to a different family. Explanation: Adaptive Server encountered an internal error affecting the current process. Reconnect to Adaptive Server. Report the error to your System Administrator.
1294	26	Lock_logical was called with an illegal 'op' parameter: %d. Explanation: An internal locking/synchronization rule was broken. Report the error to your System Administrator. Shut down and restart Adaptive Server.
1295	26	Unconditional lock request for table or page %d, dbid %d was made while holding a latch. Explanation: An internal locking/synchronization rule was broken. Report the error to your System Administrator. Shut down and restart Adaptive Server.
1298	26	Unexpected position for NKL semawait. This indicates a programmer error. Explanation: An internal locking/synchronization rule was broken. Report the error to your System Administrator. Shut down and restart Adaptive Server.
1299	26	NKL semawait is at an improper position in the queue. Explanation: An internal locking/synchronization rule was broken. Report the error to your System Administrator. Shut down and restart Adaptive Server.