Server Error Messages 600 - 699


 Descriptor for system table `%ld' in database `%d' not found in the descriptor hash table.
 Could not find row in sysindexes for dbid `%d', object `%ld',index `%d'. Run DBCC CHECKTABLE on sysindexes.
There are not enough system session descriptors available to run this query. Raise the value of the configuration parameter ’number of aux scan descriptors’ or retry your query later.
 Could not find row in sysobjects for object `%ld' in database `%.*s'.  Run DBCC checktable on sysobjects.
 An attempt was made to fetch logical page `%ld' in database `%.*s' from cache `%.*s'. Page belongs to object with id `%ld', not to object `%.*s'.
 Insufficient room was allocated in the session descriptor for object `%.*s' for search arguments. Only %d search arguments were anticipated.
Buffer holding logical page %ld of object '%.*s' in database '%.*s' was not kept in the first or second slot o f the session descriptor for that object during a scan.
 Maximum number of databases that may be accessed by a transaction is 16. This number has been exceeded by this query.
 Attempt made to end a transaction that is idle or in the middle of an update.
 Attempt made to log a row of unknown type %d.
 Request made to retrieve more rows from an already completed scan  of object `%.*s' in database `%.*s'.
Adaptive Server accessed a row that has an illegal length of %d while in data base ’%.*s’. %S_PAGE. The minimum row length is %d. The page size is %d.
 Unable to find database table.
 Attempt to hash a previously hashed descriptor for object `%.*s'  in database `%.*s'.
 Descriptor for object `%ld' in database `%d' not found in the hash table during attempt to unhash it.
 A varno of %d was passed to opentable - the largest valid value is %d.
 A deferred update was requested but the query is not one of INSERT, DELETE or UPDATE.
 Log record encountered at deferred update time with either a row length of less than 2 or an invalid log type. The log type was %d and the row length was %d.
 A log record was encountered of type %d that is not one of the valid  deallocation types.
 Opentable was passed a varno of %d. Object ’%.*s’ in database ’%.*s’ already has that session descriptor in use. This occured while opening object id %d in database id %d.
Adaptive Server failed to retrieve a row via its RID in database ’%.*s’ because the target page is not a data page. %S_RID. %S_PAGE.
Adaptive Server failed to retrieve a row via its RID in database ’%.*s’ because the requested RID has a higher number than the last RID on the page. %S_RID. %S_PAGE.
Adaptive Server failed to retrieve a row via its RID in database ’%.*s’ because the entry in the offset table for that RID is less than or equal to 0. %S_RID. %S_PAGE.
 A transaction tried to call beginupdate while in state `prepare'.
 Attempt to issue `SAVE TRANsaction' when there is no active transaction.
Clustered index row entry for data page %ld is missing in index page %ld of table '%S_OBJID' in database '%S_D BID'; index row contains data page %ld instead. You can recreate the clustered index to fix this error. Xactid is (%ld, %d).
 The end of page limit has been exceeded while building an offset table for object %ld on page %ld, page addr 0x%lx, eop addr 0x%lx, sargptr addr 0x%lx.
The length of %d passed to delete row routine for the row at offset %d is incorrect on the following page: %S_PAGE. The expected row length is %d. The offset should be no greater than %d.
Memmove() was called with a length of %d - maximum allowed length is %d. 
 The PG_DEALLOC bit set by recovery is on at runtime on the following page. %S_PAGE.
