SQL Server Errors or Failures Error: 683 to Error: 824
Error: 683, Severity: 22,
An internal error occurred while trying to convert between variable-length and fixed-length decimal formats. Run DBCC CHECKDB to check for any database corruption.
Error: 684, Severity: 22,
An internal error occurred while attempting to convert between compressed and uncompressed storage formats. Run DBCC CHECKDB to check for any corruption.
Error: 685, Severity: 22,
An internal error occurred while attempting to retrieve a backpointer for a heap forwarded record.
Error: 686, Severity: 22,
The maximum level of the B-Tree for rowset %I64d has been reached. SQL Server only supports upto 255 levels.
Error: 687, Severity: 16,
Cannot compress a nchar or nvarchar column that has an odd number of bytes.
Error: 688, Severity: 16,
Operation not allowed due to an active online index build.
Error: 689, Severity: 16,
Operation not allowed because of pending cleanup of online index build. Wait for cleanup to complete and re-run the operation.
Error: 701, Severity: 19,
There is insufficient system memory in resource pool ‘default’ to run this query.
This error occurs if there is memory pressure on the SQL Server instance. There are various reasons why this message would appear in SQL Server errorlog or when you run a particular query. Below are some things which you can start with
– Check how much free memory is available on the server. Use Task Manager or Performance monitor (Available MBytes) counter to find the available memory on the server.
– Find which process is using most of the memory on the server using performance monitor counters.
– Check how much memory SQL Server instance is using and how many SQL Server instances are related components are installed on the server.
– Make sure all SQL Server instances installed on the server have “Max Server Memory” configured in such a way that there is enough memory left for the operating system.
– There may be other related error messages around this error something like “Failed Virtual Allocate Bytes: FAIL_VIRTUAL_RESERVE 124240” which should help in identifying what kind of memory pressure this is related to.
Error: 708, Severity: 10,
Server is running low on virtual address space or machine is running low on virtual memory. Reserved memory used %d times since startup. Cancel query and re-run, decrease server load, or cancel other applications.
Error: 801, Severity: 20,
A buffer was encountered with an unexpected status of 0x%x.
Error: 802, Severity: 17,
There is insufficient memory available in the buffer pool.
Error: 803, Severity: 10,
simulated failure (DEBUG only)
Error: 805, Severity: 10,
Error: 806, Severity: 10,
audit failure (a page read from disk failed to pass basic integrity checks)
Error: 807, Severity: 10,
(no disk or the wrong disk is in the drive)
Error: 808, Severity: 10,
insufficient bytes transferred
Error: 821, Severity: 20,
Could not unhash buffer at 0x%p with a buffer page number of %S_PGID and database ID %d with HASHED status set. The buffer was not found. %S_PAGE. Contact Technical Support.
Error: 822, Severity: 21,
Could not start I/O operation for request %S_BLKIOPTR. Contact Technical Support.
Error: 823, Severity: 24,
The operating system returned error %ls to SQL Server during a %S_MSG at offset %#016I64x in file ‘%ls’. Additional messages in the SQL Server error log and system event log may provide more detail. This is a severe system-level error condition that threa
Error: 824, Severity: 24,
SQL Server detected a logical consistency-based I/O error: %ls. It occurred during a %S_MSG of page %S_PGID in database ID %d at offset %#016I64x in file ‘%ls’. Additional messages in the SQL Server error log or system event log may provide more detail.
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.
In-Depth Blogs on SQL Server, Information about SQL Server Conferences and Events, SQL Server Frequently asked questions, SQL Server Trainings.