Memmove() was called with an address of 0x%lx and a length of %d - which would cross the boundary address of 0x%lx.
 Process %d tried to remove DES resource lock that it doesn't hold  - %S_DES .
 Index shrink program returned invalid status of 0.
 Memmove() was called with an address of 0x%lx - which is not allocated memory.
 Attempt to fetch logical page %ld dbid %d failed - page is not currently allocated.
 Attempt to insert/delete row on wrong type of page. %S_PAGE.
 Attempt to add BEGINUPDATE record in transaction %S_RID that already has an active CMD.
 Attempt to begin update in transaction %S_RID which already has an active transaction.
 Attempt to read page %ld in database `%.*s' which is not allocated.
Index row entry for data row id (%ld, %d) is missing from index page %ld of index id %d of table ’%S_OBJID’ in database ’%S_DBID’. Xactid is (%ld,%d). Drop and re-create the index.
 Could not find the clustered index entry for Page %ld Objid %ld status 0x%x.  Index page %ld was searched for this entry in database `%.*s'.
 Page %ld of table ’%.*s’ (id = %ld) in dbid %d not locked.
 Startscan was called with an illegal combination of index and scan mode.
 The buffer 0x%lx should be kept in sdes 0x%lx on entry to this function and it is not.
 Buffer not rlocked. %S_BUF. %S_PAGE.
 Page %ld, dbid %d not exclusive locked.
 Page should be marked as having overflow page: %S_PAGE.
 Locking not stipulated while attempting to modify page.  %S_PAGE.
 Passed buffer pointer for previous page is for page %ld, when the actual previous page is %ld. These pages are in database `%*.s'.
 Last log page in database `%.*s' incorrectly identified as page %ld. Run DBCC checktable on syslogs.
 Table id %d contains suspect indexes. This table is only available for read-only purposes until the DBCC REINDEX command has been run on the indicated table to rebuild its suspect indexes.
 Index id %d cannot be used to access table id %d as it is SUSPECT. Please have the SA run the DBCC REINDEX command on the specified table.
 As part of a transaction rollback, an attempt was made to modify object `%S_OBJID' in database `%.*s', even though the current session is not holding an exclusive lock on that object.
 The index with index id `%d' on object with object id = `%d' was not found during cursor scan fixups. The fixup was being done for cursor `%.*s'. This is an internal error.
 The lock on page `%d' for object with object id = `%d' could not be obtained during cursor scan fixups. The fixup was being done for cursor `%.*s'. This is an internal error.
 The parameters passed to cursfix_main() were not correct. This is an internal error.
 The cursor fixup is being done for the pre delete case with the data row for a scan using a non-clustered index and there was no fixup done for pre-delete of the non-clustered index row. This is an internal error.
 The current position deleted bit is set for an SDES but there is no fixup information saved. This is an internal error.
 Illegal locking strategy encountered at scan initialization.  Object %S_OBJID, database %S_DBID.  This is an internal error.
 The cursor `%.*s' which is scanning a list of rids i.e a work table is having it's tables changed. This cursor should be read only and the tables should be private to it's query. This is an internal error.
 The length computation of the row %d is wrong. Ensure that row-length is no greater than max possible size of %d. This error was detected during cursor scan fixups for cursor ’%.*s’. This is an internal error. The processing is being stopped for the current query.
 Out of bound insert attempted on table `%.*s'.
 Writetext is not allowed in reclassify mode.
 Out of bound update attempted on table `%.*s'.
 Out of bound delete attempted on table `%.*s'.
 Invalid Buffer Cache Access: Attempt to locate page `%ld', database `%ld' in cache failed because the cache id `%ld' in scan_context is invalid. scan_context={objid `%ld', indid `%ld', cid `%ld'}. Contact Technical Support for assistance.
 Invalid Buffer Cache Access: Attempt to locate page `%ld', database `%ld' in cache failed because no object id was specified. scan_context={objid `%ld', indid `%ld', cid `%ld'}. Contact Technical Support for Assistance.
 NULL cache id specified in log record.
 Invalid Buffer Cache Access: Attempt to locate page `%ld', dbid `%ld', objid `%ld', indid `%ld' in cache failed because the cache ID was not set in the scan_context structure.  Contact Technical Support for assistance.
 Invalid Buffer Cache Access: Could not open object `%ld' in database `%d'
 Inconsistent update state found during expensive direct update of object `%ld'.
 Attempt to extend the log in database `%.*s' failed due to an internal error. The returned status was %d.
The buffer 0x%lx , page number '%ld' for object '%.*s' in database '%.*s' should be latched on entry to this f unction and it is not.
Failed to get lock on data page '%ld' row '%ld' for object '%.*s' in database '%.*s'. 
Page %ld, Row %d, for object '%.*s' in database '%.*s' is not exclusive locked. 
 Expected page %ld to be in cache `%.*s' for object id %ld, index id %d, database id %d. Instead, the server brought the page into wrong cache `%.*s'.
 Expected page %ld to be in cache `%.*s' for object id %ld, index id %d, database id %d. Instead, the server brought the page into wrong cache `%.*s'.
Insufficient CFS while redo of expanding update on page %ld belonging to object %ld. CFS - %ld, length of new row - %ld
An unexpected log record (log op %d) was encountered when scanning the log for a trigger.
Pageno in lk_pglocked (%ld) different from lockobj (%ld).
Encountered invalid logical page '%ld' while accessing object '%ld' in database '%d'. This is an internal system error. Please contact Sybase Technical  Support.
Uninitialized logical page '%ld' was read while accessing object '%ld' in database '%d'. Please contact Sybase Technical Support.
Multiple copies of logical page '%ld' from database '%d' reside in more than one cache. This is an internal system error. Please contact Sybase Technical Support.
An attempt was made to read logical page '%ld', virtpage '%ld' from virtual device '%d' for object '%ld' in database '%d'. The page was not read successfully. You may have a device problem or an operating system problem.
An attempt was made to read logical page '%ld' for object '%ld' in database '%d' from disk. Wrong logical page '%ld' was brought into cache '%.*s'.
An attempt was made to fetch logical page '%ld' in tempdb from cache '%.*s'. Page belongs to object '%ld' and not to object '%ld'. Restart of SQL Server will clear the error. Please contact your System Administrator for help.
An attempt was made to fetch logical page '%ld' for object '%ld' in database '%d' from cache '%.*s'. Wrong logical page '%ld' was found in cache.

Number	Severity	Text and Explanation
601	21	Descriptor for system table `%ld' in database `%d' not found in the descriptor hash table. Explanation: Refer to the writeup for Error 601.
602	21	Could not find row in sysindexes for dbid `%d', object `%ld',index `%d'. Run DBCC CHECKTABLE on sysindexes. 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.
603	19	There are not enough system session descriptors available to run this query. Raise the value of the configuration parameter ’number of aux scan descriptors’ or retry your query later. Explanation: Refer to the writeup for Error 603.
604	21	Could not find row in sysobjects for object `%ld' in database `%.s'. Run DBCC checktable on sysobjects. 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.
605	21	An attempt was made to fetch logical page `%ld' in database `%.s' from cache `%.s'. Page belongs to object with id `%ld', not to object `%.s'. Explanation:* Refer to the writeup for Error 605.
607	21	Insufficient room was allocated in the session descriptor for object `%.s' for search arguments. Only %d search arguments were anticipated. 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.
608	0	Buffer holding logical page %ld of object '%.s' in database '%.s' was not kept in the first or second slot o f the session descriptor for that object during a scan. Explanation: (Version 11.9.2 and higher.)
610	19	Maximum number of databases that may be accessed by a transaction is 16. This number has been exceeded by this query. Explanation: Command failed when a non-configurable limit was exceeded. Adaptive Server could not recover gracefully. Reconnect to Adaptive Server, and report the error to your System Administrator.
611	21	Attempt made to end a transaction that is idle or in the middle of an update. Explanation: Refer to the writeup for Error 611.
612	21	Attempt made to log a row of unknown type %d. Explanation: Attempt made to write a log record of unknown type. Report the error to your System Administrator.
613	21	Request made to retrieve more rows from an already completed scan of object `%.s' in database `%.s'. 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.
614	21	Adaptive Server accessed a row that has an illegal length of %d while in data base ’%.s’. %S_PAGE. The minimum row length is %d. The page size is %d. Explanation:* Refer to the writeup for Error 614.
615	21	Unable to find database table. Explanation: Run dbcc checks on the database. (This error is not raised in Adaptive Server 11.0 and higher.)
616	20	Attempt to hash a previously hashed descriptor for object `%.s' in database `%.s'. 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. (Not raised in 11.0 and higher releases).
617	20	Descriptor for object `%ld' in database `%d' not found in the hash table during attempt to unhash it. 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.
618	21	A varno of %d was passed to opentable - the largest valid value is %d. 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.
619	20	A deferred update was requested but the query is not one of INSERT, DELETE or UPDATE. 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.
620	21	Log record encountered at deferred update time with either a row length of less than 2 or an invalid log type. The log type was %d and the row length was %d. 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.
621	21	A log record was encountered of type %d that is not one of the valid deallocation types. 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.
622	20	Opentable was passed a varno of %d. Object ’%.s’ in database ’%.s’ already has that session descriptor in use. This occured while opening object id %d in database id %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.
623	21	Adaptive Server failed to retrieve a row via its RID in database ’%.s’ because the target page is not a data page. %S_RID. %S_PAGE. Explanation:* Refer to the writeup for this error.
624	21	Adaptive Server failed to retrieve a row via its RID in database ’%.s’ because the requested RID has a higher number than the last RID on the page. %S_RID. %S_PAGE. Explanation:* Refer to the writeup for this error.
625	21	Adaptive Server failed to retrieve a row via its RID in database ’%.s’ because the entry in the offset table for that RID is less than or equal to 0. %S_RID. %S_PAGE. Explanation:* Refer to the writeup for this error.
627	20	A transaction tried to call beginupdate while in state `prepare'. Explanation: There may be a problem due to an application issuing a PREPARE statement followed by an update. Check the application SQL code.
628	13	Attempt to issue `SAVE TRANsaction' when there is no active transaction. Explanation: Rerun the command that raised this error.
629	21	Clustered index row entry for data page %ld is missing in index page %ld of table '%S_OBJID' in database '%S_D BID'; index row contains data page %ld instead. You can recreate the clustered index to fix this error. Xactid is (%ld, %d). Explanation: Refer to the writeup for this error.
630	21	The end of page limit has been exceeded while building an offset table for object %ld on page %ld, page addr 0x%lx, eop addr 0x%lx, sargptr addr 0x%lx. 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.
631	21	The length of %d passed to delete row routine for the row at offset %d is incorrect on the following page: %S_PAGE. The expected row length is %d. The offset should be no greater than %d. Explanation: Refer to the writeup for this error.
632	20	Memmove() was called with a length of %d - maximum allowed length is %d. Explanation: The error may be caused by data corruption. Run dbcc checkdb on the database that was being accessed, and correct any errors reported.
633	21	The PG_DEALLOC bit set by recovery is on at runtime on the following page. %S_PAGE. Explanation: Report the error to your System Administrator. (Not raised in Release 11.0 and higher.)
634	20	Memmove() was called with an address of 0x%lx and a length of %d - which would cross the boundary address of 0x%lx. Explanation: There is a possible Adaptive Server problem. Run dbcc checks on the database that was being accessed when the error occurred.
635	20	Process %d tried to remove DES resource lock that it doesn't hold - %S_DES . Explanation: Report the error to your System Administrator. (Not raised in Release 11.0 and higher.)
637	20	Index shrink program returned invalid status of 0. Explanation: Adaptive Server encountered an internal error affecting the current process. Report the error to your System Administrator. Run dbcc indexalloc, checktable.
638	20	Memmove() was called with an address of 0x%lx - which is not allocated memory. Explanation: There is a possible Adaptive Server problem. Run dbcc checks on the database that was being accessed when the error occurred.
639	21	Attempt to fetch logical page %ld dbid %d failed - page is not currently allocated. 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.
640	21	Attempt to insert/delete row on wrong type of page. %S_PAGE. 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.
641	21	Attempt to add BEGINUPDATE record in transaction %S_RID that already has an active CMD. 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.
642	20	Attempt to begin update in transaction %S_RID which already has an active transaction. 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.
643	20	Attempt to read page %ld in database `%.s' which is not allocated. 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.
644	21	Index row entry for data row id (%ld, %d) is missing from index page %ld of index id %d of table ’%S_OBJID’ in database ’%S_DBID’. Xactid is (%ld,%d). Drop and re-create the index. Explanation: Refer to the writeup for this error.
649	21	Could not find the clustered index entry for Page %ld Objid %ld status 0x%x. Index page %ld was searched for this entry in database `%.s'. 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.
650	26	Page %ld of table ’%.s’ (id = %ld) in dbid %d not locked. Explanation:* An internal locking/synchronization rule was broken. Report the error to your System Administrator. Shut down and restart Adaptive Server.
651	26	Startscan was called with an illegal combination of index and scan mode. Explanation: An internal locking/synchronization rule was broken. Report the error to your System Administrator. Shut down and restart Adaptive Server.
652	20	The buffer 0x%lx should be kept in sdes 0x%lx on entry to this function and it is not. 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.
653	26	Buffer not rlocked. %S_BUF. %S_PAGE. Explanation: An internal locking/synchronization rule was broken. Report the error to your System Administrator. Shut down and restart Adaptive Server.
654	26	Page %ld, dbid %d not exclusive locked. Explanation: An internal locking/synchronization rule was broken. Report the error to your System Administrator. Shut down and restart Adaptive Server.
655	26	Page should be marked as having overflow page: %S_PAGE. Explanation: An internal locking/synchronization rule was broken. Report the error to your System Administrator. Shut down and restart Adaptive Server.
656	26	Locking not stipulated while attempting to modify page. %S_PAGE. Explanation: An internal locking/synchronization rule was broken. Report the error to your System Administrator. Shut down and restart Adaptive Server.
657	26	Passed buffer pointer for previous page is for page %ld, when the actual previous page is %ld. These pages are in database `%.s'. Explanation:* An internal locking/synchronization rule was broken. Report the error to your System Administrator. Shut down and restart Adaptive Server.
658	22	Last log page in database `%.s' incorrectly identified as page %ld. Run DBCC checktable on syslogs. Explanation:* Report the error to your System Administrator. (Not raised in Release 11.0 and higher.)
659	16	Table id %d contains suspect indexes. This table is only available for read-only purposes until the DBCC REINDEX command has been run on the indicated table to rebuild its suspect indexes. Explanation: Command failed due to invalid or illegal request. Check syntax, semantics, and permissions. Take any corrective action indicated by message.
660	10	Index id %d cannot be used to access table id %d as it is SUSPECT. Please have the SA run the DBCC REINDEX command on the specified table. Explanation: This is an informational message. Unless otherwise specified, no action is required. Contact your System Administrator about any warning issued in the message.
661	21	As part of a transaction rollback, an attempt was made to modify object `%S_OBJID' in database `%.s', even though the current session is not holding an exclusive lock on that object. 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.
662	18	The index with index id `%d' on object with object id = `%d' was not found during cursor scan fixups. The fixup was being done for cursor `%.s'. This is an internal error. Explanation:* Command failed due to internal Adaptive Server problem. Perform any diagnostic action indicated by message. Report the error to your System Administrator.
663	18	The lock on page `%d' for object with object id = `%d' could not be obtained during cursor scan fixups. The fixup was being done for cursor `%.s'. This is an internal error. Explanation:* Command failed due to internal Adaptive Server problem. Perform any diagnostic action indicated by message. Report the error to your System Administrator.
664	18	The parameters passed to cursfix_main() were not correct. This is an internal error. Explanation: Command failed due to internal Adaptive Server problem. Perform any diagnostic action indicated by message. Report the error to your System Administrator.
665	18	The cursor fixup is being done for the pre delete case with the data row for a scan using a non-clustered index and there was no fixup done for pre-delete of the non-clustered index row. This is an internal error. Explanation: Command failed due to internal Adaptive Server problem. Perform any diagnostic action indicated by message. Report the error to your System Administrator.
666	18	The current position deleted bit is set for an SDES but there is no fixup information saved. This is an internal error. Explanation: Command failed due to internal Adaptive Server problem. Perform any diagnostic action indicated by message. Report the error to your System Administrator.
667	26	Illegal locking strategy encountered at scan initialization. Object %S_OBJID, database %S_DBID. 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.
668	18	The cursor `%.s' which is scanning a list of rids i.e a work table is having it's tables changed. This cursor should be read only and the tables should be private to it's query. This is an internal error. Explanation:* Command failed due to internal Adaptive Server problem. Perform any diagnostic action indicated by message. Report the error to your System Administrator.
669	18	The length computation of the row %d is wrong. Ensure that row-length is no greater than max possible size of %d. This error was detected during cursor scan fixups for cursor ’%.s’. This is an internal error. The processing is being stopped for the current query. Explanation:* Command failed due to internal Adaptive Server problem. Perform any diagnostic action indicated by message. Report the error to your System Administrator.
670	16	Out of bound insert attempted on table `%.s'. Explanation:* Adaptive Server could not perform the requested action. The command violates a permission or privilege restriction. Check the command and working database context.
671	14	Writetext is not allowed in reclassify mode. Explanation: Command failed due to invalid or illegal request. Adaptive Server cannot perform the requested action. Take any corrective action indicated by the message.
672	16	Out of bound update attempted on table `%.s'. Explanation:* Adaptive Server could not perform the requested action. The command violates a permission or privilege restriction. Check the command and working database context.
673	16	Out of bound delete attempted on table `%.s'. Explanation:* Adaptive Server could not perform the requested action. The command violates a permission or privilege restriction. Check the command and working database context.
674	20	Invalid Buffer Cache Access: Attempt to locate page `%ld', database `%ld' in cache failed because the cache id `%ld' in scan_context is invalid. scan_context={objid `%ld', indid `%ld', cid `%ld'}. Contact Technical Support for assistance. 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.
675	20	Invalid Buffer Cache Access: Attempt to locate page `%ld', database `%ld' in cache failed because no object id was specified. scan_context={objid `%ld', indid `%ld', cid `%ld'}. Contact Technical Support for Assistance. 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.
676	21	NULL cache id specified in log record. Explanation: Report the error to your System Administrator. (Not raised in Release 11.0 and higher.)
677	20	Invalid Buffer Cache Access: Attempt to locate page `%ld', dbid `%ld', objid `%ld', indid `%ld' in cache failed because the cache ID was not set in the scan_context structure. Contact Technical Support for assistance. 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.
678	20	Invalid Buffer Cache Access: Could not open object `%ld' in database `%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.
679	20	Inconsistent update state found during expensive direct update of object `%ld'. 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.
680	20	Attempt to extend the log in database `%.s' failed due to an internal error. The returned status was %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.
682	20	The buffer 0x%lx , page number '%ld' for object '%.s' in database '%.s' should be latched on entry to this f unction and it is not. 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. (Version 11.9.2 and higher.)
683	20	Failed to get lock on data page '%ld' row '%ld' for object '%.s' in database '%.s'. 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. (Version 11.9.2 and higher.)
684	26	Page %ld, Row %d, for object '%.s' in database '%.s' is not exclusive locked. Explanation: An internal locking/synchronization rule was broken. Report the error to your System Administrator. Shut down and restart Adaptive Server. (Version 11.9.2 and higher.)
685	21	Expected page %ld to be in cache `%.s' for object id %ld, index id %d, database id %d. Instead, the server brought the page into wrong cache `%.s'. Explanation: Command failed due to internal Adaptive Server problem. Report the error to your System Administrator.
686	20	Expected page %ld to be in cache `%.s' for object id %ld, index id %d, database id %d. Instead, the server brought the page into wrong cache `%.s'. Explanation: Page %ld is corrupted.
688	21	Insufficient CFS while redo of expanding update on page %ld belonging to object %ld. CFS - %ld, length of new row - %ld Explanation: Command failed due to internal Adaptive Server problem. Report the error to your System Administrator.
689	10	An unexpected log record (log op %d) was encountered when scanning the log for a trigger. Explanation: Informational message. Report the error to your System Administrator.
690	20	Pageno in lk_pglocked (%ld) different from lockobj (%ld). 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.
691	20	Encountered invalid logical page '%ld' while accessing object '%ld' in database '%d'. This is an internal system error. Please contact Sybase Technical Support. Explanation: See the writeups for Error 691 and Error 605.
692	20	Uninitialized logical page '%ld' was read while accessing object '%ld' in database '%d'. Please contact Sybase Technical Support. Explanation: See the writeups for Error 692 and Error 605.
693	20	Multiple copies of logical page '%ld' from database '%d' reside in more than one cache. This is an internal system error. Please contact Sybase Technical Support. Explanation: See the writeups for Error 693 and Error 605.
694	24	An attempt was made to read logical page '%ld', virtpage '%ld' from virtual device '%d' for object '%ld' in database '%d'. The page was not read successfully. You may have a device problem or an operating system problem. Explanation: See the writeups for Error 694 and Error 605.
695	21	An attempt was made to read logical page '%ld' for object '%ld' in database '%d' from disk. Wrong logical page '%ld' was brought into cache '%.s'. Explanation:* See the writeups for Error 695 and Error 605.
696	21	An attempt was made to fetch logical page '%ld' in tempdb from cache '%.s'. Page belongs to object '%ld' and not to object '%ld'. Restart of SQL Server will clear the error. Please contact your System Administrator for help. Explanation:* See the writeups for Error 696 and Error 605.
697	21	An attempt was made to fetch logical page '%ld' for object '%ld' in database '%d' from cache '%.s'. Wrong logical page '%ld' was found in cache. Explanation:* See the writeups for Error 697 and Error 605.